Question about Maven integration

[Gerry Kaplan <gk...@kaplansoftware.com>]

I have read through the tutorial regarding 2.2 but there is one point that
is unclear. I can see how Maven will create the directories and everything
needed to get a project going, but what if there are changes to Cocoon
itself (i.e. version 2.2.1) and you want to apply those changes to your
previously built webapp? Is there a good article that talks about the
lifecycle of a Cocoon 2.2 app that is built with Maven? Also, what about
updates to Spring? I'm not sure how these pieces remain current once the
Cocoon parts are built.

 

Thanks,

Gerry Kaplan

 

Re: Question about Maven integration

["Hubert A. Klein Ikkink" <mr...@planet.nl>]

Gerry Kaplan <gkaplan <at> kaplansoftware.com> writes:
> But what if there are changes to
> Cocoon itself (i.e. version 2.2.1) and you want to apply those 
> changes to your previously
> built webapp?

Hi Gerry,

the lifecycle of a Cocoon 2.2 app will be the same as for any Maven project. 
Cocoon is nothing more than a dependency in the pom.xml file. If a 
new version is released we only have to change the version 
number in the pom.xml of Cocoon app. See the dependencies 
section in a pom.xml for a cocoon-core reference. Here is also
the version number mentioned.

> Also, what about updates to Spring?

Spring is now a dependency of the Cocoon artifacts. Maven has a mechanism 
to exclude certain dependencies to artifacts. We then have to use
the exclusions elements with a dependency. So this way we can use a 
newer version of Spring.

Kind regards, Hubert Klein Ikkink






---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org