Re: jdom-contrib on maven central?

Hi Richard.

JDOM 1.1.2 is the first maven release that was pushed through the 
'official' channels. Other maven artifacts have been pushed through by 
people/groups/individuals not related directly to the JDOM project.

We are committed to making JDOM available on maven now, and the first 
official release was to here: http://search.maven.org/#browse|-167108894

It has been something of a learning process... and there were some small 
issues with that release.... and the forthcoming 1.1.3 release (and JDOM 
2.x) will be improved.

Fundamentally, though, the issues are as follows:
- For versions already released to Maven, I can't change anything.
- I do not have 'permission' to release artifacts to 'other' 
co-ordinates (I can release to the org.jdom co-ordinate only, but 
technically the current mavan-central jdom 1.1 code is not in that 
namespace).
- JDOM 1.* is in a definite 'maintenance mode' only.
- I was not (originally) intending to release the contrib jars on to 
maven-central - it is work that I had not expected to be useful.
    -> jdom is being managed through the OSS 'nexus', and it has 
'conditions'
    -> one condition is that any 'jar' artifact is released in 
combination with a matching 'javadoc' and 'source' artifact.
    -> the javadoc for contrib is 'messy'.
    -> the source for contrib is 'messy'.

So, if I can come back with some questions of my own:

why are you using JDOM 1.1 and contrib 1.1.1 when you could be using 
1.1.2? 1.1 is *old* (November 2007)
can you wait for 2 weeks for the scheduled release of 1.1.3 (fixes a bug 
in SAXOutputter)?
what functionality in contrib are you using in your application... 
contrib is not treated as 'carefully' as the core JDOM, and it certainly 
is not as well tested. Perhaps this functionality should be in core JDOM?

So, as for putting the code in to maven, in theory I should now know 
what I am doing.... The build script for JDOM contains a target to do 
most of the work, and I can 'duplicate' it for the jdom-contrib jar. On 
the flip side, I am not a regular maven user, and I did make mistakes 
with the existing 1.1.2 'pom' file (it lists 'jaxen' as a dependency, 
but there is no jaxen 1.1.3 artifact in maven central - it should be an 
optional dependency). Unfortunately there is no way to 'fix' maven 
issues unless you release a newer version.

So, in answer to your questions:
No, we do not have plans to release contrib on maven central, but we can 
if there is a good reason....
It is an active decision because:
     1. maven central is 'new' to me, and 1.1.2 JDOM was the first 
release I have done
     2. I do not believe contrib is 'production ready' code. Certainly I 
do not pay it very much attention.
     3. contrib is not 'tidy' enough to package with a sources and 
javadoc jar to mate with the contrib jar for the OSS requirements

We (I) welcome any assistance you can provide, but, in this particular 
case, the process of pushing things to maven is fairly well automated, 
*but*, the actual maven experience we have is somewhat limited... if you 
have manpower to spare I would appreciate it if you could inspect and 
criticize/improve the process used to 'push' 1.1.2 to maven... it could 
be flawed.... and it will be the base for pushing all future versions to 
maven....

I put together some notes as I went through the 1.1.2 process here: 
https://github.com/hunterhacker/jdom/wiki/JDOM1.1.2-and-Maven

It would be great if you could inspect the 1.1.2 release to see if there 
are other issues, also the pom file 
https://github.com/hunterhacker/jdom/blob/jdom-1.x/maven.pom and the 
build.xml https://github.com/hunterhacker/jdom/blob/jdom-1.x/build.xml

Thanks

Rolf



On 15/02/2012 5:42 PM, Richard Adams wrote:
>>> Hello,
>>>
>>>  I'd like to make a Java scientific library 
>>>  (http://jlibsedml.sf.net <http://jlibsedml.sf.net/>) I'm writing 
>>> available on maven central repository.
>>> One of the criteria that is requested is that all dependencies are 
>>> also available from this repository.
>>>  We use jdom 1.1  and jdom-contrib 1.1.1 (both are excellent!) and 
>>> while jdom is on maven central, jdom-contrib doesn't appear to be .
>>>
>>>  Do you have any plans to make jdom-contrib available from the maven 
>>> central repository? If not, is this an active decision not to?
>>>  I'd be willing to put in some effort to help bundle it for the 
>>> repository if it's a question of manpower - having gone through the 
>>> process recently for another library, it is a bit of a slog.
>>>
>>> Best wishes
>>>
>>>     Richard
>
>
> _______________________________________________
> To control your jdom-interest membership:
> http://www.jdom.org/mailman/options/jdom-interest/[email protected]

_______________________________________________
To control your jdom-interest membership:
http://www.jdom.org/mailman/options/jdom-interest/[email protected]