[jdom-interest] V2.x not usable next to V1.x

[Gary Gregory]

On May 18, 2012, at 18:49, Rolf Lear <jdom at tuis.net> wrote:

> On 17/05/2012 11:21 PM, Gary Gregory wrote:
>> Hello JDOM,
>>
>> I cannot use both v2 and v1 in the same Maven or Ivy project because
>> both use the same id in Maven repositories like Maven Central.
>>
>> I want to use v2 in my app but 3rd party jars I use depends on v1.
>>
>> Gary
>> _______________________________________________
>> To control your jdom-interest membership:
>> http://www.jdom.org/mailman/options/jdom-interest/youraddr@yourhost.com
>>
>
>
> Hi Gary
>
> Sorry to drag you though the maven stress on JDOM.

C'est la vie, I hope we will all learn something out of this, process
wise and technically. :)

>
> So, I cannot have a jdom-2.0.2.jar deployed in the artifact 'jdom2'. Does not validate when I try....

>
> My options are:
>
> - change the (perfectly valid) JDOM naming convention from jdom-2.0.2.jar to jdom2-2.0.2.jar, or should that be jdom2-1.0.0, or what? What is the 'expected convention'?

See below.

> - should I do that for the maven deploy only, or should I do it for the offical JDOM release as well?

I would think it simpler for users if the jar file names are the same
for v2. So use jdom2-2.x.x for both.

> - should I double-deploy, to both jdom and jdom2

That's a pickle. IMO jdom should revert to 1.x but the cat is out of
the bag here because you cannot undeploy. So let it be.

>
> For whatever reason I am resistant to renaming the official JDOM release standard to jdom2-x.y.z.jar from jdom-x.y.z.jar.
>

I think the path of least resistance from the tooling POV is to use
the artifact Id jdom for v1 and jdom2 for v2 and accept the jar naming
that comes out of it.

Yes, you end up with the name jdom2-2.0.2.jar. That is what I've seen
come out of other apache projects.

I'm not a big fan of the naming convention but I am a big fan of
dependency management and automated tools. So I take the good with the
less tasty.

Gary