Re: [VOTE] Struts 1.3.10 Quality

[X] General Availability (GA). Ditto. On Mon, Dec 1, 2008 at 7:23 PM, Niall Pemberton <[EMAIL PROTECTED]> wrote: > [X] General Availability (GA) > > Niall > > On Sun, Nov 30, 2008 at 9:26 PM, Paul Benedict <[EMAIL PROTECTED]> wrote: >> The Struts 1.3.10 test build is now available. >> >> Release

*grr* Sorry about the whitespace diff noise.

I've updated my IDEA settings accordingly; I wish that was a per-project setting, though. Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: other cargo problems

I'm not; things seem to be going okay. Dave --- On Sun, 11/30/08, Wes Wannemacher <[EMAIL PROTECTED]> wrote: > anyone else seeing problems with Jetty and the > rest-showcase when > building 2.1.x ? I tried last night and had trouble, but > left it go. I > tried again just now, doing a `mvn clean

Re: [VOTE] Struts 1.3.10 Quality

[X] General Availability (GA) Niall On Sun, Nov 30, 2008 at 9:26 PM, Paul Benedict <[EMAIL PROTECTED]> wrote: > The Struts 1.3.10 test build is now available. > > Release notes: > > * http://struts.apache.org/1.x/userGuide/release-notes.html > > Distribution: > > * http://people.apache.org/builds

Re: empty spaces on param names

Oh my...I double checked this time: https://issues.apache.org/struts/browse/WW-2806 musachy -- "Hey you! Would you help me to carry the stone?" Pink Floyd - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-

Re: empty spaces on param names

> Are you sure you pasted the correct link? > Why would I do that? :) https://issues.apache.org/struts/browse/WW-2893 -- "Hey you! Would you help me to carry the stone?" Pink Floyd - To unsubscribe, e-mail: [EMAIL PROTECTED] F

Re: empty spaces on param names

2008/12/1 Musachy Barroso <[EMAIL PROTECTED]>: > As this ticket states: > > http://jira.opensymphony.com/browse/XW-667 Are you sure you pasted the correct link? Regards -- Lukasz http://www.lenart.org.pl/ - To unsubscribe, e-m

empty spaces on param names

As this ticket states: http://jira.opensymphony.com/browse/XW-667 Param names with spaces are not allowed. While this makes sense for action field bindings, it doesn't for a field of type map. Is there any practical reason to exclude params with empty spaces? Here is the current regex for accepte

Re: backward compatibility and Jira

--- On Mon, 12/1/08, Musachy Barroso wrote: > I opened https://issues.apache.org/struts/browse/WW-2900, > and linked the css change to it, what was the jira ticket > for the includeParams thing? Um... WW-2901. Dave - To unsub

Re: backward compatibility and Jira

I opened https://issues.apache.org/struts/browse/WW-2900, and linked the css change to it, what was the jira ticket for the includeParams thing? musachy On Mon, Dec 1, 2008 at 10:38 AM, Dave Newton <[EMAIL PROTECTED]> wrote: > --- On Mon, 12/1/08, Musachy Barroso wrote: >> Did you find out how to

Re: backward compatibility and Jira

--- On Mon, 12/1/08, Musachy Barroso wrote: > Did you find out how to do this? I can't seem to change > anything except managing versions and components. Yeah, that's all I could do too. I think it's an admin rights thing (or possibly JIRA version). On my local JIRA I can add a custom field per-

Re: backward compatibility and Jira

> One option, I guess, would be to create a "compatibility issues" issue and > link breakers to it and pull those out somehow, but that seems a little > hacky. IIRC we can add arbitrary flags for inclusion in the issues--maybe we > could add a "incompatibility" flag and mark them that way? > Di

Re: WebSphere problems

I don't know about that in "legal" terms, but it sounds like a good idea. I can never test these websphere problems because I don't have it anywhere. musachy On Sun, Nov 30, 2008 at 11:10 PM, Wes Wannemacher <[EMAIL PROTECTED]> wrote: > Since there seem to be problems from time to time with WebSp