|
Home > Archive > Apache JDO Project > January 2006 > [VOTE] Release JDO2 beta
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
[VOTE] Release JDO2 beta
|
|
| Craig L Russell 2006-01-21, 2:45 am |
| | |
| Andy Jefferson 2006-01-21, 2:45 am |
| > This is now a real vote for the release of JDO 2 beta.
+1
--
Andy
| |
| erik@jpox.org 2006-01-21, 6:30 pm |
| 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 <Craig.Russell@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/mirro...b-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!
>
>
| |
| erik@jpox.org 2006-01-21, 6:30 pm |
| 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 <Craig.Russell@Sun.COM>:
>
>
>
>
>
| |
| erik@jpox.org 2006-01-21, 6:30 pm |
| +1. the TCK is running good
Quoting Craig L Russell <Craig.Russell@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/mirro...b-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 L Russell 2006-01-21, 6:30 pm |
| | |
| Michael Bouschen 2006-01-21, 6:30 pm |
| 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/download...20_Jan_2006.zip
> <http://www.apache.org/%7Eclr/downlo...20_Jan_2006.zip>.
>
>
> Sorry for the inconvenience.
>
> Craig
>
> On Jan 20, 2006, at 8:59 PM, Craig L Russell wrote:
>
>
What do you mean with maven.xml here? The project.properties in
jdo2-tck-2.0-beta has the property maven.remote.repo.
>
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/download...pi-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.
>
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, I got: Total tests run: 1154. Failures: 4, Errors: 4.
>
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
>
> 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 L Russell 2006-01-21, 6:30 pm |
| | |
| Craig L Russell 2006-01-22, 5:46 pm |
| | |
| Andy Jefferson 2006-01-22, 5:46 pm |
| > 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
| |
| Michelle Caisse 2006-01-22, 8:47 pm |
| 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 ...
>
> What do you mean with maven.xml here? The project.properties in
> jdo2-tck-2.0-beta has the property maven.remote.repo.
>
> 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/download...pi-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.
>
> 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, I got: Total tests run: 1154. Failures: 4, Errors: 4.
>
> 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
>
>
>
| |
| Michelle Caisse 2006-01-23, 2:45 am |
| 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:
>
>
>
> 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:
>
>
Yes. Should say Find the line in the project.properties file...
[vbcol=seagreen]
-- Michelle
| |
| Michelle Caisse 2006-01-23, 2:45 am |
| 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/download...20_Jan_2006.zip
> <http://www.apache.org/%7Eclr/downlo...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/download...b-jdo/2.0-beta/
> <http://www.apache.org/%7Eclr/downlo...b-jdo/2.0-beta/>
> area for staging.
>
> 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!
>
>
| |
| Michael Bouschen 2006-01-23, 7:45 am |
| 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:
>
>
>
> 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
[vbcol=seagreen]
>
> -- Michelle
>
> Michael Bouschen wrote:
>
--
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
| |
| Michael Bouschen 2006-01-23, 7:45 am |
| 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:
>
> Yes. Should say Find the line in the project.properties file...
>
>
> -- 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
| |
| Andy Jefferson 2006-01-23, 7:45 am |
| > 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
| |
| Andy Jefferson 2006-01-23, 7:45 am |
| > 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
| |
| Michelle Caisse 2006-01-23, 5:45 pm |
| Hi Michael,
Comments below...
Michael Bouschen wrote:
> Hi Michelle,
>
>
>
> 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
| |
| Michael Bouschen 2006-01-23, 5:45 pm |
| Hi Michelle,
> Hi Michael,
>
> Comments below...
>
> Michael Bouschen wrote:
>
> 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 L Russell 2006-01-24, 5:47 pm |
| | |
| David Van Couvering 2006-01-27, 8:47 pm |
| +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/download...0_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/download...b-jdo/2.0-beta/ area
> for staging.
>
> 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 L Russell 2006-01-27, 8:47 pm |
| | |
| Michael Watzek 2006-01-27, 8:47 pm |
| +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:
>
>
> 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/
-------------------------------------------------------------------
|
|
|
|
|