On 12-08-29 1:01 PM, Keith Barlow wrote:
The plugin is a customized xjc plugin so if I understand you correctly, I have two options: 1.) Configure it for execute which requires adding code which uses the plexus-build-api to make workspace changes. (e.g. I could have the generated files added to the build path if desired or I could just leave that as a manual task but would still need a no-op implementation to be executed).
Assuming the goal is to have generated files visible as java sources in workspace, the mapping needs to runOnConfiguration=true, such that source root folders added by the plugin are created as Eclipse java project source folders. This does not require use of BuildContext runOnIncremental can be either true of false. runOnIncremental=false does not require use of BuildContext either, but source code will only be (re)generated during full/clean workspace build and will require manual project refresh. For automatic generation of sources, runOnIncremental=true and use of BuildContext is required
2.) Add it as ignore which would suppress all error messages and prevent the plugin from being executed unless I actually do a maven build. (which is essentially what happens now only I do get error messages.)
This will completely ignore the plugin in Eclipse. You will need to create java source folders in Eclipse and run the code generation manually. -- Regards, Igor
Is that correct? (Thanks in advance.) Keith On Wed, Aug 29, 2012 at 12:43 PM, Igor Fedorenko <[email protected] <mailto:[email protected]>> wrote: If your maven plugin can safely participate Eclipse incremental build, which in practice means it can either be safely ignored or plugin code uses plexus BuildContext to negotiate changes, the mapping metadata can be embedded in maven plugin itself. See [1] for more details. If mapping requires Eclipse-specific logic not currently achievable through BuildContext, then you need to write an Eclipse plugin that provides the implementation of the logic and mapping xml file. [1] http://wiki.eclipse.org/M2E___compatible_maven_plugins <http://wiki.eclipse.org/M2E_compatible_maven_plugins> -- Regards, Igor On 12-08-29 12:31 PM, Keith Barlow wrote: Hiyas, We have a customized maven plugin we use in our company which doesn't have lifecycle mapping metadata for it... How do I add a local entry to the new Lifecycle Mappings preferences feature in m2e? I looked at the developer documentation for extension development and it defines a lifecycle mapping xml blob but it looks like that needs to point to some kind of configurator class... is that required for local entries? where would it live? Thanks. Keith -- Keith Barlow /Software Engineer/ *Dell Boomi* _________________________________________________ m2e-users mailing list [email protected] <mailto:[email protected]> https://dev.eclipse.org/__mailman/listinfo/m2e-users <https://dev.eclipse.org/mailman/listinfo/m2e-users> _________________________________________________ m2e-users mailing list [email protected] <mailto:[email protected]> https://dev.eclipse.org/__mailman/listinfo/m2e-users <https://dev.eclipse.org/mailman/listinfo/m2e-users> -- Keith Barlow /Software Engineer/ *Dell Boomi* _______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
_______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
