+1 If the tooling isn't tied to a particular release of OpenJPA, I too think it should be moved into devtools.
-Jeremy On Mon, Jul 26, 2010 at 4:07 PM, Michael Dick <[email protected]>wrote: > Agree. If tools has it's own release cycle it makes sense to move it out of > trunk (if we change the release cycle decision I'd reconsider). > > Any objections to moving the code? > > -mike > > On Mon, Jul 26, 2010 at 4:00 PM, Donald Woods <[email protected]> wrote: > > > Ture, so even more the point of needing to move it out of trunk... > > Also, would be great to integrate such a "migration" tool into the > > Eclipse plugin, for an easier to use GUI approach... :-) > > > > -Donald > > > > > > On 7/26/10 4:43 PM, Pinaki Poddar wrote: > > > > > > Independency of OpenJPA at this point is deliberate. > > > Need more time to understand common operational environment for the > toll > > to > > > make such judgment. > > > For example, why some one trying to convert a classic Hibernate mapping > > > descriptor file *.hbm.xml to a JPA compliant *.orm.xml will require > > OpenJPA > > > in their execution classpath? > > > > > > > > > > > > ----- > > > Pinaki > > >
