[
http://jira.codehaus.org/browse/MAXISTOOLS-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158083#action_158083
]
Benjamin Bentmann commented on MAXISTOOLS-39:
---------------------------------------------
Forking a lifecycle from a lifecycle-bound mojo looks odd (not to mention the
performance penalty). In particular, it's very odd to fork the lifecycle up to
"compile" and then bind the mojo to "genereate-resources", i.e. an earlier
phase.
The Plexus Maven Plugin has a similar "problem", i.e. needs the compiled
classes to generate the Plexus descriptor. The solution that has been employed
there is to simply have the plugin output directly into
"${project.build.outputDirectory}" instead of "../generated-...".
> java2wsdl should fork a lifecycle
> ---------------------------------
>
> Key: MAXISTOOLS-39
> URL: http://jira.codehaus.org/browse/MAXISTOOLS-39
> Project: Maven 2.x Axis Tools Plugin
> Issue Type: Improvement
> Affects Versions: 1.2
> Environment: N/A
> Reporter: David J. M. Karlsen
>
> The generated .wsdl are not added in the resulting archive.
> This is because the plugin needs the compiled classes for generating the
> wsdl, but it is too late to add resources at this stage.
> The suggested solution is to fork a compile lifecycle and switch the phase
> from process-classes to generate-resources.
--
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
