Sorry if I misunderstood - the previous post suggested that
it was good practice to integrate your changes as part
of the build process, rather than making them manually - and
directly - to the files after building Cocoon.
I was not talking about the use case for a *single* project, but
the
Derek Hohls wrote:
Sorry if I misunderstood - the previous post suggested that
it was good practice to integrate your changes as part
of the build process, rather than making them manually - and
directly - to the files after building Cocoon.
There are two schools of thought. Some folks
Does this imply that if you have incremental changes to these
files (more projects being added to an *existing*Cocoon
installations) over time, that you should be rebuilding and
redeploying Cocoon each time? [EMAIL PROTECTED] 2005/11/26 10:41 PM
Le 26 nov. 05, à 20:56, Shawn C. Powell a écrit
You only need to rebuild Cocoon if you have integrated your product into
its build. If you use the process described at
http://wiki.apache.org/cocoon/HowToBuildAndDeployCocoonWithMaven?highlight=%28maven%29
then you only need to rebuild Cocoon when you want to upgrade it. To
integrate changes
Hello everyone,
How does one preserve/handle/integrate-changes to the toplevel runtime
configuration files such as xconf and web.xml during an update for instance
from 2.1.7 to 2.1.8?
Obviously I can backup/restore/edit but I wondered if there is something in
the docs that I'm missing or if
Le 26 nov. 05, à 20:56, Shawn C. Powell a écrit :
...How does one preserve/handle/integrate-changes to the toplevel
runtime
configuration files such as xconf and web.xml during an update for
instance
from 2.1.7 to 2.1.8?...
The best way to handle this is to avoid modifying these files
On Saturday 26 November 2005 02:41 pm, Bertrand Delacretaz wrote:
The best way to handle this is to avoid modifying these files directly,
and use our XConfToolTask with ant to patch these files at build time.
...
Thanks for pointing me in the right direction , Bertrand!
Sincerely,
Shawn C.
This is probably a good time to point out one of the features of 2.2.
You no longer need to use XConfToolTask. Instead, you can place your
xconf files into a directory where they are automatically included.
Also, you can place the component section of the sitemap in an xconf
file and
