maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Micah Hainline <>
Subject Re: groupId/artifactId mapping for Eclipse jars (was Re: in repo1 it is available)
Date Wed, 02 Apr 2008 14:08:26 GMT
> From: "Barrie Treloar" <>
> On the users lists I asked about seeding the repo with 3.2.2 eclipse jars.
> There is some talk about doing so and the naming convention that would be used.
> Jason knows who he has been talking to in the Eclipse world.

>From the user mailing list Jason wrote:

> I've been busy but before anyone publishes anything I'll try to summarize the meeting
we had at EclipseCon. 
> In a nutshell the OSGi experts around the table like Peter Krien's, and Jeff McAffer
agreed aligning the 
> artifact id in Maven with the symbolic id is the way to go in the future. I'll do the
summary some time 
> this week. Nothing should be published until this agreed upon method is embodied in the

That sounds like they've got that worked out then.  Whether the groupId is org.eclipse or doesn't 
really matter as long as we're all using the same one, and the artifactId is correct.  Thanks
for the pointer Barrie.

> (p.s the Dash vs Dot is worse because as per the conflict resolution
> the name without the dash is newer, thus 3.2.2 is considered newer
> than 3.2.2-M2_20080803 and your build fails since it can't find a
> matching version in the range [3.2.2,4.0.0)

Using the dashes in the version wasn't really what I was concerned about, I'd just be 
bummed if we ended up with 


instead of 


but it sounds like that isn't a concern any more.  I'll wait patiently for Jason to write
up the summary.

Micah Hainline

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message