JDom 1.1 is out

Carlos Sanchez added a comment - 22/Mar/08 11:22 PM please read the instructions http://maven.apache.org/guides/mini/guide-central-repository-upload.html

Paul Benedict added a comment - 08/May/08 11:27 PM Can this be reopened? Yes, it's currently incomplete, but leave it open until the request is complete, please. JDOM 1.1 is still not in the central repository and it was released Nov 2007.

Carlos Sanchez added a comment - 09/May/08 1:32 PM there's no point on reopening until somebody provides it following the instructions http://maven.apache.org/guides/mini/guide-central-repository-upload.html

Benjamin Bentmann added a comment - 23/May/08 5:42 AM Next try ;-) I started off with the existing POM for JDOM 1.0, updated dependencies and added missing bits. Still missing is the license info. According to the [JDOM FAQ| http://www.jdom.org/docs/faq.html#a0030 ], it's an "Apache-style" license but I couldn't find a browsable URL for it so not sure how to get that into the POM. Also, I propose to relocate the artifact from the group "jdom" to "org.jdom" to better match our conventions. The loose POM should provide appropriate relocation info.

Carlos Sanchez added a comment - 31/May/08 8:25 PM what do the "JDOM originally shipped with..." messages mean?

Benjamin Bentmann added a comment - 01/Jun/08 3:46 AM These comments indicate dependencies that don't match exactly the JARs included in the JDOM 1.1 distribution, similar to the comments in the [jdom-1.0.pom| http://repo1.maven.org/maven2/jdom/jdom/1.0/jdom-1.0.pom ]. For instance, JDOM comes with a Jaxen lib that they patched themselves, i.e. is no official release at all. Their Xalan lib is [2.5.D1| http://xml.apache.org/xalan-j/readme.html#notes_250 ] which was a developer release immediately before the 2.5.0 that I specified in the POM. I wasn't too scary to make these adjustments as all of them affect merely optional dependencies, i.e. the JDOM client is expected to choose these libraries on his own discretion (see the maven-release-manager). In practice, the implementations bundles with JRE 1.4+ will suffice.

Carlos Sanchez added a comment - 05/Jun/08 1:04 PM don' t know what happened with 1.0 but those custom build dependencies should be uploaded in the jdom groupId and the dependencies should point there

Benjamin Bentmann added a comment - 05/Jun/08 1:31 PM Well, feel free to upload these, too. Alternatively, you could simply delete the entire {{<dependencies>}} section which has just the same effect. All that matters is {{jdom-1.1.jar}}.

Vincent Massol added a comment - 18/Aug/08 3:06 PM Would be nice to see jdom 1.1 in a maven repo... after all those years... ;)

will vuong added a comment - 21/Aug/08 11:00 AM +1 bump for getting it done

Paul Benedict added a comment - 21/Sep/08 10:26 PM Is this going to proceed?

Carlos Sanchez added a comment - 26/Sep/08 2:33 PM uploaded with all dependent files