http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html On Oct 23, 2009, at 4:17 PM, Mark Diggory wrote:
> Doubt its the classpath unless both libraries show in your lib > folders. > > You control which is used by assuring your using an identical > groupId and ArtifactId. You can try [version-number] in your > versioning to force a specific dependency on a version. this may > propagate into the dependency tree. > > Are you writing a custom overlay into the JSPUI or XMLUI? i > > If there are specific requirements for the latest version, we should > upgrade to it in the 1.6.x trunk so you can take advantage of that > in the future. If you do not have a specific requirement, you should > probably be depending on the version provided as a dependency by > DSpace. > > IF none of that "works", go to the dspace-parent pom and change the > version in the dependencyManagement section to be the version you > require. > > Mark > > p.s. is the version you are requiring in the maven central repo? > > > On Fri, Oct 23, 2009 at 9:24 AM, Richard Jones <[email protected] > > wrote: > 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 > > <ATT00001.txt><ATT00002.txt> ------------------------------------------------------------------------------ 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
