----- Original Message ----- From: "Niall Pemberton" <[EMAIL PROTECTED]>
To: "Struts Developers List" <dev@struts.apache.org>
Sent: Monday, April 04, 2005 7:13 AM
Subject: Re: 1.2.x nightlies?
Thanks for doing this. One issue with the 1.2.x nightly binary distribution
is that it doesn't include the el taglib, which we've distributed in the
"contrib" folder with the 1.2.x versions.
Ummm....ya.....I feel really dumb now ;) I made a bunch of local changes to get this branch built all on the assumption that we did not have el (because I did not see a contrib/ folder).
Then, as part of responding to this email, I looked a little deeper and found it.....(head smack)
I did something kinda cool for this branch as well. Remember how long it took you to go from "cvs co jakarta-struts" to "ant release" (if you've ever had to do that) ??? Well, I made some changes that let's you execute Ant, with an additional target, and the Ant build will go out and grab all of the required jars and do a complete release without having to setup your build.properties file. (Wish I had that 2 years ago!! ;)
AFAIK the only thing preventing someone from using the current "trunk" el
version with Struts 1.2.x is that the Tiles taglib's package has been
changed from "o.a.s.taglib.tiles" to "o.a.s.tiles.taglib". Since it has
changed though, this means that we need to distribute the 1.2.x el taglib
branch with the Struts 1.2.x distros. I guess even if this wasn't the case,
we would still need a 1.2.x el taglib branch since the current taglib trunk
is going to diverge from the 1.2.x versions at some point anyway.
That's cool. No worries (see above). El will be part of the nightlies tonight. Thanks for pointing this out.
The only other thing I noticed was the binary distro unpacks to the
"struts-1.2.6" folder. In the past nightlies just unpacked to a "struts" (or
jakarta-struts) folder - I don't have a problem with including a version
number, but I think 1.2.6 is mis-leading - IMO "struts-1.2.7-nightly" or
"struts-nightly" or "struts-20050402" would be better.
That's correct. The way I am building the nightlies is by running Ant using the "release" target. So any one of us can change that to whatever we feel is the best name. (I need to tweak my nightly script to either ignore the x.y.z part of the name or move the copying to be part of the ant build since I can just build the 'copy from' name the same env.
If you want to make that change, go ahead, I'll see it come across and I'll patch my nightly accordingly.
Niall
Thanks again.
-- James Mitchell Software Engineer / Open Source Evangelist Consulting / Mentoring / Freelance EdgeTech, Inc. 678.910.8017 AIM: jmitchtx Yahoo: jmitchtx MSN: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
