"webapp" is now the default target and builds the "webapp" in $COCOON/build/cocoon/webapp, "war" packages this webapp into a cocoon.war.
Joerg
John Williams wrote:
Yes, I tested it and "build webapp" does exactly what I wanted and I see now in http://cocoon.apache.org/2.0/installing/ that the following is written:
"The target you WILL MOST USE IS PROBABLY THE WEBAPP TARGET which builds a Cocoon web application. For more information see below." (my uppercase)
I wonder if more attention should not be drawn to the fact the "build all" ONLY builds cocoon.jar - I know the intall page says so but intuitively (and a C make background) all sounds like the big one.
John
Joerg Heinicke wrote:
Sorry, but if you use "build webapp", these things are donw for you by the build system.
In order to test a recent fix I downloaded a CVS snapshot . My expectation was that once I had done a "build all" and copied all the necessary jars into WEB-INF I could use the configuration in cocoon-2.0/src/webapp in the snapshot's tar.gz file and be on my way.
Not so! I had to make the modifications detailed below to the
cocoon.xconf
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
