The second option has been easier for me to automate in the past, but going forward I am leaning toward a single Cocoon hosted in my servlet container with multiple applications deployed to it. Until more progress is made toward Real Blocks, I have not found a good way to generate an independently deployable artifact from a maven project.
As I have a couple of projects languishing that need this, I will probably revisit this PSN. What I might do instead of a wiki entry is an application template for the maven genapp plugin. That way, someone could just create a new directory, run maven genapp, choose the cocoon-application template, and have a skeleton to work with. OK, reading back over that I suppose a wiki entry would make sense :)
When I have some time for this I will wiki it and ping the list.
-- Ryan Hoegg ISIS Networks http://www.isisnetworks.net
Ralph Goers wrote:
Do you think you could create a wiki entry on how you set up your Cocoon project(s) using maven? I've been thinking about doing this myself, but would like to see the steps you go through.
Ralph
-----Original Message----- From: Ryan Hoegg [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 17, 2003 10:17 AM To: [EMAIL PROTECTED] Subject: Re: OT: How do you use CVS?
fwiw, I have been able to separate my unit test dependencies out by creating a subproject for my tests. My subproject depends on my original project, and it is a simple matter to override the "test:test" goal in maven.xml to run tests in the subproject instead.
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
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
