maven-m2-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Maczka Michal <>
Subject RE: further changes to the new repository layout
Date Fri, 01 Apr 2005 08:14:18 GMT

> -----Original Message-----
> From: Brett Porter []
> Sent: Friday, April 01, 2005 4:43 AM
> To: Maven 2 Developers List
> Subject: further changes to the new repository layout
> I've just updated the confluence document (hopefully for the 
> last time)
> to work around an issue.
> Artifact POMs now have the form:
> /groupId/artifactId-version.pom
> instead of:
> /groupId/artifactId-version.jar.pom
> This was necessary, as otherwise you would only ever be able 
> to inherit
> from a pom which had packaging=pom (generally a good practice anyway),
> otherwise you'd not be able to find it as no type is 
> specified in <parent/>.
> This is now more consistent (the POM always has the same 
> filename), and
> you can still find the POM for the JAR easily.
> It means that you cannot have two different projects with the 
> same group
> ID and artifact ID, but different packaging. I think this is 
> reasonable
> - I've never seen a use case for it. The commonly given TLD thing is
> covered because it should have the same POM as the JAR it 
> sprang from -
> so the ids can be the same.
> Anyway, check the document and let me know if there are any 
> issues. This
> is actually how it had inadvertently been implemented so it will save
> some work :)

That's what I was fighting for (specially with trygvis ;)) for couple of
Definitly this makes implementation simpler and more consistent. 
Actually it is rather neccesery to change it to make implementation at all

The last thing about repository layout, which I don't really like is the way
the groupId is specified.


View raw message