o do commits for large changes.
Tim
> -Original Message-
> From: Pierre Delisle [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, March 07, 2001 5:45 PM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED];
> [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: [PATCH] building too hard!
Jeff Turner wrote:
> How about using the preset CLASSPATH as a fallback, to be relied on only after
> printing a dire warning? Eg, one could have the following system (taking Ant as
> an example):
>
> if $ANT_JAR set && `$ANT_JAR` exists:
> use it
> elseif $ANT_HOME set && `$ANT_HOME/lib
> For instance, jakarta-taglib's external dependencies are:
>
> 1) Ant
> 2) JAXP
> 3) JAXP-compliant parser (xerces)
> 4) Xalan (for the
On Tue, Mar 06, 2001 at 03:00:26AM -0600, Tim Dawson wrote:
> I agree 100% -- #3 is a GREAT approach. Relying on the classpath is quite
> dangerous, and the defaults specified are probably very infrequently used.
Well.. please don't get me wrong, I hate classpaths as much as the next
battle-scar
]
Subject: Re: [PATCH] building too hard!
Jeff,
Totally agree with you regarding the complexity of the build process
of jakarta-taglibs. Thanks for documenting what you went through
to make the community aware of the current flaws.
Here is my .02 on how I believe we could fix the issues
you raised in a
Jeff,
Totally agree with you regarding the complexity of the build process
of jakarta-taglibs. Thanks for documenting what you went through
to make the community aware of the current flaws.
Here is my .02 on how I believe we could fix the issues
you raised in a clean and consistent way.
Commen
