[ https://issues.apache.org/jira/browse/JDO-621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654182#action_12654182 ]
Ilan Kirsh commented on JDO-621: -------------------------------- Following is the current ObjectDB Enhancer usage: Usage: java com.objectdb.Enhancer [ <options> | <class> | <filename> ] ... <class> - name of a class (without .class suffix) in the CLASSPATH <filename> - path to class or jar file(s), *? wildcards supported <options> include: -cp <dir> : path to input user classes -pu <name> : persistence unit name -s : include sub directories in search -d <dir> : output path for enhanced classes It would be nice to support wlidcards and subdirectories search: > java javax.jdo.Enhancer -s *.class Also, javax.jdo.Enhancer should send all the arguments, including unknown arguments to the implementation. > Add javax.jdo.JDOEnhancerMain to call the enhancer via standard API > ------------------------------------------------------------------- > > Key: JDO-621 > URL: https://issues.apache.org/jira/browse/JDO-621 > Project: JDO > Issue Type: New Feature > Components: api2 > Affects Versions: JDO 2 maintenance release 2 > Reporter: Craig Russell > Fix For: JDO 2 maintenance release 3 > > > The proposed new class will use the standard enhancer API to enhance classes. > The command line parameters would be similar to the original proposal of > JDO-591, with changes as needed to use the new class in the TCK. > 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 message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.