Hi,
just a heads up:
this commit changes the groupId of all the subprojects. The groupId
determines the directory in the maven repository for the subproject and
it used to locate any jars defined in the project dependencies.
I propose to do a 'maven tck20.build' in the trunk directory. This
Craig,
Thanks very much for your answer, that sounds very good.
Concerning the vote: As I understand you plan to make the release only
available in your home directory at apache, you do not need any approval
from the PMC for this. (You only need it if you put sumething in a
mirrored
Hi,
JUNIT encourages developers to write setUp()/tearDown() methods for test
initialization/finalization. These methods are executed for each test
method. TCK test classes follow this approach initializing the database
in setUp(), relatively deleting persistent instances in tearDown().
[ http://issues.apache.org/jira/browse/JDO-264?page=all ]
Michelle Caisse updated JDO-264:
Attachment: JDO-264.patch
This patch creates a build.properties file which contains properties that may
be modified by the iut. (See
[
http://issues.apache.org/jira/browse/JDO-264?page=comments#action_12363148 ]
Craig Russell commented on JDO-264:
---
The changes look good. I also don't know why the rename isn't shown in the diff.
Fix issues in maven.xml preventing iut goals from
[
http://issues.apache.org/jira/browse/JDO-264?page=comments#action_12363180 ]
Michelle Caisse commented on JDO-264:
-
Committed patch with revision 370285. Still open for comments.
Fix issues in maven.xml preventing iut goals from running properly
Hi Craig,
I tried calling 'maven dist' in projects api20 and tck20. It suceeded,
but some of the generated distribution files do not include the expected
files. I was able to resolve some of the issues, please see the attached
patch.
- tck20/project.properties: allow to find all tck20 sources
Thomas Fischer wrote:
Craig,
Thanks very much for your answer, that sounds very good.
Concerning the vote: As I understand you plan to make the release only
available in your home directory at apache, you do not need any approval
from the PMC for this. (You only need it if you put
Javadogs,Please review the attached RunRules. Thanks,Craig
Running the JDO 2.0 Technology Compatibility Kit
DRAFT Version 0.1
18-Jan-2006
Overview
In order to demonstrate compliance with the Java Data Objects
specification, an implementation must successfully run all of the TCK
tests that are
Hi Dan,You are right; I'll stage a release of the TCK and call for another vote once folks can see what they are voting on.Thanks,CraigOn Jan 18, 2006, at 8:29 PM, Daniel John Debrunner wrote:Thomas Fischer wrote: Craig,Thanks very much for your answer, that sounds very good.Concerning the vote:
Javadogs,I'd like to tag the JDO repository with a new branch:branches/2.0-betaand then release from there after updating the dependencies in the poms from SNAPSHOT to 2.0-beta.After tagging, any changes that are needed to the branch before release (aside from the dependency changes) will need to
11 matches
Mail list logo