db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig Russell (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JDO-279) Release tck20 as source with a binary dependency on other projects
Date Sun, 15 Jan 2006 23:51:20 GMT
    [ http://issues.apache.org/jira/browse/JDO-279?page=comments#action_12362798 ] 

Craig Russell commented on JDO-279:

This looks good. A few items we need to resolve.

1. We want to continue development on the projects but want to cut a release. What incantations
do we need to make to do this? The version in maven identifies dependencies which is fine,
but how do we actually build the 2.0-beta version to put into the local directory?

2. Slight changes will be needed if we adopt the groupId change for the api jar to be javax.jdo
instead of org.apache.jdo.

3. I think it's good that the distributed tck20 can run both the RI and the IUT with different
maven goals. The first thing the user will want to do is to run the RI and make sure it works.
Then they can install the IUT, modify their properties etc. and try to run it.

4. The version number for "beta" in the attached files should include the release number,
e.g. "2.0-beta". 

> Release tck20 as source with a binary dependency on other projects
> ------------------------------------------------------------------
>          Key: JDO-279
>          URL: http://issues.apache.org/jira/browse/JDO-279
>      Project: JDO
>         Type: Improvement
>   Components: tck20
>     Reporter: Craig Russell
>      Fix For: JDO 2 beta
>  Attachments: distrib.patch
> This proposal would repackage tck20 as a project that has no dependencies on the super-project
(../project.xml). It would continue to have binary dependencies on several of the other projects.
> This allows us to distribute the tck20 including sources to allow users to run the tck
without having to use the svn workspace. The sources are needed in order to debug the implementation
under test.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message