[ http://issues.apache.org/jira/browse/JDO-264?page=all ]
Michelle Caisse updated JDO-264:
--------------------------------
Attachment: enhanceClasspath.patch
I've attached a patch for the next portion of this issue -- creating a separate
classpath for the iut enhancer and the jdori enhancer. Currently we have
properties iut.enhancer.sourcepath, iut.enhancer.classpath,
jdo.enhancer.sourcepath, and jdo.enhancer.classpath in project.properties, but
none of these are actually used in maven.xml. I see the value in setting
iut.enhancer.classpath in a properties file and adding it to the classpath in
maven.xml and this patch does that. I think that it is more readable and
convenient to set jdo.enhancer.*path in maven.xml. I don't know if users will
need to add items to iut.enhancer.sourcepath that we cannot foresee. Feedback?
> Fix issues in maven.xml preventing iut goals from running properly
> ------------------------------------------------------------------
>
> Key: JDO-264
> URL: http://issues.apache.org/jira/browse/JDO-264
> Project: JDO
> Type: Bug
> Components: tck20
> Reporter: Michelle Caisse
> Assignee: Michelle Caisse
> Attachments: enhanceClasspath.patch
>
> maven.xml has not been properly tested on an implementation under test (iut).
> Test and fix any problems encountered.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
