[
http://issues.apache.org/jira/browse/JDO-264?page=comments#action_12361073 ]
Michael Bouschen commented on JDO-264:
--------------------------------------
0. I hope we find a way that the user does not need to change maven.xml at all
when running the TCK with an iut. I hope adapting the project.properties is all
he needs to do.
4. I agree with calling it iut.enhancer.classpath. So how about the other
classpath names? Should they become iut.classpath, jdori.classpath and
jdori.enhancer.classpath? I hope we can rename project.class.path to
iut.classpath, since I'm not sure whether project.class.path in some of the
standard goal we are using. But it's worth trying.
Since are are chaning the mavel.xml anyway: the definition of
project.class.path includes two lines
<pathelement
location="${jdo.tck.enhanced.dir}/${jdo.tck.identitytype}/${jdo.tck.identitytype}.jar"/>
<pathelement location="${jdo.tck.enhanced.dir}/${jdo.tck.identitytype}"/>
I think the first line should be:
<pathelement location="${jdo.tck.enhanced.dir}/${jdo.tck.identitytype}.jar"/>
and the second line should be removed.
> 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
