I checked out a newer version of jetty plugin (http://repo1.maven.org/maven2/org/mortbay/jetty/jetty-maven-plugin/7.0.0.1beta2/). The problem is gone there.
It seems that my problem is a bug of jetty plugin 6.1.18. aldana wrote: > > hi, > > my setting is as follows: > > rootModule > -webapp > > In pre-integration-test I start webapp with jetty plugin (webapp/pom.xml): > ---------------------------- > <plugin> > <org.mortbay.jetty</groupId> > <artifactId>maven-jetty-plugin</artifactId> > <version>6.1.18</version> > .... > <dependencies> > <dependency> > <groupId>org.hsqldb</groupId> > <artifactId>hsqldb</artifactId> > <version>1.8.0.10</version> > </dependency> > </dependencies> > .... > </plugin> > ---------------------------------- > > When running 'mvn pre-integration-test' inside webapp/ jetty starts up > fine with the hsqdlb. > > But it fails when running the same command inside rootModule/ with > ClassNotFoundError ....hsql.jdbcDriver. > > Why the heck is the <dependencies> section ignored for jetty plugin when > running it from the parent module? It is a real miracle because the > reactor itself should do nothing as also descending to the webapp/ folder > and run the maven command. > > thanks. > > > > ----- manuel aldana aldana((at))gmx.de software-engineering blog: http://www.aldana-online.de -- View this message in context: http://www.nabble.com/Very-weird-jetty-plugin-behaviour-%28excluding-plugin-dependency-when-run-from-parent-module%29-tp24205952p24206510.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
