<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi Richard.<br>
<br>
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.<br>
<br>
We are committed to making JDOM available on maven now, and the
first official release was to here:
<a class="moz-txt-link-freetext" href="http://search.maven.org/#browse">http://search.maven.org/#browse</a>|-167108894<br>
<br>
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.<br>
<br>
Fundamentally, though, the issues are as follows:<br>
- For versions already released to Maven, I can't change anything.<br>
- 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).<br>
- JDOM 1.* is in a definite 'maintenance mode' only.<br>
- 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.<br>
-> jdom is being managed through the OSS 'nexus', and it has
'conditions'<br>
-> one condition is that any 'jar' artifact is released in
combination with a matching 'javadoc' and 'source' artifact.<br>
-> the javadoc for contrib is 'messy'.<br>
-> the source for contrib is 'messy'.<br>
<br>
So, if I can come back with some questions of my own:<br>
<br>
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)<br>
can you wait for 2 weeks for the scheduled release of 1.1.3 (fixes a
bug in SAXOutputter)?<br>
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?<br>
<br>
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.<br>
<br>
So, in answer to your questions:<br>
No, we do not have plans to release contrib on maven central, but we
can if there is a good reason....<br>
It is an active decision because:<br>
1. maven central is 'new' to me, and 1.1.2 JDOM was the first
release I have done<br>
2. I do not believe contrib is 'production ready' code.
Certainly I do not pay it very much attention.<br>
3. contrib is not 'tidy' enough to package with a sources and
javadoc jar to mate with the contrib jar for the OSS requirements<br>
<br>
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....<br>
<br>
I put together some notes as I went through the 1.1.2 process here:
<a class="moz-txt-link-freetext" href="https://github.com/hunterhacker/jdom/wiki/JDOM1.1.2-and-Maven">https://github.com/hunterhacker/jdom/wiki/JDOM1.1.2-and-Maven</a><br>
<br>
It would be great if you could inspect the 1.1.2 release to see if
there are other issues, also the pom file
<a class="moz-txt-link-freetext" href="https://github.com/hunterhacker/jdom/blob/jdom-1.x/maven.pom">https://github.com/hunterhacker/jdom/blob/jdom-1.x/maven.pom</a> and the
build.xml
<a class="moz-txt-link-freetext" href="https://github.com/hunterhacker/jdom/blob/jdom-1.x/build.xml">https://github.com/hunterhacker/jdom/blob/jdom-1.x/build.xml</a><br>
<br>
Thanks<br>
<br>
Rolf<br>
<br>
<br>
<br>
On 15/02/2012 5:42 PM, Richard Adams wrote:
<blockquote
cite="mid:CACH50mum_PZ0U_c1n8fzzZUMdnvXUh3kt_-2QSb5k+gPqc+2Vg@mail.gmail.com"
type="cite">
<blockquote type="cite"
style="font-family:Helvetica;font-size:medium">
<div>
<div>
<div>
<blockquote type="cite">Hello,<br>
<br>
I'd like to make a Java scientific library (<a
moz-do-not-send="true" href="http://jlibsedml.sf.net/">http://jlibsedml.sf.net</a>)
I'm writing available on maven central repository.<br>
One of the criteria that is requested is that all
dependencies are also available from this repository.<br>
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 .<br>
<br>
Do you have any plans to make jdom-contrib available
from the maven central repository? If not, is this an
active decision not to?<br>
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.<br>
<br>
Best wishes<br>
<br>
Richard</blockquote>
</div>
</div>
</div>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
To control your jdom-interest membership:
<a class="moz-txt-link-freetext" href="http://www.jdom.org/mailman/options/jdom-interest/youraddr@yourhost.com">http://www.jdom.org/mailman/options/jdom-interest/youraddr@yourhost.com</a></pre>
</blockquote>
<br>
</body>
</html>