[
https://issues.apache.org/jira/browse/CXF-4581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13488222#comment-13488222
]
Glen Mazza commented on CXF-4581:
---------------------------------
quote: "Users that configure CXF to use external resources just need to be
aware that the codegen plugin will only be executed when a file within the
project is updated or an Eclipse clean is run."
The codegen plugin should be IDE-independent, so I think you mean an "mvn
clean", not an "mvn eclipse:clean", right? But the limitation that "the
codegen plugin will only be executed when a file within the project is updated"
seems too strict, because what if one of the externally referenced files
change? I would think Codegen should be detecting that and regenerating
artifacts as a result.
> cxf-codegen-plugin tries to generate code during "configuration" build
> ----------------------------------------------------------------------
>
> Key: CXF-4581
> URL: https://issues.apache.org/jira/browse/CXF-4581
> Project: CXF
> Issue Type: Bug
> Components: Tooling
> Reporter: Josh Beitelspacher
> Attachments:
> 0001-CXF-4581-Prevent-code-generation-during-m2e-incremen.patch
>
>
> In order to configure the workspace, m2e runs a "configuration" build prior
> to any actual builds. During this "configuration" builds plugins should only
> setup their additional source and resources directories and should not
> attempt to read or write any files in the workspace.
> In many cases it is not a problem that code generation runs too soon, but if
> any input files to the code generation process are not available then the
> code generation will fail, the target/generated-sources/cxf directory will
> not be created, and the generated-sources directory won't be added to Eclipse
> classpath.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
