On Mon, Aug 22, 2005 at 02:21:31PM +0200, Thomas Van de Velde wrote:
> Jared,
>
> I've used the solution mentioned by Brett on large projects and it works
> well. I also place a project.xml and project.properties in the Maven cvs/svn
> module that holds configuration data common to all applications on a
> project. Applications then extend this project-level pom with <extends>${
> maven.home}/project.xml</extends>
>
> I would be interested to hear how this issue is being addressed with M2. One
> solution would be to have a small M2 core that is used to bootstrap your
> project's POM, which extends a POM located on a web server. E.g. <extends>
> http://mylocalserver/projectX/project.xml</extends> I believe this is a
> feature request that has already been submitted for M1 but I am not sure how
> this would work for associated project.properties files. With M2 this should
> become simpler as all configuration data is stored in the POM. Please
> correct me if I am wrong.
In Maven 2 you have <parent> instead of <extends> like this:
<parent>
<groupId>my-group</groupId>
<artifactId>my-parent</artifactId>
<version>1.0</version>
</parent>
Which is a artifact which can be put in your normal Maven repository.
--
Trygve
signature.asc
Description: Digital signature
