I've already branched and made the changes to the poms (to make the
whole thing build correctly). To me, I'd rather get it done right than
to just push out a few updated zips, especially since this includes
the struts-2.1.8-all.zip. I'll have the build pushed out to the
staging repo in a bit and I think maybe what we can do is possibly do
a fast-track vote... I know Martin likes to make sure that we have the
required amount of time, but in this instance, it's really just a few
pom updates, so I think we should just treat it like a security fix
release...

-Wes

On Thu, Oct 1, 2009 at 2:57 PM, Paul Benedict <pbened...@apache.org> wrote:
> Oh, okay. I misunderstood. If only the Apache distribution packages
> are messed up, go ahead and replace those. I don't think that calls
> for a new build.
>
> I had bad MD5 files before. I was asked to fix those on a release
> (after the mirrors received them), and I did.
>
> Paul
>
> On Thu, Oct 1, 2009 at 12:44 PM, Musachy Barroso <musa...@gmail.com> wrote:
>> that sounds good to me. If we just overwrite 2.1.8 then the mirrors
>> will also be updated right? This is technically speaking 2.1.8.
>>
>> musachy
>>
>> On Thu, Oct 1, 2009 at 10:30 AM, Wes Wannemacher <w...@wantii.com> wrote:
>>> So, I was trying to figure out what is going on here because there are
>>> more problems with the zip than mentioned on the user@ list. Since I
>>> took site-deploy out of the release plugins default goals (to keep
>>> other artifacts from stomping the main struts.apache.org site), it had
>>> the unintended side effect of not running the site generation for the
>>> rest of the artifacts... This means that (among other things) the
>>> javadocs aren't in the docs zip.
>>>
>>> I am going to pull down the 2.1.8 sources via the tag and create a
>>> 2.1.8.1 build to fix the docs zip. I will configure the release plugin
>>> on the struts2 pom file (so that I will not be making changes to
>>> struts-master). In addition, I will fix the funky characters in
>>> filenames by passing the appropriate parameters to wget. To do this, I
>>> will have to branch SVN, so I want to make a 2.1 branch and then we
>>> can make this the time to move trunk to 2.2.0 and begin working on
>>> some of the recent ideas (incorporating xwork being the biggest).
>>>
>>>
>>> --
>>> Wes Wannemacher
>>>
>>> Head Engineer, WanTii, Inc.
>>> Need Training? Struts, Spring, Maven, Tomcat...
>>> Ask me for a quote!
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
>>> For additional commands, e-mail: dev-h...@struts.apache.org
>>>
>>>
>>
>>
>>
>> --
>> "Hey you! Would you help me to carry the stone?" Pink Floyd
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
>> For additional commands, e-mail: dev-h...@struts.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
> For additional commands, e-mail: dev-h...@struts.apache.org
>
>



-- 
Wes Wannemacher

Head Engineer, WanTii, Inc.
Need Training? Struts, Spring, Maven, Tomcat...
Ask me for a quote!

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org

Reply via email to