Re: RoughSpots ramp down
Jason +1. That would really make XWork much easier to unit test. I can help with that part of the work. - Posted via Jive Forums http://forums.opensymphony.com/thread.jspa?threadID=28543messageID=56542#56542 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: RoughSpots ramp down
Not sure about the requirements you're talking about, but it should make almost everything easier when programming to the config APIs, so I'd hazard a guess of yes. - Posted via Jive Forums http://forums.opensymphony.com/thread.jspa?threadID=28543messageID=56376#56376 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: RoughSpots ramp down
I agree - I think we should break this document down into JIRA tickets and track the discussion there. When we meet at the JavaOne BOF, we can discuss the tickets and their fix schedules further. Don Patrick Lightbody wrote: I propose that everyone get their last two cents in to the RoughSpots document today so that we can ramp down the discussions and then pick apart each issue, decide which we want/can attack right now, and come up with proposals. - Posted via Jive Forums http://forums.opensymphony.com/thread.jspa?threadID=28543messageID=55430#55430 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: RoughSpots ramp down
+1 On 5/1/06, Don Brown [EMAIL PROTECTED] wrote: I agree - I think we should break this document down into JIRA tickets and track the discussion there. When we meet at the JavaOne BOF, we can discuss the tickets and their fix schedules further. Don Patrick Lightbody wrote: I propose that everyone get their last two cents in to the RoughSpots document today so that we can ramp down the discussions and then pick apart each issue, decide which we want/can attack right now, and come up with proposals. - Posted via Jive Forums http://forums.opensymphony.com/thread.jspa?threadID=28543messageID=55430#55430 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: RoughSpots ramp down
Since I for one will most likely not be at JavaOne (though I'd like to be more for this than anything else) and I assume others will not be as well, I am wary of the idea that the JavaOne meeting would be given such importance, though understand there is so much stuff here that it is hard to type it all out. Can we discuss fix schedules in JIRA / on this list? Teleconference? :-) - Original Message From: Don Brown [EMAIL PROTECTED] To: Struts Developers List dev@struts.apache.org Sent: Monday, May 1, 2006 2:40:31 PM Subject: Re: RoughSpots ramp down I agree - I think we should break this document down into JIRA tickets and track the discussion there. When we meet at the JavaOne BOF, we can discuss the tickets and their fix schedules further. Don Patrick Lightbody wrote: I propose that everyone get their last two cents in to the RoughSpots document today so that we can ramp down the discussions and then pick apart each issue, decide which we want/can attack right now, and come up with proposals. - Posted via Jive Forums http://forums.opensymphony.com/thread.jspa?threadID=28543messageID=55430#55430 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: RoughSpots ramp down
As an Apache project, any votes and ensuing discussions must happen on the mailing list for the exact reason you mentioned.However, face-to-face meetings are good way to quickly throw out ideas and get some folks on the same page, making the list discussions quicker and more productive. You can be assured no decisions will be made outside the dev list. That said, a teleconference is still a good idea... :) Don Gabe wrote: Since I for one will most likely not be at JavaOne (though I'd like to be more for this than anything else) and I assume others will not be as well, I am wary of the idea that the JavaOne meeting would be given such importance, though understand there is so much stuff here that it is hard to type it all out. Can we discuss fix schedules in JIRA / on this list? Teleconference? :-) - Original Message From: Don Brown [EMAIL PROTECTED] To: Struts Developers List dev@struts.apache.org Sent: Monday, May 1, 2006 2:40:31 PM Subject: Re: RoughSpots ramp down I agree - I think we should break this document down into JIRA tickets and track the discussion there. When we meet at the JavaOne BOF, we can discuss the tickets and their fix schedules further. Don Patrick Lightbody wrote: I propose that everyone get their last two cents in to the RoughSpots document today so that we can ramp down the discussions and then pick apart each issue, decide which we want/can attack right now, and come up with proposals. - Posted via Jive Forums http://forums.opensymphony.com/thread.jspa?threadID=28543messageID=55430#55430 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: RoughSpots ramp down
Speaking of which, I was planning on doing some work on XWork configuration refactoring and making it runtime changeable along with removing some singletons on my flights to SFO for JavaOne... Any objections? - Posted via Jive Forums http://forums.opensymphony.com/thread.jspa?threadID=28543messageID=56095#56095 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: RoughSpots ramp down
That would be awesome. Bob On 5/1/06, Jason Carreira [EMAIL PROTECTED] wrote: Speaking of which, I was planning on doing some work on XWork configuration refactoring and making it runtime changeable along with removing some singletons on my flights to SFO for JavaOne... Any objections? - Posted via Jive Forums http://forums.opensymphony.com/thread.jspa?threadID=28543messageID=56095#56095 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: RoughSpots ramp down
Agreed. Would this make it easier/possible to have a Properties-based config and/or support wildcards? Don Bob Lee wrote: That would be awesome. Bob On 5/1/06, Jason Carreira [EMAIL PROTECTED] wrote: Speaking of which, I was planning on doing some work on XWork configuration refactoring and making it runtime changeable along with removing some singletons on my flights to SFO for JavaOne... Any objections? - Posted via Jive Forums http://forums.opensymphony.com/thread.jspa?threadID=28543messageID=56095#56095 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RoughSpots ramp down
I propose that everyone get their last two cents in to the RoughSpots document today so that we can ramp down the discussions and then pick apart each issue, decide which we want/can attack right now, and come up with proposals. - Posted via Jive Forums http://forums.opensymphony.com/thread.jspa?threadID=28543messageID=55430#55430 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
