You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by aldana <al...@gmx.de> on 2009/06/25 17:51:31 UTC
Very weird jetty-plugin behaviour (excluding plugin dependency when
run from parent module)
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-tp24205952p24205952.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Very weird jetty-plugin behaviour (excluding plugin dependency
when run from parent module)
Posted by aldana <al...@gmx.de>.
aaargh, the real cause was different.
Inside the parent-pom I mistakenly added the plugin-definition to <build>
instead of <pluginManagement>. So in the end i <dependencies> section
resolved to an empty set.
Though I find it a bit weird that when doing a multimodule build a
parent-module can override the <dependencies> setting of a plugin of a child
module. I would expect the opposite.
aldana wrote:
>
> 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-tp24205952p24207485.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Very weird jetty-plugin behaviour (excluding plugin dependency
when run from parent module)
Posted by aldana <al...@gmx.de>.
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org