Modified: db/jdo/site/docs/svn.html URL: http://svn.apache.org/viewvc/db/jdo/site/docs/svn.html?rev=581218&r1=581217&r2=581218&view=diff ============================================================================== --- db/jdo/site/docs/svn.html (original) +++ db/jdo/site/docs/svn.html Tue Oct 2 05:59:21 2007 @@ -1,457 +1,58 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - Apache JDO - Source Code - - - - - - - - - - - -
- -Apache JDO - - - - Source Code - -
- - - - - - - - - - - - -
-
-
- - - - - - - - -

General

- -

Community

- -

Development

- -
- - - - -
- - Source Code Version Control - -
-
-

Apache JDO uses Subversion to manage its source code. +Java Data Objects (JDO) - Source Code

Source Code Version Control

Apache JDO uses Subversion to manage its source code. If you're new to Subversion, you can check out the -online book about Subversion. +online book about Subversion. Note that we are currently using Subversion 1.1.x (there are separate versions of the book covering 1.0 and 1.1). -

-

-To receive notice of commits to the repository subscribe to jdo-commits@db.apache.org by sending email to jdo-commits-subscribe@db.apache.org.

-
-

-

- - - - -
- - Web Access to Subversion - -
-
-

+

+To receive notice of commits to the repository subscribe to jdo-commits@db.apache.org by sending email to jdo-commits-subscribe@db.apache.org.

Web Access to Subversion

If you just want to browse the source code, you can use the - + ViewCVS web interface to Subversion. This is current at all times. -

-
-

-

- - - - -
- - Checking Out Code Using Subversion - -
-
-

Anyone can check code out of Subversion. You only need to specify a +

Checking Out Code Using Subversion

Anyone can check code out of Subversion. You only need to specify a username and password to update the Subversion repository, and only JDO committers can do that. -If you are a committer, are working from behind a firewall, or are connected to the internet through a proxy server, please see the sections below for more information.

- - - - -
- - Anonymous check out from Subversion - -
-
-

Use a command like:

-
% svn checkout http://svn.apache.org/repos/asf/db/jdo 
-

Once you have Apache JDO checked out you can update the source by executing the following command from within the jdo.

-
+If you are a committer, are working from behind a firewall, or are connected to the internet through a proxy server, please see the sections below for more information.

Anonymous check out from Subversion

Use a command like:

% svn checkout http://svn.apache.org/repos/asf/db/jdo 

Once you have Apache JDO checked out you can update the source by executing the following command from within the jdo.

 % svn update
-
-
-

- - - - -
- - Access from behind a firewall - -
-
-

For those users who are stuck behind a corporate firewall which is blocking http access to the Subversion repository, you can try to access it via HTTPS:

-
+

Access from behind a firewall

For those users who are stuck behind a corporate firewall which is blocking http access to the Subversion repository, you can try to access it via HTTPS:

 % svn checkout https://svn.apache.org/repos/asf/db/jdo
-
-
-

- - - - -
- - Access through a proxy - -
-
-

The Subversion client can go through a proxy, if you configure it to do so. First, edit your "servers" configuration file to indicate which proxy to use. The files location depends on your operating system. On Linux or Unix it is located in the directory "~/.subversion". On Windows it is in "%APPDATA%\Subversion". (Try "echo %APPDATA%", note this is a hidden directory.)

-

There are comments in the file explaining what to do. If you don't have that file, get the latest Subversion client and run any command; this will cause the configuration directory and template files to be created.

-

Example : Edit the 'servers' file and add something like :

-
+

Access through a proxy

The Subversion client can go through a proxy, if you configure it to do so. First, edit your "servers" configuration file to indicate which proxy to use. The files location depends on your operating system. On Linux or Unix it is located in the directory "~/.subversion". On Windows it is in "%APPDATA%\Subversion". (Try "echo %APPDATA%", note this is a hidden directory.)

There are comments in the file explaining what to do. If you don't have that file, get the latest Subversion client and run any command; this will cause the configuration directory and template files to be created.

Example : Edit the 'servers' file and add something like :

 [global]
 http-proxy-host = your.proxy.name
 http-proxy-port = 3128
-
-

Please use the regular http proxy settings in case you want to access the the repository from the Sun network (SWAN).

-
-

- - - - -
- - Committer access - -
-
-

Everyone can access the Apache JDO Subversion repository via HTTPS, but Apache JDO Committers must checkout the Subversion repository via HTTPS.

-
+

Please use the regular http proxy settings in case you want to access the the repository from the Sun network (SWAN).

Committer access

Everyone can access the Apache JDO Subversion repository via HTTPS, but Apache JDO Committers must checkout the Subversion repository via HTTPS.

 % svn checkout https://svn.apache.org/repos/asf/db/jdo
-
-
-

- - - - -
- - NetBeans CVS repository access - -
-
-

The btree subproject checks out the NetBeans mdr btree implementation. This requires cvs being installed on your system. The official NetBeans cvs host might not work if you are behind a firewall that blocks the cvs port. Please consult the NetBeans sources page for more info.

-

If you do not have a cvs client installed on your system you can download the NetBeans mdr btree sources here. Unzip the file in the btree directory and comment out (or remove) the definition of the preGoal java:prepare-filesystem.

-
-

-
-

-

- - - - -
- - Submitting Code Changes - -
-
- - - - -
- - Submitting a patch - -
-
-

If you make changes to Apache JDO, and would like to contribute the to the project, you should create a patch and send it to the jdo-dev alias jdo-dev@db.apache.org. To create a patch, simply execute the following command:

-
+

NetBeans CVS repository access

The btree subproject checks out the NetBeans mdr btree implementation. This requires cvs being installed on your system. The official NetBeans cvs host might not work if you are behind a firewall that blocks the cvs port. Please consult the NetBeans sources page for more info.

If you do not have a cvs client installed on your system you can download the NetBeans mdr btree sources here. Unzip the file in the btree directory and comment out (or remove) the definition of the preGoal java:prepare-filesystem.

Submitting Code Changes

Submitting a patch

If you make changes to Apache JDO, and would like to contribute the to the project, you should create a patch and send it to the jdo-dev alias jdo-dev@db.apache.org. To create a patch, simply execute the following command:

 % svn diff > your-changes.patch
-
-
-

- - - - -
- - Committing changes to subversion - -
-
-

+

Committing changes to subversion

To commit changes to the Subversion repository, you must be an Apache JDO committer. See Get Involved for information on how to become a committer and how to set up your password once you become a committer. -

-

+

Once your password is set, you can use a command like this to commit: -

-
+

 $> svn commit --username your-username
 Authentication realm: <https://svn.apache.org:443> ASF Committers
 Password for 'your-username': your-password
-
-

You can also pass your password on the command line directly, but this is a security problem on multiuser unix computers (the command line arguments are available via the ps command). Here is the command if you are Windows or a single user unix computer:

-
+

You can also pass your password on the command line directly, but this is a security problem on multiuser unix computers (the command line arguments are available via the ps command). Here is the command if you are Windows or a single user unix computer:

 $> svn commit --username your-username --password your-password
-
-

Remember to replace 'your-username' and 'your-password' with your actual username and password on svn.apache.org.

-
-

-
-

-

- - - - -
- - Building JDO from Source - -
-
-

Refer to the Wiki +

Remember to replace 'your-username' and 'your-password' with your actual username and password on svn.apache.org.

Building JDO from Source

Refer to the Wiki page for details. Note that the JDO project is subdivided into several -smaller projects, and each project is built separately.

-
-

-

- - - - -
- - Using Subversion on Windows with cygwin - -
-
-

If you use Subversion on Windows under cygwin, you may find that the Subversion client automatically assigns the executable property to non-executable files. In that case, you would see this at the bottom of an svn diff of the file: -

-
+smaller projects, and each project is built separately. 

Using Subversion on Windows with cygwin

If you use Subversion on Windows under cygwin, you may find that the Subversion client automatically assigns the executable property to non-executable files. In that case, you would see this at the bottom of an svn diff of the file: +

 Property changes on: test/sql/derby/datastoreidentity/schema1.sql
 ___________________________________________________________________
 Name: svn:executable
    + *
-
-

This section explains the source of the problem and suggests some actions to avoid it.

- - - - -
- - Background - -
-
-

Subversion carries executable information in the built-in property called svn:executable. This property, unlike others, may be present or absent, but it has no value. You can add it or delete it, but but you cannot change its value.

-

In theory, Subversion ignores Windows file permissions and by default does not set svn:executable. However, cygwin svn acts like Unix svn and determines the svn:executable property based on file permissions.

-

If you create a file from the cygwin command line, by default it is executable only if the filename ends with .bat, .com or .exe, or if its content starts with #!. [This is what the doc says, but you may see -x for all files.] If you create a file using a Windows tool, by default its Windows permissions are executable by all. Cygwin interprets the Unix-style permissions this way as well. If the file is executable by all, cygwin svn sets the svn:executable property on the file when you invoke svn add.

-
-

- - - - -
- - Removing existing executable properties from the repository - -
-
-

You can use svn propdel to remove the svn:executable property from your working copy. -

-
+

This section explains the source of the problem and suggests some actions to avoid it.

Background

Subversion carries executable information in the built-in property called svn:executable. This property, unlike others, may be present or absent, but it has no value. You can add it or delete it, but but you cannot change its value.

In theory, Subversion ignores Windows file permissions and by default does not set svn:executable. However, cygwin svn acts like Unix svn and determines the svn:executable property based on file permissions.

If you create a file from the cygwin command line, by default it is executable only if the filename ends with .bat, .com or .exe, or if its content starts with #!. [This is what the doc says, but you may see -x for all files.] If you create a file using a Windows tool, by default its Windows permissions are executable by all. Cygwin interprets the Unix-style permissions this way as well. If the file is executable by all, cygwin svn sets the svn:executable property on the file when you invoke svn add.

Removing existing executable properties from the repository

You can use svn propdel to remove the svn:executable property from your working copy. +

     svn propdel -R svn:executable .
-
-

will recursively remove the svn:executable property from all of the files below the current directory. You can use this and commit the files to clean the repository if necessary.

-
-

- - - - -
- - Preventing Subversion from adding unwanted executable properties - -
-
-

Windows/cygwin users who don't want to have to think about using svn propdel or chmod on each added file can use a non-cygwin version of svn. The Subversion 1.2.3 Win32 binaries, downloadable from the link at the bottom of http://subversion.tigris.org/project_packages.html, appear to work well. After installation add the svn.exe location to your Windows PATH variable. If you are switching from cygwin svn to Win32 svn

-
    +

    will recursively remove the svn:executable property from all of the files below the current directory. You can use this and commit the files to clean the repository if necessary.

    Preventing Subversion from adding unwanted executable properties

    Windows/cygwin users who don't want to have to think about using svn propdel or chmod on each added file can use a non-cygwin version of svn. The Subversion 1.2.3 Win32 binaries, downloadable from the link at the bottom of http://subversion.tigris.org/project_packages.html, appear to work well. After installation add the svn.exe location to your Windows PATH variable. If you are switching from cygwin svn to Win32 svn

    1. Remove the subversion component from your cygwin installation because when svn is invoked from a cygwin window, the cygwin version is found even if your cygwin/bin directory is later on the path. (In the Select Packages window of the setup wizard, navigate to the subversion package in the Devel. category. Click on the status icon until Uninstall is displayed. Click next and continue through the wizard until installation is complete.)

    2. Copy the servers file and the auth folder from the sygwin ~/.subversion directory to C:\Documents and Settings\<user>\Application Data\Subversion used by Win32 subversion.

    3. -
    -

    Note that windows svn uses backslash as the path separator when displaying file names. You cannot just copy and paste this file name to another svn command when running from within a cygwin shell. You need to enclose the file name into double quotes.

    -

    Alternatively, Windows users can set file permissions in Windows Explorer. (Right-click on the top-level folder & select Properties. Select the Security tab. Click Advanced. Remove all instances of Read & Execute from the Permission Entries. Click "Reset permissions on all child objects and enable propogations of inheritable permissions". Click Apply. OK. OK.) You will have to do this again when you do a clean checkout to a new directory.

    -
-

-
-

-

-
-
-
-
- Copyright © 2003-2007, The Apache Software Foundation -
-
- - - - - - - - - - - - - - - - - - - - - - - - +

Note that windows svn uses backslash as the path separator when displaying file names. You cannot just copy and paste this file name to another svn command when running from within a cygwin shell. You need to enclose the file name into double quotes.

Alternatively, Windows users can set file permissions in Windows Explorer. (Right-click on the top-level folder & select Properties. Select the Security tab. Click Advanced. Remove all instances of Read & Execute from the Permission Entries. Click "Reset permissions on all child objects and enable propogations of inheritable permissions". Click Apply. OK. OK.) You will have to do this again when you do a clean checkout to a new directory.


\ No newline at end of file Modified: db/jdo/site/docs/tck.html URL: http://svn.apache.org/viewvc/db/jdo/site/docs/tck.html?rev=581218&r1=581217&r2=581218&view=diff ============================================================================== --- db/jdo/site/docs/tck.html (original) +++ db/jdo/site/docs/tck.html Tue Oct 2 05:59:21 2007 @@ -1,231 +1,29 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - Apache JDO - TCK - - - - - - - - - - - -
- -Apache JDO - - - - Technology Compatibility Kit - -
- - - - - - - - - - - - -
-
-
- - - - - - - - -

General

- -

Community

- -

Development

- -
- - - - -
- - About the Technology Compatibility Kit - -
-
-

+Java Data Objects (JDO) - TCK

About the Technology Compatibility Kit

In order to demonstrate compliance with the Java Data Objects specification, an implementation must pass all of the tests in the Technology Compatibility Kit (TCK). The TCK is released as a packaged Java source tree. Maven is the driver of a test run. You must download and install -Maven 1.0.x +Maven 1.0.x before running the TCK. -

-
-

-

- - - - -
- - Running the TCK - -
-
-

To run the Technology Compatibility Kit: +

Running the TCK

To run the Technology Compatibility Kit:

  1. Download and extract the TCK source package.
  2. Follow the instructions in the Prerequisites section of - README.txt. + README.txt.
  3. - Follow the procedure in RunRules.html in the jdo2-tck-version directory. + Follow the procedure in RunRules.html in the jdo2-tck-version directory.
-

-
-

-

- - - - -
- - Demonstrating Compliance - -
-
-

+

Demonstrating Compliance

Vendors must post test results on a publicly accessible web site for examination by the public. The posting includes the output of the test run, which consists of multiple log files containing configuration information and test results. For an example of the -required posting, please see http://db.apache.org/jdo/tck/final.

-
-

-

-
-
-
-
- Copyright © 2003-2007, The Apache Software Foundation -
-
- - - - - - - - - - - - - - - - - - - - - - - - +required posting, please see http://db.apache.org/jdo/tck/final.


\ No newline at end of file Modified: db/jdo/site/docs/team-list.html URL: http://svn.apache.org/viewvc/db/jdo/site/docs/team-list.html?rev=581218&r1=581217&r2=581218&view=diff ============================================================================== --- db/jdo/site/docs/team-list.html (original) +++ db/jdo/site/docs/team-list.html Tue Oct 2 05:59:21 2007 @@ -1,429 +1,19 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - Apache JDO - Project Team - - - - - - - - - - - -
- -Apache JDO - - - - Project Team - -
- - - - - - - - - - - - -
-
-
- - - - - - - - -

General

- -

Community

- -

Development

- -
- - - - -
- - The Apache JDO Team - -
-
-

+Java Data Objects (JDO) - Project Team

The Apache JDO Team

The people listed below have made significant contributions to JDO by working long and hard to make quality software for the rest of the world to use. -

-

+

If you would like to contribute to JDO, please see the roadmap list to find areas where you can contribute. If there is nothing in there that suits your interest, but you still have ideas, please feel free to suggest them on the mailing list. -

-

+

If you would like to become a committer, please see Get Involved. -

-
-

-

- - - - -
- - Apache JDO Committers - -
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - Name - - - - Organization - -
- - Matthew Adams - - - - Interface21 - -
- - Erik Bengtson - - - - JPOX - -
- - Michael Bouschen - - - - Tech@Spree - -
- - Michelle Caisse - - - - Sun Microsystems, Inc. - -
- - Andy Jefferson - - - - JPOX - -
- - Patrick Linskey - - - - Solarmetric - -
- - Geir Magnusson Jr. - - - - IBM - -
- - Brian McCallister - - - -   - -
- - Craig Russell - - - - Sun Microsystems, Inc. - -
- - Dain Sundstrom - - - -   - -
- - Brian Topping - - - -   - -
- - Michael Watzek - - - - Tech@Spree - -
- - Martin Zaun - - - - Sun Microsystems, Inc. - -
-
-

-

- - - - -
- - Apache JDO Contributors - -
-
- - - - - - - - - - - - - -
- - Name - - - - Organization - -
- - Chris Beams - - - -   - -
- - Ilan Kirsch - - - - ObjectDB - -
-
-

-

-
-
-
-
- Copyright © 2003-2007, The Apache Software Foundation -
-
- - - - - - - - - - - - - - - - - - - - - - - - +

Apache JDO Committers

NameOrganization
Matthew AdamsInterface21
Erik BengtsonJPOX
Michael BouschenTech@Spree
Michelle CaisseSun Microsystems, Inc.
Andy JeffersonJPOX
Patrick LinskeySolarmetric
Geir Magnusson Jr.IBM
Brian McCallister
Craig RussellSun Microsystems, Inc.
Dain Sundstrom
Brian Topping
Michael WatzekTech@Spree
Martin ZaunSun Microsystems, Inc.

Apache JDO Contributors

NameOrganization
Chris Beams
Ilan KirschObjectDB

\ No newline at end of file