Attendees: Michael Bouschen, Michael Watzek, Michelle Caisse, Matthew
Adams, Martin Zaun, Craig Russell, Erik Bengtson, and Geoff Hendry.
Our regular meeting was held Friday, May 13 at 9 am PST to discuss JDO
TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International:
The ideal thing would be if commenting out a test in
JDOTCKTestCases had the expected behavior. I figured
that allTests.list was there for the purpose of
cresating summary stats, so it could tell you that 10
tests were excluded or something like that. But I
noticed that all the tests I commented
Hi Geoff,
are you planning the join the conference call tomorrow? I am interested
to learn about how to put things into a maven repo such that it can be
used as a dependency for a maven project. It would be nice if we could
define this as a binary dependency in case you are not interested to
The dependency on CVS is bad. I use subversion, and
had to go off and download 2 different CVS clients,
and both failed when maven tried to call them. I had
to grab the code through winCVS, and wound up updating
fromn the head instead of the proper tag.
All this would go away if you would simply
1. XML Schema (Brian T - specifics on orm dtd issues, Craig - dtd issues
fixed?)
Craig checked in changes to the jdo.dtd and orm.dtd.
AI: Michelle will try the changes.
Works, at least whatever is in the latest JPOX build works. (The issue
was the foreign-key attribute of the field element.)
This is now JDO-51, assigned to me.
-- Michelle
Michael Bouschen wrote:
Hi Michelle,
yes, we need to describe the dependencies in the README.txt. I propose
the following build order:
JDO1: api11, btree, ri11, tck11
JDO2: api20, tck20
Another alternative is using the multiproject support of
Hi, Geoff,
I'm not really sure of the purpose of JDOTCKTestCases.list. I hope
Michael can explain this. In fact if you run the runtck or runtck.jdori
targets, they read allTests.list. When I want to run a shorter set, I
keep a copy of allTests.list and delete entries to run only the set that
OK, so am am able to run the tck11 against JDOMax.
There are two files in test/conf that seem to
enumerate the test cases: allTests.list and
JDOTCKTestCases.list.
Why 2 files?
What is the recommended way to have an exclude list
(JavaTest parlance). I'm assuming I just comment the
tests out in
Hi Craig, hi Geoff,
I'm not sure whether you need to explicitly login into the cvs
repository at netbeans. After removing the corresponding entry from my
.cvspass file I was able to check out the sources by doing a maven build
in the btree directory. However, trying a cvs login as Craig
Hi Geoff,
we do not use the latest btree sources, because they require JDK1.4 and
have some external dependencies (as you figured out). Please have a look
at project.properties in the btree directory. Ir defines a cvs tag we
use when checking out the files from the netbeans repository:
Hi Michelle,
yes, we need to describe the dependencies in the README.txt. I propose
the following build order:
JDO1: api11, btree, ri11, tck11
JDO2: api20, tck20
Another alternative is using the multiproject support of maven. You can
call 'maven -Dgoal=build multiproject:goal' in the directory
Never mind my question about the assertions. Now this:
java:compile:
[echo] Compiling to
E:\apachetck\trunk\btree/target/classes
[javac] Compiling 55 source files to
E:\apachetck\trunk\btree\target\classes
E:\apachetck\trunk\btree\mdr\src\org\netbeans\mdr\persistence\btreeimpl\btreeind
The CVS checkout was failing in the maven btree build
target. Apparently I also failed to manually checkout
the btree/impl package when I tried to do so manually
with CVS.
Because I was able to succesfully checkout the
persistence parent package of impl, I concluded that
the repo was messed up
I'm trying to run the tck11 enhance goal.
There is a dependency on jdo-btree-SNAPSHOT.
When I try to execute the three CVS commands to get
the code, I succesfully get
org\netbeans\mdr\persistence package, but the
btreeimpl subpackage appears to not exist. If I create
the btreeimpl subpackage by
Hi, Geoff,
All you need to do is check out the jdo project and build the
subprojects in the correct order. You will get six subprojects from the
jdo subversion repository:
api11
api20
btree
ri11
tck11
tck20
To get the btree jar in your local repository with the appropriate name
you just do
15 matches
Mail list logo
