--- "David M. Karr" <[EMAIL PROTECTED]> wrote:
> >>>>> "David" == David Graham <[EMAIL PROTECTED]> writes:
> 
>     David> While we're somewhat on this topic I'd like to get some
> clarification on
>     David> the build process.  Why do struts-el and struts-legacy get
> built with the
>     David> standard Struts build file?  Struts-EL has *never* built on
> my machine and
>     David> I have just taken it on faith the rest of Struts built
> properly.  Also,
>     David> after struts-legacy was added I've had to run my builds
> twice.  The first
>     David> one always fails and the second succeeds (well, not really
> succeeds
>     David> because struts-el fails).
> 
> So what compile errors are you getting in Struts-EL and Struts-Legacy?

I don't get any compile errors.  It's a problem with jars not being in the
right place or my build.properties being incorrect.  I don't mean this in
any negative way but I'm not interested in building struts-el.  When I
build Struts I'm mainly interested in picking up a webapp and running
through it to see if my changes work.  

If there's no concrete reason to build struts-el with Struts, I'd like to
see them separated to simplify the build process.  This specific problem
will go away when struts-el is part of the taglib distro but I think there
is a more general problem of building contrib packages along with the
standard packages.

David

> 
> -- 
> ===================================================================
> David M. Karr          ; Java/J2EE/XML/Unix/C++
> [EMAIL PROTECTED]   ; SCJP; SCWCD
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to