Update: the corresponding S2 issue [1] should be fixed now too (crosscheck
highly appreciated). This introduced the need to update XW dependencies to
2.0.2-SNAPSHOT. I've talked with Rainer about the release schedule for XW
- if everything works as planned, this weekend a release can be expected.
On 3/28/07, Dave Newton <[EMAIL PROTECTED]> wrote:
Is this in the
http://people.apache.org/builds/struts/2.0.7/ build?
No, the patch hasn't been applied to either the 2.0.x branch or the HEAD.
-T.
-
To unsubscribe, e-mail: [E
--- Ted Husted <[EMAIL PROTECTED]> wrote:
> It'd be especially jiggy if one or two people using
> annotations could
> look at WW-1796 and confirm that it's a good thing.
>
> * https://issues.apache.org/struts/browse/WW-1796
Is this in the
http://people.apache.org/builds/struts/2.0.7/ build?
d.
You could check the MailReader WIP into the Sandbox first,
* http://svn.apache.org/viewvc/struts/sandbox/trunk/
and when it's done, then we can decide what to do.
One way to do that would be to use SVN copy, checkout the copy, and
then paste over any files you've already changed, and check that
--- Ted Husted <[EMAIL PROTECTED]> wrote:
> You might check what you have into the sandbox, as a
> call for other volunteers. Seeing the blow by blow
in
> the Subversion logs might also be instructive for
> anyone thinking of doing the same thing with
> another application.
Oh, I didn't know (a)
You might check what you have into the sandbox, as a call for other
volunteers. Seeing the blow by blow in the Subversion logs might also
be instructive for anyone thinking of doing the same thing with
another application.
On 3/28/07, Dave Newton <[EMAIL PROTECTED]> wrote:
--- James Mitchell <[E
--- James Mitchell <[EMAIL PROTECTED]> wrote:
> Are you working on a zero-config mailreader?
I had started a conversion after the first call and
had asked about dealing with its interceptors :/ I
didn't have the annotation patches yet.
d.
_
Are you working on a zero-config mailreader?
--
James Mitchell
The Ruby Roundup
http://www.rubyroundup.com/
On Mar 28, 2007, at 4:59 AM, Dave Newton wrote:
--- Ted Husted <[EMAIL PROTECTED]> wrote:
It'd be especially jiggy if one or two people using
annotations could look at WW-1796 and con
--- Ted Husted <[EMAIL PROTECTED]> wrote:
> It'd be especially jiggy if one or two people using
> annotations could look at WW-1796 and confirm that
> it's a good thing.
>
> * https://issues.apache.org/struts/browse/WW-1796
I'll lend a pair of user-eyes to that as part of my
zero-config mailread
The build is final, and people following this thread can use it if
they choose. The grade is a matter of votes. Mine's +1 for a
test-build, since I don't believe the changes made here warrant
explaining why it's only a beta, or explaining that the i18n tag
doesn't work. But, other PMC members mig
Agreed, but that doesn't prevent us from finalizing 2.0.7 as beta though
does it? Since most of the work is already done, it seems worth putting
out there for those that prefer the other 2.0.7 fixes to the i18n tag?
Ted Husted wrote:
I doubt that there will be enough binding GA votes for the
I doubt that there will be enough binding GA votes for the release
when the i18n tag is broken. We'll just have to go on to 2.0.8 as soon
as a new XW release is available.
-Ted.
On 3/27/07, Rene Gielen <[EMAIL PROTECTED]> wrote:
I should have fixed the according XWork issue [1] for XW 2.0.2-SNA
I should have fixed the according XWork issue [1] for XW 2.0.2-SNAPSHOT.
To fix WW-1856, we have to upgrade XWork dependency.
Unfortunately, the conditions under which this issue shows up are far
from rare. Any use of the i18n tag is likely to cause troubles. I can
reproduce various cases wh
I seem to have the same issue here in a customer project, but since it is
portlet environment, I was not sure yet whether it was a porlet related issue...
- Rene
On Tue, 27 Mar 2007 10:55:27 +0200 (CEST), "Rainer Hermanns" <[EMAIL
PROTECTED]> wrote:
> James,
>
> there is a blocking error for x
Confirmed.
https://issues.apache.org/struts/browse/WW-1856
On 3/26/07, James Mitchell <[EMAIL PROTECTED]> wrote:
In trying to fix a few insignificant items in the the mailreader, and
Feel free to fix the significant items too. :)
The data access layers uses several anti-patterns, like using
James,
there is a blocking error for xwork 2.0.2 [1] that seems to be related.
I am trying to work on this the coming weekend and release xw 2.0.2
ASAP with this and other fixes.
+1 for beta
cheers,
Rainer
[1] http://jira.opensymphony.com/browse/XW-487
> In trying to fix a few insignificant it
In trying to fix a few insignificant items in the the mailreader, and
I'm seeing some weirdness in the i18n tagby weirdness, I mean
that it's broke.
Can someone confirm?
If so, my vote goes to +1 for beta.
--
James Mitchell
The Ruby Roundup
http://www.rubyroundup.com/
On Mar 21, 2007
Ted Husted wrote:
+1
[ ] Leave at test build
[ ] Alpha
[ ] Beta
[x] General Availability (GA)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
> >The vote will remain open for at least 72 hours, longer upon
>> > > > request. A vote can be amended at any time to upgrade or downgrade
>> the
>> > > > quality of the release based on future experience. If an initial
>> vote
>> >
certain obligations. A
> binding vote not only states an opinion, but means that the voter is
> agreeing to help do the work
>
> -Ted.
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e
Am Freitag, 23. März 2007 schrieb Ted Husted:
> Actually, that's perfect :)
+1 (GA) then :)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Actually, that's perfect :)
On 3/23/07, Piero Sartini <[EMAIL PROTECTED]> wrote:
I am using 2.0.7 since it became available to develop my application.
Everything works fine and there are no problems. But I am not sure if this is
enough to make a vote or if more extensive testing is expected.
Pi
I am using 2.0.7 since it became available to develop my application.
Everything works fine and there are no problems. But I am not sure if this is
enough to make a vote or if more extensive testing is expected.
Piero
-
To uns
+1 (GA)
On 3/23/07, Ted Husted <[EMAIL PROTECTED]> wrote:
There's not an actual drop-dead date. Like merit, quality votes never expire.
The 72-hour clause just means that if we had 3 +1s by then, and
nothing seemed awry, we might go ahead and announce it. Hey,
elsewhere, I've been known to ca
There's not an actual drop-dead date. Like merit, quality votes never expire.
The 72-hour clause just means that if we had 3 +1s by then, and
nothing seemed awry, we might go ahead and announce it. Hey,
elsewhere, I've been known to cast positive quality votes even weeks
after the announcement, j
User-boy here, likewise--I have a new gig and won't be
able to look at it until Sunday.
--- Philip Luppens <[EMAIL PROTECTED]> wrote:
> Same here .. it would be easier if we could extend
> the period until
> after the weekend, making it easier for those not
> able to work on S2
> during the day/w
Same here .. it would be easier if we could extend the period until
after the weekend, making it easier for those not able to work on S2
during the day/week.
Phil
On 3/23/07, James Mitchell <[EMAIL PROTECTED]> wrote:
Unfortunately, I got pulled away on a critical issue and was not able
to run t
Unfortunately, I got pulled away on a critical issue and was not able
to run through this as fully as I would have liked.
So +0 from me, unless I can find more time before the 72 hours runs out.
--
James Mitchell
The Ruby Roundup
http://www.rubyroundup.com/
On Mar 21, 2007, at 4:59 PM, Ted
certain obligations. A
> binding vote not only states an opinion, but means that the voter is
> agreeing to help do the work
>
> -Ted.
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e
The Struts 2.0.7 test build is now available.
Release notes:
* http://struts.apache.org/2.x/docs/release-notes-207.html
Distribution:
* http://people.apache.org/builds/struts/2.0.7/
The Maven 2 staging repository is not yet available, but when it
is, it will be in the u
30 matches
Mail list logo
