cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Beitelspacher (JIRA)" <>
Subject [jira] [Commented] (CXF-4581) cxf-codegen-plugin tries to generate code during "configuration" build
Date Thu, 01 Nov 2012 02:57:12 GMT


Josh Beitelspacher commented on CXF-4581:

I should have been more clear in my comment. This change only affects incremental builds inside
Eclipse. When building from the command line cxf-codegen-plugin will continue to check for
changes in externally referenced files during every build.

When the cxf-codegen-plugin is called during an Eclipse incremental build, the cxf-codegen-plugin
will also check for changes in externally referenced files. The problem is that changing one
of the externally referenced files inside Eclipse won't actually trigger an increment build.
The user has to touch a file or run "Project -> Clean..." in Eclipse to trigger a clean
(which will immediately be followed by an automatic rebuild). The attached patch doesn't address
this problem because there is no easy way to solve it. Instead of mentioning this issue in
the comments I should probably have opened a new issue for it.

All the attached patch does is prevent the cxf-codegen-plugin from trying to generate code
during the m2e configuration build. It shouldn't have any impact at all when mvn is run from
the command line.
> cxf-codegen-plugin tries to generate code during "configuration" build
> ----------------------------------------------------------------------
>                 Key: CXF-4581
>                 URL:
>             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:

View raw message