Joost,
The example you provided has to do with conventions for the groupId,
which I don't see as an issue for any of the projects in the java.net
repository. My concern is about whether or not jaxb versions 1 and 2
are different versions of the same set of artifact or different sets
entirely. I can imagine arguments either way, but I found it
puzzling that the api and impl seem to be treated differently in that
regard. I brought it up because once artifacts get placed in a
repository it is generally a bad idea to move them later so i just
wanted to make sure that there was consensus on artifactIds and
versions.
greg kick
http://kickstyle.net/
On Jul 22, 2006, at 3:25 PM, Joost Cassee wrote:
> Gregory Kick schreef:
>
>> there's also this issue of jaxb1 vs. jaxb version 1. the api has
>> an artifactId of jaxb-api and versions 1.0 or 2.0 while the
>> implementations have artifacts jaxb1-impl and jaxb-impl (version
>> 2). it seems that this should be more consistent. however, i see
>> the argument for not changing it and confusing people... any
>> thoughts?
>
> There is support for migrating names in maven2 repos. See for
> example the move from hibernate/hibernate to org.hibernate/hibernate.
>
> - Joost
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jaxb.dev.java.net
> For additional commands, e-mail: users-help_at_jaxb.dev.java.net
>
>