[
https://issues.apache.org/jira/browse/OPENJPA-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15120999#comment-15120999
]
Anders Hammar commented on OPENJPA-2622:
----------------------------------------
Some info for anyone finding this issue.
I've successfully used a m2e connector for v2.2.2 of the plugin, which can be
found at
https://raw.githubusercontent.com/hwellmann/m2eclipse-extras/master/p2/ .
Takari incremental build support API requires Java 7, so going that path would
force the maven plugin to require Java 7 (just for building, not the target
level). Doing it "correctly" would probably also imply a rather large re-write
of the plugin logic (only pass changed classes to the enhancer for example).
I think that a good path forward would be to add m2e support by the
plexus-build-api (as described in the link in the description of this ticket).
It's a rather small change. And then plan for a improved solution using
Takari's incremental build support API.
> Make maven plugin m2e compatible
> --------------------------------
>
> Key: OPENJPA-2622
> URL: https://issues.apache.org/jira/browse/OPENJPA-2622
> Project: OpenJPA
> Issue Type: Improvement
> Reporter: Anders Hammar
> Labels: maven
>
> It would be great if the enhance goal of openjpa-maven-plugin was compatible
> with m2e, so that the entity classes are incrementally enhanced in Eclipse.
> This would remove the need for misc workarounds when using build-time
> enhancement during IDE development/testing.
> See https://wiki.eclipse.org/M2E_compatible_maven_plugins
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
