[
https://issues.apache.org/jira/browse/JDO-621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Craig Russell updated JDO-621:
------------------------------
Attachment: jdo-621.patch
Please review this patch. It is for the api2 project as well as the tck2
project.
The changes since the last patch:
1. The JDOEnhancerTest uses the basedir (maven) system property instead of
<current-directory> to allow running the api2 build/test from either the api2
directory or the trunk (branch) directory.
2. Updates the tck2 signature file to incorporate the changes to Constants.java.
3. Updates the tck2 project.properties file to use the standard
javax.jdo.Enhancer to enhance the tck model classes.
I've run the tck in both ri and tck mode with these changes.
> 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
> Assignee: Craig Russell
> Fix For: JDO 2 maintenance release 3
>
> Attachments: jdo-621.patch
>
>
> 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.
