Hi Folks, Doing a spot of tidying up on my own DSpace module, I notice that my code relies on a more recent version of the ROME library than DSpace.
I wonder if any of the maven gurus out there can tell me what the best way to manage this is? My module's pom specifies one version and the DSpace pom specifies another, and when they are built together it is unclear which version is going to get used at run-time (in practice, it appears to always be the older version, probably due to the order they are picked up for the classpath). Is there some way to tell maven to always use the latest version of a dependency, irrespective of what one of the modules says, or do I have to patch the DSpace pom on all systems which use my module? Cheers, Richard -- Richard Jones Head of Repository Systems, Symplectic Limited e: [email protected] t: 0845 026 4755 t: +44 (0)207 7334036 w: http://www.symplectic.co.uk/ ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Dspace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-devel
