I think we found that maven just used the plugin from our tree. I tested
this by adding silly debug statements in one of the Java files from the
plugin. But that might only be true if you are building the whole
project tree, as opposed to just building a war module. Hmmm... I don't
think we tes
; at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPackaging(DefaultLifecycleExecutor.java:1011)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:975)
>> at
&
My project was using a modified version of the war plugin for a while. I
decided that the best solution was to make the plugin another module in
our project. This solution seemed easier than managing a release process
for the modified plugin separately, or requiring team members to do
something
xecutor.java:453)
Thanks,
JP4
--
View this message in context:
http://www.nabble.com/Modified-WAR-Plugin-tf2268007.html#a6294602
Sent from the Maven - Users forum at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
