[ https://issues.apache.org/jira/browse/JDO-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Craig Russell updated JDO-591: ------------------------------ Component/s: (was: tck2-legacy) (was: api2-legacy) (was: specification) (was: tck2) Fix Version/s: (was: JDO 2 maintenance release 2) JDO 2 maintenance release 3 Moving this to 2.3; awaiting a volunteer to take it. > Enhancer Invocation API > ----------------------- > > Key: JDO-591 > URL: https://issues.apache.org/jira/browse/JDO-591 > Project: JDO > Issue Type: New Feature > Components: api2 > Reporter: Andy Jefferson > Fix For: JDO 2 maintenance release 3 > > > Having a standard interface to invoke the enhancer makes a lot of sense so we > can have interchangeability of enhancers (for implementations that support > BinaryCompatibility). > A start point (for discussions) could be > java -cp classpath {enhancer-class} [options] [jdo-files] [class-files] > where options can be > -persistenceUnit persistence-unit-name : Name of a "persistence-unit" > to enhance the classes for > -d target-dir-name : Write the enhanced classes to the specified > directory > -checkonly : Just check the classes for enhancement status > -v : verbose output > This then allows enhancement of the specified classes, or the classes defined > by the specified JDO files, or the classes defined by the specified > persistence-unit. > What other control would people like to see ? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.