Re: new to STRUTS
Lew <l...@nospam.lewscanon.com> wrote:
relative paths in the classpath. In fact, relative classpaths are a great way
to ensure portability of your build script.
ck wrote:
If at all you call this a build script how do you ensure portability?
I never called this a build script.
C:\java\login>javac -classpath WEB-INF\lib\commons-
beanutils-1.7.0.jar;WEB-INF
\lib\commons-validator-1.3.1.jar;WEB-INF\lib\commons-
digester-1.8.jar;WEB-INF\li
b\oro-2.0.8.jar;WEB-INF\lib\struts-core-1.3.8.jar;WEB-INF\lib
\standard-1.0.2.jar
;WEB-INF\lib\struts-extras-1.3.8;WEB-INF\lib\struts-
scripting-1.3.8.jar;C:\Sun\S
DK\lib\j2ee.jar;"C:\Program Files\Apache Group\Tomcat 5.5\common\lib
\servlet-api.jar"
I would certainly not call it a script,
No one would, unless, of course, those commands were issued from a batch file
and what the OP gave us was the echo of that run.
I would rather like to set Environment variable or use ANT script than to type something so messy
every time(In windows once you close command prompt you cant get
the history of commands) or at least use a batch file.
envars are not the way to go unless you only use your computer from one
project. Ant is definitely the way to go.
My use of the term "build script" was meant to be a big, fat hint to the OP
that if they weren't using a build script, they should. The notion that the
original process was not scripted was meant to be highlighted through irony.
Glad you caught it. (Surely you didn't think I was being anything but ironic?)
-- Lew