D:
cd D:\Sources\cvs
d:\cvsnt\cvs -d:pserver:guest@cvs.dev.java.net:/cvs login
d:\cvsnt\cvs -d:pserver:guest@cvs.dev.java.net:/cvs co jforum
d:\cvsnt\cvs -d:pserver:guest@cvs.dev.java.net:/cvs logout
redhand wrote:I dunno what's files Raphael said you to substitute but when I've to deploy a new cvs version, I copy all *.class because initial install should be compiled with a different version of java, then all others files in their respectives directory regardless they are or not present in destination (e.g. a new properties file) Only one except is template (*.htm) if you have made some modifications, you could easily use some free tools like windiff to quiclky made the diff and apply it
redhand wrote:In the CVS directory, there is a file "build.xml". This file is used by Ant to compile *.java to *.class so you have to use Ant to make a new build from sources. This CVS is not a repository for binaries like *.class.
So after installating Ant, go to cvs/jforum in shell and type command "ant", that should build every *.java to class.
If you can't I can provide you some zip containing last build from CVS
ken0 wrote:I don't think you can safely replace only the changed classes. I replace the whole WEB-INF/classes directory on my production copy with the newly compiled classes.
still, it is CVS current after all and not STABLE so you are taking a risk.
Consider Paul's rocket mass heater. |