[ http://issues.apache.org/jira/browse/JDO-279?page=all ]
Michael Bouschen updated JDO-279:
---------------------------------
Attachment: distrib.patch
I propose to add a new directory called distrib to the tck20 project. It
includes slightly adapted versions of project.xml, project.properties and
maven.xml where any depedencies to the super projrect are removed. These files
will refer to beta or fcs version of the jdo2-api and jpox project instead of
a SNAPSHOT version.
The attached path distrib.patch adds the distrib directory with the three files
mentioned above. It also adds a new goal distrib to the maven.xml in tck20. The
distrib goal creates a jar called jdo2-tck-beta-distrib.jar in the distrib
directory. It includes all the sources (from subdirectories conf, java, jdo,
orm, sql and testdata) plus the maven config files project.xml,
project.properties and maven.xml from the distrib directory.
Please note, the patch distrib.patch is not a complete solution for the issue,
it is meant to stimulate the discussion. We might want to consider splitting
the goals from maven.xml such that all the jdori goals stay in the tck20
version where the iut goals go into the distrib version.
The config files under distrib already use the new groupId org.apache.jdo. So
if you test them you need to manually adapt your local maven repository. You
also need to copy the jndi files fscontext.jar and providerutil.jar to the
lib/ext directory after unpackaing the distribution. Another change is that the
build rule in the distrib version of maven.xml does not automatically run the
jdori.
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
