geronimo-scm mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From s..@geronimo.apache.org
Subject [Apache Geronimo Wiki] New: GettingSourceCode
Date Fri, 11 Feb 2005 17:18:13 GMT
   Date: 2005-02-11T09:18:12
   Editor: TobyCabot
   Wiki: Apache Geronimo Wiki
   Page: GettingSourceCode
   URL: http://wiki.apache.org/geronimo/GettingSourceCode

   no comment

New Page:

[[TableOfContents]]

= Overview =

Geronimo uses [http://subversion.tigris.org/ Subversion] to manage its source code. 
Instructions on Subversion use can be found [http://svnbook.red-bean.com here].

= Web Access =

[http://svn.apache.org/viewcvs.cgi/geronimo/trunk/?root=Apache-SVN]

= Anonymous access =

Geronimo source can be checked out anonymously with this command:
 {{{
$> svn checkout http://svn.apache.org/repos/asf/geronimo/trunk geronimo
}}}

Once you have Geronimo checked out you can update the source by executing the following command
from within the '''geronimo''' directory.

 {{{
$> svn update
}}}

Once you've got the code you'll probably want to build it; for instructions see [wiki:Building
Building].

= Web access =
    
[http://svn.apache.org/viewcvs.cgi/geronimo/trunk/?root=Apache-SVN]

= 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/geronimo/trunk geronimo
}}}

= 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
}}}

= Submitting a Patch =
    
If you make changes to Geronimo, and would like to contribute the to the project, you should
create a patch and post it to the [http://nagoya.apache.org/jira/secure/BrowseProject.jspa?id=10220
Geronimo JIRA issue tracker].  To create a patch, simply execute the following command:

 {{{
$> svn diff > your-changes.patchInstructions on [http://subversion.tigris.org/ Subversion]
use can be found [http://svnbook.red-bean.com here].

= Developer Access =
    
Everyone can access the Geronimo Subversion repository via HTTPS, but Geronimo Committers
must checkout the Subversion repository via HTTPS.
 {{{
$> svn checkout https://svn.apache.org/repos/asf/geronimo/trunk geronimo
}}}
    
To commit changes to the repository must, you must set your password on the Apache Subversion
server.  To set your password, use ssh to connect to svn.apache.org, and enter the command
'''svnpasswd'''. This will prompt you to enter a svn password of your choice (Pick a safe
password).  Now, now your are ready to commit changes using your username/password.  Execute
the following command to commit your changes (svn will prompt your for your password)
  {{{
$> 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:
  {{{
$> 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.

Mime
View raw message