[
https://issues.apache.org/jira/browse/CXF-4152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13220537#comment-13220537
]
Stevo Slavic commented on CXF-4152:
-----------------------------------
I agree with Daniel - my request was to make plugin m2e 1.1 compatible. There
are already efforts being taken to provide m2e connector for cxf-codegen-plugin
(e.g. see [here|https://github.com/sonatype/m2eclipse-extras/tree/cxf]), I've
tried it myself too, but there are few downsides:
- when maven plugin uses custom configuration API, m2e connector (practically
eclipse OSGi bundle) to read that configuration it needs plugin configuration
API to be published as OSGi bundle too, or repackage it in m2e connector just
to add OSGi metadata so it can be used;
- m2e connector (lifecycle mapping metadata) that is published, installed and
maintained separately from maven plugin that it connects with m2e will make
using plugin harder.
Nobody knows better cxf-codegen-plugin and how it should behave in eclipse than
cxf community.
> Make cxf-codegen-plugin m2e compatible
> --------------------------------------
>
> Key: CXF-4152
> URL: https://issues.apache.org/jira/browse/CXF-4152
> Project: CXF
> Issue Type: Improvement
> Components: Tooling
> Affects Versions: 2.5.2
> Reporter: Stevo Slavic
>
> See [1] and [2] for more info
> [1]: http://wiki.eclipse.org/M2E_plugin_execution_not_covered
> [2]: http://wiki.eclipse.org/M2E_compatible_maven_plugins
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
