Just a note to anybody else trying this. If you follow the instructions on the CVN link page, you'll end up checking out all branches of both the interpreter and the docs. The command to use to check out just the most recent code version is:
svn co https://svn.sourceforge.net/svnroot/oorexx/oorexx/trunk <dir>
David, the oorexx/oorexx bit looks a bit confusing. I think we might want to rename the code and docs to be "interpreter" and "docs" to remove the "oorexx" redundancy. Fortunately, this is something easy to do with Subversion.
I have created the ooRexx Subversion repository on SourceForge. This repository currently holds the ooRexx 4.0 development tree. The 3.x version of ooRexx will continue to be held within the SourceForge CVS repository. All of the core ooRexx developers have had their access privileges updated for Subversion and all other should have read access to the repository. See the SF Subversion tab on the ooRexx project page for help working with the repository.
Both the current ooRexx 4.0 code base was imported into SVN as well as a copy of the 3.1 docs base (with some changes).
There is also a Subversion config file that was placed in the repository (/svnconfig/config). This is the suggested Subversion configuration file for use with ooRexx. It has entries which explicitly specify what files are binary and which files are text-based. It is highly recommended that you use this configuration file when checking out or updating the repository.
I made a few minor changes to the oorexx tree so you may need to do some work to the Makefiles to get back to where you were.
W. David Ashley
Lab Based Services System p
IBM Systems & Technology Group
Office Phone: 512-838-0609 T/L 678-0609
Mobile Phone: 512-289-7506
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
Oorexx-devel mailing list