Thanks
I explicitly set the version and have got what I need.
May just have been more careful.
Ron
On 20/08/2010 11:56 AM, Dennis Lundberg wrote:
When testing issues before the 2.1 release of the WAR plugin I can
across one issue where the configuration wouldn't "stick" if it was in
the parent's build/pluginManagement section. When the configuration was
moved to the child module's build/plugins section it worked. However I
couldn't understand why.
There's an issue for this in JIRA:
http://jira.codehaus.org/browse/MWAR-149
On 2010-08-20 16:53, Ron Wheeler wrote:
Found a new oddity that perhaps someone can explain.
I am trying to build a WAR file using maven-war-plugin
If I put the proper configuration in the module's POM I get the Manifest
that I want.
If I just put it in the parent in the plug-in section without any
mention of the plug-in at all in the module I do get a WAR file but I do
not get the Manifest that I want.
If I put the plugin configuration in the parent's dependencyManagement
section and put a reference just to the plug-in in the module, I get the
WAR file without the Manifest that I want.
This is the whole configuration section that gives me the Manifest.
<configuration>
<warSourceDirectory>WebContent</warSourceDirectory>
<archive>
<manifest>
<addDefaultImplementationEntries>true</addDefaultImplementationEntries>
<addDefaultSpecificationEntries>true</addDefaultSpecificationEntries>
</manifest>
</archive>
</configuration>
It appears that Maven is bypassing the plug-in unless it is explicit in
the module POM.
Is this right or am I missing something to get maven-war-plugin to be
configured in the parent POM?
Ron
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
