Hi folks! The current version of the openjpa-maven-plugin is 1.0-SNAPSHOT.
Today, Rahul and I had a discussion about whether to change the current version schema of the openjpa-maven-plugin to be align with the versions of openjpa itself. The openjpa-maven-plugin uses openjpa for compile time enhancement, SQL creation and schema-mapping creation. So although there may be no change in the source needed, this has a really deep impact on how it behaves. (See e.g. the following openjpa bugs: https://issues.apache.org/jira/browse/OPENJPA-722 https://issues.apache.org/jira/browse/OPENJPA-733 ) I'd like to change the version schema (and release the plugins) to: .) openjpa-maven-plugin-1.1.0 -> openjpa-1.1.0 .) openjpa-maven-plugin-1.2.0 -> openjpa-1.2.0 .) openjpa-maven-plugin-1.2.1 -> openjpa-1.2.1 PRO: + this will explicitly show the openjpa version used + no need to fumble around with <dependencies> sections in the plugin config + no more surprises because the plugin uses openjpa-1.2.0 but the project uses 1.1.0 and one simply forgot to pommel the dependency CON: + in case of bugs, we'd have to use e.g. 1.2.0.1, 1.2.0.2 etc + in case of bugs, we'd have to run multiple release (1.2.0.1, 1.1.0.1, etc) please vote: +1: yes, let's change the version schema 0: I don't care, either one will work -1: nope, I see some problems, let's release 1.0, 1.1 and so on txs and LieGrue, strub --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
