On Sat, 9 Aug 2003, David M. Karr wrote:
> Date: 09 Aug 2003 19:28:39 -0700
> From: David M. Karr <[EMAIL PROTECTED]>
> Reply-To: Struts Developers List <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Re: cvs commit: jakarta-struts/contrib/struts-el build.xml
>
> >>>>> "craigmcc" == craigmcc <[EMAIL PROTECTED]> writes:
>
> craigmcc> craigmcc 2003/08/09 18:21:43
> craigmcc> Modified: contrib/struts-el build.xml
> craigmcc> Log:
> craigmcc> Modify the build.xml for struts-el to have a hard-coded reference to
> the
> craigmcc> struts.jar in the parent Struts source tree (i.e. output of "ant
> dist").
> craigmcc> This makes it possible to compile struts-el even when the user has a
> craigmcc> "${user.home}/build.properties" file that defines a struts.jar
> property
> craigmcc> (as I do, because I *use* Struts in lots of different packages).
>
> I assume this is to address the issue with compile errors?
>
>
Yes ... you were right on the money about my build using the wrong JAR
file. It's because I have the following settings in my
${user.home}/build.properties file so I can use 1.1 final in all my
regular projects that use Struts:
struts.home=/usr/local/jakarta-struts-1.1
struts.jar=${struts.home}/lib/struts.jar
Since there's no way to tell Ant to undefine a property, I changed the
struts-el build to use a relative path to find struts.jar instead of the
property.
It works now, so we should see a nightly build succeed tonight.
Craig
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
