On 5/20/05, Walter Vandeweyer <[EMAIL PROTECTED]> wrote:
> I did find out that is very comfortable to use POM inheritance, by writing a
> central Project.xml, and having all the others extending from it, like :
>
> <extend>${basedir}/../project.xml</extend>
>
> However there is a problem when building versioned modules. Maven checks out
> the code from CVS into a directory like:
>
> ${my-project-home}/target/checkouts
>
> This way Maven expects the parent POM to be located in the 'checkouts'
> directory of every module that is used in my project.
Yes, this is a known problem. You can look at a workaround in Maven's
SVN (see maven.xml in plugin-parent).
> Is there any way to dynamically refer to 1 parent POM when using a repository?
> Is there also a solution to versioning the parent POM, in order to be able to
> extend from the correct parent pom version when building the EAR?
While this is completely fixed in Maven2, we're still looking at
backporting it to Maven 1.1.
Cheers,
Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
