> -----Original Message-----
> From: Stoffels, Ralf (FWI-AW2) [mailto:[EMAIL PROTECTED]
> Sent: Monday, January 26, 2004 10:49 PM
> To: '[EMAIL PROTECTED]'
> Subject: Problem with artifact:install
>
>
> 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.
>
>
I don't think so. I prefer to have untouched POM in the repository.
At the moment you can use
<extend>${maven.repo.local}/path_to_your_pom</extend>
This should work as long as POM interpolation will work (AFAIR there were
some plans to drop this feature).
Generally I think that repository should be involved in inheritance process.
and instead of:
<extends../common/project.xml</extend>
we can think about something like:
<extend>
<groupId>foo</>
<artifactId>common</artifactId>
<version>1.0</version>
</extend>
This will be important for continuous integration systems which should be
able to checkout and build project
having its POM and nothing else in "the database of POMs" (whatever it
means).
It will probably mean that some of the POM attributes cannot be inherited
(in example above those are: groupId, artifactId, version)
Michal
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
