The JBossAS codebase has moved to SVN as of July 31 2006. See SubversionMigrationGuide.
The JBoss cvs repository has been moved to cvs.forge.jboss.com as of Apr 20 2005.
Note that the anonymous repository is a mirror of the comitter repository that is synched every 5 minutes.
$ cd /tmp/cvsgrab/ $ cvsgrab -webInterface FishEye1_0 -url \ http://fisheye.jboss.com/viewrep/JBoss/jrunit -destDir .
This will create the JBoss/jrunit directory. Just replaced jrunit with the module you want.
If you want to check out the entire repo with cvsgrab, just leave off the module:
$ cd /tmp/cvsgrab/ $ cvsgrab -webInterface FishEye1_0 -url \ http://fisheye.jboss.com/viewrep/JBoss -destDir .
Or, if you want a branch:
$ cd /tmp/cvsgrab/ $ cvsgrab -webInterface FishEye1_0 -url \ http://fisheye.jboss.com/viewrep/~br=Branch_4_0/JBoss -destDir .
Or a tag:
$ cd /tmp/cvsgrab/ $ cvsgrab -webInterface FishEye1_0 -url \ http://fisheye.jboss.com/viewrep/~br=Branch_4_0,tag=sometag/JBoss -destDir .
export CVS_RSH=ssh export CVSROOT=:ext:email@example.com:/cvsroot/jboss
If you are a JBoss employee, your username is the same as your existing cvs.jboss.com username.
If you are not a JBoss Employee, then your username is your existing SourceForge username OR your jboss.com username.
There is NO shell access, only cvs over ssh, similar to SourceForge.
All committer access is authenticated via SSH. There is no password based committer access. You need to supply an SSH protocol version 2 public key for access to be granted.
This could be done using the ssh-keygen utility as:
ssh-keygen -t dsa -C 'cvs.forge.jboss.com access' -f mykey
ssh-keygen -t rsa -C 'cvs.forge.jboss.com access' -f mykey
Getting Committer Access
1. To get commit access to JBoss CVS, you must first agree to one of the following contributor agreements:
This does not grant you access, but is required before you can submit any code to JBoss. This agreement must be accepted by JBoss, submission does not guarantee acceptance.
2. You need to have demonstrated an understanding of the codebase and testsuite by submitting patches for bugs/enchancements to jira before we will grant committer access. This is decided by project leads.
3. After your contributor agreement has been accepted, you can submit an access request to firstname.lastname@example.org including:
Your full name.
Your SSH public key, for CVS access.
A valid email address for us to use.
Your SourceForge username IF you had committer access before the CVS migration
Your jboss.org website username.
What projects/repositories you need access to.
Please make sure to use the email address and name you used on your contributor agreement, so that we can match up the data more quickly.
If you have trouble
If you don't know your username or have any trouble, just send an email to email@example.com.
Using CVS with SSH
Here are some links from other sites with similar SSH/CVS setups. Please feel free to add other links or instructions, correct mistakes, comment on incorrect or out dated info, etc.
Here are some links for instructions on using TortoiseCVS with ssh and some brief instructions:
Make sure TortoiseCVS is configured correctly for SSH.
In Windows Explorer right click and choose CVS>Preferences...
In the tools tab, make sure the SSH application points to TortoisePlink.exe (e.g. C:\Program Files\<pathtoprogram>\TortoiseCVS\TortoisePlink.exe). And the SSH parameters are -l "%u" "%h"
Make your keys available to SSH
Download Pageant from http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html
Run Pageant and add your private key.
Do the checkout
In Windows Explorer right click and choose CVS Checkout...
Specify :ext:<username>@cvs.forge.jboss.com:/cvsroot/jboss as the CVSROOT.
Specify jboss-head as the module name.
Hit OK and the download should begin.
Here are some links for instructions on using IntelliJ with ssh. Note that IntelliJ uses the OpenSSH format for the ssh keys. So you will need to export these from Putty (using the puttygen tool) unless you use the external plink and pagent config (recommended)
Is it possible to use CVS with putty plink? from the IntelliJ Technology Network ( ITN )
HOW-TO: Using CVS over SSH with IntelliJ IDEA on Window - seems out of date, ymmv
And how about Eclipse with ssh. Note that Eclipse uses the OpenSSH format for the ssh keys. So you will need to export these from Putty (using the puttygen tool) unless you use the external plink and pagent config (recommended).