I don't think there will be any facility for distinguishing compile-time dependencies from runtime dependencies in 1.0, but in practice I haven't found much need for this. One exception is the servlet API.
-- Ryan Hoegg ISIS Networks http://www.isisnetworks.net
Ralph Goers wrote:
We are using Maven. It handles the dependencies nicely, although the current release doesn't differentiate between dependencies needed to build, those for unit-testing, and those needed at runtime. Maven has a repository where dependent jars are placed. Migration from one release of Cocoon to another involves building cocoon with only the desired blocks, looking at the jars in WEB-INF/lib from that and copying them into the global repository (this requires renaming the cocoon jars to include a version number), and then modifying the various project.xml files to specify the correct dependencies. Once the project.xml is checked in, everyone else will automatically have their local repositories updated when they checkout/update and build.
I check into my CVS project the sitemap.xmap, cocoon.xconf and other files that Cocoon builds so they will be included as part of the webapp.
Ralph
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
