[
https://issues.apache.org/jira/browse/OPENJPA-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12996109#comment-12996109
]
Michael Dick commented on OPENJPA-1934:
---------------------------------------
Back to your comments from Feb 4th.
1. This seems reasonable. If we were to refactor the enhancer and other tools
we'd move this plugin with them. In the meantime it seams reasonable for it to
be part of the main project.
2. I don't see a reason to include a maven plugin in openjpa-all. If you're
going to use the maven plugin you'd pick it up from maven central (once we've
released it there). Having it in openjpa-all would just clutter it up.
What about the site for the maven plugin? I'm assuming that entails the usage
and other 'generic' maven plugin docs. Seems like it would want to go someone
off the main OpenJPA page, or is there a better place for it?
> contribute an openjpa-maven-plugin
> -----------------------------------
>
> Key: OPENJPA-1934
> URL: https://issues.apache.org/jira/browse/OPENJPA-1934
> Project: OpenJPA
> Issue Type: New Feature
> Components: tooling
> Reporter: Mark Struberg
> Assignee: Michael Dick
> Fix For: 2.2.0
>
> Attachments: openjpa-tools-2.tar.gz, openjpa-tools.tar.gz
>
>
> I'd like to contribute an openjpa-maven-plugin which got mainly written by
> Rahul Thakur and me over at codehaus.org. All is ALv2 licensed and the code
> provenance is pretty clear.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
