How would that behave when you have multiple levels of inheritance?
Just assume a flat directory structure?
Mauro
On 5/12/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> Hi,
>
> A lot of values in the POM, when inherited, need to be extended to add
> the additional path to it. Things like URL, SCM, site distribution URL
> are all tedious to reproduce in every child POM just to add
> ${pom.artifactId} to the end.
>
> One option is to actually add pom.artifactId to the end of each of those
> when it is inherited and for now I've done just that.
>
> However, I anticipate this won't always be correct - the directory name
> may not be pom.artifactId (it may be the intersection of pom.artifactId
> and pom.groupId), or it may have an additional path in between, esp when
> it comes to subversion.
>
> One alternative I considered was to take the difference between the
> parent file location and the current file location, but that relies on
> the existence of a USD.
>
> So, I propose the following syntax to be specified in the parent POM:
>
> http://svn.apache.org/repos/asf/maven/wagon/trunk[/${pom.artifactId}]
>
> The value in [...] would be discarded in the POM in which it is defined,
> but used in a child, ie:
> http://svn.apache.org/repos/asf/maven/wagon/trunk
> ... in pom.xml
> http://svn.apache.org/repos/asf/maven/wagon/trunk/wagon-provider-api
> ... in wagon-provider-api/pom.xml
>
> This allows a bit more flexiblity, reduces the amount of duplication and
> retains the goal of master build == inherited build.
>
> Thoughts?
>
> - Brett
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
