You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Ted Husted <hu...@apache.org> on 2007/09/28 16:19:08 UTC
2.1.0 Build/Release Plan
I'd like to propose 7 Oct 2007 as a tag date for the 2.1.0 version. If
anyone would be interested in helping with the build, please don't be
shy!
Pursuant to some other discussions, for the 2.1.x series, I renamed
the Release Notes to Version Notes, since we also use the word
"release" in another sense. We've been putting the "Release Plan" in
the notes lately, and for now, I labeled it the "Build/Release Plan",
since, as it stands, a "Release Plan" is required by our charter.
Again, any help with the build/release would be welcome!
For the record, personally, I do not consider the 2.1.x series to be
"feature locked". If people want to continue to add new features and
conduct refactorings in later 2.0.x milestones, that's fine with me.
Of course, as always, any destructive API changes should be subject
to the usual deprecate/release/remove protocol.
If there are any features or API signatures that we deprecated in
2.0.x that we would like to remove for 2.1.x, this would be a good
time to apply the patch!
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: 2.1.0 Build/Release Plan
Posted by Antonio Petrelli <an...@gmail.com>.
2007/10/1, Wendy Smoak <ws...@gmail.com>:
>
> On 10/1/07, Ted Husted <hu...@apache.org> wrote:
>
> > We can create a build without moving to a release. I'd really like to
> > "tap the keg" on 2.1.x.
>
> There was some talk of using the Maven Release Plugin for Struts 2.1,
> did that get worked out?
I think it should work, but I cannot be sure until I make a real test. In
fact, I was thinking of volunteering for release (just to test the new
release process), but until XWork 2.1 is released I cannot do much.
Keep in mind that the release plugin will not let you proceed until
> all snapshot dependencies have been removed. (Tagged builds are
> supposed to be reproducible, and they can't be if they involve
> snapshots.)
XWork is the only remaining snapshot dependency:
https://issues.apache.org/struts/browse/WW-2151
Antonio
Re: 2.1.0 Build/Release Plan
Posted by Wendy Smoak <ws...@gmail.com>.
On 10/1/07, Ted Husted <hu...@apache.org> wrote:
> We can create a build without moving to a release. I'd really like to
> "tap the keg" on 2.1.x.
There was some talk of using the Maven Release Plugin for Struts 2.1,
did that get worked out?
Keep in mind that the release plugin will not let you proceed until
all snapshot dependencies have been removed. (Tagged builds are
supposed to be reproducible, and they can't be if they involve
snapshots.)
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: 2.1.0 Build/Release Plan
Posted by Ted Husted <hu...@apache.org>.
We can create a build without moving to a release. I'd really like to
"tap the keg" on 2.1.x.
Another issue we should address is our reliance on Rainer and me as
release managers. It's simply not acceptable for either project to
grind to a halt because a single volunteer is on vacation.
If the XWork release process is documented someplace, I"d be happy to
give a try myself. At least then Rainer and I could backup each other.
-Ted.
On 9/28/07, Ian Roughley <ia...@fdar.com> wrote:
> I think he might be on vacation.
>
> Musachy Barroso wrote:
> > Any idea when that might be? I haven't seen Rainer on #struts for a
> > couple of weeks :)
> >
> > musachy
> >
> > On 9/28/07, Antonio Petrelli <an...@gmail.com> wrote:
> >
> >> 2007/9/28, Ted Husted <hu...@apache.org>:
> >>
> >>> I'd like to propose 7 Oct 2007 as a tag date for the 2.1.0 version. If
> >>> anyone would be interested in helping with the build, please don't be
> >>> shy!
> >>>
> >>
> >> Ted, sincerely I wish to wait until XWork 2.1 is released, so we don't have
> >> any snapshot dependency.
> >>
> >> Antonio
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: 2.1.0 Build/Release Plan
Posted by Ian Roughley <ia...@fdar.com>.
I think he might be on vacation.
Musachy Barroso wrote:
> Any idea when that might be? I haven't seen Rainer on #struts for a
> couple of weeks :)
>
> musachy
>
> On 9/28/07, Antonio Petrelli <an...@gmail.com> wrote:
>
>> 2007/9/28, Ted Husted <hu...@apache.org>:
>>
>>> I'd like to propose 7 Oct 2007 as a tag date for the 2.1.0 version. If
>>> anyone would be interested in helping with the build, please don't be
>>> shy!
>>>
>>
>> Ted, sincerely I wish to wait until XWork 2.1 is released, so we don't have
>> any snapshot dependency.
>>
>> Antonio
>>
>>
>
>
>
Re: 2.1.0 Build/Release Plan
Posted by Musachy Barroso <mu...@gmail.com>.
Any idea when that might be? I haven't seen Rainer on #struts for a
couple of weeks :)
musachy
On 9/28/07, Antonio Petrelli <an...@gmail.com> wrote:
> 2007/9/28, Ted Husted <hu...@apache.org>:
> >
> > I'd like to propose 7 Oct 2007 as a tag date for the 2.1.0 version. If
> > anyone would be interested in helping with the build, please don't be
> > shy!
>
>
>
> Ted, sincerely I wish to wait until XWork 2.1 is released, so we don't have
> any snapshot dependency.
>
> Antonio
>
--
"Hey you! Would you help me to carry the stone?" Pink Floyd
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: 2.1.0 Build/Release Plan
Posted by Musachy Barroso <mu...@gmail.com>.
I'm using it for development and it is working fine so far.
musachy
On 10/2/07, Don Brown <mr...@twdata.org> wrote:
> As the Struts 2.1.0 release won't be GA, what about releasing an XWork
> 2.1-beta1 release?
>
> Don
>
> On 10/2/07, Don Brown <mr...@twdata.org> wrote:
> > I'm pretty much done, actually. The only other major thing I was
> > considering, but probably won't get to, was removing commons-logging.
> > I'll try to spend some time to help close out 2.1 issues.
> >
> > Don
> >
> > On 10/2/07, Rainer Hermanns <he...@aixcept.de> wrote:
> > > Don is busy with some important refactorings and enhancements for XWork 2.1.
> > > But I think that until these already commited changes are fully tested and
> > > stabilized, no xwork 2.1 release will happen.
> > >
> > > There are some other open xwork issues, that need to be addressed prior to
> > > a release.
> > >
> > > cheers,
> > > Rainer
> > >
> > > > 2007/9/28, Ted Husted <hu...@apache.org>:
> > > >>
> > > >> I'd like to propose 7 Oct 2007 as a tag date for the 2.1.0 version. If
> > > >> anyone would be interested in helping with the build, please don't be
> > > >> shy!
> > > >
> > > >
> > > >
> > > > Ted, sincerely I wish to wait until XWork 2.1 is released, so we don't
> > > > have
> > > > any snapshot dependency.
> > > >
> > > > Antonio
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > > For additional commands, e-mail: dev-help@struts.apache.org
> > >
> > >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
--
"Hey you! Would you help me to carry the stone?" Pink Floyd
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: 2.1.0 Build/Release Plan
Posted by Ted Husted <hu...@apache.org>.
We can have as many phases as we like. We often vote a distribution as
"beta" first, and announce it to the use list, and then depending on
that experience, vote again and reclassify the "beta" to "GA".
A key idea is that we should be releasing the same set of bits that we
tested, without change. Aside from the people here, our only other
testing group are subscribers to the Struts user mailing list. We need
to release a set of bits to that group, let everyone test it, and if
the bits are joyful, declare them GA. The quality we assign to a
release should not be a matter of personal belief, it should be
determined by what we have found through actual experience in the
field.
Of course, we could do something like distribute a set of bits tagged
as a "release candidate", and if the RC is found joyful, we could
copy or rename the tag, build a distribution from the same tag, and
call it the GA. But, of course, those would not be the same bits, only
very similar bits. Even if we assume that we can build an equivalent
distribution from the same tag under a new name, all the helpful souls
who have been using these bits in production would have to change JARs
again. An approach like this simply creates more work for everyone,
without producing a single tangible benefit. (How rude!)
If later we find a problem with a release, we should also downgrade it
from GA to beta, or Alpha. Actually, we should do this with the
releases prior to 2.0.9, since I don't think any of us would recommend
that those distributions be used in production.
-Ted.
On 10/2/07, Antonio Petrelli <an...@gmail.com> wrote:
> It is a pretty interesting process, but probably the vote call should be
> changed. There will be a "two-phase" vote, where:
> - in the first phase, we vote if we want the test build released (without
> mentioning the quality);
> - in the second phase we vote the quality.
> Thoughts?
>
> Antonio
>
--
HTH, Ted <http://www.husted.com/ted/blog/>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: 2.1.0 Build/Release Plan
Posted by Antonio Petrelli <an...@gmail.com>.
2007/10/2, Ted Husted <hu...@apache.org>:
>
> we could issue a
> XWork 2.1.0, with no hope of voting it GA, just as we want to do with
> Struts 2.1.0. Later, we could issue XW 2.1.1 and Struts 2.1.1, try
> them both together, and if all is well, vote XW GA and then Struts GA,
> without re-releasing any new artifacts.
It is a pretty interesting process, but probably the vote call should be
changed. There will be a "two-phase" vote, where:
- in the first phase, we vote if we want the test build released (without
mentioning the quality);
- in the second phase we vote the quality.
Thoughts?
Antonio
Re: 2.1.0 Build/Release Plan
Posted by Ted Husted <hu...@apache.org>.
I'd strongly prefer that XWork continue to utilize the same milestone
release system that Struts uses. Under this system, we could issue a
XWork 2.1.0, with no hope of voting it GA, just as we want to do with
Struts 2.1.0. Later, we could issue XW 2.1.1 and Struts 2.1.1, try
them both together, and if all is well, vote XW GA and then Struts GA,
without re-releasing any new artifacts.
If we had done this a year ago, we could have had a Struts GA release
in Septermber 2006, rather than February 2007.
-Ted.
On 10/2/07, Don Brown <mr...@twdata.org> wrote:
> As the Struts 2.1.0 release won't be GA, what about releasing an XWork
> 2.1-beta1 release?
>
> Don
>
> On 10/2/07, Don Brown <mr...@twdata.org> wrote:
> > I'm pretty much done, actually. The only other major thing I was
> > considering, but probably won't get to, was removing commons-logging.
> > I'll try to spend some time to help close out 2.1 issues.
> >
> > Don
> >
> > On 10/2/07, Rainer Hermanns <he...@aixcept.de> wrote:
> > > Don is busy with some important refactorings and enhancements for XWork 2.1.
> > > But I think that until these already commited changes are fully tested and
> > > stabilized, no xwork 2.1 release will happen.
> > >
> > > There are some other open xwork issues, that need to be addressed prior to
> > > a release.
> > >
> > > cheers,
> > > Rainer
> > >
> > > > 2007/9/28, Ted Husted <hu...@apache.org>:
> > > >>
> > > >> I'd like to propose 7 Oct 2007 as a tag date for the 2.1.0 version. If
> > > >> anyone would be interested in helping with the build, please don't be
> > > >> shy!
> > > >
> > > >
> > > >
> > > > Ted, sincerely I wish to wait until XWork 2.1 is released, so we don't
> > > > have
> > > > any snapshot dependency.
> > > >
> > > > Antonio
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > > For additional commands, e-mail: dev-help@struts.apache.org
> > >
> > >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
--
HTH, Ted <http://www.husted.com/ted/blog/>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: 2.1.0 Build/Release Plan
Posted by Antonio Petrelli <an...@gmail.com>.
2007/10/2, Don Brown <mr...@twdata.org>:
>
> As the Struts 2.1.0 release won't be GA, what about releasing an XWork
> 2.1-beta1 release?
Or even alpha :-)
Antonio
Re: 2.1.0 Build/Release Plan
Posted by Don Brown <mr...@twdata.org>.
As the Struts 2.1.0 release won't be GA, what about releasing an XWork
2.1-beta1 release?
Don
On 10/2/07, Don Brown <mr...@twdata.org> wrote:
> I'm pretty much done, actually. The only other major thing I was
> considering, but probably won't get to, was removing commons-logging.
> I'll try to spend some time to help close out 2.1 issues.
>
> Don
>
> On 10/2/07, Rainer Hermanns <he...@aixcept.de> wrote:
> > Don is busy with some important refactorings and enhancements for XWork 2.1.
> > But I think that until these already commited changes are fully tested and
> > stabilized, no xwork 2.1 release will happen.
> >
> > There are some other open xwork issues, that need to be addressed prior to
> > a release.
> >
> > cheers,
> > Rainer
> >
> > > 2007/9/28, Ted Husted <hu...@apache.org>:
> > >>
> > >> I'd like to propose 7 Oct 2007 as a tag date for the 2.1.0 version. If
> > >> anyone would be interested in helping with the build, please don't be
> > >> shy!
> > >
> > >
> > >
> > > Ted, sincerely I wish to wait until XWork 2.1 is released, so we don't
> > > have
> > > any snapshot dependency.
> > >
> > > Antonio
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > For additional commands, e-mail: dev-help@struts.apache.org
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: 2.1.0 Build/Release Plan
Posted by Ted Husted <hu...@apache.org>.
Thanks for keeping this going, Don. Decoupling OGNL as you've outlined
here and on the XWork Developers Forum is an important step forward.
And now that we have an XWork Developers forum, I'll start watching it
:)
On 10/2/07, Don Brown <mr...@twdata.org> wrote:
> I'm pretty much done, actually. The only other major thing I was
> considering, but probably won't get to, was removing commons-logging.
> I'll try to spend some time to help close out 2.1 issues.
>
> Don
>
> On 10/2/07, Rainer Hermanns <he...@aixcept.de> wrote:
> > Don is busy with some important refactorings and enhancements for XWork 2.1.
> > But I think that until these already commited changes are fully tested and
> > stabilized, no xwork 2.1 release will happen.
> >
> > There are some other open xwork issues, that need to be addressed prior to
> > a release.
> >
> > cheers,
> > Rainer
> >
> > > 2007/9/28, Ted Husted <hu...@apache.org>:
> > >>
> > >> I'd like to propose 7 Oct 2007 as a tag date for the 2.1.0 version. If
> > >> anyone would be interested in helping with the build, please don't be
> > >> shy!
> > >
> > >
> > >
> > > Ted, sincerely I wish to wait until XWork 2.1 is released, so we don't
> > > have
> > > any snapshot dependency.
> > >
> > > Antonio
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: 2.1.0 Build/Release Plan
Posted by Don Brown <mr...@twdata.org>.
I'm pretty much done, actually. The only other major thing I was
considering, but probably won't get to, was removing commons-logging.
I'll try to spend some time to help close out 2.1 issues.
Don
On 10/2/07, Rainer Hermanns <he...@aixcept.de> wrote:
> Don is busy with some important refactorings and enhancements for XWork 2.1.
> But I think that until these already commited changes are fully tested and
> stabilized, no xwork 2.1 release will happen.
>
> There are some other open xwork issues, that need to be addressed prior to
> a release.
>
> cheers,
> Rainer
>
> > 2007/9/28, Ted Husted <hu...@apache.org>:
> >>
> >> I'd like to propose 7 Oct 2007 as a tag date for the 2.1.0 version. If
> >> anyone would be interested in helping with the build, please don't be
> >> shy!
> >
> >
> >
> > Ted, sincerely I wish to wait until XWork 2.1 is released, so we don't
> > have
> > any snapshot dependency.
> >
> > Antonio
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: 2.1.0 Build/Release Plan
Posted by Ted Husted <hu...@apache.org>.
On 10/18/07, Antonio Petrelli <an...@gmail.com> wrote:
> 2007/10/18, Ted Husted <hu...@apache.org>:
> >
> > 0 (b) Edit the site/xdocs/index.xml file to change the "Download Now"
> > label to the pending version, and to change the "Getting Started" link
> > to also point to the pending version.
> >
> > 2 (b) Edit the site/xdocs/index.xml file to change the "Download
> > Now" label to the pending version, and to change the "Getting Started"
> > link to also point to the pending version.
>
>
>
> Errr.. this might be a stupid question but... what is the difference between
> the two?
One makes an interim change in order to tag the version, and the other
roll-back while we test the version and assign a quality grade.
> +1 (sigh), this bug seems like a big problem. Do you think that 2.0.9 should
> be flagged as "beta" then?
The way to do that would be for people to change their votes. I've
already changed my own vote for everything prior to 2.0.9. I haven't
personally verified this one myself yet, so I haven't changed my 2.0.9
vote either.
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: 2.1.0 Build/Release Plan
Posted by Antonio Petrelli <an...@gmail.com>.
2007/10/18, Ted Husted <hu...@apache.org>:
>
> 0 (b) Edit the site/xdocs/index.xml file to change the "Download Now"
> label to the pending version, and to change the "Getting Started" link
> to also point to the pending version.
>
> 2 (b) Edit the site/xdocs/index.xml file to change the "Download
> Now" label to the pending version, and to change the "Getting Started"
> link to also point to the pending version.
Errr.. this might be a stupid question but... what is the difference between
the two?
As it stands, I'd be happy to proceed with 2.1.0 as soon as we address
> WW-2264. We might also want to skip 2.0.11 for the same reason, and go
> onto 2.0.12.
+1 (sigh), this bug seems like a big problem. Do you think that 2.0.9 should
be flagged as "beta" then?
Antonio
Re: 2.1.0 Build/Release Plan
Posted by Ted Husted <hu...@apache.org>.
Just to follow up on the build issues, I broke out the items regarding
updating the S2 home page.
0 (b) Edit the site/xdocs/index.xml file to change the "Download Now"
label to the pending version, and to change the "Getting Started" link
to also point to the pending version.
2 (b) Edit the site/xdocs/index.xml file to change the "Download
Now" label to the pending version, and to change the "Getting Started"
link to also point to the pending version.
As it stands, I'd be happy to proceed with 2.1.0 as soon as we address
WW-2264. We might also want to skip 2.0.11 for the same reason, and go
onto 2.0.12.
-Ted.
On 10/17/07, Antonio Petrelli <an...@gmail.com> wrote:
> 2007/10/17, Antonio Petrelli <an...@gmail.com>:
> > https://issues.apache.org/struts/browse/WW-2258
>
> Whoops! There is also:
> https://issues.apache.org/struts/browse/WW-2259
>
> Antonio
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: 2.1.0 Build/Release Plan
Posted by Antonio Petrelli <an...@gmail.com>.
2007/10/17, Antonio Petrelli <an...@gmail.com>:
> https://issues.apache.org/struts/browse/WW-2258
Whoops! There is also:
https://issues.apache.org/struts/browse/WW-2259
Antonio
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: 2.1.0 Build/Release Plan
Posted by Antonio Petrelli <an...@gmail.com>.
2007/10/17, Ted Husted <hu...@apache.org>:
>
> If no one else is available, I'll could go ahead and roll Struts 2.1.0
> on 21 October 2007, just to get the "ball rolling". (Otherwise, I'll
> just end up posting weekly snapshots anyway.)
Sorry Ted, for not being the release manager this time. In the meantime, I
will fix the new issues:
https://issues.apache.org/struts/browse/WW-2258
and i *promise* that I will be the next release manager.
Ciao
Antonio
Re: 2.1.0 Build/Release Plan
Posted by Ted Husted <hu...@apache.org>.
On 10/17/07, Antonio Petrelli <an...@gmail.com> wrote:
> The classifier will be "backport" instead of "j4", right? BTW, the
> retrotranslator plugin for Maven 2 seems to be ok (I tried with Tiles 2), is
> there a reason not to using it?
Yes, the names are out-of-sync, and it might be simplier to just use
struts2-backport as the distribution file.
> Sorry, I cannot understand, the "index.xml" is already in the repository, so
> we could edit, commit, and then release. Do you mean that the generated "
> index.html" is replaced by the one with the same name under Confluence?
I've been hacking my local copy before uploading the files. Ideally,
we'd want to edit the index.xml, do the tagging, and then edit it back
again so that the head points to the GA release. If the pending
release goes GA, we could edit the head again.
Or, we could drop the version number from the image.
> Ted, at this point I have a question: there are some issues to be fixed
> before the release plugin could be used.
> Do you want me to fix them, and then try to release the 2.1.0 version (but
> it will take a while), or do you want to release 2.1.0 ASAP and fix these
> issues later?
> In the latter case, I think I will pass, and let Rainer do the release :-D
Once we roll the minor or major version number, there's usually four
to six milestones until we get the first GA. We've been referring
people to Struts 2.1 for new and improved features for several months
now. Since we do not have a full nightly build, it seems to be past
time that we provided a distribution. If we start now, we might have
something by early next year (e.g. February). Otherwise, we'll be
looking at late next year. (Meaning, we're back to an eighteen+ month
release cycle.)
If no one else is available, I'll could go ahead and roll Struts 2.1.0
on 21 October 2007, just to get the "ball rolling". (Otherwise, I'll
just end up posting weekly snapshots anyway.)
-Ted.
>
> Thanks
> Antonio
>
--
HTH, Ted <http://www.husted.com/ted/blog/>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: 2.1.0 Build/Release Plan
Posted by Antonio Petrelli <an...@gmail.com>.
2007/10/17, Ted Husted <hu...@apache.org>:
>
> I should mention that right now the Maven builds are not creating the
> -docs artifact or doing the J4 backports. I don't know if the release
> plugin is setup to do those too now.
Thanks for the mention :-) The release plugin won't do it automatically, so
I need to configure it in some ways (an assembly descriptor for -docs, a new
profile for J4).
(Do we even want to keep running the J4 backport for 2.1? If so, we
> might want to change the distribution artifact from -j4 to -backport,
> to match the repository.)
The classifier will be "backport" instead of "j4", right? BTW, the
retrotranslator plugin for Maven 2 seems to be ok (I tried with Tiles 2), is
there a reason not to using it?
Another "sticky wicket" is that the current version number is embedded
> in the home page for the Struts 2 area:
>
> * http://struts.apache.org/2.0.9/index.html
>
> We've been editing the docs/index.html file locally to change download
> label to version 2.0.# (<small>version 2.0.#</small>). Otherwise, when
> we archive the page, it cites the prior version rather than (what will
> be) the current version.The index page actually in the repository
> (rather than confluence), so we could also edit it before and after
> the tagging. Or, we could stop citing the version number :)
Sorry, I cannot understand, the "index.xml" is already in the repository, so
we could edit, commit, and then release. Do you mean that the generated "
index.html" is replaced by the one with the same name under Confluence?
Ted, at this point I have a question: there are some issues to be fixed
before the release plugin could be used.
Do you want me to fix them, and then try to release the 2.1.0 version (but
it will take a while), or do you want to release 2.1.0 ASAP and fix these
issues later?
In the latter case, I think I will pass, and let Rainer do the release :-D
Thanks
Antonio
Re: 2.1.0 Build/Release Plan
Posted by Ted Husted <hu...@apache.org>.
On 10/16/07, Antonio Petrelli <an...@gmail.com> wrote:
> I can be the release manager if it is ok. I would like to test the release
> plugin (and fix the problems that may arise).
That would be great, Antonio!
I should mention that right now the Maven builds are not creating the
-docs artifact or doing the J4 backports. I don't know if the release
plugin is setup to do those too now.
(Do we even want to keep running the J4 backport for 2.1? If so, we
might want to change the distribution artifact from -j4 to -backport,
to match the repository.)
Another "sticky wicket" is that the current version number is embedded
in the home page for the Struts 2 area:
* http://struts.apache.org/2.0.9/index.html
We've been editing the docs/index.html file locally to change download
label to version 2.0.# (<small>version 2.0.#</small>). Otherwise, when
we archive the page, it cites the prior version rather than (what will
be) the current version.The index page actually in the repository
(rather than confluence), so we could also edit it before and after
the tagging. Or, we could stop citing the version number :)
I'll be around this week and Monday if there are any questions. Later
next week, I'll be at the Ajax Experience in Boston, so I don't know
what my availability will be like. Of course, Rainer has been through
the Struts 2 release process too.
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: 2.1.0 Build/Release Plan
Posted by Antonio Petrelli <an...@gmail.com>.
2007/10/15, Ted Husted <hu...@apache.org>:
>
> So does anyone want to have a go at rolling 2.1.0 beta? If not, I can
> run through the numbers later this week.
I can be the release manager if it is ok. I would like to test the release
plugin (and fix the problems that may arise).
Antonio
Re: 2.1.0 Build/Release Plan
Posted by Ted Husted <hu...@apache.org>.
Thanks, Rainer.
So does anyone want to have a go at rolling 2.1.0 beta? If not, I can
run through the numbers later this week.
-Ted.
On 10/15/07, Rainer Hermanns <he...@aixcept.de> wrote:
> Sorry for the delay...
> XWork 2.1.0 was just released.
>
> I updated Struts2 pom.xml in trunk accordingly
> o bumped xwork version to 2.1.0
> o added OpenSymphony Maven2 repository
> o corrected xwork's groupId (com.opensymphony)
>
> The xwork jars are soon mirrored to the main repositories, but
> are available here [1] or as download bundle here [2].
>
> Let me know, if you need anything else.
>
> tia,
> Rainer
>
>
> [1] http://maven2.opensymphony.com/com/opensymphony/xwork/2.1.0/
> [2] https://xwork.dev.java.net/servlets/ProjectDocumentList?folderID=8173
>
> > Ted,
> > I'll try to get the release out today or tomorrow.
> >
> > cheers
> > Rainer
> >
> >> Would it be possible to create a XWork 2.1.0 for testing purposes,
> >> with the understanding that refactorings and fixes will continue with
> >> XWork 2.1.1, before a GA release.
> >>
> >> Experience has taught me to become nervous when a codebase stays in
> >> "snapshot" state this long, since there are always things that we
> >> miss, and it might be a good idea to try and get "the ball rolling"
> >> soon.
> >>
> >> -Ted.
> >>
> >> On 10/2/07, Rainer Hermanns <he...@aixcept.de> wrote:
> >>> Don is busy with some important refactorings and enhancements for XWork
> >>> 2.1.
> >>> But I think that until these already commited changes are fully tested
> >>> and
> >>> stabilized, no xwork 2.1 release will happen.
> >>>
> >>> There are some other open xwork issues, that need to be addressed prior
> >>> to
> >>> a release.
> >>>
> >>> cheers,
> >>> Rainer
> >>>
> >>> > 2007/9/28, Ted Husted <hu...@apache.org>:
> >>> >>
> >>> >> I'd like to propose 7 Oct 2007 as a tag date for the 2.1.0 version.
> >>> If
> >>> >> anyone would be interested in helping with the build, please don't
> >>> be
> >>> >> shy!
> >>> >
> >>> >
> >>> >
> >>> > Ted, sincerely I wish to wait until XWork 2.1 is released, so we
> >>> don't
> >>> > have
> >>> > any snapshot dependency.
> >>> >
> >>> > Antonio
> >>> >
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> >>> For additional commands, e-mail: dev-help@struts.apache.org
> >>>
> >>>
> >>
> >>
> >> --
> >> HTH, Ted <http://www.husted.com/ted/blog/>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> >> For additional commands, e-mail: dev-help@struts.apache.org
> >>
> >>
> >
> >
> > --
> > Rainer Hermanns
> > aixcept
> > Mariahilfstrasse 9
> > 52062 Aachen - Germany
> > w: http://aixcept.de/
> > t: +49-241-4012247
> > m: +49-170-3432912
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > For additional commands, e-mail: dev-help@struts.apache.org
> >
> >
>
>
> --
> Rainer Hermanns
> aixcept
> Mariahilfstrasse 9
> 52062 Aachen - Germany
> w: http://aixcept.de/
> t: +49-241-4012247
> m: +49-170-3432912
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
--
HTH, Ted <http://www.husted.com/ted/blog/>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: 2.1.0 Build/Release Plan
Posted by Antonio Petrelli <an...@gmail.com>.
2007/10/15, Rainer Hermanns <he...@aixcept.de>:
> Let me know, if you need anything else.
Great work Rainer!
Just a thing: could you change the svn commit comment pointing to the
WW-2151 issue?
See:
https://issues.apache.org/struts/browse/WW-2151
If you want, you can close this issue too.
Thanks
Antonio
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: 2.1.0 Build/Release Plan
Posted by Rainer Hermanns <he...@aixcept.de>.
Sorry for the delay...
XWork 2.1.0 was just released.
I updated Struts2 pom.xml in trunk accordingly
o bumped xwork version to 2.1.0
o added OpenSymphony Maven2 repository
o corrected xwork's groupId (com.opensymphony)
The xwork jars are soon mirrored to the main repositories, but
are available here [1] or as download bundle here [2].
Let me know, if you need anything else.
tia,
Rainer
[1] http://maven2.opensymphony.com/com/opensymphony/xwork/2.1.0/
[2] https://xwork.dev.java.net/servlets/ProjectDocumentList?folderID=8173
> Ted,
> I'll try to get the release out today or tomorrow.
>
> cheers
> Rainer
>
>> Would it be possible to create a XWork 2.1.0 for testing purposes,
>> with the understanding that refactorings and fixes will continue with
>> XWork 2.1.1, before a GA release.
>>
>> Experience has taught me to become nervous when a codebase stays in
>> "snapshot" state this long, since there are always things that we
>> miss, and it might be a good idea to try and get "the ball rolling"
>> soon.
>>
>> -Ted.
>>
>> On 10/2/07, Rainer Hermanns <he...@aixcept.de> wrote:
>>> Don is busy with some important refactorings and enhancements for XWork
>>> 2.1.
>>> But I think that until these already commited changes are fully tested
>>> and
>>> stabilized, no xwork 2.1 release will happen.
>>>
>>> There are some other open xwork issues, that need to be addressed prior
>>> to
>>> a release.
>>>
>>> cheers,
>>> Rainer
>>>
>>> > 2007/9/28, Ted Husted <hu...@apache.org>:
>>> >>
>>> >> I'd like to propose 7 Oct 2007 as a tag date for the 2.1.0 version.
>>> If
>>> >> anyone would be interested in helping with the build, please don't
>>> be
>>> >> shy!
>>> >
>>> >
>>> >
>>> > Ted, sincerely I wish to wait until XWork 2.1 is released, so we
>>> don't
>>> > have
>>> > any snapshot dependency.
>>> >
>>> > Antonio
>>> >
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>
>>>
>>
>>
>> --
>> HTH, Ted <http://www.husted.com/ted/blog/>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> For additional commands, e-mail: dev-help@struts.apache.org
>>
>>
>
>
> --
> Rainer Hermanns
> aixcept
> Mariahilfstrasse 9
> 52062 Aachen - Germany
> w: http://aixcept.de/
> t: +49-241-4012247
> m: +49-170-3432912
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
--
Rainer Hermanns
aixcept
Mariahilfstrasse 9
52062 Aachen - Germany
w: http://aixcept.de/
t: +49-241-4012247
m: +49-170-3432912
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: 2.1.0 Build/Release Plan
Posted by Rainer Hermanns <he...@aixcept.de>.
Ted,
I'll try to get the release out today or tomorrow.
cheers
Rainer
> Would it be possible to create a XWork 2.1.0 for testing purposes,
> with the understanding that refactorings and fixes will continue with
> XWork 2.1.1, before a GA release.
>
> Experience has taught me to become nervous when a codebase stays in
> "snapshot" state this long, since there are always things that we
> miss, and it might be a good idea to try and get "the ball rolling"
> soon.
>
> -Ted.
>
> On 10/2/07, Rainer Hermanns <he...@aixcept.de> wrote:
>> Don is busy with some important refactorings and enhancements for XWork
>> 2.1.
>> But I think that until these already commited changes are fully tested
>> and
>> stabilized, no xwork 2.1 release will happen.
>>
>> There are some other open xwork issues, that need to be addressed prior
>> to
>> a release.
>>
>> cheers,
>> Rainer
>>
>> > 2007/9/28, Ted Husted <hu...@apache.org>:
>> >>
>> >> I'd like to propose 7 Oct 2007 as a tag date for the 2.1.0 version.
>> If
>> >> anyone would be interested in helping with the build, please don't be
>> >> shy!
>> >
>> >
>> >
>> > Ted, sincerely I wish to wait until XWork 2.1 is released, so we don't
>> > have
>> > any snapshot dependency.
>> >
>> > Antonio
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> For additional commands, e-mail: dev-help@struts.apache.org
>>
>>
>
>
> --
> HTH, Ted <http://www.husted.com/ted/blog/>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
--
Rainer Hermanns
aixcept
Mariahilfstrasse 9
52062 Aachen - Germany
w: http://aixcept.de/
t: +49-241-4012247
m: +49-170-3432912
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: 2.1.0 Build/Release Plan
Posted by Ted Husted <hu...@apache.org>.
Would it be possible to create a XWork 2.1.0 for testing purposes,
with the understanding that refactorings and fixes will continue with
XWork 2.1.1, before a GA release.
Experience has taught me to become nervous when a codebase stays in
"snapshot" state this long, since there are always things that we
miss, and it might be a good idea to try and get "the ball rolling"
soon.
-Ted.
On 10/2/07, Rainer Hermanns <he...@aixcept.de> wrote:
> Don is busy with some important refactorings and enhancements for XWork 2.1.
> But I think that until these already commited changes are fully tested and
> stabilized, no xwork 2.1 release will happen.
>
> There are some other open xwork issues, that need to be addressed prior to
> a release.
>
> cheers,
> Rainer
>
> > 2007/9/28, Ted Husted <hu...@apache.org>:
> >>
> >> I'd like to propose 7 Oct 2007 as a tag date for the 2.1.0 version. If
> >> anyone would be interested in helping with the build, please don't be
> >> shy!
> >
> >
> >
> > Ted, sincerely I wish to wait until XWork 2.1 is released, so we don't
> > have
> > any snapshot dependency.
> >
> > Antonio
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
--
HTH, Ted <http://www.husted.com/ted/blog/>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: 2.1.0 Build/Release Plan
Posted by Rainer Hermanns <he...@aixcept.de>.
Don is busy with some important refactorings and enhancements for XWork 2.1.
But I think that until these already commited changes are fully tested and
stabilized, no xwork 2.1 release will happen.
There are some other open xwork issues, that need to be addressed prior to
a release.
cheers,
Rainer
> 2007/9/28, Ted Husted <hu...@apache.org>:
>>
>> I'd like to propose 7 Oct 2007 as a tag date for the 2.1.0 version. If
>> anyone would be interested in helping with the build, please don't be
>> shy!
>
>
>
> Ted, sincerely I wish to wait until XWork 2.1 is released, so we don't
> have
> any snapshot dependency.
>
> Antonio
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: 2.1.0 Build/Release Plan
Posted by Antonio Petrelli <an...@gmail.com>.
2007/9/28, Ted Husted <hu...@apache.org>:
>
> I'd like to propose 7 Oct 2007 as a tag date for the 2.1.0 version. If
> anyone would be interested in helping with the build, please don't be
> shy!
Ted, sincerely I wish to wait until XWork 2.1 is released, so we don't have
any snapshot dependency.
Antonio
Re: 2.1.0 Build/Release Plan
Posted by Don Brown <mr...@twdata.org>.
Also, I cleaned up a lot of the logging output during the unit tests,
but there still are a bunch of warnings about some properties not
being set. Is this a result of the OGNL error propagation fix? Any
way to either fix the warnings or turn them off?
Don
On 10/25/07, Don Brown <mr...@twdata.org> wrote:
> I think the problem has been fixed on trunk. Give it a go and let me know.
>
> Don
>
> On 10/25/07, Rainer Hermanns <he...@aixcept.de> wrote:
> > James,
> >
> > you need to checkout trunk, not the 2.0.x branch.
> > I can confirm the problem under OSX with -Xmx2048m.
> >
> > Rainer
> >
> > > That's odd. I have the same settings, but I'm on a Mac. Not sure if
> > > that's the reason, but I can try it on my work (XP) if you need me to.
> > >
> > >
> > > --
> > > James Mitchell
> > >
> > >
> > >
> > > On Oct 24, 2007, at 3:02 PM, Ted Husted wrote:
> > >
> > >> On 10/23/07, James Mitchell <jm...@gmail.com> wrote:
> > >>> Hmmm ... it worked fine for me.
> > >>>
> > >>> What errors are you getting?
> > >>
> > >> OOM on LabelTest (see prior message).
> > >>
> > >> On this machine, MAVEN_OPTS is set to -Xmx1024m
> > >>
> > >> I had the same problem on the desktop, and raising the Xmx didn't
> > >> seem to help.
> > >>
> > >> -Ted.
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > >> For additional commands, e-mail: dev-help@struts.apache.org
> > >>
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > > For additional commands, e-mail: dev-help@struts.apache.org
> > >
> > >
> >
> >
> > --
> > Rainer Hermanns
> > aixcept
> > Mariahilfstrasse 9
> > 52062 Aachen - Germany
> > w: http://aixcept.de/
> > t: +49-241-4012247
> > m: +49-170-3432912
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > For additional commands, e-mail: dev-help@struts.apache.org
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: 2.1.0 Build/Release Plan
Posted by Ted Husted <hu...@apache.org>.
Thanks, Don. That seems to work. I'll try running the release from my
laptop tonight. Hopefully, I have the right keys with me to sign it.
Otherwise, I'll sign it when I get back.
-Ted.
On 10/25/07, Don Brown <mr...@twdata.org> wrote:
> I think the problem has been fixed on trunk. Give it a go and let me know.
>
> Don
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: 2.1.0 Build/Release Plan
Posted by Eric Rank <er...@lo-fi.net>.
Thanks Don,
The out of memory build problem has been fixed for me as well!
Eric Rank
On Oct 25, 2007, at 4:12 AM, Don Brown wrote:
> I think the problem has been fixed on trunk. Give it a go and let
> me know.
>
> Don
Re: 2.1.0 Build/Release Plan
Posted by Don Brown <mr...@twdata.org>.
I think the problem has been fixed on trunk. Give it a go and let me know.
Don
On 10/25/07, Rainer Hermanns <he...@aixcept.de> wrote:
> James,
>
> you need to checkout trunk, not the 2.0.x branch.
> I can confirm the problem under OSX with -Xmx2048m.
>
> Rainer
>
> > That's odd. I have the same settings, but I'm on a Mac. Not sure if
> > that's the reason, but I can try it on my work (XP) if you need me to.
> >
> >
> > --
> > James Mitchell
> >
> >
> >
> > On Oct 24, 2007, at 3:02 PM, Ted Husted wrote:
> >
> >> On 10/23/07, James Mitchell <jm...@gmail.com> wrote:
> >>> Hmmm ... it worked fine for me.
> >>>
> >>> What errors are you getting?
> >>
> >> OOM on LabelTest (see prior message).
> >>
> >> On this machine, MAVEN_OPTS is set to -Xmx1024m
> >>
> >> I had the same problem on the desktop, and raising the Xmx didn't
> >> seem to help.
> >>
> >> -Ted.
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> >> For additional commands, e-mail: dev-help@struts.apache.org
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > For additional commands, e-mail: dev-help@struts.apache.org
> >
> >
>
>
> --
> Rainer Hermanns
> aixcept
> Mariahilfstrasse 9
> 52062 Aachen - Germany
> w: http://aixcept.de/
> t: +49-241-4012247
> m: +49-170-3432912
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: 2.1.0 Build/Release Plan
Posted by Rainer Hermanns <he...@aixcept.de>.
James,
you need to checkout trunk, not the 2.0.x branch.
I can confirm the problem under OSX with -Xmx2048m.
Rainer
> That's odd. I have the same settings, but I'm on a Mac. Not sure if
> that's the reason, but I can try it on my work (XP) if you need me to.
>
>
> --
> James Mitchell
>
>
>
> On Oct 24, 2007, at 3:02 PM, Ted Husted wrote:
>
>> On 10/23/07, James Mitchell <jm...@gmail.com> wrote:
>>> Hmmm ... it worked fine for me.
>>>
>>> What errors are you getting?
>>
>> OOM on LabelTest (see prior message).
>>
>> On this machine, MAVEN_OPTS is set to -Xmx1024m
>>
>> I had the same problem on the desktop, and raising the Xmx didn't
>> seem to help.
>>
>> -Ted.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> For additional commands, e-mail: dev-help@struts.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
--
Rainer Hermanns
aixcept
Mariahilfstrasse 9
52062 Aachen - Germany
w: http://aixcept.de/
t: +49-241-4012247
m: +49-170-3432912
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: 2.1.0 Build/Release Plan
Posted by James Mitchell <jm...@gmail.com>.
That's odd. I have the same settings, but I'm on a Mac. Not sure if
that's the reason, but I can try it on my work (XP) if you need me to.
--
James Mitchell
On Oct 24, 2007, at 3:02 PM, Ted Husted wrote:
> On 10/23/07, James Mitchell <jm...@gmail.com> wrote:
>> Hmmm ... it worked fine for me.
>>
>> What errors are you getting?
>
> OOM on LabelTest (see prior message).
>
> On this machine, MAVEN_OPTS is set to -Xmx1024m
>
> I had the same problem on the desktop, and raising the Xmx didn't
> seem to help.
>
> -Ted.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: 2.1.0 Build/Release Plan
Posted by Ted Husted <hu...@apache.org>.
On 10/23/07, James Mitchell <jm...@gmail.com> wrote:
> Hmmm ... it worked fine for me.
>
> What errors are you getting?
OOM on LabelTest (see prior message).
On this machine, MAVEN_OPTS is set to -Xmx1024m
I had the same problem on the desktop, and raising the Xmx didn't seem to help.
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: 2.1.0 Build/Release Plan
Posted by James Mitchell <jm...@gmail.com>.
Hmmm ... it worked fine for me.
What errors are you getting?
I just did:
[jmitchell@MBP17 ~/svn/STRUTS_2_0_X]$ mvn clean install -Pall
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Struts 2
[INFO] Struts 2 Core
[INFO] Struts Plugins
[INFO] Struts 2 Codebehind Plugin
[INFO] Struts 2 Configuration Browser Plugin
[INFO] Struts 2 Jasper Reports Plugin
[INFO] Struts 2 JFreeChart Plugin
[INFO] Struts 2 JSF Plugin
[INFO] Struts 2 Pell Multipart Plugin
[INFO] Struts 2 Plexus Plugin
[INFO] Struts 2 Sitegraph Plugin
[INFO] Struts 2 Sitemesh Plugin
[INFO] Struts 2 Spring Plugin
[INFO] Struts 2 Struts 1 Plugin
[INFO] Struts 2 Tiles Plugin
[INFO] Webapps
[INFO] Blank Webapp
[INFO] Starter Webapp
[INFO] Portlet Webapp
[INFO] Showcase Webapp
[INFO]
------------------------------------------------------------------------
----
[INFO] Building Struts 2
[INFO] task-segment: [clean, install]
[INFO]
------------------------------------------------------------------------
----
[INFO] [clean:clean]
[INFO] Deleting directory /Users/jmitchell/svn/STRUTS_2_0_X/target
[INFO] Deleting directory /Users/jmitchell/svn/STRUTS_2_0_X/target/
classes
[INFO] Deleting directory /Users/jmitchell/svn/STRUTS_2_0_X/target/
test-classes
[INFO] Deleting directory /Users/jmitchell/svn/STRUTS_2_0_X/target/site
[INFO] [site:attach-descriptor]
[WARNING] Unable to load parent project from repository: Could not
find the model file '/Users/jmitchell/svn/STRUTS_2_0_X/../pom.xml'.
[INFO] [install:install]
[INFO] Installing /Users/jmitchell/svn/STRUTS_2_0_X/pom.xml to /Users/
jmitchell/.m2/repository/org/apache/struts/struts2-parent/2.0.12-
SNAPSHOT/struts2-parent-2.0.12-SNAPSHOT.pom
[INFO]
------------------------------------------------------------------------
----
[INFO] Building Struts 2 Core
[INFO] task-segment: [clean, install]
[INFO]
------------------------------------------------------------------------
----
[INFO] [clean:clean]
[INFO] Deleting directory /Users/jmitchell/svn/STRUTS_2_0_X/core/target
[INFO] Deleting directory /Users/jmitchell/svn/STRUTS_2_0_X/core/
target/classes
...
...
<big-ass-snip/>
...
...
[INFO] [compiler:testCompile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [surefire:test]
[INFO] No tests to run.
[INFO] [war:war]
[INFO] Exploding webapp...
[INFO] Assembling webapp struts2-showcase in /Users/jmitchell/svn/
STRUTS_2_0_X/apps/showcase/target/struts2-showcase
[INFO] Copy webapp webResources to /Users/jmitchell/svn/STRUTS_2_0_X/
apps/showcase/target/struts2-showcase
[INFO] Generating war /Users/jmitchell/svn/STRUTS_2_0_X/apps/showcase/
target/struts2-showcase.war
[INFO] Building war: /Users/jmitchell/svn/STRUTS_2_0_X/apps/showcase/
target/struts2-showcase.war
[INFO] [install:install]
[INFO] Installing /Users/jmitchell/svn/STRUTS_2_0_X/apps/showcase/
target/struts2-showcase.war to /Users/jmitchell/.m2/repository/org/
apache/struts/struts2-showcase/2.0.12-SNAPSHOT/struts2-
showcase-2.0.12-SNAPSHOT.war
[INFO]
[INFO]
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
------------------------------------------------------------------------
[INFO] Struts 2 ..............................................
SUCCESS [1.919s]
[INFO] Struts 2 Core .........................................
SUCCESS [2:00.786s]
[INFO] Struts Plugins ........................................
SUCCESS [0.205s]
[INFO] Struts 2 Codebehind Plugin ............................
SUCCESS [2.152s]
[INFO] Struts 2 Configuration Browser Plugin .................
SUCCESS [0.802s]
[INFO] Struts 2 Jasper Reports Plugin ........................
SUCCESS [20.427s]
[INFO] Struts 2 JFreeChart Plugin ............................
SUCCESS [2.878s]
[INFO] Struts 2 JSF Plugin ...................................
SUCCESS [0.873s]
[INFO] Struts 2 Pell Multipart Plugin ........................
SUCCESS [0.789s]
[INFO] Struts 2 Plexus Plugin ................................
SUCCESS [0.452s]
[INFO] Struts 2 Sitegraph Plugin .............................
SUCCESS [2.944s]
[INFO] Struts 2 Sitemesh Plugin ..............................
SUCCESS [0.524s]
[INFO] Struts 2 Spring Plugin ................................
SUCCESS [2.543s]
[INFO] Struts 2 Struts 1 Plugin ..............................
SUCCESS [1.963s]
[INFO] Struts 2 Tiles Plugin .................................
SUCCESS [0.744s]
[INFO] Webapps ...............................................
SUCCESS [0.720s]
[INFO] Blank Webapp ..........................................
SUCCESS [4.200s]
[INFO] Starter Webapp ........................................
SUCCESS [2.381s]
[INFO] Portlet Webapp ........................................
SUCCESS [2.752s]
[INFO] Showcase Webapp .......................................
SUCCESS [10.384s]
[INFO]
------------------------------------------------------------------------
[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 3 minutes 1 second
[INFO] Finished at: Tue Oct 23 13:13:04 EDT 2007
[INFO] Final Memory: 21M/52M
[INFO]
------------------------------------------------------------------------
--
James Mitchell
On Oct 23, 2007, at 10:18 AM, Ted Husted wrote:
> Argh!
>
> I'm getting test-build errors on the HEAD. I don't know if these are
> the same we were having before, or a new issue. I double my heap
> setting to 2048, but no joy. So, it's probably looping.
>
> ---
>
> [#attr.templateDir]
> 2007-10-23 10:13:37,090 WARN [CommonsLogger.java:46] : Could not
> find property
> [#attr.templateDir]
> Tests run: 5, Failures: 2, Errors: 0, Skipped: 3, Time elapsed:
> 32.296 sec <<< F
> AILURE!
> Running org.apache.struts2.dispatcher.StreamResultTest
> Tests run: 12, Failures: 1, Errors: 0, Skipped: 11, Time elapsed:
> 21.157 sec <<<
> FAILURE!
> Running org.apache.struts2.views.jsp.ui.LabelTest
> org.apache.maven.surefire.booter.SurefireExecutionException: Java
> heap space; ne
> sted exception is java.lang.OutOfMemoryError: Java heap space
> java.lang.OutOfMemoryError: Java heap space
> [INFO]
> ----------------------------------------------------------------------
> --
> [ERROR] BUILD FAILURE
> [INFO]
> ----------------------------------------------------------------------
> --
> [INFO] There are test failures.
> [INFO]
> ----------------------------------------------------------------------
> --
> [INFO] For more information, run Maven with the -e switch
> [INFO]
> ----------------------------------------------------------------------
> --
> [INFO] Total time: 2 minutes 58 seconds
> [INFO] Finished at: Tue Oct 23 10:14:49 EDT 2007
> [INFO] Final Memory: 26M/47M
> [INFO]
> ----------------------------------------------------------------------
> --
>
> ---
>
> I'm on my way to Boston for the AE today. I don't think I'll be able
> to look into this myself, but someone else does, I should be able to
> roll it on my laptop there.
>
> -Ted.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: 2.1.0 Build/Release Plan
Posted by James Mitchell <jm...@gmail.com>.
I've got a little bit of time today, I'll take a look at it.
--
James Mitchell
On Oct 23, 2007, at 10:18 AM, Ted Husted wrote:
> Argh!
>
> I'm getting test-build errors on the HEAD. I don't know if these are
> the same we were having before, or a new issue. I double my heap
> setting to 2048, but no joy. So, it's probably looping.
>
> ---
>
> [#attr.templateDir]
> 2007-10-23 10:13:37,090 WARN [CommonsLogger.java:46] : Could not
> find property
> [#attr.templateDir]
> Tests run: 5, Failures: 2, Errors: 0, Skipped: 3, Time elapsed:
> 32.296 sec <<< F
> AILURE!
> Running org.apache.struts2.dispatcher.StreamResultTest
> Tests run: 12, Failures: 1, Errors: 0, Skipped: 11, Time elapsed:
> 21.157 sec <<<
> FAILURE!
> Running org.apache.struts2.views.jsp.ui.LabelTest
> org.apache.maven.surefire.booter.SurefireExecutionException: Java
> heap space; ne
> sted exception is java.lang.OutOfMemoryError: Java heap space
> java.lang.OutOfMemoryError: Java heap space
> [INFO]
> ----------------------------------------------------------------------
> --
> [ERROR] BUILD FAILURE
> [INFO]
> ----------------------------------------------------------------------
> --
> [INFO] There are test failures.
> [INFO]
> ----------------------------------------------------------------------
> --
> [INFO] For more information, run Maven with the -e switch
> [INFO]
> ----------------------------------------------------------------------
> --
> [INFO] Total time: 2 minutes 58 seconds
> [INFO] Finished at: Tue Oct 23 10:14:49 EDT 2007
> [INFO] Final Memory: 26M/47M
> [INFO]
> ----------------------------------------------------------------------
> --
>
> ---
>
> I'm on my way to Boston for the AE today. I don't think I'll be able
> to look into this myself, but someone else does, I should be able to
> roll it on my laptop there.
>
> -Ted.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: 2.1.0 Build/Release Plan
Posted by Ted Husted <hu...@apache.org>.
Argh!
I'm getting test-build errors on the HEAD. I don't know if these are
the same we were having before, or a new issue. I double my heap
setting to 2048, but no joy. So, it's probably looping.
---
[#attr.templateDir]
2007-10-23 10:13:37,090 WARN [CommonsLogger.java:46] : Could not find property
[#attr.templateDir]
Tests run: 5, Failures: 2, Errors: 0, Skipped: 3, Time elapsed: 32.296 sec <<< F
AILURE!
Running org.apache.struts2.dispatcher.StreamResultTest
Tests run: 12, Failures: 1, Errors: 0, Skipped: 11, Time elapsed: 21.157 sec <<<
FAILURE!
Running org.apache.struts2.views.jsp.ui.LabelTest
org.apache.maven.surefire.booter.SurefireExecutionException: Java heap space; ne
sted exception is java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] There are test failures.
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2 minutes 58 seconds
[INFO] Finished at: Tue Oct 23 10:14:49 EDT 2007
[INFO] Final Memory: 26M/47M
[INFO] ------------------------------------------------------------------------
---
I'm on my way to Boston for the AE today. I don't think I'll be able
to look into this myself, but someone else does, I should be able to
roll it on my laptop there.
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org