On 19 July 2011 09:16, Stephen Connolly <stephen.alan.conno...@gmail.com> wrote:
> On 19 July 2011 16:44, Hilco Wijbenga <hilco.wijbe...@gmail.com> wrote:
>
>> On 19 July 2011 03:01, Cem Koc <cemalettin....@gmail.com> wrote:
>> > I have 3 level multi module maven project. I want to utilize a common
>> plugin
>> > configuration at parent pom and the rest of the 2nd and 3rd level modules
>> > will utilize this configuration. The plugin configuration has a
>> > configuration file for 3rd level modules such as:
>> >
>> >
>> <mypluging-config-source-path>../../conf/myplugin</mypluging-config-source-path>
>> >
>> > But this configuration could not be used by 2rd level modules. They need
>> >
>> >
>> <mypluging-config-source-path>../conf/myplugin</mypluging-config-source-path>
>> >
>> > What is the best way to use a common path for all modules in a project
>> even
>> > at root parent pom?
>>
>> You could set a property with an absolute path in the parent.
>> Something like <parent-path>${basedir}</parent-path>. Then you can use
>> that as a starting point:
>>
>
> Not really as inheritance will kill you by resetting the property in the
> child project.
Mmmh, yeah, I guess ${basedir} is not a great idea. :-) So either set
*all* properties in the parent (and then simply use them in the
children) or use an environment variable (${env.SHARED_CONF_DIR}).
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
