RE: Change Control and source versioning

Change management --

CVS is built into WDSCi.

I have installed a CVS server on a Windows server, before that an
xServer, and use the "Team" facilities built into WDSCi.

The price was right. It has been really stable.

Or you can use a commercial CVS and pay $20 a month or so.

Subversion is replacing CVS, but you have to add a plug-in to use it.
Subversion would give you more options for commercial support.

-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx
[mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of Neill Harper
Sent: Friday, October 17, 2008 12:02 PM
To: java400-l@xxxxxxxxxxxx
Subject: Change Control and source versioning

I'm working on my first Java project, that will be running on the i5.



Does anybody have any tips for Change control and source checkout.



I'm using WDSC and we have an excellent package by MKS called
Implementer
(or CM) that does very well for RPG, Synon etc, especially when it comes
to
having multiple dev and testing environments. It looks like it can be
used
for .class and .java but not for .jar.



I was wondering what most people do? Do you keep everything in jars or
just
point your class path to a big folder with all of the classes in it.



Any info would be appreciated.



Thanks



Neill