[
https://issues.apache.org/jira/browse/JDO-621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654184#action_12654184
]
Andy Jefferson commented on JDO-621:
------------------------------------
Whether it is called "Enhancer" or JDOEnhancerMain I really don't care since a
user will invoke via a plugin or Ant task etc.
All options should have shortform and longform, so "-pu" and "-persistenceUnit"
should be valid (just as "-v"/"-verbose" will be)
> Also, javax.jdo.Enhancer should send all the arguments, including unknown
> arguments to the implementation.
How is it to do that ? The JDOEnhancerMain/Enhancer will be looking for an
implementation of JDOEnhancer in the classpath via the services registry. When
it finds one it creates an instance and makes use of the JDOEnhancer API. This
API defines what features are supported.
> 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.
