openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Struberg (JIRA)" <>
Subject [jira] Commented: (OPENJPA-1934) contribute an openjpa-maven-plugin
Date Fri, 04 Feb 2011 10:43:48 GMT


Mark Struberg commented on OPENJPA-1934:

Txs 4 the input!
There are a few thematic areas which we need to discuss

> Would suggest that any tool that has a tight version dependency on the openjpa artifacts,
> should go into the main build instead if in the tools subproject..... 

I think this is true and I honestly don't see any project which is (on a long term) _not_
depending on the openjpa version.
I originally also thought that the openjpa-maven-plugin can be made independent of the openjpa
version. But then you cannot pickup new OpenJPA features in your tool!

So I'd suggest that the openjpa-tools normally also share the release cycle of the openjpa
project. Of course, it is _always_ possible to just release a submodule on it's own! For example,
it would easily be possible to _backport_ the openjpa-maven-plugin (or any other new tool)
to the 2.1.0 branch and release only the maven plugin as 2.1.0-bp-1.

2.) should the openjpa-tools be packaged into openjpa-all?
That depends on how you see this package. Currently it is a jar, so I'd interpret this should
only contain the classes needed for the runtime execution. So this should imo _not_ include
the various openjpa-tools.

If openjpa-all would be a binary distribution package, then the tools definitely belong there
too. But in this case it should not be a jar but rather a zip + tar.gz!

> contribute an openjpa-maven-plugin 
> -----------------------------------
>                 Key: OPENJPA-1934
>                 URL:
>             Project: OpenJPA
>          Issue Type: New Feature
>          Components: tooling
>            Reporter: Mark Struberg
>             Fix For: 2.2.0
> I'd like to contribute an openjpa-maven-plugin which got mainly written by Rahul Thakur
and me over at All is ALv2 licensed and the code provenance is pretty clear.

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message