Hi Andrew,
I'm afraid this is not possible in Maven 1 (See
http://maven.apache.org/maven-1.x/using/customising.html) for more
information. You could add a maven.xml file to the root of your project
and use the anttasks to delete the old and insert your new jar into your
cms lib directory.
Regards,
Jeroen Reijn
Andrew J. Savory wrote:
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.
--
Met vriendelijke groet,
Kind regards,
Jeroen Reijn
Hippo
Oosteinde 11
1017WT Amsterdam
The Netherlands
Tel +31 (0)20 5224466
********************************************
Hippocms-dev: Hippo CMS development public mailinglist
