dspace-api depends on net.java.dev.rome:rome:1.0.0 and rometools:rome-modules:1.0 which depends on rometools:rome:1.0. So we wind up with rome-1.0.jar AND rome-1.0.0.jar in the built kit.
It looks as though the Rome project moved from java.net to Github around 1.0 time, that the rometools versions are thus the latest, and that we should therefore be depending on rometools:rome:1.0 rather than net.java.dev.rome:rome:1.0.0. That would harmonize with the transitive dependency and not leave us wondering what the classloader will do when it finds two rome-*.jar archives. Does anyone know why we should not change this? It's probably not a big problem.... -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Machines should not be friendly. Machines should be obedient.
signature.asc
Description: Digital signature
------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
