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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
