[
http://jira.codehaus.org/browse/MWAS-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David J. M. Karlsen closed MWAS-31.
-----------------------------------
Resolution: Not A Bug
Fix Version/s: 1.0.1
This should be done inside of the pluginManagement section and will work
flawlessy then: http://maven.apache.org/ref/2.0.8/maven-model/maven.html
> allow configuration to be done in a parent pom rather than just in an ear
> -------------------------------------------------------------------------
>
> Key: MWAS-31
> URL: http://jira.codehaus.org/browse/MWAS-31
> Project: Maven 2.x WebSphere 6 Plugin
> Issue Type: Improvement
> Affects Versions: 1.0
> Reporter: Jim Sellers
> Assignee: David J. M. Karlsen
> Fix For: 1.0.1
>
>
> Almost all our builds are multimodule with this structure:
> parent
> |__ ear project
> |__ war project
> or
> parent
> |__ external ear project
> |__ external war project
> |__ internal ear project
> |__ internal war project
> |__ common jar
> If the config is put into the parent because things like wasHome, host, etc
> would be the same. However this prevents from running the lifecycle from the
> top level because in classes like WsDefaultBindingsMojo it errors out if
> packaging is not "ear".
> Please change it to warn and then just skip the plugin if it's not the
> correct type.
> If you want, I can attach a sample multi-module project to demo what I mean.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
