You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Shane Isbell <sh...@gmail.com> on 2008/11/22 18:56:52 UTC

Re: svn commit: r719473 - in /maven/components/trunk/maven-mercury: ./ src/ src/main/ src/main/java/ src/main/java/org/ src/main/java/org/apache/ src/main/java/org/apache/maven/ src/main/java/org/apache/maven/mercury/ src/main/resources/ src/main/res

I think that the maven-project-builder would be a good location for the
super pom, as this component is used both by maven-mercury and
maven-project.

Shane

On Sat, Nov 22, 2008 at 8:52 AM, Benjamin Bentmann <
benjamin.bentmann@udo.edu> wrote:

> Hi,
>
>  Author: sisbell
>> Date: Thu Nov 20 20:50:50 2008
>> New Revision: 719473
>>
>> URL: http://svn.apache.org/viewvc?rev=719473&view=rev
>> Log:
>> Import of maven mercury project.
>>
>> Added:
>>    [...]
>>
>>  maven/components/trunk/maven-mercury/src/main/resources/org/apache/maven/project/pom-4.0.0.xml
>>
>
> This file duplicates the one contained in maven-project. Is there a major
> reason to do so and take the risk of getting this redundancy out of sync?
> Should we maybe better create a new sub module (e.g. maven-super-pom) to
> host this resource for sharing?
>
>
> Benjamin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>