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 -- 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] https://dev.eclipse.org/mailman/listinfo/m2e-users
_______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
