The objective is to make the JDOM 1.1.2 jar available on maven-central so that other projects can just suck in the jdom jars by setting the appropriate dependencies in their project configurations.
This functionality is complete now. Skip to the end of the document for details on how it was done.
... yes, an 'invented' word, but, in a different sense: "What we don't want!"
This feature is now done for JDOM 1.1.2. Here are the details of how it was implemented.
The path chosen is the 'manual' process of uploading a maven 'Bundle' to maven-central. This process is abtracted significantly. It is easier to understand the process 'backwards':
To build the maven bundle using the ant target you need to have a way to sign the jars. If we were using a full maven build process it would be relatively easy to set this up. Since we don't, you need to set up the process 'the hard way'. Here's how I did it (I have done it on both Windows, and linux, but windows is the more complicated, and the one I normally use - my laptop is windows) :
gpg -abv somefile. You should be prompted for a 'passphrase'.
Last edited by rolfl,