DO NOT REPLY [Bug 37722] - A hierarchy of ignored component still outputs the children

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Re: Milestones proposal: Step 1

On 11/30/05, Don Brown <[EMAIL PROTECTED]> wrote: > > I take it the "Target tickets to milestones" proposal passed, and thanks > for all the feedback. As the first step, could Martin or Craig please > make the following Bugzilla changes: I'll leave this thread open for a bit, to allow for discus

Milestones proposal: Step 1

I take it the "Target tickets to milestones" proposal passed, and thanks for all the feedback. As the first step, could Martin or Craig please make the following Bugzilla changes: Milestone changes - Remove all "Family" milestones - Rename "(.*) Milestone" to \1 (redundant w/o the family one

Re: svn commit: r350142 - /struts/action/trunk/src/java/org/apache/struts/action/DynaActionFormClass.java

On 11/30/05, Laurie Harper <[EMAIL PROTECTED]> wrote: > > Wendy Smoak wrote: > > On 11/30/05, Martin Cooper <[EMAIL PROTECTED]> wrote: > > > >> There was a thread somewhere recently (I'm afraid I don't recall where) > >> about going in the opposite direction, for a good reason that I don't > >> rec

Re: [PROPOSAL] Target tickets to milestones and use as roadmap

+1 (non-binding). Definitely a good way to add a lot more clarity about where things stand and what needs doing. L. Don Brown wrote: I propose we use an automated, easy to understand roadmap that relies on Bugzilla tickets marked against Milestones. With all the action in the Struts project

Re: svn commit: r350142 - /struts/action/trunk/src/java/org/apache/struts/action/DynaActionFormClass.java

Wendy Smoak wrote: On 11/30/05, Martin Cooper <[EMAIL PROTECTED]> wrote: There was a thread somewhere recently (I'm afraid I don't recall where) about going in the opposite direction, for a good reason that I don't recall. I'm hoping someone else here saw the same thing and has a better memory.

DO NOT REPLY [Bug 37730] New: - Enhanced DynaActionForms cannot be correct deserialized

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Re: svn commit: r350142 - /struts/action/trunk/src/java/org/apache/struts/action/DynaActionFormClass.java

On 11/30/05, Martin Cooper <[EMAIL PROTECTED]> wrote: > There was a thread somewhere recently (I'm afraid I don't recall where) > about going in the opposite direction, for a good reason that I don't > recall. I'm hoping someone else here saw the same thing and has a better > memory. ;-) IIRC, the

Re: [PROPOSAL] Target tickets to milestones and use as roadmap

From the peanut gallery... How we do this stuff at my day job is that we create versions in Jira for each of the milestones (which I think is what you guys are talking about) which lets us use the roadmap feature, etc.. We also create an artificial milestone called "Future" that we assign th

Re: svn commit: r350142 - /struts/action/trunk/src/java/org/apache/struts/action/DynaActionFormClass.java

On 11/30/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Author: laurieh > Date: Wed Nov 30 19:56:35 2005 > New Revision: 350142 > > URL: http://svn.apache.org/viewcvs?rev=350142&view=rev > Log: > Fix non-static Log instance, which was breaking serializability. There was a thread somewhere r

svn commit: r350142 - /struts/action/trunk/src/java/org/apache/struts/action/DynaActionFormClass.java

Author: laurieh Date: Wed Nov 30 19:56:35 2005 New Revision: 350142 URL: http://svn.apache.org/viewcvs?rev=350142&view=rev Log: Fix non-static Log instance, which was breaking serializability. Modified: struts/action/trunk/src/java/org/apache/struts/action/DynaActionFormClass.java Modified:

svn commit: r350137 - /struts/el/branches/STRUTS_1_2_BRANCH/project.xml

Author: wsmoak Date: Wed Nov 30 19:49:42 2005 New Revision: 350137 URL: http://svn.apache.org/viewcvs?rev=350137&view=rev Log: Updated for 1.2.8 and added dependency scope hints for Maven 2. Modified: struts/el/branches/STRUTS_1_2_BRANCH/project.xml Modified: struts/el/branches/STRUTS_1_2_BR

svn commit: r350131 - in /struts/action/trunk/src: java/org/apache/struts/util/DynaBeanInterceptor.java test/org/apache/struts/action/TestCGLibDynaActionForm.java

Author: laurieh Date: Wed Nov 30 19:37:06 2005 New Revision: 350131 URL: http://svn.apache.org/viewcvs?rev=350131&view=rev Log: Re-apply changes from r349286, but only generate indexed getter/setter for array-typed properties (not lists). Also fixed the log instance to be static and updated the un

Re: [PROPOSAL] Target tickets to milestones and use as roadmap

+1 for JIRA. I was going to suggest it right off the bat when the WebWorks merger was proposed but I decided to hold back since nobody seemed to like the suggestion the last time I made it ;-) Martin is right about the SVN integration. You get some nice linkage between issues and SVN revisions a

Re: CGLib DynaActioForm problem (was [VOTE] Confirm the Struts Action Library 1.3.0 release plan)

On 11/30/05, Laurie Harper <[EMAIL PROTECTED]> wrote: > > Niall Pemberton wrote: > > On 11/30/05, Laurie Harper <[EMAIL PROTECTED]> wrote: > >> Niall Pemberton wrote: > >>> On 11/29/05, Niall Pemberton <[EMAIL PROTECTED]> wrote: > On 11/29/05, Laurie Harper <[EMAIL PROTECTED]> wrote: > > N

Re: CGLib DynaActioForm problem (was [VOTE] Confirm the Struts Action Library 1.3.0 release plan)

Niall Pemberton wrote: On 11/30/05, Laurie Harper <[EMAIL PROTECTED]> wrote: Niall Pemberton wrote: On 11/29/05, Niall Pemberton <[EMAIL PROTECTED]> wrote: On 11/29/05, Laurie Harper <[EMAIL PROTECTED]> wrote: Niall Pemberton wrote: Also looked like the property types were the wrong way roun

DO NOT REPLY [Bug 37722] - A hierarchy of ignored component still outputs the children

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Re: Commit template (was [PROPOSAL] Target tickets to milestones and use as roadmap)

On 11/30/05, Don Brown <[EMAIL PROTECTED]> wrote: > > > > Niall Pemberton wrote: > > generated is a better approach to commit generated. I've started > > getting into the habit of pasting the commit url into the bug ticket > > when I close something as fixed. Thats another good way of keeping a > >

Re: [PROPOSAL] Target tickets to milestones and use as roadmap

On 11/30/05, Hubert Rabago <[EMAIL PROTECTED]> wrote: > > On 11/30/05, Don Brown <[EMAIL PROTECTED]> wrote: > > > > And a big thank you for the +1's :) Any more? > > > > Don > > > > +1. > > Any chance we can come up with a way to automatically collect the > information that we've started to put in

Re: Tough Questions on Struts and Webwork Integration

On 11/30/05, Ted Husted <[EMAIL PROTECTED]> wrote: > > Or vice-versa. :) I have a strong preference for Confluence, and > Atlassian is providing this space for use of Apache projects. I'd > like to look into making similar arrangements for use of the Jive > forums. I am very much against taking

Re: CGLib DynaActioForm problem (was [VOTE] Confirm the Struts Action Library 1.3.0 release plan)

Niall Pemberton wrote: On 11/30/05, Laurie Harper <[EMAIL PROTECTED]> wrote: Niall Pemberton wrote: On 11/29/05, Niall Pemberton <[EMAIL PROTECTED]> wrote: On 11/29/05, Laurie Harper <[EMAIL PROTECTED]> wrote: Niall Pemberton wrote: Also looked like the property types were the wrong way roun

Re: Commit template (was [PROPOSAL] Target tickets to milestones and use as roadmap)

On 11/30/05, Don Brown <[EMAIL PROTECTED]> wrote: > Hubert Rabago wrote: > > On 11/30/05, Don Brown <[EMAIL PROTECTED]> wrote: > > > >>Yeah, I've been using that changes thing with stxx for years now. I > >>believe it > >>started with Forrest. Anyways, sure, that would work too, although I'd >

Re: Commit template (was [PROPOSAL] Target tickets to milestones and use as roadmap)

Niall Pemberton wrote: generated is a better approach to commit generated. I've started getting into the habit of pasting the commit url into the bug ticket when I close something as fixed. Thats another good way of keeping a link. OT, but Trac does that for you automatically :) Don Niall

Re: Commit template (was [PROPOSAL] Target tickets to milestones and use as roadmap)

On 11/30/05, Don Brown <[EMAIL PROTECTED]> wrote: > Greg Reddin wrote: > > > > On Nov 30, 2005, at 1:49 PM, Don Brown wrote: > > > >> There was in the CVS days, and I don't believe I've seen it since. > >> I'm thinking something simple like: > >> Adding this new feature > >> PR: 234 > >> Type: (fix

Re: Commit template (was [PROPOSAL] Target tickets to milestones and use as roadmap)

Greg Reddin wrote: On Nov 30, 2005, at 1:49 PM, Don Brown wrote: There was in the CVS days, and I don't believe I've seen it since. I'm thinking something simple like: Adding this new feature PR: 234 Type: (fix, add, update, documentation) Contributed By: Sarah Jones Just a clarification

Re: Commit template (was [PROPOSAL] Target tickets to milestones and use as roadmap)

On Nov 30, 2005, at 1:49 PM, Don Brown wrote: There was in the CVS days, and I don't believe I've seen it since. I'm thinking something simple like: Adding this new feature PR: 234 Type: (fix, add, update, documentation) Contributed By: Sarah Jones Just a clarification: Are we saying ever

Re: [PROPOSAL] Target tickets to milestones and use as roadmap

What we have done with WebWork is use Confluence to generate all our documentation. Then we use the JIRA macro plugin to include all the issues. We also have a standard Confluence template for release notes, making each release consistent: http://wiki.opensymphony.com/display/WW/Previous+releases

Commit template (was [PROPOSAL] Target tickets to milestones and use as roadmap)

Hubert Rabago wrote: On 11/30/05, Don Brown <[EMAIL PROTECTED]> wrote: Yeah, I've been using that changes thing with stxx for years now. I believe it started with Forrest. Anyways, sure, that would work too, although I'd prefer even the xml to be automatically generated. What if we went back

Re: [PROPOSAL] Target tickets to milestones and use as roadmap

On 11/30/05, Niall Pemberton <[EMAIL PROTECTED]> wrote: > Maybe jira has something smarter, but I found a maven feature recently > working on Commons Resources - you can specify an "issue" number in > the change log and attribute credit ("due-to") and as long as you have > the issue tracking *forma

Re: [PROPOSAL] Target tickets to milestones and use as roadmap

On 11/30/05, Don Brown <[EMAIL PROTECTED]> wrote: > And a big thank you for the +1's :) Any more? +1 (And for automating release notes/change logs as much as possible.) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For

Re: [PROPOSAL] Target tickets to milestones and use as roadmap

Side note: I'd really like to start recognizing contributions more visibly and consistently than we do today, and I like that feature of the changes doc. I know I always have a warm fuzzy when my little patch is mentioned in a project's release notes somewhere. :) Don Don Brown wrote: Yeah,

Re: [PROPOSAL] Target tickets to milestones and use as roadmap

Yeah, I've been using that changes thing with stxx for years now. I believe it started with Forrest. Anyways, sure, that would work too, although I'd prefer even the xml to be automatically generated. What if we went back to having a commit message template that could be parsed for info like

Re: [PROPOSAL] Target tickets to milestones and use as roadmap

Hmm...we definately need to look at automating this stuff - way too much manual effort. What about writing a little webapp to manage this info? Regarding connecting commits and bugs, if we were consistent how we referred to bugs in our commit messages, we could perodically run 'svn log' then p

Re: [PROPOSAL] Target tickets to milestones and use as roadmap

On 11/30/05, Hubert Rabago <[EMAIL PROTECTED]> wrote: > On 11/30/05, Don Brown <[EMAIL PROTECTED]> wrote: > > > > And a big thank you for the +1's :) Any more? > > > > Don > > > > +1. > > Any chance we can come up with a way to automatically collect the > information that we've started to put in t

Re: [PROPOSAL] Target tickets to milestones and use as roadmap

Ted proposed before that we collect them into a "wish list" type of page on the wiki. I don't know if it still makes sense now if we'll be adopting WW anyway. If it does, though, we could start with http://issues.apache.org/bugzilla/show_bug.cgi?id=5739, maybe devote one section (or page) to it,

Re: [PROPOSAL] Target tickets to milestones and use as roadmap

On 11/30/05, Don Brown <[EMAIL PROTECTED]> wrote: > > And a big thank you for the +1's :) Any more? > > Don > +1. Any chance we can come up with a way to automatically collect the information that we've started to put in the release notes as well? The table consisting of SVN revision # and bugz

Re: [PROPOSAL] Target tickets to milestones and use as roadmap

Personally, I agree, although I know there are those that see them still as a valuable source of ideas. By emphasizing Milestones, though, they will fade into the background. I'd be in favor of a "Probably Never" resolution though :) Don Niall Pemberton wrote: On 11/30/05, Don Brown <[EMAI

Re: [PROPOSAL] Target tickets to milestones and use as roadmap

On 11/30/05, Don Brown <[EMAIL PROTECTED]> wrote: > JIRA is already on Apache servers. > > But back to the topic, what do folks think of the proposal to target tickets > to > milestones and use them for release planning? I think we should start > immediately by creating upcoming milestones, and g

DO NOT REPLY [Bug 37722] New: - A hierarchy of ignored component still outputs the children

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Re: Tough Questions on Struts and Webwork Integration

Joe Germuska wrote: There isn't directly, and this was one of the first additions I made to WebWork when I started Struts Ti. In WebWork, the servlet dispatcher does everything prior and including identifying the Action, then hands it off to the interceptor chain. My code in Struts Ti replac

Re: Tough Questions on Struts and Webwork Integration

There isn't directly, and this was one of the first additions I made to WebWork when I started Struts Ti. In WebWork, the servlet dispatcher does everything prior and including identifying the Action, then hands it off to the interceptor chain. My code in Struts Ti replaced this with a servle

Re: [PROPOSAL] Target tickets to milestones and use as roadmap

JIRA is already on Apache servers. Outstanding! +1 -- James Mitchell Software Engineer / Open Source Evangelist Consulting / Mentoring / Freelance 678.910.8017 - Original Message - From: "Don Brown" <[EMAIL PROTECTED]> To: "Struts Developers List" Sent: Wednesday, November 30, 20

Re: Tough Questions on Struts and Webwork Integration

Pilgrim, Peter wrote: If I understand you rightly the traditional `RequestProcessor' derived process flow, namely ActionServlet => RequestProcessor => Action => View is gone to be replaced by the WebWork / X Work processing chain. If someone has invested in Commons Chain command will

Re: [PROPOSAL] Target tickets to milestones and use as roadmap

Here's my (advisory-only) +1. As someone who's been working on a project (Beehive) that's always had a dependency on Struts, I think this would really help increase the transparency of the release process. Rich Patrick Lightbody wrote: >I don't think I get to vote just yet, but I'd be a big +1.

Re: [PROPOSAL] Target tickets to milestones and use as roadmap

And a big thank you for the +1's :) Any more? +1 -- Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Narrow minds are weapons made for mass destruction" -The Ex - To unsubscribe, e-mail: [EMAIL PROT

RE: Tough Questions on Struts and Webwork Integration

> -Original Message- > From: Don Brown [mailto:[EMAIL PROTECTED] ==== > > Pilgrim, Peter wrote: > > > Ok great so is Ted Husted also involved in the 2nd edition > > and I presume Manning is fine with both Struts in Action > > and Webwork in Action in the future ``merging'' as one. >

Re: [PROPOSAL] Target tickets to milestones and use as roadmap

I don't think I get to vote just yet, but I'd be a big +1. JIRA tends to encourage you to do this anyway, and I find it it is a great way to manage a project a at a low level. On 11/30/05, Don Brown <[EMAIL PROTECTED]> wrote: > Greg Reddin wrote: > > > > On Nov 30, 2005, at 11:21 AM, Don Brown wro

Re: [PROPOSAL] Target tickets to milestones and use as roadmap

Greg Reddin wrote: On Nov 30, 2005, at 11:21 AM, Don Brown wrote: But back to the topic, what do folks think of the proposal to target tickets to milestones and use them for release planning? +1. It's basically just a formalization of what we do on the wiki now, right? Kinda. When we

Re: [PROPOSAL] Target tickets to milestones and use as roadmap

On Nov 30, 2005, at 11:21 AM, Don Brown wrote: But back to the topic, what do folks think of the proposal to target tickets to milestones and use them for release planning? +1. It's basically just a formalization of what we do on the wiki now, right? I think we should start immediately

Re: [PROPOSAL] Target tickets to milestones and use as roadmap

JIRA is already on Apache servers. But back to the topic, what do folks think of the proposal to target tickets to milestones and use them for release planning? I think we should start immediately by creating upcoming milestones, and going through all our old tickets and assigning them to the

Re: [PROPOSAL] Target tickets to milestones and use as roadmap

I know we've had the Jira vs. Bugzilla discussion before, but given the size and momentum of our product(s)/community, I think the driving reasons for staying on Bugzilla are not as valid as they once were. I've had the fortune of using both on paying gigs and while Jira definitely has perks

DO NOT REPLY [Bug 37717] - struts-el-1.2.8.jar invalid in apache repsitory

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 37479] - Identify action paths

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 37719] - Add onpaste attribute to BaseFieldTag

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Re: [PROPOSAL] Target tickets to milestones and use as roadmap

Sure, moving to JIRA would also be fine. The thrust of this proposal is that we start using Milestones and targetting tickets towards them. The roadmap tool we use is a minor point. Even if we switched with JIRA, we'd still have to change how we use the ticketing system. As for switching, I

DO NOT REPLY [Bug 37717] - struts-el-1.2.8.jar invalid in apache repsitory

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 37719] New: - Add onpaste attribute to BaseFieldTag

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 37717] - struts-el-1.2.8.jar invalid in apache repsitory

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

svn commit: r349964 - /struts/action/branches/STRUTS_1_2_BRANCH/doc/project.xml

Author: niallp Date: Wed Nov 30 07:25:49 2005 New Revision: 349964 URL: http://svn.apache.org/viewcvs?rev=349964&view=rev Log: Update source repository link: change core-->action and point to STRUTS_1_2_BRANCH Modified: struts/action/branches/STRUTS_1_2_BRANCH/doc/project.xml Modified: stru

Re: [PROPOSAL] Target tickets to milestones and use as roadmap

On Nov 30, 2005, at 6:25 AM, Ted Husted wrote: Or, we could JIRA for the new projects, which supports Roadmaps directly. I think I'd be more in favor of this with Jira than Bugzilla, but I'm +0 even with Bugzilla. Greg ---

[Struts Wiki] Update of "StrutsXssVulnerability" by NiallPemberton

Dear Wiki user, You have subscribed to a wiki page or wiki category on "Struts Wiki" for change notification. The following page has been changed by NiallPemberton: http://wiki.apache.org/struts/StrutsXssVulnerability -

[Struts Wiki] Update of "StrutsUpgradeNotes127to128" by NiallPemberton

Dear Wiki user, You have subscribed to a wiki page or wiki category on "Struts Wiki" for change notification. The following page has been changed by NiallPemberton: http://wiki.apache.org/struts/StrutsUpgradeNotes127to128 -

[Struts Wiki] Update of "StrutsUpgradeNotes124to127" by NiallPemberton

Dear Wiki user, You have subscribed to a wiki page or wiki category on "Struts Wiki" for change notification. The following page has been changed by NiallPemberton: http://wiki.apache.org/struts/StrutsUpgradeNotes124to127 -

DO NOT REPLY [Bug 37717] - struts-el-1.2.8.jar invalid in apache repsitory

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Re: Clarification on Shale Framewok

I would suggest that you read the notes that Rod Johnson, the creator of Spring, on Shale for starters. Shale should be called "Huckster". On 11/29/05, Kade Jeevan Kumar <[EMAIL PROTECTED]> wrote: > Hi! > > I worked on Struts 1.1 and also on 1.2. I came across Shale framework > which is loo

DO NOT REPLY [Bug 37717] New: - struts-el-1.2.8.jar invalid in apache repsitory

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Re: [ANNOUNCEMENT][shale] Struts Shale 1.0.0 Release Candidate 1 Available

On 11/30/05, Ted Husted <[EMAIL PROTECTED]> wrote: > On 11/30/05, Niall Pemberton <[EMAIL PROTECTED]> wrote: > > IMO cross posting is incorrect in all cases - better to post separate > > "duplicate" announcements to both lists. That way threads don't get > > mixed up with people replying inadverte

Re: [ANNOUNCEMENT][shale] Struts Shale 1.0.0 Release Candidate 1 Available

On 11/30/05, Niall Pemberton <[EMAIL PROTECTED]> wrote: > IMO cross posting is incorrect in all cases - better to post separate > "duplicate" announcements to both lists. That way threads don't get > mixed up with people replying inadvertently to the wrong list, as I > did in this case. Would we

Re: [ANNOUNCEMENT][shale] Struts Shale 1.0.0 Release Candidate 1 Available

On 11/30/05, Rahul Akolkar <[EMAIL PROTECTED]> wrote: > Since I couldn't find the relevant thread(s) in the archives - What is > the intent behind not announcing on the user list? Avoiding potential > for confusion? If one goes by the premise that users are (a very > important part of) the develop

Re: [PROPOSAL] Target tickets to milestones and use as roadmap

Or, we could JIRA for the new projects, which supports Roadmaps directly. * http://tinyurl.com/8m4d6 -Ted. On 11/30/05, Don Brown <[EMAIL PROTECTED]> wrote: > I propose we use an automated, easy to understand roadmap that relies on > Bugzilla tickets marked against Milestones. > > With all the a

Re: Tough Questions on Struts and Webwork Integration

Or vice-versa. :) I have a strong preference for Confluence, and Atlassian is providing this space for use of Apache projects. I'd like to look into making similar arrangements for use of the Jive forums. -Ted. On 11/29/05, Don Brown <[EMAIL PROTECTED]> wrote: > Ted, I've started to bring some o

svn commit: r349931 - in /struts/apps/trunk/mailreader/src/webapp/WEB-INF: entities/welcome-click.xml webtest.xml

Author: husted Date: Wed Nov 30 04:19:30 2005 New Revision: 349931 URL: http://svn.apache.org/viewcvs?rev=349931&view=rev Log: MailReader - Add WebTest entity for following link back to Welcome page. Added: struts/apps/trunk/mailreader/src/webapp/WEB-INF/entities/welcome-click.xml Modified:

[EMAIL PROTECTED]: Project struts-action (in module struts) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project struts-action has an issue affecting its community integration. This issue affect

[EMAIL PROTECTED]: Project struts-action (in module struts) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project struts-action has an issue affecting its community integration. This issue affect

Re: [ANNOUNCEMENT][shale] Struts Shale 1.0.0 Release Candidate 1 Available

On 11/26/05, Craig McClanahan <[EMAIL PROTECTED]> wrote: > The purpose for a release candidate in this case is it's the first time ... > and we've already caught some packaging errors that need to be cleaned up. > Shale will follow the (overlapping and not always consistent) guidelines > posted on

CGLib DynaActioForm problem (was [VOTE] Confirm the Struts Action Library 1.3.0 release plan)

On 11/30/05, Laurie Harper <[EMAIL PROTECTED]> wrote: > Niall Pemberton wrote: > > On 11/29/05, Niall Pemberton <[EMAIL PROTECTED]> wrote: > >> On 11/29/05, Laurie Harper <[EMAIL PROTECTED]> wrote: > >>> Niall Pemberton wrote: > Also looked like the property types were the wrong way round for

Re: [PROPOSAL] Target tickets to milestones and use as roadmap

On 11/30/05, Don Brown <[EMAIL PROTECTED]> wrote: > I propose we use an automated, easy to understand roadmap that relies on > Bugzilla tickets marked against Milestones. > > With all the action in the Struts project lately, it is hard to see what > is going on where, and specifically, qualitativel