This may be a dumb question, but is there any reason to not combine all the
commons-*.jar libraries into one jar file? I am attempting to clean up our server's
classpath, and combining all these jars would really help out.
TIA,
Jason
If one component was upgraded, you'd have to replace the whole shootin'
match.
- Original Message -
From: Jason Vinson [EMAIL PROTECTED]
To: Struts Users Mailing List [EMAIL PROTECTED]
Sent: Friday, February 21, 2003 8:28 AM
Subject: combining commons-*.jar
This may be a dumb question
[EMAIL PROTECTED]
Subject: Re: combining commons-*.jar
If one component was upgraded, you'd have to replace the whole shootin'
match.
- Original Message -
From: Jason Vinson [EMAIL PROTECTED]
To: Struts Users Mailing List [EMAIL PROTECTED]
Sent: Friday, February 21, 2003 8:28 AM
actually there.
Then again, maybe your situation is different...
chris
- Original Message -
From: Jason Vinson [EMAIL PROTECTED]
To: Struts Users Mailing List [EMAIL PROTECTED]
Sent: Friday, February 21, 2003 8:33 AM
Subject: Re: Re: combining commons-*.jar
So if there was an upgrade, i
: Chris Trawick [EMAIL PROTECTED]
Sent: 02/21/03 08:46 AM
To: Struts Users Mailing List [EMAIL PROTECTED]
Subject: Re: Re: combining commons-*.jar
What is cleaning up the classpath about anyway? For building? Ant takes
care of that, just use a lib directory. For deployment? Try /WEB-INF/lib
PROTECTED]
Sent: 02/21/03 08:46 AM
To: Struts Users Mailing List [EMAIL PROTECTED]
Subject: Re: Re: combining commons-*.jar
What is cleaning up the classpath about anyway? For building? Ant
takes
care of that, just use a lib directory. For deployment? Try /WEB-INF/lib
or use your container's
: combining commons-*.jar
I think bundling them is a very bad idea. It may seem like it's saving
you
time for the classpath issue but I think it would only hurt you in the
long
run. Upgrading components becomes difficult and the next person
maintaining
the project will likely be confused.
David
: combining commons-*.jar
I think bundling them is a very bad idea. It may seem like it's saving
you
time for the classpath issue but I think it would only hurt you in the
long
run. Upgrading components becomes difficult and the next person
maintaining
the project will likely
8 matches
Mail list logo