[jdom-interest] V2.x not usable next to V1.x
jdom at tuis.net
Fri May 18 07:27:32 PDT 2012
Where were you for this discussion:
So, the problem is as follows.... Maven imposes naming requirements for
'We' decided that this is JDOM 2.0.0, not JDOM2 1.0.0, and also not JDOM2
2.0.0, etc. Thus, the *main* download will be the jar jdom-2.0.0.jar.
This means that the maven artifact id *must* be 'jdom', not 'jdom2'.
At the time I was not aware how hard/impossible it would be to have both
jdom 1.x and 2.x sourced from maven....
Maven is the 'secondary' distribution system for JDOM. The primary JDOM
source is from www.jdom.org. The jars downloaded from maven should be
identical to the ones from jdom.org.
There are about 15k downloads a month from www.jdom.org of 1.x versions of
There are about 35k downloads a month from maven-central of 1.x versions
There are about 10k downloads a month from www.jdom.org of 2.0.x versions
There are about 1k downloads a month from maven-central of 2.0.x versions
The maven downloads show an *opposite* distribution of downloads compared
Here are maven's statistics for the three months Feb, Mar, Apr:
here's the graph....
JDOM 1.1 (released 2007) was downloaded 92K times in 3 months.
1.1.2 (released last Aug) downloaded 6.5k times in 3 months.
1.1.3 (released in Feb) just 3.5k times in 3 months
Note that Maven does not even have JDOM 1.1.1 (from 2009) .....
So, it shows a distinct 'inertia' in maven users. For all I know they are
not even aware that JDOM 2.x has happened.... My guess would be that 90% of
maven users do not pay attention to their code....
In a 'short while' I want to be in the position to say: "JDOM 1.x is no
longer being maintained". It is not in *my* interests to do it.... it is
essentially unchanged since 2007. If people have problems in JDOM 1.x I'm
going to want to say "Upgrade to 2.x". I am targeting about December 2012
What all this rambling boils down to is:
1. I don't want to have to change JDOM's jar file name from jdom-2.0.x.jar
2. maven is the 'secondary' distribution system
3. you can ask your 'dependency' code to upgrade to jdom 2.x (they should
be doing it anyway).
4. The bell has already been rung on this... I can't un-ring this maven
5. maven users are 'lazy' about keeping in touch with their dependencies,
and this will 'prod' them.
6. This is all a maven problem (by design or implementation, I am not
7. maven 'users' (including apache commons) are happy to do their own
8. maven is a PITA ..... :(
As you can tell, maven support 'requirement' has not been a happy
process.... in hindsight I probably should have just said no .... On the
other hand, now that I have the automated build system working, it is not
hard to publish to maven, as long as it conforms to JDOM's standards, I'm
Now that I have established my 'aversion' to the maven model, can you
suggest a way out of this predicament that also conforms to the JDOM
'standard'... ? I promise to consider any suggestions....
On Fri, 18 May 2012 08:29:28 -0400, Gary Gregory <garydgregory at gmail.com>
> Hi All,
> For good or bad, I ended learning more than I care about Maven being the
> release manager for several Apache Commons components.
> Our rule in Commons is that when you change a package name, you must
> the Maven artifact id.
> My suggestion is to do this in your POM:
> Depending on your philosophy, you could also re-publish the Maven
> for 2.0.1. But this is usually considered bad form because the POM needs
> change and you would then have 2 2.0.1 version with different pom.xml in
> your sources jar.
More information about the jdom-interest