The primary requirement is that it be in the Maven Central or other
repositories that we use. JDOM is only at 1.1 in the maven central repository.
You can search that repository here.
http://mvnrepository.com/artifact/org.jdom/jdom
http://mvnrepository.com/artifact/jdom/jdom
You'll need to
The first time around might be a trial, but if we did a quick review before
regression testing each minor release, once the first one was done, it would
probably be an easy task. Obviously it would be beneficial to the stability of
the platform considering the amount of transitive bug fixes
I have been testing with jdom 1.1 since December and jdom 1.1.1 for the last
couple of weeks with no negative side effects, but I'll look a little closer
before I get back to you. It's become more of a question now that we're
actually doing our 1.6 migration to production.
..\Wendy
Wendy
Hello,
Is there any reason that Dspace uses jdom 1.0 and not the currently recommended
(by jdom) version 1.1.1? I would like to use it for some code in dsp...@mit
(in the dspace-api project level), but I want to be sure not to step on code
elsewhere in dspace.
I found this info on dom 1.1
