If these are the requirements (release independent of OpenJPA releases), then the code should not go into openjpa/trunk but should go into openjpa/devtools/ as a separate subproject, like the Eclipse plugin.
For now, I've added a openjpa-tools/pom.xml which will allow you to build a jar based on trunk, until we decide where this code will end up. -Donald On 7/26/10 3:41 PM, Pinaki Poddar wrote: > > Here is a *suggested requirement* list : > > 1.1: The tools should be available in a separate openjpa-tools.jar. > Because at this stage openjpa-tools.jar should evolve faster than openjpa > releases. > > 1.2: The openjpa-tools.jar should be separate download from the usual > download page. > > 1.3: The tools documentation should be separate from openjpa documents. > > 1.4: The docs can be packaged in the openjpa-tools.zip. > > > All these requirements has "at this stage" flavor. These choices will evolve > with the progress of this exercise. > > Thoughts? > > > > > > ----- > Pinaki
