rynam0,
I don't think the ${project.parent.basedir} variable is predefined. I tried
it, but maven doesn't recognize it.
Aymeric
rynam0 wrote:
>
> Have you tried using ${project.parent.basedir}?
>
> On Apr 9, 2010 3:31 AM, "Aymeric Alibert" <[email protected]> wrote:
>
>
> Nick,
>
> The only solution I could find is to create a 'filters' directory at the
> project top level. The structure would be:
> project/filters/filter-dev.properties
> project/module1/src/main/filters/filter-dev.proerties
>
> and define the following in the POM:
> <filters>
>
> <filter>${basedir}/../filters/filter-${environment}.properties</filter>
>
>
> <filter>src/main/filters/filter-${environment}.properties</filter>
> </filters>
> I don't like the fact it relies on relative path, but it works. Would be
> better if there were a variable refering to the top level project
> directory,
> but I couldn't find one.
>
> Hope it helps.
>
> Aymeric
>
>
>
>
>
> klauer wrote:
>>
>> Hey Aymeric,
>>
>> Did you ever find a solution to this? I can see how this m...
> --
> View this message in context:
> http://old.nabble.com/global-filter-on-multi-modules-project-tp27929774p28188617.html
>
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ----------------------------------...
>
>
--
View this message in context:
http://old.nabble.com/global-filter-on-multi-modules-project-tp27929774p28195753.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
