On Mar 11, 2004, at 12:24 PM, Nathan Bubna wrote:
Geir Magnusson Jr said:On Mar 11, 2004, at 12:01 PM, Nathan Bubna wrote:Marin� A. J�nsson said:Four of the five errors are because of two methods in the o.a.v.t.s.StrutsUtils class that have been deprecated in Velocity Tools v1.1, and will be removed in v1.2. They do not result from broken interfaces in Struts - we were using classes and variables that had been deprecated in Struts v1.1 and apparently have been removed from Struts v1.2.
yeah, i saw these in the nag when it first started. i don't know what
to do
about it, except try and get our 1.1 out and remove the deprecated
stuff as
planned.
How far away is it? can you just branch at the 1.1 tag and then fix head? All gump will care about is head.
we put out 1.1-rc1 a couple weeks ago. no reports of problems since, and no
plans to add features. the only change i'm thinking of making right now is
Nathan Green's patch to fix all those stupid javadoc warnings during the
build. so, i figure we'll just let rc1 stew for a few more weeks and then
release 1.1 final.
as for branching, there is no plain "1.1" tag yet, and my experience of CVS
doesn't yet include making branches so i'm not even sure what that involves.
Then how do you have any idea what you put out as 1.1?
Here is what I do w/ Vel. I branch w/ the version (VEL_1_3_BRANCH) and then tag on releases of that version. 1.1-rc1, 1.1-rc2, 1.1 1.1.1, etc
so if you haven't changed since releaseing 1.1-rc1, you could do the same, and then fix head, knowing that you can keep going on the 1.1 branch for release, and any subsequent fixes or changes is you so desired (like if you wanted a 1.1.1 for a fix to 1.1.)
-- Geir Magnusson Jr 203-247-1713(m) [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
