Adding the dependency to your project.xml should give you a lib dir with both jars.
Then, we normally remove the old one with a maven postgoal (see maven.xml of the cms for example) regards Ard > > Hi, > > I have a site that extends the hippocms, and so I want to add > additional dependencies to my build. I'm using a setup > similar to http://www.hippocms.org/display/CMS/08.+Extending+Hippo+CMS > > In my top-level project.xml (or common-project.xml, I've > tried both) I've added my dependency: > > <dependency> > <id>foo:bar</id> > <version>1.2.3</version> > <type>jar</type> > <properties> > <cocoon.bundle>true</cocoon.bundle> > <war.bundle>true</war.bundle> > </properties> > </dependency> > > ... but an older version happens to already exist in the CMS: > > <dependency> > <id>foo:bar</id> > <version>1.2.2</version> > <type>jar</type> > <properties> > <cocoon.bundle>true</cocoon.bundle> > <war.bundle>true</war.bundle> > </properties> > </dependency> > > It seems that the only version deployed to my webapp is 1.2.2 > (ie the old version). It looks like the 'extend' option in > editor/project.xml actually works the opposite way round to > what I need: > <extend>${basedir}/../common-project.xml</extend> > ... with editor/project.xml overriding anything I specify. > > Is there a way to give my dependencies precedence, other than > patching/modifying editor/project.xml? > > > Thanks, > > Andrew. > -- > Andrew Savory > Tel: +44 (0)870 741 6658 Fax: +44 (0)700 598 1135 > Sourcesense - making sense of Open Source: http://www.sourcesense.com > > ******************************************** > Hippocms-dev: Hippo CMS development public mailinglist >
******************************************** Hippocms-dev: Hippo CMS development public mailinglist
