One way that springs to mind is to put the filter properties files in a separate project, then in each project use the dependency plugin to unpack that artifact and then use the properties files. However, using filtering in each and every one of your projects with the same properties files makes me wondering if there isn't a better option (a "nice" way of saying that there might be something wrong in your build design :-) ).
/Anders On Tue, Dec 15, 2009 at 09:44, Michael Ebert <[email protected]> wrote: > Hi, > > i'm facing the following issue: > > I've got a multi module project and resources filtering is activated > in every module: > > <resources> > <resource> > <directory>src/main/resources</directory> > <filtering>true</filtering> > </resource> > </resources> > > The directory layout: > > parent > | -- src/main/filters > | -- pom.xml > | -- module-a > | -- src/main/resources > | -- pom.xml > | -- module-b > | -- src/main/resources > | -- pom.xml > > My filter files currently reside under src/main/filters in the parent > project and are referenced from within the submodules via > > <filters> > <filter>..\src\main\filters\${env}-filter.properties</filter> > </filters> > > So far so good, that works. But I'm getting into troubles when I try > to build the modules separately, precise when continuum does so. > Continuum checks out the modules in a flat hierarchy and builds the > modules --non-recursive (one can get around that but that's not my > intention): > > parent > | -- src/main/filters > | -- pom.xml > module-a > | -- src/main/resources > | -- pom.xml > module-b > | -- src/main/resources > | -- pom.xml > > Obviously, the relative referenced > ..\src\main\filters\${env}-filter.properties doesn't work any more. > > Is there any possibility for having my filter files at another common > place, that is reachable for every module, regardless of the directory > layout? That must be a common problem but I haven't found any solution > so far. > > Thanks, > micha. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
