[
http://jira.codehaus.org/browse/MWAS-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=142867#action_142867
]
Paul Benedict commented on MWAS-9:
----------------------------------
I am almost absolutely sure pulling configuration from other plugins is
considered a bad practice. The correct solution is to use toolchains, which is
what Maven developers created to resolve this issue in an acceptable manner.
> Pull compiler compliance level from compiler-plugin configuration for
> EjbDeploy goal
> ------------------------------------------------------------------------------------
>
> Key: MWAS-9
> URL: http://jira.codehaus.org/browse/MWAS-9
> Project: Maven 2.x WebSphere 6 Plugin
> Issue Type: Improvement
> Environment: N/A
> Reporter: David J. M. Karlsen
> Assignee: David J. M. Karlsen
> Priority: Minor
> Fix For: 1.0-alpha-3
>
>
> Pull the compiler compliance level from
> mavenProject.getBuild().getPluginsAsMap() (from the compiler plugin) - so
> that
> http://mojo.codehaus.org/was6-maven-plugin/ejbdeploy-mojo.html#jdkComplianceLevel
> is obsolete.
> Note that
> http://mojo.codehaus.org/was6-maven-plugin/ejbdeploy-mojo.html#legacyMode
> still needs to be respected as the compliance level is not respected in older
> versions of WAS ant tasks.
--
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
