On 8/29/05, dan tran <[EMAIL PROTECTED]> wrote:
> For example:
>
> <parent>
> <groupId>parentgroupid<groupId>
> <artifactId>parentid</artifactId>
> <version>${my.version}</version>
> </parent>
This won't work without specifying my.version in every POM (you need
to know what the parent is to find the value of my.version in the
parent).
> <dependencies>
> <dependency>
> <groupId>parentgroupid<groupId>
> <artifactId>parentid</artifactId>
> <version>${my.version}</version>
> </dependency>
> </dependencies>
You can achieve this with <dependencyManagement/> in the root POM. You
can already use ${version} there to use the current version.
>
> This will help tremendously interm usabitlity where can just modify
> my
> root pom and cut a new release without going to every sub project
> to change the version numbers and deal with SCM.
>
We plan to look at not requiring a parent version and doing some
intelligent discovery of the parent. It was controversial so it may or
may not go ahead.
> In parent pom i can have
>
> <properties>
> <otherprojectincludepath>
> ${basedir}/../../licencemanager/src/main/h
> </otherprojectincludepath>
> many more....
> </properties>
Why can't you just inherit the plugin configuration for this? Also,
this won't work if the paths aren't exactly ../...
> Other plugins can benefit this as well. For example multiple plugins can
> reused
> ${finalName} expression in their builds configuration
That already works - ${build.finalName}
> Is it possible in term of M2 architecture?
Certainly, but I don't think it is necessary...
Cheers,
Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
