hi Jesse! There are a few things which cannot be fixed without binding the plugin to a specific OpenJPA version. This is only possible if we move the plugin over from codehaus to the OpenJPA tools project.
I already talk to a few involved people here and codehaus and with the OpenJPA PMC and got a big +1 from every one of them so far. So this will most likely be the last release on codehaus but for sure not the last of this plugin! This development of this plugin _will_ be continued, the question is only if it isn't better to continue the development more closely bound to the OpenJPA core project. I will call a [DISCUSS] or [VOTE] for the move on this list shortly. txs and LieGrue, strub --- On Thu, 12/2/10, Jesse Farinacci <[email protected]> wrote: > From: Jesse Farinacci <[email protected]> > Subject: Re: [mojo-dev] [VOTE] release openjpa-maven-plugin 1.2 > To: [email protected] > Date: Thursday, December 2, 2010, 1:19 PM > Greetings, > > On Mon, Nov 29, 2010 at 12:36 PM, Mark Struberg <[email protected]> > wrote: > > > > I'd like to release the > > openjpa-maven-plugin-1.2 > > Is this part of some level set prior to handing the plugin > over to > Apache OpenJPA? I've come to depend on the openjpa-m-p and > at least > one thing that is vital for my organization has been closed > as WONT > FIX. Thanks! > > -Jesse > > -- > There are 10 types of people in this world, those > that can read binary and those that can not. > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
