How hard would it be to create an archetype to create the pom
automatically? Users would then either just build and run it or edit it
first to remove stuff they don't care about.
Telling them to create pom.xml inheriting from core-cocoon-webapp still
requires that they a) know how to do that and b) know what samples exist
that they can add.
Ralph
Vadim Gritsenko wrote:
On Jan 7, 2008, at 2:32 AM, Ralph Goers wrote:
But if they want to build the sample site and run it what would they do?
Create pom.xml inheriting from core/cocoon-webapp and add dependencies
to all of the *-sample blocks you want, followed by mvn install
jetty:run should do it.
Vadim
