Stoffels, Ralf (FWI-AW2) wrote:
> Hi,
>
> artifact:install copies the project.xml file without any modifications to
> the repository.
>
> This entails that the extend element looses its reference. Therefore all
> references to the
> extended project (like ${pom.groupId}) are dangling and can't be resolved
> anymore.
>
> artifact:install should resolve these references before copying.
Actually, there is a workaround for that:
1) make the superproject a project in it's own right - and deploy it to
your repository.
2) extend through the local repository:
<extends>${maven.repo.local}/somegroup/poms/someartifact-version.pom</extends>
There is a caveat however - pom:install(-snapshot) must be epxlicitly
called on the superproject before the sub projects are processed -
<extends> is processed earlier than the dependencies, so depending on
the superproject does not help.
Therefore it would be a good idea to enhance maven so you could actually
do something like:
<extends>
<groupId>somegroup</groupId>
<artifactId>someartifact</artifactId>
<version>version</version>
</extends>
And it would fetch the POM from remote repo if no yet present, and then
proceed like described before.
R.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
