[EMAIL PROTECTED] wrote: > Hi, > > I've got a question regarding the cocoon-maven-plugin. > I want to use this rapid development feature in a multi-module project. > It usually worked in my project, but it stopped working since I made a > major change. > > So my question is, how can I debug this feature? > How can I determine what's wrong with my configuration? > > Here is my setup: > > In my parent pom, there is the following plugin call (that should be > used by all the other modules): > <plugin> > <groupId>org.apache.cocoon</groupId> > <artifactId>cocoon-maven-plugin</artifactId> > <executions> > <execution> > <id>prepare</id> > <phase>compile</phase> > <goals> > <goal>prepare</goal> > </goals> > </execution> > </executions> > </plugin> > > In each module, I have a rcl.properties with the self containing entry > pointing to its target directory: > my.project.module.block%classes-dir=./target/classes > > In my home-module there is a rcl.properties pointing to all the other > modules: > #HOME > my.project.home.block%classes-dir=./target/classes > > #OTHERS > my.project.module1.block%classes-dir=../module1/target/classes > my.project.module2.block%classes-dir=../module2/target/classes > my.project.module3.block%classes-dir=../module3/target/classes > > calling mvn jetty:run gives the following output <snip/>
Check the files in ./target/rcl/webapp/WEB-INF/cocoon. The *.conf files are the classpath configuration and in spring/rcl.properties you can find all paths that override the servlet context paths. -- Reinhard Pötz Managing Director, {Indoqa} GmbH http://www.indoqa.com/en/people/reinhard.poetz/ Member of the Apache Software Foundation Apache Cocoon Committer, PMC member [EMAIL PROTECTED] ________________________________________________________________________ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]