Yup, I agree. Did this separate subproject require approval from Apache Board?
Donald Woods wrote: > > For Geronimo, we also setup a Devtools subproject for our Eclipse > plugins. I would suggest doing that for OpenJPA, as the maven builds > are different enough that you don't want non-Eclipse users to deal with > the delays of downloading an Eclipse runtime for the build steps. Also, > you may want to release the tooling more or less often than a given > branch(es) or support different levels of Eclipse with different > versions of the plugins. > > > -Donald > > > Kevin Sutter wrote: >> Hi Pinaki, >> Thanks for starting this activity. I've noticed that OpenEJB has a >> separate >> project for the OpenEJB Eclipse Plugin. Maybe we should consider >> following >> the same path? Not sure if it's a lot of overhead to have a separate >> project like that or not. >> >> Thoughts? >> Kevin >> >> On Mon, Feb 23, 2009 at 9:55 AM, Pinaki Poddar <[email protected]> >> wrote: >> >>> Hi, >>> For Eclipse IDE users, a plugin is available to help development with >>> OpenJPA [1]. It adds a builder step to Java projects in Eclipse >>> workspace >>> so >>> that all your persistent classes are bytecode enhanced as part of the >>> Eclipse's incremental compilation process. >>> Please note that, at this point, this plugin is in very early stage of >>> development and is not part of official OpenJPA release or maintenance. >>> >>> [1] >>> http://people.apache.org/~ppoddar/eclipse/index.html<http://people.apache.org/%7Eppoddar/eclipse/index.html> >>> >>> Regards -- >>> >>> Pinaki >>> -- >>> View this message in context: >>> http://n2.nabble.com/Eclipse-Plugin-for-OpenJPA-tp2372730p2372730.html >>> Sent from the OpenJPA Users mailing list archive at Nabble.com. >>> >>> >> > > -- View this message in context: http://n2.nabble.com/Eclipse-Plugin-for-OpenJPA-tp2372730p2373995.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
