db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Bouschen (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JDO-647) Run TCK using Maven2 for consistency
Date Sun, 29 Jan 2012 17:07:10 GMT

    [ https://issues.apache.org/jira/browse/JDO-647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13195794#comment-13195794

Michael Bouschen commented on JDO-647:

Thanks Andy for resolving the logging issue!

The patch looks good. 
Just one issue: the patch works when running the tck from the directory tck. But when running
the tck from the trunk directory (e.g. calling mvn clean nstall in trunk), it fails to find
the datanucleus.txt file. I think this can be fixed by changig the default-value of the implLogFile
instance variable from ${basedir}/datanucleus.txt  to ${user.dir}/datanucleus.txt:

     * Location of implementation log file.
     * @parameter expression="${jdo.tck.impl.logfile}"
     *      default-value="${user.dir}/datanucleus.txt"
     * @required
    private String implLogFile;
> Run TCK using Maven2 for consistency
> ------------------------------------
>                 Key: JDO-647
>                 URL: https://issues.apache.org/jira/browse/JDO-647
>             Project: JDO
>          Issue Type: Improvement
>          Components: tck
>    Affects Versions: JDO 3 (3.0)
>            Reporter: Andy Jefferson
>            Assignee: Michelle Caisse
>             Fix For: JDO 3 maintenance release 1 (3.1)
>         Attachments: JDO-647-default-cfgList.patch, JDO-647-impl-log.patch, JDO-647-pom-properties.zip,
JDO-647-rootPomChanges.patch, RunRules.patch, api_pom.diff, exectck.zip, exectck.zip, pom.xml,
> Since api2 now builds using Maven2 it makes a heck of a lot of sense to build/run the
TCK using that too. It also means that the DataNucleus M1 repo (which only exists for use
of this TCK) can be deleted. Please consider upgrading to Maven2

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message