You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jdo-dev@db.apache.org by Craig L Russell <Cr...@Sun.COM> on 2006/01/21 05:59:48 UTC
[VOTE] Release JDO2 beta
This is now a real vote for the release of JDO 2 beta.
Here's how to test the jdo 2.0-beta staging release.
1. Download the TCK source release from http://www.apache.org/~clr/
downloads/mirror-dist-db-jdo/2.0-beta/jdo2-tck-src-20_Jan_2006.zip.
2. Unzip the release into a directory, hereinafter called <dist>.
3. Change to the <dist> directory: cd <dist>
4. The release depends on artifacts that are only available on the
staging release area, so you need to edit the maven location from
which the artifacts are downloaded. Find the line of maven.xml in the
project.properties file with the maven.remote.repo property, and add
"http://www.apache.org/~clr/downloads/maven" to the ibiblio and jpox
urls. The JPOX releases might not be available until Sunday evening.
Interim, you can manually download the nightly SNAPSHOT build and
rename the jar file to the 1.1.0-beta-6 version.
5. Change to the jdo2-tck-2.0-beta directory. This is the working
directory for the testing of the release.
6. Open and read the RunRules.html document and perform as many of
the steps therein as you like.
7. If you run maven runtck.jdori from the jdo2-tck-2.0-beta
directory, you should expect 4 or 5 errors and 4 or 5 failures in
1152 JUnit tests.
8. If you like, you can also check out the source distributions of
the api20, core20, and enhancer20. These are also in the http://
www.apache.org/~clr/downloads/mirror-dist-db-jdo/2.0-beta/ area for
staging.
Please send feedback to jdo-dev@db.apache.org.
Thanks,
Craig
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: [VOTE] Release JDO2 beta
Posted by Andy Jefferson <an...@jpox.org>.
> This is now a real vote for the release of JDO 2 beta.
+1
--
Andy
Re: [VOTE] Release JDO2 beta
Posted by Andy Jefferson <an...@jpox.org>.
> The JPOX releases might not be available until Sunday evening.
> Interim, you can manually download the nightly SNAPSHOT build and
> rename the jar file to the 1.1.0-beta-6 version.
JPOX Core/Enhancer 1.1.0-beta-6 are now released.
You can get them from SourceForge:
http://www.sf.net/projects/jpox/
or from JPOX's Maven repo:
http://www.jpox.org/downloads/maven/
--
Andy
Re: [VOTE] Release JDO2 beta
Posted by er...@jpox.org.
+1. the TCK is running good
Quoting Craig L Russell <Cr...@Sun.COM>:
> This is now a real vote for the release of JDO 2 beta.
>
> Here's how to test the jdo 2.0-beta staging release.
>
> 1. Download the TCK source release from http://www.apache.org/~clr/
> downloads/mirror-dist-db-jdo/2.0-beta/jdo2-tck-src-20_Jan_2006.zip.
>
> 2. Unzip the release into a directory, hereinafter called <dist>.
>
> 3. Change to the <dist> directory: cd <dist>
>
> 4. The release depends on artifacts that are only available on the
> staging release area, so you need to edit the maven location from
> which the artifacts are downloaded. Find the line of maven.xml in the
> project.properties file with the maven.remote.repo property, and add
> "http://www.apache.org/~clr/downloads/maven" to the ibiblio and jpox
> urls. The JPOX releases might not be available until Sunday evening.
> Interim, you can manually download the nightly SNAPSHOT build and
> rename the jar file to the 1.1.0-beta-6 version.
>
> 5. Change to the jdo2-tck-2.0-beta directory. This is the working
> directory for the testing of the release.
>
> 6. Open and read the RunRules.html document and perform as many of
> the steps therein as you like.
>
> 7. If you run maven runtck.jdori from the jdo2-tck-2.0-beta
> directory, you should expect 4 or 5 errors and 4 or 5 failures in
> 1152 JUnit tests.
>
> 8. If you like, you can also check out the source distributions of
> the api20, core20, and enhancer20. These are also in the http://
> www.apache.org/~clr/downloads/mirror-dist-db-jdo/2.0-beta/ area for
> staging.
>
> Please send feedback to jdo-dev@db.apache.org.
>
> Thanks,
>
> Craig
>
> Craig Russell
> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
> 408 276-5638 mailto:Craig.Russell@sun.com
> P.S. A good JDO? O, Gasp!
>
>
Re: [VOTE] Release JDO2 beta
Posted by Michael Watzek <mw...@spree.de>.
+1.
Total tests run: 1154. Failures: 4, Errors: 4.
4 of 48 configurations failed.
Regards,
Michael
Craig L Russell wrote:
> The release looks good from my testing.
>
> +1 to release.
>
> Everyone else, please vote before Friday morning.
>
> Thanks,
>
> Craig
>
> On Jan 21, 2006, at 11:41 AM, Craig L Russell wrote:
>
>> Oops, the URL below is wrong. It should be
>> http://www.apache.org/~clr/downloads/mirror-dist-db-jdo/2.0-beta/jdo2-tck-2.0-beta-src-24_Jan_2006.zip.
>> Sorry for the inconvenience.
>>
>> Craig
>>
>> On Jan 20, 2006, at 8:59 PM, Craig L Russell wrote:
>>
>>> This is now a real vote for the release of JDO 2 beta.
>>>
>>> Here's how to test the jdo 2.0-beta staging release.
>>>
>>> 1. Download the TCK source release from <above link>
>>>
>>> 2. Unzip the release into a directory, hereinafter called <dist>.
>>>
>>> 3. Change to the <dist> directory: cd <dist>
>>>
>>> 4. The release depends on artifacts that are only available on the
>>> staging release area, so you need to edit the maven location from
>>> which the artifacts are downloaded. Find the line of maven.xml in the
>>> project.properties file with the maven.remote.repo property, and add
>>> "http://people.apache.org/~clr/downloads/maven" to the ibiblio and
>>> jpox urls. The JPOX releases might not be available until Sunday
>>> evening. Interim, you can manually download the nightly SNAPSHOT
>>> build and rename the jar file to the 1.1.0-beta-6 version.
>>>
>>> 5. Change to the jdo2-tck-2.0-beta directory. This is the working
>>> directory for the testing of the release.
>>>
>>> 6. Open and read the RunRules.html document and perform as many of
>>> the steps therein as you like.
>>>
>>> 7. If you run maven runtck.jdori from the jdo2-tck-2.0-beta
>>> directory, you should expect 4 or 5 errors and 4 or 5 failures in
>>> 1152 JUnit tests.
>>>
>>> 8. If you like, you can also check out the source distributions of
>>> the api20, core20, and enhancer20. These are also in the
>>> http://www.apache.org/~clr/downloads/mirror-dist-db-jdo/2.0-beta/
>>> area for staging.
>>>
>>> Please send feedback to jdo-dev@db.apache.org
>>> <ma...@db.apache.org>.
>>>
>>> Thanks,
>>>
>>> Craig
>>>
>>> Craig Russell
>>> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
>>> 408 276-5638 mailto:Craig.Russell@sun.com
>>> P.S. A good JDO? O, Gasp!
>>>
>>
>> Craig Russell
>> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
>> 408 276-5638 mailto:Craig.Russell@sun.com
>> P.S. A good JDO? O, Gasp!
>>
>
> Craig Russell
>
> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
>
> 408 276-5638 mailto:Craig.Russell@sun.com
>
> P.S. A good JDO? O, Gasp!
>
>
--
-------------------------------------------------------------------
Michael Watzek Tech@Spree Engineering GmbH
mailto:mwa.tech@spree.de Buelowstr. 66
Tel.: ++49/30/235 520 36 10783 Berlin - Germany
Fax.: ++49/30/217 520 12 http://www.spree.de/
-------------------------------------------------------------------
Re: [VOTE] Release JDO2 beta
Posted by Craig L Russell <Cr...@Sun.COM>.
The release looks good from my testing.
+1 to release.
Everyone else, please vote before Friday morning.
Thanks,
Craig
On Jan 21, 2006, at 11:41 AM, Craig L Russell wrote:
> Oops, the URL below is wrong. It should be
> http://www.apache.org/~clr/downloads/mirror-dist-db-jdo/2.0-beta/
> jdo2-tck-2.0-beta-src-24_Jan_2006.zip.
> Sorry for the inconvenience.
>
> Craig
>
> On Jan 20, 2006, at 8:59 PM, Craig L Russell wrote:
>
>> This is now a real vote for the release of JDO 2 beta.
>>
>> Here's how to test the jdo 2.0-beta staging release.
>>
>> 1. Download the TCK source release from <above link>
>>
>> 2. Unzip the release into a directory, hereinafter called <dist>.
>>
>> 3. Change to the <dist> directory: cd <dist>
>>
>> 4. The release depends on artifacts that are only available on the
>> staging release area, so you need to edit the maven location from
>> which the artifacts are downloaded. Find the line of maven.xml in
>> the project.properties file with the maven.remote.repo property,
>> and add "http://people.apache.org/~clr/downloads/maven" to the
>> ibiblio and jpox urls. The JPOX releases might not be available
>> until Sunday evening. Interim, you can manually download the
>> nightly SNAPSHOT build and rename the jar file to the 1.1.0-beta-6
>> version.
>>
>> 5. Change to the jdo2-tck-2.0-beta directory. This is the working
>> directory for the testing of the release.
>>
>> 6. Open and read the RunRules.html document and perform as many of
>> the steps therein as you like.
>>
>> 7. If you run maven runtck.jdori from the jdo2-tck-2.0-beta
>> directory, you should expect 4 or 5 errors and 4 or 5 failures in
>> 1152 JUnit tests.
>>
>> 8. If you like, you can also check out the source distributions of
>> the api20, core20, and enhancer20. These are also in the http://
>> www.apache.org/~clr/downloads/mirror-dist-db-jdo/2.0-beta/ area
>> for staging.
>>
>> Please send feedback to jdo-dev@db.apache.org.
>>
>> Thanks,
>>
>> Craig
>>
>> Craig Russell
>> Architect, Sun Java Enterprise System http://java.sun.com/products/
>> jdo
>> 408 276-5638 mailto:Craig.Russell@sun.com
>> P.S. A good JDO? O, Gasp!
>>
>
> Craig Russell
> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
> 408 276-5638 mailto:Craig.Russell@sun.com
> P.S. A good JDO? O, Gasp!
>
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: [VOTE] Release JDO2 beta
Posted by Craig L Russell <Cr...@Sun.COM>.
Just for clarity:
This vote is to release the JDO 2 beta that consists of:
JDO 2.0 beta API jar and source (javax.jdo package)
JDO 2.0 beta core jar and source (org.apache.jdo package)
JDO 2.0 beta enhancer jar and source (org.apache.jdo package)
JDO 2.0 beta TCK source (org.apache.jdo package)
These artifacts are considered unstable and beta quality level.
The jar and source artifacts will be published on Apache internal web
sites and pushed to ibiblio and mirror sites.
Craig
On Jan 21, 2006, at 12:08 PM, Craig L Russell wrote:
> Oops again. The text of the URL is correct but the underlying URL
> is wrong. Try this: http://www.apache.org/~clr/downloads/mirror-
> dist-db-jdo/2.0-beta/jdo2-tck-2.0-beta-src-20_Jan_2006.zip
>
> Or just start from the top and navigate through the links.
>
> Craig
>
> On Jan 21, 2006, at 11:41 AM, Craig L Russell wrote:
>
>> Oops, the URL below is wrong. It should be wrong URL (see above)
>>
>> Sorry for the inconvenience.
>>
>> Craig
>>
>> On Jan 20, 2006, at 8:59 PM, Craig L Russell wrote:
>>
>>> This is now a real vote for the release of JDO 2 beta.
>>>
>>> Here's how to test the jdo 2.0-beta staging release.
>>>
>>> 1. Download the TCK source release from wrong URL (see above)
>>>
>>> 2. Unzip the release into a directory, hereinafter called <dist>.
>>>
>>> 3. Change to the <dist> directory: cd <dist>
>>>
>>> 4. The release depends on artifacts that are only available on
>>> the staging release area, so you need to edit the maven location
>>> from which the artifacts are downloaded. Find the line in the
>>> project.properties file with the maven.remote.repo property, and
>>> add "http://www.apache.org/~clr/downloads/maven" to the ibiblio
>>> and jpox urls. [This might not work in your environment. ]The
>>> JPOX releases might not be available until Sunday evening.
>>> Interim, you can manually download the nightly SNAPSHOT build and
>>> rename the jar file to the 1.1.0-beta-6 version and put it into
>>> your local repository.
>>>
>>> 5. Change to the jdo2-tck-2.0-beta directory. This is the working
>>> directory for the testing of the release.
>>>
>>> 6. Open and read the RunRules.html document and perform as many
>>> of the steps therein as you like.
>>>
>>> 7. If you run maven runtck.jdori from the jdo2-tck-2.0-beta
>>> directory, you should expect 4 or 5 errors and 4 or 5 failures in
>>> 1154 JUnit tests.
>>>
>>> 8. If you like, you can also check out the source distributions
>>> of the api20, core20, and enhancer20. These are also in the
>>> http://www.apache.org/~clr/downloads/mirror-dist-db-jdo/2.0-beta/
>>> area for staging.
>>>
>>> Please send feedback to jdo-dev@db.apache.org.
>>>
>>> Thanks,
>>>
>>> Craig
>>>
>>> Craig Russell
>>> Architect, Sun Java Enterprise System http://java.sun.com/
>>> products/jdo
>>> 408 276-5638 mailto:Craig.Russell@sun.com
>>> P.S. A good JDO? O, Gasp!
>>>
>>
>> Craig Russell
>> Architect, Sun Java Enterprise System http://java.sun.com/products/
>> jdo
>> 408 276-5638 mailto:Craig.Russell@sun.com
>> P.S. A good JDO? O, Gasp!
>>
>
> Craig Russell
> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
> 408 276-5638 mailto:Craig.Russell@sun.com
> P.S. A good JDO? O, Gasp!
>
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: [VOTE] Release JDO2 beta
Posted by Craig L Russell <Cr...@Sun.COM>.
Oops again. The text of the URL is correct but the underlying URL is
wrong. Try this: http://www.apache.org/~clr/downloads/mirror-dist-db-
jdo/2.0-beta/jdo2-tck-2.0-beta-src-20_Jan_2006.zip
Or just start from the top and navigate through the links.
Craig
On Jan 21, 2006, at 11:41 AM, Craig L Russell wrote:
> Oops, the URL below is wrong. It should be http://www.apache.org/
> ~clr/downloads/mirror-dist-db-jdo/2.0-beta/jdo2-tck-2.0-beta-
> src-20_Jan_2006.zip.
>
> Sorry for the inconvenience.
>
> Craig
>
> On Jan 20, 2006, at 8:59 PM, Craig L Russell wrote:
>
>> This is now a real vote for the release of JDO 2 beta.
>>
>> Here's how to test the jdo 2.0-beta staging release.
>>
>> 1. Download the TCK source release from http://www.apache.org/~clr/
>> downloads/mirror-dist-db-jdo/2.0-beta/jdo2-tck-src-20_Jan_2006.zip.
>>
>> 2. Unzip the release into a directory, hereinafter called <dist>.
>>
>> 3. Change to the <dist> directory: cd <dist>
>>
>> 4. The release depends on artifacts that are only available on the
>> staging release area, so you need to edit the maven location from
>> which the artifacts are downloaded. Find the line of maven.xml in
>> the project.properties file with the maven.remote.repo property,
>> and add "http://www.apache.org/~clr/downloads/maven" to the
>> ibiblio and jpox urls. The JPOX releases might not be available
>> until Sunday evening. Interim, you can manually download the
>> nightly SNAPSHOT build and rename the jar file to the 1.1.0-beta-6
>> version.
>>
>> 5. Change to the jdo2-tck-2.0-beta directory. This is the working
>> directory for the testing of the release.
>>
>> 6. Open and read the RunRules.html document and perform as many of
>> the steps therein as you like.
>>
>> 7. If you run maven runtck.jdori from the jdo2-tck-2.0-beta
>> directory, you should expect 4 or 5 errors and 4 or 5 failures in
>> 1152 JUnit tests.
>>
>> 8. If you like, you can also check out the source distributions of
>> the api20, core20, and enhancer20. These are also in the http://
>> www.apache.org/~clr/downloads/mirror-dist-db-jdo/2.0-beta/ area
>> for staging.
>>
>> Please send feedback to jdo-dev@db.apache.org.
>>
>> Thanks,
>>
>> Craig
>>
>> Craig Russell
>> Architect, Sun Java Enterprise System http://java.sun.com/products/
>> jdo
>> 408 276-5638 mailto:Craig.Russell@sun.com
>> P.S. A good JDO? O, Gasp!
>>
>
> Craig Russell
> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
> 408 276-5638 mailto:Craig.Russell@sun.com
> P.S. A good JDO? O, Gasp!
>
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: [VOTE] Release JDO2 beta
Posted by Craig L Russell <Cr...@Sun.COM>.
I agree with Michael and Michelle that the proposed JDO2 beta bits
are fatally flawed and need to be respun.
We need to fix the missing build.properties and fix the RunRules.html
in order to have people test the IUT. Without these fixes there can
be minimum testing of the tck functionality.
I'll post a new version as soon as I can get onto a public network.
Craig
On Jan 23, 2006, at 10:46 AM, Michael Bouschen wrote:
> Hi Michelle,
>
>> Hi Michael,
>>
>> Comments below...
>>
>> Michael Bouschen wrote:
>>
>>> Hi Michelle,
>>>
>>>> Hi Craig,
>>>>
>>>> I have the same problem as Michael has with the maven automatic
>>>> download of the jdo beta jars. I will try manually downloading
>>>> them. Also, a comment on RunRules.html:
>>>>
>>>>> From the installation directory, call maven tck20.build which
>>>>> will build the jar files used in the tests, create the Derby
>>>>> database, install the schema into the Derby database, and run
>>>>> the TCK on the Reference Implementation.
>>>>>
>>>>> From the installation directory, change to the tck20 directory.
>>>>> Then call maven runtck.iut
>>>>
>>>>
>>>>
>>>>
>>>> I think these directions were appropriate for a source
>>>> distribution of the product. Now I believe it should say to
>>>> call maven build, then (from the same directory) call maven
>>>> runtck.iut.
>>>
>>>
>>>
>>> Good point!
>>>
>>> The instructions above say to call maven tck20.build from
>>> installation directory. This calls maven build in the tck20
>>> directory, but before it calls maven build in api20, core20 and
>>> enhancer20. So these directories need to be in place for maven
>>> tck20.build to succeed.
>>>
>>> I agree it should say to do a maven build in the tck20 directory.
>>>
>>> Regards Michael
>>>
>> What tck20 directory? I don't see that the old tck20, api20, ...
>> directories exist in this distribution at all. After unzipping,
>> there is the root dir with README.txt and jdo-tck-2.0-beta. jdo-
>> tck-2.0-beta is the equivalent to the source tck20 directory and
>> contains the project files, src directory, and after maven build,
>> target and iut_jars directories. Or maybe you just meant to say
>> it should say to do a maven build in the jdo-tck-2.0-beta directory?
>
> Oops, you are right this is what I meant to say.
>
> Regards Michael
>
>>
>>
>> -- Michelle
>
>
>
> --
> Michael Bouschen Tech@Spree Engineering GmbH
> mailto:mbo.tech@spree.de http://www.tech.spree.de/
> Tel.:++49/30/235 520-33 Buelowstr. 66
> Fax.:++49/30/2175 2012 D-10783 Berlin
>
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: [VOTE] Release JDO2 beta
Posted by Michael Bouschen <mb...@spree.de>.
Hi Michelle,
> Hi Michael,
>
> Comments below...
>
> Michael Bouschen wrote:
>
>> Hi Michelle,
>>
>>> Hi Craig,
>>>
>>> I have the same problem as Michael has with the maven automatic
>>> download of the jdo beta jars. I will try manually downloading
>>> them. Also, a comment on RunRules.html:
>>>
>>>> From the installation directory, call maven tck20.build which will
>>>> build the jar files used in the tests, create the Derby database,
>>>> install the schema into the Derby database, and run the TCK on the
>>>> Reference Implementation.
>>>>
>>>> From the installation directory, change to the tck20 directory.
>>>> Then call maven runtck.iut
>>>
>>>
>>>
>>>
>>> I think these directions were appropriate for a source distribution
>>> of the product. Now I believe it should say to call maven build,
>>> then (from the same directory) call maven runtck.iut.
>>
>>
>>
>> Good point!
>>
>> The instructions above say to call maven tck20.build from
>> installation directory. This calls maven build in the tck20
>> directory, but before it calls maven build in api20, core20 and
>> enhancer20. So these directories need to be in place for maven
>> tck20.build to succeed.
>>
>> I agree it should say to do a maven build in the tck20 directory.
>>
>> Regards Michael
>>
> What tck20 directory? I don't see that the old tck20, api20, ...
> directories exist in this distribution at all. After unzipping, there
> is the root dir with README.txt and jdo-tck-2.0-beta. jdo-tck-2.0-beta
> is the equivalent to the source tck20 directory and contains the
> project files, src directory, and after maven build, target and
> iut_jars directories. Or maybe you just meant to say it should say to
> do a maven build in the jdo-tck-2.0-beta directory?
Oops, you are right this is what I meant to say.
Regards Michael
>
>
> -- Michelle
--
Michael Bouschen Tech@Spree Engineering GmbH
mailto:mbo.tech@spree.de http://www.tech.spree.de/
Tel.:++49/30/235 520-33 Buelowstr. 66
Fax.:++49/30/2175 2012 D-10783 Berlin
Re: [VOTE] Release JDO2 beta
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi Michael,
Comments below...
Michael Bouschen wrote:
> Hi Michelle,
>
>> Hi Craig,
>>
>> I have the same problem as Michael has with the maven automatic
>> download of the jdo beta jars. I will try manually downloading
>> them. Also, a comment on RunRules.html:
>>
>>> From the installation directory, call maven tck20.build which will
>>> build the jar files used in the tests, create the Derby database,
>>> install the schema into the Derby database, and run the TCK on the
>>> Reference Implementation.
>>>
>>> From the installation directory, change to the tck20 directory. Then
>>> call maven runtck.iut
>>
>>
>>
>> I think these directions were appropriate for a source distribution
>> of the product. Now I believe it should say to call maven build,
>> then (from the same directory) call maven runtck.iut.
>
>
> Good point!
>
> The instructions above say to call maven tck20.build from installation
> directory. This calls maven build in the tck20 directory, but before
> it calls maven build in api20, core20 and enhancer20. So these
> directories need to be in place for maven tck20.build to succeed.
>
> I agree it should say to do a maven build in the tck20 directory.
>
> Regards Michael
>
What tck20 directory? I don't see that the old tck20, api20, ...
directories exist in this distribution at all. After unzipping, there
is the root dir with README.txt and jdo-tck-2.0-beta. jdo-tck-2.0-beta
is the equivalent to the source tck20 directory and contains the project
files, src directory, and after maven build, target and iut_jars
directories. Or maybe you just meant to say it should say to do a maven
build in the jdo-tck-2.0-beta directory?
-- Michelle
Re: [VOTE] Release JDO2 beta
Posted by Michael Bouschen <mb...@spree.de>.
Hi Michelle,
> Hi Craig,
>
> I have the same problem as Michael has with the maven automatic download
> of the jdo beta jars. I will try manually downloading them. Also, a
> comment on RunRules.html:
>
>> From the installation directory, call maven tck20.build which will
>> build the jar files used in the tests, create the Derby database,
>> install the schema into the Derby database, and run the TCK on the
>> Reference Implementation.
>>
>> From the installation directory, change to the tck20 directory. Then
>> call maven runtck.iut
>
>
> I think these directions were appropriate for a source distribution of
> the product. Now I believe it should say to call maven build, then
> (from the same directory) call maven runtck.iut.
Good point!
The instructions above say to call maven tck20.build from installation
directory. This calls maven build in the tck20 directory, but before it
calls maven build in api20, core20 and enhancer20. So these directories
need to be in place for maven tck20.build to succeed.
I agree it should say to do a maven build in the tck20 directory.
Regards Michael
>
> -- Michelle
>
> Michael Bouschen wrote:
>
>> Hi Craig,
>>
>> +1 for the released version.
>>
>> The distribution is running good, I tested it with the SNAPSHOT
>> release of JPOX as you described below.
>> However, I'm having problems with downloading the jdo2-beta jars from
>> the maven repository, please see below ...
>>
>>> Oops, the URL below is wrong. It should be
>>> http://www.apache.org/~clr/downloads/mirror-dist-db-jdo/2.0-beta/jdo2-tck-2.0-beta-src-20_Jan_2006.zip
>>> <http://www.apache.org/%7Eclr/downloads/mirror-dist-db-jdo/2.0-beta/jdo2-tck-src-20_Jan_2006.zip>.
>>>
>>>
>>> Sorry for the inconvenience.
>>>
>>> Craig
>>>
>>> On Jan 20, 2006, at 8:59 PM, Craig L Russell wrote:
>>>
>>>> This is now a real vote for the release of JDO 2 beta.
>>>>
>>>> Here's how to test the jdo 2.0-beta staging release.
>>>>
>>>> 1. Download the TCK source release from
>>>> http://www.apache.org/~clr/downloads/mirror-dist-db-jdo/2.0-beta/jdo2-tck-src-20_Jan_2006.zip
>>>> <http://www.apache.org/%7Eclr/downloads/mirror-dist-db-jdo/2.0-beta/jdo2-tck-src-20_Jan_2006.zip>.
>>>>
>>>>
>>>> 2. Unzip the release into a directory, hereinafter called <dist>.
>>>>
>>>> 3. Change to the <dist> directory: cd <dist>
>>>>
>>>> 4. The release depends on artifacts that are only available on the
>>>> staging release area, so you need to edit the maven location from
>>>> which the artifacts are downloaded. Find the line of maven.xml in
>>>> the project.properties file with the maven.remote.repo property, and
>>>> add
>>>
>>>
>>>
>> What do you mean with maven.xml here? The project.properties in
>> jdo2-tck-2.0-beta has the property maven.remote.repo.
>>
>>>> "http://www.apache.org/~clr/downloads/maven
>>>> <http://www.apache.org/%7Eclr/downloads/maven>" to the ibiblio and
>>>> jpox urls. The JPOX releases might not be available until Sunday
>>>> evening. Interim, you can manually download the nightly SNAPSHOT
>>>> build and rename the jar file to the 1.1.0-beta-6 version.
>>>
>>>
>>>
>> I added the above to the maven.remote.repo property. But I'm having
>> problems resolving the dependencies via maven, I get the following
>> error message:
>> Attempting to download jdo2-api-2.0-beta.jar.
>> Error retrieving artifact from [
>> http://www.apache.org/~clr/downloads/maven/javax.jdo/jars/jdo2-api-2.0-beta.jar]:
>> java.
>> io.IOException: Unknown error downloading; status code was: 302
>> WARNING: Failed to download jdo2-api-2.0-beta.jar.
>>
>> However, I could download the jars manually using the above url. So I
>> really do not know why I could not download it via maven.
>>
>>>>
>>>> 5. Change to the jdo2-tck-2.0-beta directory. This is the working
>>>> directory for the testing of the release.
>>>>
>>>> 6. Open and read the RunRules.html document and perform as many of
>>>> the steps therein as you like.
>>>
>>>
>>>
>> The file RunRule.html is included twice: in the root and under
>> jdo2-tck-2.0-beta. Maybe this is a left over from merging my recent
>> 'maven dist' support changes into the workspace you used to create the
>> distribution file.
>>
>>>>
>>>> 7. If you run maven runtck.jdori from the jdo2-tck-2.0-beta
>>>> directory, you should expect 4 or 5 errors and 4 or 5 failures in
>>>> 1152 JUnit tests.
>>>
>>>
>>>
>> Yes, I got: Total tests run: 1154. Failures: 4, Errors: 4.
>>
>>>>
>>>> 8. If you like, you can also check out the source distributions of
>>>> the api20, core20, and enhancer20. These are also in the
>>>> http://www.apache.org/~clr/downloads/mirror-dist-db-jdo/2.0-beta/
>>>> <http://www.apache.org/%7Eclr/downloads/mirror-dist-db-jdo/2.0-beta/>
>>>> area for staging.
>>>
>>>
>>>
>> I realized some minor issues:
>> - The directory iut_jars is not included in the distribution, but it
>> will be created on the first run of maven from the jdo2-tck-2.0-beta
>> directory. This might be confusing, if you want to copy the iut jars
>> before running maven. Maybe we could change this and include it as an
>> empty directory. I'll take a look.
>> - We forgot to include the assertions directory into the distribution.
>> I'll take a look.
>> - The lib/ext directory is in the parent directory of jdo2-tck-beta,
>> not parallel to test as stated in the RunRules.
>>
>> Regards Michael
>>
>>>>
>>>> Please send feedback to jdo-dev@db.apache.org
>>>> <ma...@db.apache.org>.
>>>>
>>>> Thanks,
>>>>
>>>> Craig
>>>>
>>>> Craig Russell
>>>> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
>>>> 408 276-5638 mailto:Craig.Russell@sun.com
>>>> P.S. A good JDO? O, Gasp!
>>>>
>>>
>>> Craig Russell
>>>
>>> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
>>>
>>> 408 276-5638 mailto:Craig.Russell@sun.com
>>>
>>> P.S. A good JDO? O, Gasp!
>>>
>>>
>>
>>
--
Michael Bouschen Tech@Spree Engineering GmbH
mailto:mbo.tech@spree.de http://www.tech.spree.de/
Tel.:++49/30/235 520-33 Buelowstr. 66
Fax.:++49/30/2175 2012 D-10783 Berlin
Issue with commons-httpclient?
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi Maveners,
The latest Maven 1.0.2 has a problem when using these directions:
Find the line of maven.xml in the project.properties file with the
maven.remote.repo property, and add "http://www.apache.org/~clr/
downloads/maven" to the ibiblio and jpox urls.
What happens is that www.apache.org/~clr is redirected to
people.apache.org and this redirection is not resolved by the
httpclient used by Maven.
Are there any plans to update the code or the version of the jar file
used in Maven? Would you like more information or should I file a bug?
Regards,
Craig
Background:
> Regarding the problem with automatic maven download of the jdo2 jars:
> maven can download the files automatically if the URL refers to
> people.apache.org instead of www.apache.org:
> http://people.apache.org/~clr/downloads/maven
>
On Jan 23, 2006, at 3:02 AM, Andy Jefferson wrote:
>> FYI. Maven (1.0), or the associated plugin, is probably using
>> "commons-httpclient"
>> with a version that doesn't understand HTTP redirects. The same
>> broken
>> functionality has been noticed on the Maven "SourceForge" plugin
>> (when
>> SourceForge decided to add redirecting into their upload URLs).
>
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Issue with commons-httpclient?
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi Maveners,
The latest Maven 1.0.2 has a problem when using these directions:
Find the line of maven.xml in the project.properties file with the
maven.remote.repo property, and add "http://www.apache.org/~clr/
downloads/maven" to the ibiblio and jpox urls.
What happens is that www.apache.org/~clr is redirected to
people.apache.org and this redirection is not resolved by the
httpclient used by Maven.
Are there any plans to update the code or the version of the jar file
used in Maven? Would you like more information or should I file a bug?
Regards,
Craig
Background:
> Regarding the problem with automatic maven download of the jdo2 jars:
> maven can download the files automatically if the URL refers to
> people.apache.org instead of www.apache.org:
> http://people.apache.org/~clr/downloads/maven
>
On Jan 23, 2006, at 3:02 AM, Andy Jefferson wrote:
>> FYI. Maven (1.0), or the associated plugin, is probably using
>> "commons-httpclient"
>> with a version that doesn't understand HTTP redirects. The same
>> broken
>> functionality has been noticed on the Maven "SourceForge" plugin
>> (when
>> SourceForge decided to add redirecting into their upload URLs).
>
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: [VOTE] Release JDO2 beta
Posted by Andy Jefferson <an...@jpox.org>.
> FYI. Maven (1.0), or the associated plugin, is probably using "httputils"
> with a version that doesn't understand HTTP redirects. The same broken
> functionality has been noticed on the Maven "SourceForge" plugin (when
> SourceForge decided to add redirecting into their upload URLs).
That should have said "commons-httpclient" and not httputils.
--
Andy
Re: [VOTE] Release JDO2 beta
Posted by Andy Jefferson <an...@jpox.org>.
> I noticed inside a browser http://www.apache.org/~clr/downloads/maven is
> automatically redirected to people.apache.org, so it results in the
> address you described below.
FYI. Maven (1.0), or the associated plugin, is probably using "httputils" with
a version that doesn't understand HTTP redirects. The same broken
functionality has been noticed on the Maven "SourceForge" plugin (when
SourceForge decided to add redirecting into their upload URLs).
--
Andy
Re: [VOTE] Release JDO2 beta
Posted by Michael Bouschen <mb...@spree.de>.
Hi Michelle,
interesting!
I noticed inside a browser http://www.apache.org/~clr/downloads/maven is
automatically redirected to people.apache.org, so it results in the
address you described below. So can we publish the people.apache.org
address to be used with maven?
Regards Michael
> Hi,
>
> Regarding the problem with automatic maven download of the jdo2 jars:
> maven can download the files automatically if the URL refers to
> people.apache.org instead of www.apache.org:
>
> http://people.apache.org/~clr/downloads/maven
>
> Michelle Caisse wrote:
>
>> Hi Craig,
>>
>> I have the same problem as Michael has with the maven automatic
>> download of the jdo beta jars. I will try manually downloading them.
>> Also, a comment on RunRules.html:
>>
>>> From the installation directory, call maven tck20.build which will
>>> build the jar files used in the tests, create the Derby database,
>>> install the schema into the Derby database, and run the TCK on the
>>> Reference Implementation.
>>>
>>> From the installation directory, change to the tck20 directory. Then
>>> call maven runtck.iut
>>
>>
>>
>> I think these directions were appropriate for a source distribution of
>> the product. Now I believe it should say to call maven build, then
>> (from the same directory) call maven runtck.iut.
>>
>> -- Michelle
>>
>> Michael Bouschen wrote:
>>
>>>>>
>>>>>
>>>>> 4. The release depends on artifacts that are only available on the
>>>>> staging release area, so you need to edit the maven location from
>>>>> which the artifacts are downloaded. Find the line of maven.xml in
>>>>> the project.properties file with the maven.remote.repo property,
>>>>> and add
>>>>
>>>>
>>>>
>>>>
>>> What do you mean with maven.xml here? The project.properties in
>>> jdo2-tck-2.0-beta has the property maven.remote.repo.
>>
>>
> Yes. Should say Find the line in the project.properties file...
>
>>>
>>>>> "http://www.apache.org/~clr/downloads/maven
>>>>> <http://www.apache.org/%7Eclr/downloads/maven>" to the ibiblio and
>>>>> jpox urls. The JPOX releases might not be available until Sunday
>>>>> evening. Interim, you can manually download the nightly SNAPSHOT
>>>>> build and rename the jar file to the 1.1.0-beta-6 version.
>>>>
>>>>
>>>>
>>>>
>>> I added the above to the maven.remote.repo property. But I'm having
>>> problems resolving the dependencies via maven, I get the following
>>> error message:
>>> Attempting to download jdo2-api-2.0-beta.jar.
>>> Error retrieving artifact from [
>>> http://www.apache.org/~clr/downloads/maven/javax.jdo/jars/jdo2-api-2.0-beta.jar]:
>>> java.
>>> io.IOException: Unknown error downloading; status code was: 302
>>> WARNING: Failed to download jdo2-api-2.0-beta.jar.
>>>
>>> However, I could download the jars manually using the above url. So I
>>> really do not know why I could not download it via maven.
>>>
>
> -- Michelle
--
Michael Bouschen Tech@Spree Engineering GmbH
mailto:mbo.tech@spree.de http://www.tech.spree.de/
Tel.:++49/30/235 520-33 Buelowstr. 66
Fax.:++49/30/2175 2012 D-10783 Berlin
Re: [VOTE] Release JDO2 beta
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi,
Regarding the problem with automatic maven download of the jdo2 jars:
maven can download the files automatically if the URL refers to
people.apache.org instead of www.apache.org:
http://people.apache.org/~clr/downloads/maven
Michelle Caisse wrote:
> Hi Craig,
>
> I have the same problem as Michael has with the maven automatic
> download of the jdo beta jars. I will try manually downloading them.
> Also, a comment on RunRules.html:
>
>> From the installation directory, call maven tck20.build which will
>> build the jar files used in the tests, create the Derby database,
>> install the schema into the Derby database, and run the TCK on the
>> Reference Implementation.
>>
>> From the installation directory, change to the tck20 directory. Then
>> call maven runtck.iut
>
>
> I think these directions were appropriate for a source distribution of
> the product. Now I believe it should say to call maven build, then
> (from the same directory) call maven runtck.iut.
>
> -- Michelle
>
> Michael Bouschen wrote:
>
>>>>
>>>>
>>>> 4. The release depends on artifacts that are only available on the
>>>> staging release area, so you need to edit the maven location from
>>>> which the artifacts are downloaded. Find the line of maven.xml in
>>>> the project.properties file with the maven.remote.repo property,
>>>> and add
>>>
>>>
>>>
>> What do you mean with maven.xml here? The project.properties in
>> jdo2-tck-2.0-beta has the property maven.remote.repo.
>
Yes. Should say Find the line in the project.properties file...
>>
>>>> "http://www.apache.org/~clr/downloads/maven
>>>> <http://www.apache.org/%7Eclr/downloads/maven>" to the ibiblio and
>>>> jpox urls. The JPOX releases might not be available until Sunday
>>>> evening. Interim, you can manually download the nightly SNAPSHOT
>>>> build and rename the jar file to the 1.1.0-beta-6 version.
>>>
>>>
>>>
>> I added the above to the maven.remote.repo property. But I'm having
>> problems resolving the dependencies via maven, I get the following
>> error message:
>> Attempting to download jdo2-api-2.0-beta.jar.
>> Error retrieving artifact from [
>> http://www.apache.org/~clr/downloads/maven/javax.jdo/jars/jdo2-api-2.0-beta.jar]:
>> java.
>> io.IOException: Unknown error downloading; status code was: 302
>> WARNING: Failed to download jdo2-api-2.0-beta.jar.
>>
>> However, I could download the jars manually using the above url. So I
>> really do not know why I could not download it via maven.
>>
-- Michelle
Re: [VOTE] Release JDO2 beta
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi Craig,
I have the same problem as Michael has with the maven automatic download
of the jdo beta jars. I will try manually downloading them. Also, a
comment on RunRules.html:
> From the installation directory, call maven tck20.build which will
> build the jar files used in the tests, create the Derby database,
> install the schema into the Derby database, and run the TCK on the
> Reference Implementation.
>
> From the installation directory, change to the tck20 directory. Then
> call maven runtck.iut
I think these directions were appropriate for a source distribution of
the product. Now I believe it should say to call maven build, then
(from the same directory) call maven runtck.iut.
-- Michelle
Michael Bouschen wrote:
> Hi Craig,
>
> +1 for the released version.
>
> The distribution is running good, I tested it with the SNAPSHOT
> release of JPOX as you described below.
> However, I'm having problems with downloading the jdo2-beta jars from
> the maven repository, please see below ...
>
>> Oops, the URL below is wrong. It should be
>> http://www.apache.org/~clr/downloads/mirror-dist-db-jdo/2.0-beta/jdo2-tck-2.0-beta-src-20_Jan_2006.zip
>> <http://www.apache.org/%7Eclr/downloads/mirror-dist-db-jdo/2.0-beta/jdo2-tck-src-20_Jan_2006.zip>.
>>
>>
>> Sorry for the inconvenience.
>>
>> Craig
>>
>> On Jan 20, 2006, at 8:59 PM, Craig L Russell wrote:
>>
>>> This is now a real vote for the release of JDO 2 beta.
>>>
>>> Here's how to test the jdo 2.0-beta staging release.
>>>
>>> 1. Download the TCK source release from
>>> http://www.apache.org/~clr/downloads/mirror-dist-db-jdo/2.0-beta/jdo2-tck-src-20_Jan_2006.zip
>>> <http://www.apache.org/%7Eclr/downloads/mirror-dist-db-jdo/2.0-beta/jdo2-tck-src-20_Jan_2006.zip>.
>>>
>>>
>>> 2. Unzip the release into a directory, hereinafter called <dist>.
>>>
>>> 3. Change to the <dist> directory: cd <dist>
>>>
>>> 4. The release depends on artifacts that are only available on the
>>> staging release area, so you need to edit the maven location from
>>> which the artifacts are downloaded. Find the line of maven.xml in
>>> the project.properties file with the maven.remote.repo property, and
>>> add
>>
>>
> What do you mean with maven.xml here? The project.properties in
> jdo2-tck-2.0-beta has the property maven.remote.repo.
>
>>> "http://www.apache.org/~clr/downloads/maven
>>> <http://www.apache.org/%7Eclr/downloads/maven>" to the ibiblio and
>>> jpox urls. The JPOX releases might not be available until Sunday
>>> evening. Interim, you can manually download the nightly SNAPSHOT
>>> build and rename the jar file to the 1.1.0-beta-6 version.
>>
>>
> I added the above to the maven.remote.repo property. But I'm having
> problems resolving the dependencies via maven, I get the following
> error message:
> Attempting to download jdo2-api-2.0-beta.jar.
> Error retrieving artifact from [
> http://www.apache.org/~clr/downloads/maven/javax.jdo/jars/jdo2-api-2.0-beta.jar]:
> java.
> io.IOException: Unknown error downloading; status code was: 302
> WARNING: Failed to download jdo2-api-2.0-beta.jar.
>
> However, I could download the jars manually using the above url. So I
> really do not know why I could not download it via maven.
>
>>>
>>> 5. Change to the jdo2-tck-2.0-beta directory. This is the working
>>> directory for the testing of the release.
>>>
>>> 6. Open and read the RunRules.html document and perform as many of
>>> the steps therein as you like.
>>
>>
> The file RunRule.html is included twice: in the root and under
> jdo2-tck-2.0-beta. Maybe this is a left over from merging my recent
> 'maven dist' support changes into the workspace you used to create the
> distribution file.
>
>>>
>>> 7. If you run maven runtck.jdori from the jdo2-tck-2.0-beta
>>> directory, you should expect 4 or 5 errors and 4 or 5 failures in
>>> 1152 JUnit tests.
>>
>>
> Yes, I got: Total tests run: 1154. Failures: 4, Errors: 4.
>
>>>
>>> 8. If you like, you can also check out the source distributions of
>>> the api20, core20, and enhancer20. These are also in the
>>> http://www.apache.org/~clr/downloads/mirror-dist-db-jdo/2.0-beta/
>>> <http://www.apache.org/%7Eclr/downloads/mirror-dist-db-jdo/2.0-beta/>
>>> area for staging.
>>
>>
> I realized some minor issues:
> - The directory iut_jars is not included in the distribution, but it
> will be created on the first run of maven from the jdo2-tck-2.0-beta
> directory. This might be confusing, if you want to copy the iut jars
> before running maven. Maybe we could change this and include it as an
> empty directory. I'll take a look.
> - We forgot to include the assertions directory into the distribution.
> I'll take a look.
> - The lib/ext directory is in the parent directory of jdo2-tck-beta,
> not parallel to test as stated in the RunRules.
>
> Regards Michael
>
>>>
>>> Please send feedback to jdo-dev@db.apache.org
>>> <ma...@db.apache.org>.
>>>
>>> Thanks,
>>>
>>> Craig
>>>
>>> Craig Russell
>>> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
>>> 408 276-5638 mailto:Craig.Russell@sun.com
>>> P.S. A good JDO? O, Gasp!
>>>
>>
>> Craig Russell
>>
>> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
>>
>> 408 276-5638 mailto:Craig.Russell@sun.com
>>
>> P.S. A good JDO? O, Gasp!
>>
>>
>
>
Re: Test instructions for Release JDO2 beta
Posted by Craig L Russell <Cr...@Sun.COM>.
Hi Michael,
On Jan 21, 2006, at 12:01 PM, Michael Bouschen wrote:
> Hi Craig,
>
> +1 for the released version.
>
> The distribution is running good, I tested it with the SNAPSHOT
> release of JPOX as you described below.
> However, I'm having problems with downloading the jdo2-beta jars
> from the maven repository, please see below ...
>
>>> 4. The release depends on artifacts that are only available on
>>> the staging release area, so you need to edit the maven location
>>> from which the artifacts are downloaded. Find the line of
>>> maven.xml in the project.properties file with the
>>> maven.remote.repo property, and add
>>
> What do you mean with maven.xml here? The project.properties in
> jdo2-tck-2.0-beta has the property maven.remote.repo.
Of course you are right. [The test information needs to be put onto a
wiki and maintained. This was an oversight on my part.]
>
>>> "http://www.apache.org/~clr/downloads/maven <http://
>>> www.apache.org/%7Eclr/downloads/maven>" to the ibiblio and jpox
>>> urls. The JPOX releases might not be available until Sunday
>>> evening. Interim, you can manually download the nightly SNAPSHOT
>>> build and rename the jar file to the 1.1.0-beta-6 version.
>>
> I added the above to the maven.remote.repo property. But I'm having
> problems resolving the dependencies via maven, I get the following
> error message:
> Attempting to download jdo2-api-2.0-beta.jar.
> Error retrieving artifact from [ http://www.apache.org/~clr/
> downloads/maven/javax.jdo/jars/jdo2-api-2.0-beta.jar]: java.
> io.IOException: Unknown error downloading; status code was: 302
> WARNING: Failed to download jdo2-api-2.0-beta.jar.
>
> However, I could download the jars manually using the above url. So
> I really do not know why I could not download it via maven.
This is mysterious. I get similar results:
Attempting to download jdo2-api-2.0-beta.jar.
Error retrieving artifact from [ http://www.jpox.org/downloads/maven
http://www.apache.org/~clr/downloads/maven/javax.jdo/jars/jdo2-
api-2.0-beta.jar]: java.lang.IllegalArgumentException: Invalid uri '/
downloads/maven http://www.apache.org/~clr/downloads/maven/javax.jdo/
jars/jdo2-api-2.0-beta.jar': escaped absolute path not valid
WARNING: Failed to download jdo2-api-2.0-beta.jar.
The build cannot continue because of the following unsatisfied
dependency:
jdo2-api-2.0-beta.jar
Anyone around here know what the issue is?
>
>>>
>>> 5. Change to the jdo2-tck-2.0-beta directory. This is the working
>>> directory for the testing of the release.
>>>
>>> 6. Open and read the RunRules.html document and perform as many
>>> of the steps therein as you like.
>>
> The file RunRule.html is included twice: in the root and under jdo2-
> tck-2.0-beta. Maybe this is a left over from merging my recent
> 'maven dist' support changes into the workspace you used to create
> the distribution file.
Yes. Good catch.
> I realized some minor issues:
> - The directory iut_jars is not included in the distribution, but
> it will be created on the first run of maven from the jdo2-tck-2.0-
> beta directory. This might be confusing, if you want to copy the
> iut jars before running maven. Maybe we could change this and
> include it as an empty directory. I'll take a look.
Yes, good idea. Your patch copied everything though. I guess it
should be empty.
> - We forgot to include the assertions directory into the
> distribution. I'll take a look.
Your patch looks good.
> - The lib/ext directory is in the parent directory of jdo2-tck-
> beta, not parallel to test as stated in the RunRules.
I'll update the RunRules. At least it isn't there twice.
Thanks for the usual thorough review.
Craig
>
> Regards Michael
>
>>>
>>> Please send feedback to jdo-dev@db.apache.org <mailto:jdo-
>>> dev@db.apache.org>.
>>>
>>> Thanks,
>>>
>>> Craig
>>>
>>> Craig Russell
>>> Architect, Sun Java Enterprise System http://java.sun.com/
>>> products/jdo
>>> 408 276-5638 mailto:Craig.Russell@sun.com
>>> P.S. A good JDO? O, Gasp!
>>>
>>
>> Craig Russell
>>
>> Architect, Sun Java Enterprise System http://java.sun.com/products/
>> jdo
>>
>> 408 276-5638 mailto:Craig.Russell@sun.com
>>
>> P.S. A good JDO? O, Gasp!
>>
>>
>
>
> --
> Michael Bouschen Tech@Spree Engineering GmbH
> mailto:mbo.tech@spree.de http://www.tech.spree.de/
> Tel.:++49/30/235 520-33 Buelowstr. 66
> Fax.:++49/30/2175 2012 D-10783 Berlin
>
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: [VOTE] Release JDO2 beta
Posted by Michael Bouschen <mb...@spree.de>.
Hi Craig,
+1 for the released version.
The distribution is running good, I tested it with the SNAPSHOT release
of JPOX as you described below.
However, I'm having problems with downloading the jdo2-beta jars from
the maven repository, please see below ...
> Oops, the URL below is wrong. It should
> be http://www.apache.org/~clr/downloads/mirror-dist-db-jdo/2.0-beta/jdo2-tck-2.0-beta-src-20_Jan_2006.zip
> <http://www.apache.org/%7Eclr/downloads/mirror-dist-db-jdo/2.0-beta/jdo2-tck-src-20_Jan_2006.zip>.
>
>
> Sorry for the inconvenience.
>
> Craig
>
> On Jan 20, 2006, at 8:59 PM, Craig L Russell wrote:
>
>> This is now a real vote for the release of JDO 2 beta.
>>
>> Here's how to test the jdo 2.0-beta staging release.
>>
>> 1. Download the TCK source release from
>> http://www.apache.org/~clr/downloads/mirror-dist-db-jdo/2.0-beta/jdo2-tck-src-20_Jan_2006.zip
>> <http://www.apache.org/%7Eclr/downloads/mirror-dist-db-jdo/2.0-beta/jdo2-tck-src-20_Jan_2006.zip>.
>>
>> 2. Unzip the release into a directory, hereinafter called <dist>.
>>
>> 3. Change to the <dist> directory: cd <dist>
>>
>> 4. The release depends on artifacts that are only available on the
>> staging release area, so you need to edit the maven location from
>> which the artifacts are downloaded. Find the line of maven.xml in the
>> project.properties file with the maven.remote.repo property, and add
>
What do you mean with maven.xml here? The project.properties in
jdo2-tck-2.0-beta has the property maven.remote.repo.
>> "http://www.apache.org/~clr/downloads/maven
>> <http://www.apache.org/%7Eclr/downloads/maven>" to the ibiblio and
>> jpox urls. The JPOX releases might not be available until Sunday
>> evening. Interim, you can manually download the nightly SNAPSHOT
>> build and rename the jar file to the 1.1.0-beta-6 version.
>
I added the above to the maven.remote.repo property. But I'm having
problems resolving the dependencies via maven, I get the following error
message:
Attempting to download jdo2-api-2.0-beta.jar.
Error retrieving artifact from [
http://www.apache.org/~clr/downloads/maven/javax.jdo/jars/jdo2-api-2.0-beta.jar]:
java.
io.IOException: Unknown error downloading; status code was: 302
WARNING: Failed to download jdo2-api-2.0-beta.jar.
However, I could download the jars manually using the above url. So I
really do not know why I could not download it via maven.
>>
>> 5. Change to the jdo2-tck-2.0-beta directory. This is the working
>> directory for the testing of the release.
>>
>> 6. Open and read the RunRules.html document and perform as many of
>> the steps therein as you like.
>
The file RunRule.html is included twice: in the root and under
jdo2-tck-2.0-beta. Maybe this is a left over from merging my recent
'maven dist' support changes into the workspace you used to create the
distribution file.
>>
>> 7. If you run maven runtck.jdori from the jdo2-tck-2.0-beta
>> directory, you should expect 4 or 5 errors and 4 or 5 failures in
>> 1152 JUnit tests.
>
Yes, I got: Total tests run: 1154. Failures: 4, Errors: 4.
>>
>> 8. If you like, you can also check out the source distributions of
>> the api20, core20, and enhancer20. These are also in the
>> http://www.apache.org/~clr/downloads/mirror-dist-db-jdo/2.0-beta/
>> <http://www.apache.org/%7Eclr/downloads/mirror-dist-db-jdo/2.0-beta/>
>> area for staging.
>
I realized some minor issues:
- The directory iut_jars is not included in the distribution, but it
will be created on the first run of maven from the jdo2-tck-2.0-beta
directory. This might be confusing, if you want to copy the iut jars
before running maven. Maybe we could change this and include it as an
empty directory. I'll take a look.
- We forgot to include the assertions directory into the distribution.
I'll take a look.
- The lib/ext directory is in the parent directory of jdo2-tck-beta, not
parallel to test as stated in the RunRules.
Regards Michael
>>
>> Please send feedback to jdo-dev@db.apache.org
>> <ma...@db.apache.org>.
>>
>> Thanks,
>>
>> Craig
>>
>> Craig Russell
>> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
>> 408 276-5638 mailto:Craig.Russell@sun.com
>> P.S. A good JDO? O, Gasp!
>>
>
> Craig Russell
>
> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
>
> 408 276-5638 mailto:Craig.Russell@sun.com
>
> P.S. A good JDO? O, Gasp!
>
>
--
Michael Bouschen Tech@Spree Engineering GmbH
mailto:mbo.tech@spree.de http://www.tech.spree.de/
Tel.:++49/30/235 520-33 Buelowstr. 66
Fax.:++49/30/2175 2012 D-10783 Berlin
Re: [VOTE] Release JDO2 beta
Posted by Craig L Russell <Cr...@Sun.COM>.
Oops, the URL below is wrong. It should be http://www.apache.org/
~clr/downloads/mirror-dist-db-jdo/2.0-beta/jdo2-tck-2.0-beta-
src-20_Jan_2006.zip.
Sorry for the inconvenience.
Craig
On Jan 20, 2006, at 8:59 PM, Craig L Russell wrote:
> This is now a real vote for the release of JDO 2 beta.
>
> Here's how to test the jdo 2.0-beta staging release.
>
> 1. Download the TCK source release from http://www.apache.org/~clr/
> downloads/mirror-dist-db-jdo/2.0-beta/jdo2-tck-src-20_Jan_2006.zip.
>
> 2. Unzip the release into a directory, hereinafter called <dist>.
>
> 3. Change to the <dist> directory: cd <dist>
>
> 4. The release depends on artifacts that are only available on the
> staging release area, so you need to edit the maven location from
> which the artifacts are downloaded. Find the line of maven.xml in
> the project.properties file with the maven.remote.repo property,
> and add "http://www.apache.org/~clr/downloads/maven" to the ibiblio
> and jpox urls. The JPOX releases might not be available until
> Sunday evening. Interim, you can manually download the nightly
> SNAPSHOT build and rename the jar file to the 1.1.0-beta-6 version.
>
> 5. Change to the jdo2-tck-2.0-beta directory. This is the working
> directory for the testing of the release.
>
> 6. Open and read the RunRules.html document and perform as many of
> the steps therein as you like.
>
> 7. If you run maven runtck.jdori from the jdo2-tck-2.0-beta
> directory, you should expect 4 or 5 errors and 4 or 5 failures in
> 1152 JUnit tests.
>
> 8. If you like, you can also check out the source distributions of
> the api20, core20, and enhancer20. These are also in the http://
> www.apache.org/~clr/downloads/mirror-dist-db-jdo/2.0-beta/ area for
> staging.
>
> Please send feedback to jdo-dev@db.apache.org.
>
> Thanks,
>
> Craig
>
> Craig Russell
> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
> 408 276-5638 mailto:Craig.Russell@sun.com
> P.S. A good JDO? O, Gasp!
>
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: [VOTE] Release JDO2 beta
Posted by David Van Couvering <da...@apache.org>.
+1
Craig L Russell wrote:
> This is now a real vote for the release of JDO 2 beta.
>
> Here's how to test the jdo 2.0-beta staging release.
>
> 1. Download the TCK source release from
> http://www.apache.org/~clr/downloads/mirror-dist-db-jdo/2.0-beta/jdo2-tck-src-20_Jan_2006.zip.
>
> 2. Unzip the release into a directory, hereinafter called <dist>.
>
> 3. Change to the <dist> directory: cd <dist>
>
> 4. The release depends on artifacts that are only available on the
> staging release area, so you need to edit the maven location from which
> the artifacts are downloaded. Find the line of maven.xml in the
> project.properties file with the maven.remote.repo property, and add
> "http://www.apache.org/~clr/downloads/maven" to the ibiblio and jpox
> urls. The JPOX releases might not be available until Sunday
> evening. Interim, you can manually download the nightly SNAPSHOT build
> and rename the jar file to the 1.1.0-beta-6 version.
>
> 5. Change to the jdo2-tck-2.0-beta directory. This is the working
> directory for the testing of the release.
>
> 6. Open and read the RunRules.html document and perform as many of the
> steps therein as you like.
>
> 7. If you run maven runtck.jdori from the jdo2-tck-2.0-beta directory,
> you should expect 4 or 5 errors and 4 or 5 failures in 1152 JUnit tests.
>
> 8. If you like, you can also check out the source distributions of the
> api20, core20, and enhancer20. These are also in the
> http://www.apache.org/~clr/downloads/mirror-dist-db-jdo/2.0-beta/ area
> for staging.
>
> Please send feedback to jdo-dev@db.apache.org
> <ma...@db.apache.org>.
>
> Thanks,
>
> Craig
>
> Craig Russell
>
> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
>
> 408 276-5638 mailto:Craig.Russell@sun.com
>
> P.S. A good JDO? O, Gasp!
>
>
Re: [VOTE] Release JDO2 beta
Posted by er...@jpox.org.
False alert. :) It only happens if running under windows and placed inside a
folder with spaces in the name, like c:\document and settings\jdo2\
Regards,
Quoting erik@jpox.org:
> I downloaded from SVN jdo2 branch because the files are not available to
> download, and I had several times the same NoClassDefFoundError error, which
> was not logged to anywhere.
>
> privateRuntck.jdori:
> [mkdir] Created dir: C:\Documents and Settings\ebengtso\My
> Documents\jpoxwor
> kspace\2.0-beta\tck20\target\logs\20060121-151045
> [echo] Run all configurations on jdori
> exclude:
>
> doRuntck.jdori:
> [java] java.lang.NoClassDefFoundError: and
> [java] Exception in thread "main"
> [java] [ERROR] Java Result: 1
> [echo] Finished run with database="derby"
> identitytype="applicationidentity"
> mapping="".
>
> exclude:
>
> doRuntck.jdori:
> Overriding previous definition of reference to this.jdori.classpath
> [java] java.lang.NoClassDefFoundError: and
> [java] Exception in thread "main"
> [java] [ERROR] Java Result: 1
> [echo] Finished run with database="derby"
> identitytype="applicationidentity"
> mapping="".
>
> exclude:
>
> doRuntck.jdori:
> Overriding previous definition of reference to this.jdori.classpath
> [java] java.lang.NoClassDefFoundError: and
> [java] Exception in thread "main"
> [java] [ERROR] Java Result: 1
> [echo] Finished run with database="derby"
> identitytype="applicationidentity"
> mapping="".
>
> exclude:
>
>
>
>
> Quoting Craig L Russell <Cr...@Sun.COM>:
>
> > This is now a real vote for the release of JDO 2 beta.
> >
> > Here's how to test the jdo 2.0-beta staging release.
> >
> > 1. Download the TCK source release from http://www.apache.org/~clr/
> > downloads/mirror-dist-db-jdo/2.0-beta/jdo2-tck-src-20_Jan_2006.zip.
> >
> > 2. Unzip the release into a directory, hereinafter called <dist>.
> >
> > 3. Change to the <dist> directory: cd <dist>
> >
> > 4. The release depends on artifacts that are only available on the
> > staging release area, so you need to edit the maven location from
> > which the artifacts are downloaded. Find the line of maven.xml in the
> > project.properties file with the maven.remote.repo property, and add
> > "http://www.apache.org/~clr/downloads/maven" to the ibiblio and jpox
> > urls. The JPOX releases might not be available until Sunday evening.
> > Interim, you can manually download the nightly SNAPSHOT build and
> > rename the jar file to the 1.1.0-beta-6 version.
> >
> > 5. Change to the jdo2-tck-2.0-beta directory. This is the working
> > directory for the testing of the release.
> >
> > 6. Open and read the RunRules.html document and perform as many of
> > the steps therein as you like.
> >
> > 7. If you run maven runtck.jdori from the jdo2-tck-2.0-beta
> > directory, you should expect 4 or 5 errors and 4 or 5 failures in
> > 1152 JUnit tests.
> >
> > 8. If you like, you can also check out the source distributions of
> > the api20, core20, and enhancer20. These are also in the http://
> > www.apache.org/~clr/downloads/mirror-dist-db-jdo/2.0-beta/ area for
> > staging.
> >
> > Please send feedback to jdo-dev@db.apache.org.
> >
> > Thanks,
> >
> > Craig
> >
> > Craig Russell
> > Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
> > 408 276-5638 mailto:Craig.Russell@sun.com
> > P.S. A good JDO? O, Gasp!
> >
> >
>
>
>
>
Re: [VOTE] Release JDO2 beta
Posted by er...@jpox.org.
I downloaded from SVN jdo2 branch because the files are not available to
download, and I had several times the same NoClassDefFoundError error, which
was not logged to anywhere.
privateRuntck.jdori:
[mkdir] Created dir: C:\Documents and Settings\ebengtso\My Documents\jpoxwor
kspace\2.0-beta\tck20\target\logs\20060121-151045
[echo] Run all configurations on jdori
exclude:
doRuntck.jdori:
[java] java.lang.NoClassDefFoundError: and
[java] Exception in thread "main"
[java] [ERROR] Java Result: 1
[echo] Finished run with database="derby" identitytype="applicationidentity"
mapping="".
exclude:
doRuntck.jdori:
Overriding previous definition of reference to this.jdori.classpath
[java] java.lang.NoClassDefFoundError: and
[java] Exception in thread "main"
[java] [ERROR] Java Result: 1
[echo] Finished run with database="derby" identitytype="applicationidentity"
mapping="".
exclude:
doRuntck.jdori:
Overriding previous definition of reference to this.jdori.classpath
[java] java.lang.NoClassDefFoundError: and
[java] Exception in thread "main"
[java] [ERROR] Java Result: 1
[echo] Finished run with database="derby" identitytype="applicationidentity"
mapping="".
exclude:
Quoting Craig L Russell <Cr...@Sun.COM>:
> This is now a real vote for the release of JDO 2 beta.
>
> Here's how to test the jdo 2.0-beta staging release.
>
> 1. Download the TCK source release from http://www.apache.org/~clr/
> downloads/mirror-dist-db-jdo/2.0-beta/jdo2-tck-src-20_Jan_2006.zip.
>
> 2. Unzip the release into a directory, hereinafter called <dist>.
>
> 3. Change to the <dist> directory: cd <dist>
>
> 4. The release depends on artifacts that are only available on the
> staging release area, so you need to edit the maven location from
> which the artifacts are downloaded. Find the line of maven.xml in the
> project.properties file with the maven.remote.repo property, and add
> "http://www.apache.org/~clr/downloads/maven" to the ibiblio and jpox
> urls. The JPOX releases might not be available until Sunday evening.
> Interim, you can manually download the nightly SNAPSHOT build and
> rename the jar file to the 1.1.0-beta-6 version.
>
> 5. Change to the jdo2-tck-2.0-beta directory. This is the working
> directory for the testing of the release.
>
> 6. Open and read the RunRules.html document and perform as many of
> the steps therein as you like.
>
> 7. If you run maven runtck.jdori from the jdo2-tck-2.0-beta
> directory, you should expect 4 or 5 errors and 4 or 5 failures in
> 1152 JUnit tests.
>
> 8. If you like, you can also check out the source distributions of
> the api20, core20, and enhancer20. These are also in the http://
> www.apache.org/~clr/downloads/mirror-dist-db-jdo/2.0-beta/ area for
> staging.
>
> Please send feedback to jdo-dev@db.apache.org.
>
> Thanks,
>
> Craig
>
> Craig Russell
> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
> 408 276-5638 mailto:Craig.Russell@sun.com
> P.S. A good JDO? O, Gasp!
>
>
Re: [VOTE] Release JDO2 beta
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi Craig,
I think we need to post this information on the download page of the JDO
home page (http://db.apache.org/jdo/downloads.html). There we can also
post release notes which would include errata for RunRules.html. With
that in place, I would vote for releasing.
-- Michelle
Craig L Russell wrote:
> This is now a real vote for the release of JDO 2 beta.
>
> Here's how to test the jdo 2.0-beta staging release.
>
> 1. Download the TCK source release from
> http://www.apache.org/~clr/downloads/mirror-dist-db-jdo/2.0-beta/jdo2-tck-src-20_Jan_2006.zip
> <http://www.apache.org/%7Eclr/downloads/mirror-dist-db-jdo/2.0-beta/jdo2-tck-src-20_Jan_2006.zip>.
>
> 2. Unzip the release into a directory, hereinafter called <dist>.
>
> 3. Change to the <dist> directory: cd <dist>
>
> 4. The release depends on artifacts that are only available on the
> staging release area, so you need to edit the maven location from
> which the artifacts are downloaded. Find the line of maven.xml in the
> project.properties file with the maven.remote.repo property, and add
> "http://www.apache.org/~clr/downloads/maven
> <http://www.apache.org/%7Eclr/downloads/maven>" to the ibiblio and
> jpox urls. The JPOX releases might not be available until Sunday
> evening. Interim, you can manually download the nightly SNAPSHOT build
> and rename the jar file to the 1.1.0-beta-6 version.
>
> 5. Change to the jdo2-tck-2.0-beta directory. This is the working
> directory for the testing of the release.
>
> 6. Open and read the RunRules.html document and perform as many of the
> steps therein as you like.
>
> 7. If you run maven runtck.jdori from the jdo2-tck-2.0-beta directory,
> you should expect 4 or 5 errors and 4 or 5 failures in 1152 JUnit tests.
>
> 8. If you like, you can also check out the source distributions of the
> api20, core20, and enhancer20. These are also in the
> http://www.apache.org/~clr/downloads/mirror-dist-db-jdo/2.0-beta/
> <http://www.apache.org/%7Eclr/downloads/mirror-dist-db-jdo/2.0-beta/>
> area for staging.
>
> Please send feedback to jdo-dev@db.apache.org
> <ma...@db.apache.org>.
>
> Thanks,
>
> Craig
>
> Craig Russell
>
> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
>
> 408 276-5638 mailto:Craig.Russell@sun.com
>
> P.S. A good JDO? O, Gasp!
>
>