Re: [ANNOUNCEMENT] Struts 1.1 Release Candidate 2 released
This is great, great news. Thank you Martin, thank you Struts-dev. I am going to celebrate when it's out. Ted Husted wrote: Just a note on the RC2 status. Martin posted the release vote for FileUpload on Monday, and there are already 3 binding +1s. yeah!/ We've one outstanding Bugzilla ticket against RC2, which we should be able to either resolve or postpone. Given the imminent release of FU 1.0, I plan to post the Struts 1.1 Final Release vote tomorrow, so that we can roll it out on June 29. double-yeah!/ -Ted. -- Vic Cekvenich, Struts Instructor, 1-800-917-JAVA Advanced a href =baseBeans.comStruts Training/a and project recovery in North East. Open Source a href =baseBeans.comContent Management/a basicPortal sofware Best practicea href =baseBeans.comStruts Support/a v.1.1 helper ScafflodingXPress - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANNOUNCEMENT] Struts 1.1 Release Candidate 2 released
Just a note on the RC2 status. Martin posted the release vote for FileUpload on Monday, and there are already 3 binding +1s. yeah!/ We've one outstanding Bugzilla ticket against RC2, which we should be able to either resolve or postpone. Given the imminent release of FU 1.0, I plan to post the Struts 1.1 Final Release vote tomorrow, so that we can roll it out on June 29. double-yeah!/ -Ted. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem encountered after installing Struts 1.1 Release Candidate 2.
On 06/23/2003 08:43:05 PM Poon, Johnny wrote: Hi, I'm using WSAD 5.0. I just downloaded the Struts 1.1 Release Candidate 2 binary from: http://apache.mirrorcentral.com/dist/jakarta/struts/binaries/jakarta-struts- 1.1-rc1.zip. I then deleted the files of Struts 1.1 RC1 from my WSAD. I installed the RC2 by following the installation instruction in here: http://jakarta.apache.org/struts/userGuide/installation.html. WSAD then complained about my code: The method isEmpty() is undefined for the type org.apache.struts.action.ActionErrors ActionErrors.isEmpty() was working fine with the Struts RC1 binary. Have anyone encountered the same problem or am I missing something? I'd have to say that you are missing something. :) Did you rebuild your project after adding in the new Struts files? I usually just copy/replace the pertinent Struts files (actually using the system explorer) from the downloaded binaries, then refresh my project in WSAD, then rebuild the project. This process has worked well for me. Susan Bradeen JP. - 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: Problem encountered after installing Struts 1.1 Release Candidate 2.
Susan, Thanks for the reply. I discovered that somehow after copying the files to WSAD, my classpath was changed. Anyway, the problem has been solved. Thanks again. JP. -Original Message- From: Susan Bradeen [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 24, 2003 9:09 AM To: Struts Users Mailing List Subject: Re: Problem encountered after installing Struts 1.1 Release Candidate 2. On 06/23/2003 08:43:05 PM Poon, Johnny wrote: Hi, I'm using WSAD 5.0. I just downloaded the Struts 1.1 Release Candidate 2 binary from: http://apache.mirrorcentral.com/dist/jakarta/struts/binaries/jakarta-struts- 1.1-rc1.zip. I then deleted the files of Struts 1.1 RC1 from my WSAD. I installed the RC2 by following the installation instruction in here: http://jakarta.apache.org/struts/userGuide/installation.html. WSAD then complained about my code: The method isEmpty() is undefined for the type org.apache.struts.action.ActionErrors ActionErrors.isEmpty() was working fine with the Struts RC1 binary. Have anyone encountered the same problem or am I missing something? I'd have to say that you are missing something. :) Did you rebuild your project after adding in the new Struts files? I usually just copy/replace the pertinent Struts files (actually using the system explorer) from the downloaded binaries, then refresh my project in WSAD, then rebuild the project. This process has worked well for me. Susan Bradeen JP. - 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]
Problem encountered after installing Struts 1.1 Release Candidate 2.
Hi, I'm using WSAD 5.0. I just downloaded the Struts 1.1 Release Candidate 2 binary from: http://apache.mirrorcentral.com/dist/jakarta/struts/binaries/jakarta-struts- 1.1-rc1.zip. I then deleted the files of Struts 1.1 RC1 from my WSAD. I installed the RC2 by following the installation instruction in here: http://jakarta.apache.org/struts/userGuide/installation.html. WSAD then complained about my code: The method isEmpty() is undefined for the type org.apache.struts.action.ActionErrors ActionErrors.isEmpty() was working fine with the Struts RC1 binary. Have anyone encountered the same problem or am I missing something? JP. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [FRIDAY] SIA Trivia Game - Re: [ANNOUNCEMENT] Struts 1.1 Release Candidate 2 released
expletive/ I'm reading this right now. -jaafar -Original Message- From: Gemes Tibor [mailto:[EMAIL PROTECTED] Sent: Sunday, June 22, 2003 1:06 PM To: Struts Users Mailing List Subject: Re: [FRIDAY] SIA Trivia Game - Re: [ANNOUNCEMENT] Struts 1.1 Release Candidate 2 released The mother of several children may be the father of several more. If no one gets this now, then I'm *really* dating myself (so to speak). =:0) http://www.amazon.com/exec/obidos/ASIN/0441478123/ref%3Dnosim/sealarksgo odbook/002-1744259-1793629 Tib - 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: [FRIDAY] SIA Trivia Game - Re: [ANNOUNCEMENT] Struts 1.1 Release Candidate 2 released
That would be freud. Rick -Original Message- From: Ted Husted [mailto:[EMAIL PROTECTED] Sent: Saturday, June 21, 2003 4:03 PM To: Struts Users Mailing List Subject: Re: [FRIDAY] SIA Trivia Game - Re: [ANNOUNCEMENT] Struts 1.1 Release Candidate 2 released OK, here's the first clue, as to the author: Sometimes a cigar is just a cigar. And, in this case, I'll accept the author as well as the title. -Ted. Ted Husted wrote: Martin Cooper wrote: The Struts team is proud to announce the release of Struts 1.1 Release Candidate 2. As many of you know, one of the stepping stones in getting RC2 out was falling back to the 1.02 implementation of the GenericDataSource. Which brings to mind a quote from another of my favorite science fiction novels: Sometimes a step backward is step in the right direction. A signed copy of Struts in Action to person who identifies the book or author by emailing me *directly* at [EMAIL PROTECTED] . This may be a hard one, so I may have to post some clues later =:0) -Ted. -- Ted Husted, Struts in Action http://husted.com/struts/book.html - 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: [FRIDAY] SIA Trivia Game - Re: [ANNOUNCEMENT] Struts 1.1 Release Candidate 2 released
- Original Message - From: Ted Husted [EMAIL PROTECTED] To: Struts Users Mailing List [EMAIL PROTECTED] Sent: Friday, June 20, 2003 2:20 PM Subject: [FRIDAY] SIA Trivia Game - Re: [ANNOUNCEMENT] Struts 1.1 Release Candidate 2 released Martin Cooper wrote: The Struts team is proud to announce the release of Struts 1.1 Release Candidate 2. As many of you know, one of the stepping stones in getting RC2 out was falling back to the 1.02 implementation of the GenericDataSource. Which brings to mind a quote from another of my favorite science fiction novels: Sometimes a step backward is step in the right direction. I have read your book and many other tips. But I definitely miss the signature cause what I found is Two steps backward are a big step forward sometimes. A signed copy of Struts in Action to person who identifies the book or author by emailing me *directly* at [EMAIL PROTECTED] . This may be a hard one, so I may have to post some clues later =:0) -Ted. -- Ted Husted, Struts in Action http://husted.com/struts/book.html Jing - 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: [ANNOUNCEMENT] Struts 1.1 Release Candidate 2 released
I agree, thanks for making our lives easier. Go have a beer or something! -Original Message- From: Vic Cekvenich [mailto:[EMAIL PROTECTED] Sent: Monday, June 09, 2003 6:45 PM To: [EMAIL PROTECTED] Subject: Re: [ANNOUNCEMENT] Struts 1.1 Release Candidate 2 released Of course: Thanks very much Struts-Dev. for your time/talents and a gift to the community at large. .V Martin Cooper wrote: The Struts team is proud to announce the release of Struts 1.1 Release Candidate 2. This release includes some new functionality, but mostly just fixes for a number of bugs which were reported against earlier versions. The Struts Team believes that this release is ready for prime time, hence its designation as a release candidate. The binary distribution is available at: http://www.apache.org/dist/jakarta/struts/binaries/ and the source distribution is available at: http://www.apache.org/dist/jakarta/struts/source/ In addition, the library distribution, which contains updated binaries without the sample applications, is available at: http://www.apache.org/dist/jakarta/struts/library/ Details of the changes in this release are available in the Release Notes, which can be found here: http://jakarta.apache.org/struts/userGuide/release-notes-1.1-rc2.html Special thanks to Ted Husted for his help in preparing this release. -- Martin Cooper -- Vic Cekvenich, Struts Instructor, 1-800-917-JAVA Advanced a href =baseBeans.comStruts Training/a and project recovery in North East. Open Source a href =baseBeans.comContent Management/a basicPortal sofware Best practicea href =baseBeans.comStruts Support/a v.1.1 helper ScafflodingXPress - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [ANNOUNCEMENT] Struts 1.1 Release Candidate 2 released
+1 -Original Message- From: Mike Ash [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 10, 2003 9:50 AM To: 'Struts Users Mailing List' Subject: RE: [ANNOUNCEMENT] Struts 1.1 Release Candidate 2 released I agree, thanks for making our lives easier. Go have a beer or something! -Original Message- From: Vic Cekvenich [mailto:[EMAIL PROTECTED] Sent: Monday, June 09, 2003 6:45 PM To: [EMAIL PROTECTED] Subject: Re: [ANNOUNCEMENT] Struts 1.1 Release Candidate 2 released Of course: Thanks very much Struts-Dev. for your time/talents and a gift to the community at large. .V Martin Cooper wrote: The Struts team is proud to announce the release of Struts 1.1 Release Candidate 2. This release includes some new functionality, but mostly just fixes for a number of bugs which were reported against earlier versions. The Struts Team believes that this release is ready for prime time, hence its designation as a release candidate. The binary distribution is available at: http://www.apache.org/dist/jakarta/struts/binaries/ and the source distribution is available at: http://www.apache.org/dist/jakarta/struts/source/ In addition, the library distribution, which contains updated binaries without the sample applications, is available at: http://www.apache.org/dist/jakarta/struts/library/ Details of the changes in this release are available in the Release Notes, which can be found here: http://jakarta.apache.org/struts/userGuide/release-notes-1.1-rc2.html Special thanks to Ted Husted for his help in preparing this release. -- Martin Cooper -- Vic Cekvenich, Struts Instructor, 1-800-917-JAVA Advanced a href =baseBeans.comStruts Training/a and project recovery in North East. Open Source a href =baseBeans.comContent Management/a basicPortal sofware Best practicea href =baseBeans.comStruts Support/a v.1.1 helper ScafflodingXPress - 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: [ANNOUNCEMENT] Struts 1.1 Release Candidate 2 released
Well said. Great work you guys. We appreciate using such an excellent product. Enjoy the praises for this at JavaOne! :-) Tim -Original Message- From: Vic Cekvenich [mailto:[EMAIL PROTECTED] Sent: Monday, June 09, 2003 6:45 PM To: [EMAIL PROTECTED] Subject: Re: [ANNOUNCEMENT] Struts 1.1 Release Candidate 2 released Of course: Thanks very much Struts-Dev. for your time/talents and a gift to the community at large. .V Martin Cooper wrote: The Struts team is proud to announce the release of Struts 1.1 Release Candidate 2. This release includes some new functionality, but mostly just fixes for a number of bugs which were reported against earlier versions. The Struts Team believes that this release is ready for prime time, hence its designation as a release candidate. The binary distribution is available at: http://www.apache.org/dist/jakarta/struts/binaries/ and the source distribution is available at: http://www.apache.org/dist/jakarta/struts/source/ In addition, the library distribution, which contains updated binaries without the sample applications, is available at: http://www.apache.org/dist/jakarta/struts/library/ Details of the changes in this release are available in the Release Notes, which can be found here: http://jakarta.apache.org/struts/userGuide/release-notes-1.1-rc2.html Special thanks to Ted Husted for his help in preparing this release. -- Martin Cooper - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANNOUNCEMENT] Struts 1.1 Release Candidate 2 released
Of course: Thanks very much Struts-Dev. for your time/talents and a gift to the community at large. .V Martin Cooper wrote: The Struts team is proud to announce the release of Struts 1.1 Release Candidate 2. This release includes some new functionality, but mostly just fixes for a number of bugs which were reported against earlier versions. The Struts Team believes that this release is ready for prime time, hence its designation as a release candidate. The binary distribution is available at: http://www.apache.org/dist/jakarta/struts/binaries/ and the source distribution is available at: http://www.apache.org/dist/jakarta/struts/source/ In addition, the library distribution, which contains updated binaries without the sample applications, is available at: http://www.apache.org/dist/jakarta/struts/library/ Details of the changes in this release are available in the Release Notes, which can be found here: http://jakarta.apache.org/struts/userGuide/release-notes-1.1-rc2.html Special thanks to Ted Husted for his help in preparing this release. -- Martin Cooper -- Vic Cekvenich, Struts Instructor, 1-800-917-JAVA Advanced a href =baseBeans.comStruts Training/a and project recovery in North East. Open Source a href =baseBeans.comContent Management/a basicPortal sofware Best practicea href =baseBeans.comStruts Support/a v.1.1 helper ScafflodingXPress - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANNOUNCEMENT] Struts 1.1 Release Candidate 2 released
The Struts team is proud to announce the release of Struts 1.1 Release Candidate 2. This release includes some new functionality, but mostly just fixes for a number of bugs which were reported against earlier versions. The Struts Team believes that this release is ready for prime time, hence its designation as a release candidate. The binary distribution is available at: http://www.apache.org/dist/jakarta/struts/binaries/ and the source distribution is available at: http://www.apache.org/dist/jakarta/struts/source/ In addition, the library distribution, which contains updated binaries without the sample applications, is available at: http://www.apache.org/dist/jakarta/struts/library/ Details of the changes in this release are available in the Release Notes, which can be found here: http://jakarta.apache.org/struts/userGuide/release-notes-1.1-rc2.html Special thanks to Ted Husted for his help in preparing this release. -- Martin Cooper - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [ANNOUNCEMENT] Struts 1.1 Release Candidate 1 released
-Original Message- From: Martin Cooper [mailto:[EMAIL PROTECTED] Sent: 23 February 2003 09:22 To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: [ANNOUNCEMENT] Struts 1.1 Release Candidate 1 released The Struts team is proud to announce the release of Struts 1.1 Release Candidate 1. This release includes some new functionality, as well as fixes for a number of bugs which were reported against earlier versions. The Struts Team believes that this release is ready for prime time, hence its designation as a release candidate. The binary distribution is available at: http://www.apache.org/dist/jakarta/struts/binaries/ ---- Yeah! Me too. Congratulations on getting another release out of the door to all of y'all! -- Peter Pilgrim, Struts/J2EE Consultant, RBoS FM, Risk IT Tel: +44 (0)207-375-4923 Visit our Internet site at http://www.rbsmarkets.com This e-mail is intended only for the addressee named above. As this e-mail may contain confidential or privileged information, if you are not the named addressee, you are not authorised to retain, read, copy or disseminate this message or any part of it. The Royal Bank of Scotland plc is registered in Scotland No 90312 Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB Regulated by the Financial Services Authority - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANNOUNCEMENT] Struts 1.1 Release Candidate 1 released
The Struts team is proud to announce the release of Struts 1.1 Release Candidate 1. This release includes some new functionality, as well as fixes for a number of bugs which were reported against earlier versions. The Struts Team believes that this release is ready for prime time, hence its designation as a release candidate. The binary distribution is available at: http://www.apache.org/dist/jakarta/struts/binaries/ and the source distribution is available at: http://www.apache.org/dist/jakarta/struts/source/ In addition, the library distribution, which contains updated binaries without the sample applications, is available at: http://www.apache.org/dist/jakarta/struts/library/ Details of the changes in this release are available in the Release Notes, which can be found here: http://jakarta.apache.org/struts/userGuide/release-notes-1.1-rc1.html -- Martin Cooper - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [ANNOUNCEMENT] Struts 1.1 Release Candidate 1 released
I'd like to take a second to thank Martin publically for all the (relatively thankless) work he does putting together the releases. Without him slaving over a hot terminal, we'd never get these puppies out the door. James - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [ANNOUNCEMENT] Struts 1.1 Release Candidate 1 released
Thank You Martin!! :) James Turner [EMAIL PROTECTED] wrote:I'd like to take a second to thank Martin publically for all the (relatively thankless) work he does putting together the releases. Without him slaving over a hot terminal, we'd never get these puppies out the door. James - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Post your free ad now! Yahoo! Canada Personals
Struts 1.1 release
Sorry for the probably, better sure, stupid question, but I have seen an email from Craig saying that Struts 1.1 would be released at Idus of March and a :-) icon after. For the non-English speakers, and do not laught of us, please: was he joking? We can not understand the nounce of the expression, and it is important for our future planning. We would appreciate you save a set of messages paraphrasing this question. TIA, Adolfo. _ Protect your PC - get McAfee.com VirusScan Online http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963 -- To unsubscribe, e-mail: mailto:struts-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:struts-user-help;jakarta.apache.org
RE: Struts 1.1 release
Yep. It was a joke.(I hope!) March is quite a long time from now, and I think they dont have all that many bugs left to correct (you can see the list of open bugs in Bugzilla (if you can figure out how to search the darn thing effectively!)) so with luck it would be ready sometime before then? (Thats just my guess though and Im not on the dev team so I could be completely wrong!) The ides of march was the date on which Julius Ceasar was assasinated by his mates in the senate (all honourable men). He had (according to Shakespeares play about it) been warned by a soothsayer to beware the ides of march - a phrase well known to this day... See: http://www.travel-italy.com/ct/episodes/ides.html for more information on ancient Roman chronological nomenclature -Original Message- From: Adolfo Miguelez [mailto:pelly69;hotmail.com] Sent: Wednesday, November 06, 2002 18:14 To: [EMAIL PROTECTED] Subject: Struts 1.1 release Sorry for the probably, better sure, stupid question, but I have seen an email from Craig saying that Struts 1.1 would be released at Idus of March and a :-) icon after. For the non-English speakers, and do not laught of us, please: was he joking? We can not understand the nounce of the expression, and it is important for our future planning. We would appreciate you save a set of messages paraphrasing this question. TIA, Adolfo. _ Protect your PC - get McAfee.com VirusScan Online http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963 -- To unsubscribe, e-mail: mailto:struts-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:struts-user-help;jakarta.apache.org -- To unsubscribe, e-mail: mailto:struts-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:struts-user-help;jakarta.apache.org
Re: What it will take for a 1.1 release... (was RE: Struts 1.1 Release)
I think the same:-) A beta 3 would help us with the customer. Thomas At 11:08 17.10.2002 +0100, Vilya Harvey wrote: Because of all these having been incorporated, I think Struts is now way past something that should have been called a 1.1 release. According to the ... Well, a little perspective is necessary here -- Tiles and Validator have been in the 1.1 mix since well before 1.1.b2. I do believe that the EL taglibs were added after 1.1b2, so maybe there's a bit of feature creep -- but they seem real handy if you have the liberty of using JSP 1.2 (wish I did...) Don't get me wrong: I'm definitely not complaining about those features being added. I think they're great! And because it's all contributed stuff, it's not like it's taking up valuable development time that would otherwise have been spent on improving the core. My only point is that Struts is doing itself a disservice with it's current release numbering. I'm fortunate in that my company has the good sense to use 1.1 despite the fact that it's still called a beta; it seems that other readers of this list are not so fortunate. But it would be a very hard sell to convince our clients to let us use a nightly build of _anything_ in their applications. Maybe it's just about time to flag a (stable) nightly build as beta 3? I definitely agree that this would be useful. I would prefer it to go slightly further though, into being a milestone plan along the same lines as the one Mozilla has (i.e. to set out the features and bug fixes that are targetted for the next N releases, rather than just the next one). I find that gives a very clear picture of where the project is at. It does need to be kept up to date, though... Do you have any time to offer towards creating such a plan? Everybody pitches in around here... I will help in any way that I can, although my time _is_ limited. I think Mozilla has a much larger community, and does it have more people who get paid to work on it? Yes, it does, but I'm not sure how relevant that is. It needn't be a highly detailed plan: I would expect it to start off fairly general and add details as milestones get closer. Not that it's not a good goal -- just that wishing won't make it so! Agreed! Cheers, Vil. -- Vilya Harvey, Consultant [EMAIL PROTECTED] / digital steps / (W) +44 (0)1483 469 480 (M) +44 (0)7816 678 457 http://www.digitalsteps.com/ --Disclaimer-- This e-mail and any attachments may be confidential and/or legally privileged. If you have received this email and you are not a named addressee, please inform the sender at Digital Steps Ltd by phone on +44 (0)1483 469 480 or by reply email and then delete the email from your system. If you are not a named addressee you must not use, disclose, distribute, copy, print or rely on this email. Although Digital Steps Ltd routinely screens for viruses, addressees should check this email and any attachments for viruses. Digital Steps Ltd makes no representation or warranty as to the absence of viruses in this email or any attachments. -- To unsubscribe, e-mail: mailto:struts-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:struts-user-help;jakarta.apache.org -- To unsubscribe, e-mail: mailto:struts-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:struts-user-help;jakarta.apache.org
Re: What it will take for a 1.1 release... (was RE: Struts 1.1 Release)
Because of all these having been incorporated, I think Struts is now way past something that should have been called a 1.1 release. According to the ... Well, a little perspective is necessary here -- Tiles and Validator have been in the 1.1 mix since well before 1.1.b2. I do believe that the EL taglibs were added after 1.1b2, so maybe there's a bit of feature creep -- but they seem real handy if you have the liberty of using JSP 1.2 (wish I did...) Don't get me wrong: I'm definitely not complaining about those features being added. I think they're great! And because it's all contributed stuff, it's not like it's taking up valuable development time that would otherwise have been spent on improving the core. My only point is that Struts is doing itself a disservice with it's current release numbering. I'm fortunate in that my company has the good sense to use 1.1 despite the fact that it's still called a beta; it seems that other readers of this list are not so fortunate. But it would be a very hard sell to convince our clients to let us use a nightly build of _anything_ in their applications. Maybe it's just about time to flag a (stable) nightly build as beta 3? I definitely agree that this would be useful. I would prefer it to go slightly further though, into being a milestone plan along the same lines as the one Mozilla has (i.e. to set out the features and bug fixes that are targetted for the next N releases, rather than just the next one). I find that gives a very clear picture of where the project is at. It does need to be kept up to date, though... Do you have any time to offer towards creating such a plan? Everybody pitches in around here... I will help in any way that I can, although my time _is_ limited. I think Mozilla has a much larger community, and does it have more people who get paid to work on it? Yes, it does, but I'm not sure how relevant that is. It needn't be a highly detailed plan: I would expect it to start off fairly general and add details as milestones get closer. Not that it's not a good goal -- just that wishing won't make it so! Agreed! Cheers, Vil. -- Vilya Harvey, Consultant [EMAIL PROTECTED] / digital steps / (W) +44 (0)1483 469 480 (M) +44 (0)7816 678 457 http://www.digitalsteps.com/ --Disclaimer-- This e-mail and any attachments may be confidential and/or legally privileged. If you have received this email and you are not a named addressee, please inform the sender at Digital Steps Ltd by phone on +44 (0)1483 469 480 or by reply email and then delete the email from your system. If you are not a named addressee you must not use, disclose, distribute, copy, print or rely on this email. Although Digital Steps Ltd routinely screens for viruses, addressees should check this email and any attachments for viruses. Digital Steps Ltd makes no representation or warranty as to the absence of viruses in this email or any attachments. -- To unsubscribe, e-mail: mailto:struts-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:struts-user-help;jakarta.apache.org
Re: [OT] RE: Struts 1.1 Release
Perhaps Big Brother can autoreply mail contains STRUTS 1.1 RELEASE DATE ;) --- micael [EMAIL PROTECTED] a écrit : Anyone wonder why all of a sudden this question becomes so popular? At 12:47 AM 10/16/2002 -0400, you wrote: It wouldn't matter if it was plastered on the main struts page (WITH BLINKING TEXT), someone would still askLOL. James Mitchell Software Engineer/Struts Evangelist http://www.open-tools.org -Original Message- From: Andrew Hill [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 16, 2002 12:46 AM To: Struts Users Mailing List Subject: RE: Struts 1.1 Release Ye gods! Here we go again: snip The 12th of April 2156 at 15:28 in the afternoon. Or perhaps even sooner if its ready before then... ;-) /snip Hey Craig? Any chance we can get my more specific answer for this question into the FAQ? -Original Message- From: Bachan Sadanandan [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 16, 2002 05:54 To: Struts Users Mailing List Subject: Struts 1.1 Release Hi all, Any idea when Struts 1.1 would be ready for Production .??? Thanks ! Bachan -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] Micael --- This electronic mail transmission and any accompanying documents contain information belonging to the sender which may be confidential and legally privileged. This information is intended only for the use of the individual or entity to whom this electronic mail transmission was sent as indicated above. If you are not the intended recipient, any disclosure, copying, distribution, or action taken in reliance on the contents of the information contained in this transmission is strictly prohibited. If you have received this transmission in error, please delete the message. Thank you -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] ___ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: [OT] RE: Struts 1.1 Release
Hehe. Seems Im not the only one with this idea. :-) Just realised my reply on this only went to James so heres a copy to second Emmanuel's motion: snip We need a listbot to autoreply to any such message and filter it from hitting the list. Also this listbot should have a 'personality' modelled on Dogbert rather than just replying with the FAQ contents everytime ;-) Once in place we could use it to filter other things too... (ie: messages from Mark that it calculates have been sent before he has had time for his morning coffee, etc...) /snip -Original Message- From: Emmanuel Boudrant [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 16, 2002 15:51 To: Struts Users Mailing List Subject: Re: [OT] RE: Struts 1.1 Release Perhaps Big Brother can autoreply mail contains STRUTS 1.1 RELEASE DATE ;) --- micael [EMAIL PROTECTED] a écrit : Anyone wonder why all of a sudden this question becomes so popular? At 12:47 AM 10/16/2002 -0400, you wrote: It wouldn't matter if it was plastered on the main struts page (WITH BLINKING TEXT), someone would still askLOL. James Mitchell Software Engineer/Struts Evangelist http://www.open-tools.org -Original Message- From: Andrew Hill [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 16, 2002 12:46 AM To: Struts Users Mailing List Subject: RE: Struts 1.1 Release Ye gods! Here we go again: snip The 12th of April 2156 at 15:28 in the afternoon. Or perhaps even sooner if its ready before then... ;-) /snip Hey Craig? Any chance we can get my more specific answer for this question into the FAQ? -Original Message- From: Bachan Sadanandan [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 16, 2002 05:54 To: Struts Users Mailing List Subject: Struts 1.1 Release Hi all, Any idea when Struts 1.1 would be ready for Production .??? Thanks ! Bachan -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] Micael --- This electronic mail transmission and any accompanying documents contain information belonging to the sender which may be confidential and legally privileged. This information is intended only for the use of the individual or entity to whom this electronic mail transmission was sent as indicated above. If you are not the intended recipient, any disclosure, copying, distribution, or action taken in reliance on the contents of the information contained in this transmission is strictly prohibited. If you have received this transmission in error, please delete the message. Thank you -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] ___ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: What it will take for a 1.1 release... (was RE: Struts 1.1 Release)
Guys, Before I say anything more, I'd just like to say that it's great to see the discussion taking place here... From: Joe Germuska [mailto:[EMAIL PROTECTED]] Sent: 16 October 2002 00:35 To: Struts Users Mailing List Subject: What it will take for a 1.1 release... (was RE: Struts 1.1 Release) Struts committers are volunteers. That is, they get no compensation for their work on Struts. Therefore, is it so surprising that their primary motivation is pride in their work? This means that they are in no hurry to release too early. I think this is well understood and appreciated by all, and I certainly have no problem with this. I keep beating myself up about having no time to contribute anything - even writing my initial email seemed to take too much time out of my schedule - so the effort and work undertaken by all contributors is admired. Also, as volunteers, they are likely to devote their time to the most interesting problems. It appears that few of them find the formal management of the Struts development process to be a very interesting problem. This is a bigger open-ended question than the immediate discussion here that I'm sure will have many different perspectives and opinions, but I'll just put it here so that people can offer their thoughts: how far can open source projects based on the work of volunteers, or more specifically (Jakarta/XML/etc) Apache projects go towards following the formalised development process, e.g. as we have to follow for our applications in our strictly controlled environments? What are the practical barriers to this:| e.g. dependence on lack of people willing and/or able to take on this boring stuff. How does this affect take up of such products in large organisations - e.g. off the top of my head, I can think of about 10 projects in my immediate area, leaving aside the many others here, that would I could get to start adopting Struts 1.1 if I could make it available to them. That said, Struts components like Tiles, Validator, and most recently, the EL version of the tag libraries were all dreamed up by someone who saw a need, and they were adopted into Struts because those people committed their own energy to making something happen. Perhaps what Struts needs are some people who are interested in managing the development process enough that they'll donate time and energy to it. Or perhaps there will be a company that finds Struts promising enough that it will endorse some of its staff spending time and energy while on the job? I think you've identified one of the requirements, but as we've all noted, the reality dictates that this will be very difficult. The latter part is another battle that we're fighting about how to allow our developers to contribute components we write as part of our development of our applications back into open source projects without breaking our policies and raising concerns on intellectual property rights. I don't know of any official versioning policy besides the vision of the committers. Perhaps they would concede that it would be OK to release Struts 1.1 sooner with the understanding that there might be a Struts 1.1.1 later. Then again, they probably think that anyway, and they just believe that Struts 1.1 isn't ready yet. It would be very useful to get some clarification of what the current take on this is... The Release Plan page on the Jakarta site lists the bugs which are officially targeted for a 1.1 release. However, it's pretty out of date. Perhaps turning this into a living document would be a good volunteer opportunity? I think this is a good idea - would be somewhere where people could just go and know that they an clear and accurate picture of the current release status, which they can take back into their discussions. Do others agree, and that this is possible and practical? It turns out that only two are actually new and open (10537, 7353), plus one which was reassigned to Commons Validator and switched to an enhancement. (10584) (details below, since I was taking notes in my email client...) From that, you'd think a 1.1 release was just around the corner!! However, it's not going to be that easy. My Bugzilla query turns up 39 non-Enhancement open bugs against Struts. Some of these are very old and may no longer be relevant. (For example, a few refer to the original File Upload piece, while Struts now uses commons-fileupload.) Maybe the first step would be to draft a release plan, even if it had no specific date on it, if only to track the bugs which were considered critical fixes for a full release. A question for committers: is this something you feel you should draft? Or would you accept a draft from a volunteer? (For the next edition of the release plan that gets posted on the site, I'd suggesting putting HTML links straight into bugzilla for each issue, to make it easier for people to track things.) Another significant issue
Re: What it will take for a 1.1 release... (was RE: Struts 1.1 Release)
From: Joe Germuska [mailto:[EMAIL PROTECTED]] ... From that, you'd think a 1.1 release was just around the corner!! However, it's not going to be that easy. My Bugzilla query turns up 39 non-Enhancement open bugs against Struts. Some of these are very old and may no longer be relevant. (For example, a few refer to the original File Upload piece, while Struts now uses commons-fileupload.) After reading this, I took a quick look at Bugzilla. It seems that a lot of the bugs still marked as 'open' have actually had patches submitted. I don't know if this is because the patches were found to be incorrect, but I didn't see any comment to that effect during my quick trawl. So maybe the problem is that bugs just aren't being closed when they're fixed. That said, Struts components like Tiles, Validator, and most recently, the EL version of the tag libraries were all dreamed up by someone who saw a need, and they were adopted into Struts because those people committed their own energy to making something happen. Because of all these having been incorporated, I think Struts is now way past something that should have been called a 1.1 release. According to the release plan document, 1.1 beta 2 was supposed to be feature-complete; the intent was to provide a stable base for bugfixes and documentation updates, leading to the 1.1 final release. As someone pointed out earlier in this thread, now that all of this additional (wonderful!) functionality has been added it's much more like a 2.0 release. From: [EMAIL PROTECTED] ... The Release Plan page on the Jakarta site lists the bugs which are officially targeted for a 1.1 release. However, it's pretty out of date. Perhaps turning this into a living document would be a good volunteer opportunity? I think this is a good idea - would be somewhere where people could just go and know that they an clear and accurate picture of the current release status, which they can take back into their discussions. Do others agree, and that this is possible and practical? I definitely agree that this would be useful. I would prefer it to go slightly further though, into being a milestone plan along the same lines as the one Mozilla has (i.e. to set out the features and bug fixes that are targetted for the next N releases, rather than just the next one). I find that gives a very clear picture of where the project is at. It does need to be kept up to date, though... Vil. -- Vilya Harvey, Consultant [EMAIL PROTECTED] / digital steps / (W) +44 (0)1483 469 480 (M) +44 (0)7816 678 457 http://www.digitalsteps.com/ --Disclaimer-- This e-mail and any attachments may be confidential and/or legally privileged. If you have received this email and you are not a named addressee, please inform the sender at Digital Steps Ltd by phone on +44 (0)1483 469 480 or by reply email and then delete the email from your system. If you are not a named addressee you must not use, disclose, distribute, copy, print or rely on this email. Although Digital Steps Ltd routinely screens for viruses, addressees should check this email and any attachments for viruses. Digital Steps Ltd makes no representation or warranty as to the absence of viruses in this email or any attachments. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Struts 1.1 Release
I agree on all these points... I had a heck of a time getting them to agree to develop on struts while it was a beta... I really did not want to go back to 1.0 Part of me still wants to keep a beta program in place though -Original Message- From: Andrew Hill [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 15, 2002 10:44 PM To: Struts Users Mailing List Subject: RE: Struts 1.1 Release I am rather of the opinion that the struts versioning nomenclature is a wee bit on the humble side. This beta release of 1.1 is pretty stable. I dont see why you cant just loosen up your standards a bit and call it 1.1 , then when all the bugs are fixed call that 1.2 , etc... For 'bigger' or more stable version changes use bigger numbers. Really 1.1 is so much better then 1.02 that you should be calling it 2.0 when it is released (and the current beta releases should be something like 1.99) That will help keep the corporate monkeys off peoples backs and lead to more impressively high sounding version numbers. :-) -Original Message- From: news [mailto:[EMAIL PROTECTED]]On Behalf Of V. Cekvenich Sent: Wednesday, October 16, 2002 08:36 To: [EMAIL PROTECTED] Subject: Re: Struts 1.1 Release [EMAIL PROTECTED] wrote: I totally understand and agree with the release policy, but I think it's worth remembering that a lot of these questions are driven by the constraints of users' environments - e.g. in corporate environments like ours, there any many people like myself continually fighting to get great open source products like Struts into the organisation so that development teams can use them, and the latest versions of them. However, this has to be done within the processes and policies that apply to any third party software, commercial or otherwise. Not trying to whine - but I fight the same battles. I work for a big, conservative company. Telling people it's a 'beta' release - regardless of what that means - makes it much more difficult to get things approved. Probably a greater percentage of your users than you realize are still using 1.02 for the sole reason that 1.1 is still called 'beta'. Worse, probably a lot of projects have started off that had to use 1.02 because it was the 'stable release' - and then the development teams struggled. I saw one project dump struts because they had trouble getting it to do what they wanted (they were forced to use 1.02). IMO, That could not possibly be a source of failure. I and others had 1.02 projects just fine! Statistically 80% of projects fail due to requirements, so that would be my first guess. (More numbers? most projects fail period, and that 99% of code in production is written by 1% of programmers) If they had tech issues, they could have gone with a experienced mentor who has had Struts code in production before, which is cost effective. And one needs to ask, why use open source? http://www.opensource.org/advocacy/case_for_business.php Because it is *better* quality is one good reason. my 2c, .V -- - This e-mail message (including attachments, if any) is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, proprietary , confidential and exempt from disclosure. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender and erase this e-mail message immediately. -- - -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Struts 1.1 Release
Really 1.1 is so much better then 1.02 that you should be calling it 2.0 when it is released (and the current beta releases should be something like 1.99) Of course Java is at 1.4.1. How similar is 1.4 to 1.0? And why do they call 1.2+ Java 2? Why didn't they just call it Java 2.0? Will there ever be a Java 2.0 or will it just go to 1.100? Coming from a Microsoft background (and finally seeing the light), I'm not familiar with the strange versioning strategy in the Java Community and it's always baffled me. At our company we release a new major version every year whether we need to or not. I'm working to evangelize things like Struts and open source in general, and part of that may be trying to change the perception of release names, and words like beta. Greg -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Struts 1.1 Release
On Wed, 16 Oct 2002 [EMAIL PROTECTED] wrote: Date: Wed, 16 Oct 2002 09:21:04 -0500 From: [EMAIL PROTECTED] Reply-To: Struts Users Mailing List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: RE: Struts 1.1 Release Really 1.1 is so much better then 1.02 that you should be calling it 2.0 when it is released (and the current beta releases should be something like 1.99) Of course Java is at 1.4.1. How similar is 1.4 to 1.0? And why do they call 1.2+ Java 2? Why didn't they just call it Java 2.0? Will there ever be a Java 2.0 or will it just go to 1.100? Coming from a Microsoft background (and finally seeing the light), I'm not familiar with the strange versioning strategy in the Java Community and it's always baffled me. At our company we release a new major version every year whether we need to or not. I'm working to evangelize things like Struts and open source in general, and part of that may be trying to change the perception of release names, and words like beta. Every product strategy is different, but most Java projects I'm familiar with or involved in don't flip the major version number unless there are significant backwards incompatibilities and/or very substantial new features. By that rule, we could have called it Struts 2.0 instead, but I want to emphasize the fact that 1.0 based apps should generally run fine in 1.1 unless you're doing some really intricate things. (In other words, the engineers picked the version number instead of the marketing folks :-). For future versions of Struts, I'd likely support the x.y.z style that Tomcat 4.1 (and Apache httpd server releases) use, where you do a milestone with no implied quality label at all, and it's then assigned an alpha, beta, or general availability label after the fact, based on feedback. But it's too late in the 1.1 cycle to change things that radically this time around. Greg Craig -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Struts 1.1 Release
Poss diff for front page? $ diff -n index.html nextstrutsversionindex.html d45 3 a47 8 a name=Welcome/atable width=100% cellpadding=5 cellspacing=5 border=0trtd bgcolor=#023264font size=+1 face=arial,helvetica,sanserif color=#ffstrongWelcome to Stru ts/strong/font/td/trtrtdblockquote h1THE NEXT VERSION OF STRUTS WILL BE RELEASED WHEN THE CUURENTLY OPEN BUGS ARE DEALTH WITH/h1 pWelcome to Struts! The goal of this project is to provide an chanoch - The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. Although we routinely screen for viruses, recipients should check this e-mail and any attachment for viruses. We make no warranty as to absence of viruses in this e-mail or any attachments. -Original Message- From: James Mitchell [mailto:[EMAIL PROTECTED]] Sent: 16 October 2002 05:47 To: Struts Users Mailing List; [EMAIL PROTECTED] Subject: RE: Struts 1.1 Release It wouldn't matter if it was plastered on the main struts page (WITH BLINKING TEXT), someone would still askLOL. James Mitchell Software Engineer/Struts Evangelist http://www.open-tools.org -Original Message- From: Andrew Hill [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 16, 2002 12:46 AM To: Struts Users Mailing List Subject: RE: Struts 1.1 Release Ye gods! Here we go again: snip The 12th of April 2156 at 15:28 in the afternoon. Or perhaps even sooner if its ready before then... ;-) /snip Hey Craig? Any chance we can get my more specific answer for this question into the FAQ? -Original Message- From: Bachan Sadanandan [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 16, 2002 05:54 To: Struts Users Mailing List Subject: Struts 1.1 Release Hi all, Any idea when Struts 1.1 would be ready for Production .??? Thanks ! Bachan -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Struts 1.1 Release
but I want to emphasize the fact that 1.0 based apps should generally run fine in 1.1 unless you're doing some really intricate things. That's a good point. You'd hate to imply to 1.0.2 users that their stuff won't run on the next version. For future versions of Struts, I'd likely support the x.y.z style that Tomcat 4.1 (and Apache httpd server releases) use, where you do a milestone with no implied quality label at all, and it's then assigned an alpha, beta, or general availability label after the fact, based on feedback. I see a lot of value in this approach. It sort of avoids the whole issue that beta seems to mean something different with open source, or at least Apache products than it does with commercial stuff. Greg -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Struts 1.1 Release
Maybe you could pronounce beta as better everytime you talk to people ;-) Perhaps we could have a label for those builds that are noted as being more stable. Something along the lines of 'Very High Stability', so you would have: struts1.1-beta and struts1.1-VHS Seriously though I find the versioning in the Java world quite ridiculous. The marketing guys at Sun had the right idea with Java2 - the actual JVM versions really ought to follow this! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 16, 2002 22:21 To: [EMAIL PROTECTED] Subject: RE: Struts 1.1 Release Really 1.1 is so much better then 1.02 that you should be calling it 2.0 when it is released (and the current beta releases should be something like 1.99) Of course Java is at 1.4.1. How similar is 1.4 to 1.0? And why do they call 1.2+ Java 2? Why didn't they just call it Java 2.0? Will there ever be a Java 2.0 or will it just go to 1.100? Coming from a Microsoft background (and finally seeing the light), I'm not familiar with the strange versioning strategy in the Java Community and it's always baffled me. At our company we release a new major version every year whether we need to or not. I'm working to evangelize things like Struts and open source in general, and part of that may be trying to change the perception of release names, and words like beta. Greg -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Struts 1.1 Release
Hi all, Any idea when Struts 1.1 would be ready for Production .??? Thanks ! Bachan -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Struts 1.1 Release
Were you subscribed to the mailing list earlier today when this was discussed? Struts 1.1 will be released when it's released. Period. No variation from that. That said, even the beta versions of Struts far exceed other software in terms of usefulness and reliability, so don't worry about formal release dates and just start using the thing. Simon - Simon P. Chappell [EMAIL PROTECTED] Java Programming Specialist www.landsend.com Lands' End, Inc. (608) 935-4526 -Original Message- From: Bachan Sadanandan [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 15, 2002 4:54 PM To: Struts Users Mailing List Subject: Struts 1.1 Release Hi all, Any idea when Struts 1.1 would be ready for Production .??? Thanks ! Bachan -- To unsubscribe, e-mail: mailto:struts-user-[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Struts 1.1 Release
Wow, 2 of these questions in one day! Please don't ask this again, search the archives or the jakarta site for the release policy. David From: Bachan Sadanandan [EMAIL PROTECTED] Reply-To: Struts Users Mailing List [EMAIL PROTECTED] To: Struts Users Mailing List [EMAIL PROTECTED] Subject: Struts 1.1 Release Date: Tue, 15 Oct 2002 14:53:49 -0700 Hi all, Any idea when Struts 1.1 would be ready for Production .??? Thanks ! Bachan -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] _ Surf the Web without missing calls! Get MSN Broadband. http://resourcecenter.msn.com/access/plans/freeactivation.asp -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Struts 1.1 Release
OK guys, be gentle... -Original Message- From: Bachan Sadanandan [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 15, 2002 4:54 PM To: Struts Users Mailing List Subject: Struts 1.1 Release Hi all, Any idea when Struts 1.1 would be ready for Production .??? Thanks ! Bachan -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Struts 1.1 Release
Thanks .I wanted to know how stable it is .??? Thanks for your feedback... -Original Message- From: Chap October 15, 2002 2:58 PM To: Struts Users Mailing List Subject: RE: Struts 1.1 Release Were you subscribed to the mailing list earlier today when this was discussed? Struts 1.1 will be released when it's released. Period. No variation from that. That said, even the beta versions of Struts far exceed other software in terms of usefulness and reliability, so don't worry about formal release dates and just start using the thing. Simon - Simon P. Chappell [EMAIL PROTECTED] Java Programming Specialist www.landsend.com Lands' End, Inc. (608) 935-4526 -Original Message- From: Bachan Sadanandan [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 15, 2002 4:54 PM To: Struts Users Mailing List Subject: Struts 1.1 Release Hi all, Any idea when Struts 1.1 would be ready for Production .??? Thanks ! Bachan -- To unsubscribe, e-mail: mailto:struts-user-[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Struts 1.1 Release
Any idea when Struts 1.1 would be ready for Production .??? Is this like when the guy asks for water in the movie 'Coyote Ugly'? ;) http://jakarta.apache.org/struts/userGuide/kickstart.html#release -- Wendy
RE: Struts 1.1 Release
I totally understand and agree with the release policy, but I think it's worth remembering that a lot of these questions are driven by the constraints of users' environments - e.g. in corporate environments like ours, there any many people like myself continually fighting to get great open source products like Struts into the organisation so that development teams can use them, and the latest versions of them. However, this has to be done within the processes and policies that apply to any third party software, commercial or otherwise. Specifically, in our case, I am the product owner of Struts here among other products from the Apache family of projects here and it is my responsibility to make the standard builds of Struts on our software distribution servers so that development can reference this for use by their applications, as must be done for all external software (it's an audit point). However, in order to do this, I must get the new version approved by a central department which is extremely difficult, if not impossible for software that is tagged as beta regardless of the quality. (Yes, you can imagine how commercial software vendors deal with this in their versioning policy... :-( ) Therefore, all our applications are currently stuck on v1.0.2 rather than the latest and greatest 1.1 regardless of how stable it may be in practice. I know that we are not alone in this kind of approach, and that this kind of situation and red tape is the reality in big organisations... Working in one of our architecture teams, I advise application development teams in our area when it comes to working out and implementing their roadmaps, and part of this requires the recommendation of technologies on the basis of an understanding of when certain products such as Struts can be made available for their use - this applies equally to any kind of software. So I would be interested in hearing any suggestions about how we could resolve the need for us to have a better understanding of how close we are to a final release of any given version, e.g. clearly listing the issues that are preventing a release being deemed as 1.1 quality on the website? Would it be possible to change the versioning policy so that more non-beta dot releases are made possible, since many components are known to have no issues? These are just some ideas - they may well not be workable but I would like to know what could be done, since it is very frustrating for me and others like me to play with great beta products and rave about them to colleagues, but not be able to make them available for use by their applications - this ultimately results in a lack of interest and apathy towards such products, which is a great shame given their quality. Hope something useful can come out of this! Best regards, Kosh -Original Message- From: Chappell, Simon P [mailto:[EMAIL PROTECTED]] Sent: 15 October 2002 22:58 To: Struts Users Mailing List Subject: RE: Struts 1.1 Release Were you subscribed to the mailing list earlier today when this was discussed? Struts 1.1 will be released when it's released. Period. No variation from that. That said, even the beta versions of Struts far exceed other software in terms of usefulness and reliability, so don't worry about formal release dates and just start using the thing. Simon - Simon P. Chappell [EMAIL PROTECTED] Java Programming Specialist www.landsend.com Lands' End, Inc. (608) 935-4526 -Original Message- From: Bachan Sadanandan [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 15, 2002 4:54 PM To: Struts Users Mailing List Subject: Struts 1.1 Release Hi all, Any idea when Struts 1.1 would be ready for Production .??? Thanks ! Bachan -- To unsubscribe, e-mail: mailto:struts-user-[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] Visit our website at http://www.ubswarburg.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed
RE: Struts 1.1 Release
Hi Kosh , I understand your concern and we are also facing the same dilemma about using the Beta Version and also future of Struts in the light of JSF release. Thanks ! Bachan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 15, 2002 3:26 PM To: [EMAIL PROTECTED] Subject: RE: Struts 1.1 Release I totally understand and agree with the release policy, but I think it's worth remembering that a lot of these questions are driven by the constraints of users' environments - e.g. in corporate environments like ours, there any many people like myself continually fighting to get great open source products like Struts into the organisation so that development teams can use them, and the latest versions of them. However, this has to be done within the processes and policies that apply to any third party software, commercial or otherwise. Specifically, in our case, I am the product owner of Struts here among other products from the Apache family of projects here and it is my responsibility to make the standard builds of Struts on our software distribution servers so that development can reference this for use by their applications, as must be done for all external software (it's an audit point). However, in order to do this, I must get the new version approved by a central department which is extremely difficult, if not impossible for software that is tagged as beta regardless of the quality. (Yes, you can imagine how commercial software vendors deal with this in their versioning policy... :-( ) Therefore, all our applications are currently stuck on v1.0.2 rather than the latest and greatest 1.1 regardless of how stable it may be in practice. I know that we are not alone in this kind of approach, and that this kind of situation and red tape is the reality in big organisations... Working in one of our architecture teams, I advise application development teams in our area when it comes to working out and implementing their roadmaps, and part of this requires the recommendation of technologies on the basis of an understanding of when certain products such as Struts can be made available for their use - this applies equally to any kind of software. So I would be interested in hearing any suggestions about how we could resolve the need for us to have a better understanding of how close we are to a final release of any given version, e.g. clearly listing the issues that are preventing a release being deemed as 1.1 quality on the website? Would it be possible to change the versioning policy so that more non-beta dot releases are made possible, since many components are known to have no issues? These are just some ideas - they may well not be workable but I would like to know what could be done, since it is very frustrating for me and others like me to play with great beta products and rave about them to colleagues, but not be able to make them available for use by their applications - this ultimately results in a lack of interest and apathy towards such products, which is a great shame given their quality. Hope something useful can come out of this! Best regards, Kosh -Original Message- From: Chappell, Simon P [mailto:[EMAIL PROTECTED]] Sent: 15 October 2002 22:58 To: Struts Users Mailing List Subject: RE: Struts 1.1 Release Were you subscribed to the mailing list earlier today when this was discussed? Struts 1.1 will be released when it's released. Period. No variation from that. That said, even the beta versions of Struts far exceed other software in terms of usefulness and reliability, so don't worry about formal release dates and just start using the thing. Simon - Simon P. Chappell [EMAIL PROTECTED] Java Programming Specialist www.landsend.com Lands' End, Inc. (608) 935-4526 -Original Message- From: Bachan Sadanandan [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 15, 2002 4:54 PM To: Struts Users Mailing List Subject: Struts 1.1 Release Hi all, Any idea when Struts 1.1 would be ready for Production .??? Thanks ! Bachan -- To unsubscribe, e-mail: mailto:struts-user-[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] Visit our website at http://www.ubswarburg.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost
RE: Struts 1.1 Release
I totally understand and agree with the release policy, but I think it's worth remembering that a lot of these questions are driven by the constraints of users' environments - e.g. in corporate environments like ours, there any many people like myself continually fighting to get great open source products like Struts into the organisation so that development teams can use them, and the latest versions of them. However, this has to be done within the processes and policies that apply to any third party software, commercial or otherwise. Not trying to whine - but I fight the same battles. I work for a big, conservative company. Telling people it's a 'beta' release - regardless of what that means - makes it much more difficult to get things approved. Probably a greater percentage of your users than you realize are still using 1.02 for the sole reason that 1.1 is still called 'beta'. Worse, probably a lot of projects have started off that had to use 1.02 because it was the 'stable release' - and then the development teams struggled. I saw one project dump struts because they had trouble getting it to do what they wanted (they were forced to use 1.02). --- This e-mail message (including attachments, if any) is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, proprietary , confidential and exempt from disclosure. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender and erase this e-mail message immediately. --- -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Struts 1.1 Release
On Tue, 15 Oct 2002 [EMAIL PROTECTED] wrote: Date: Tue, 15 Oct 2002 18:46:01 -0400 From: [EMAIL PROTECTED] Reply-To: Struts Users Mailing List [EMAIL PROTECTED] To: Struts Users Mailing List [EMAIL PROTECTED] Subject: RE: Struts 1.1 Release I totally understand and agree with the release policy, but I think it's worth remembering that a lot of these questions are driven by the constraints of users' environments - e.g. in corporate environments like ours, there any many people like myself continually fighting to get great open source products like Struts into the organisation so that development teams can use them, and the latest versions of them. However, this has to be done within the processes and policies that apply to any third party software, commercial or otherwise. Not trying to whine - but I fight the same battles. I work for a big, conservative company. Telling people it's a 'beta' release - regardless of what that means - makes it much more difficult to get things approved. Probably a greater percentage of your users than you realize are still using 1.02 for the sole reason that 1.1 is still called 'beta'. Worse, probably a lot of projects have started off that had to use 1.02 because it was the 'stable release' - and then the development teams struggled. I saw one project dump struts because they had trouble getting it to do what they wanted (they were forced to use 1.02). You guys's whines are not half as loud as my wails when I consider how long 1.1 has waited for a final release :-(. Unfortunately, schedules are one of the prices when it's an all-volunteer effort (no, Sun doesn't pay me to work on Struts, and what they do pay me for is very very time-consuming). Recently, we've added a couple of additional committers -- in part, to help eliminate the existing backlog of bugs (but also, of course, to build up the team that will come up with future things to top Struts 1.1 :-). I hope to see improvement -- but it's not rational to try to make any promises when none of us can control the amount of time we have available to devote to finishing Struts 1.1. Craig McClanahan -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Struts 1.1 Release
[EMAIL PROTECTED] wrote: I totally understand and agree with the release policy, but I think it's worth remembering that a lot of these questions are driven by the constraints of users' environments - e.g. in corporate environments like ours, there any many people like myself continually fighting to get great open source products like Struts into the organisation so that development teams can use them, and the latest versions of them. However, this has to be done within the processes and policies that apply to any third party software, commercial or otherwise. Not trying to whine - but I fight the same battles. I work for a big, conservative company. Telling people it's a 'beta' release - regardless of what that means - makes it much more difficult to get things approved. Probably a greater percentage of your users than you realize are still using 1.02 for the sole reason that 1.1 is still called 'beta'. Worse, probably a lot of projects have started off that had to use 1.02 because it was the 'stable release' - and then the development teams struggled. I saw one project dump struts because they had trouble getting it to do what they wanted (they were forced to use 1.02). IMO, That could not possibly be a source of failure. I and others had 1.02 projects just fine! Statistically 80% of projects fail due to requirements, so that would be my first guess. (More numbers? most projects fail period, and that 99% of code in production is written by 1% of programmers) If they had tech issues, they could have gone with a experienced mentor who has had Struts code in production before, which is cost effective. And one needs to ask, why use open source? http://www.opensource.org/advocacy/case_for_business.php Because it is *better* quality is one good reason. my 2c, .V --- This e-mail message (including attachments, if any) is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, proprietary , confidential and exempt from disclosure. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender and erase this e-mail message immediately. --- -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Struts 1.1 Release
IMO, That could not possibly be a source of failure. I and others had 1.02 projects just fine! Statistically 80% of projects fail due to requirements, so that would be my first guess. (More numbers? most projects fail period, and that 99% of code in production is written by 1% of programmers) Point not argued - though the pages were extremely dynamic. Each page had a variable number of fields (potentially 20 or more). Each field had a variable number of options (again up to 20 each) - and depending on the data, the options may have required a text entry field, radio buttons or checkboxes (more than one option chosen). All with tight validations driven by the user's personal information. The validations varied by the data values as well (validations were different depending on option types). I believe some features from 1.1 would have made things easier for them - though it is hard to say. And regarding: 99% of code in production is written by 1% of programmers - I'm 99% sure that this is at least a 1% exaggeration. :-} Kevin --- This e-mail message (including attachments, if any) is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, proprietary , confidential and exempt from disclosure. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender and erase this e-mail message immediately. --- -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Struts 1.1 Release
I am rather of the opinion that the struts versioning nomenclature is a wee bit on the humble side. This beta release of 1.1 is pretty stable. I dont see why you cant just loosen up your standards a bit and call it 1.1 , then when all the bugs are fixed call that 1.2 , etc... For 'bigger' or more stable version changes use bigger numbers. Really 1.1 is so much better then 1.02 that you should be calling it 2.0 when it is released (and the current beta releases should be something like 1.99) That will help keep the corporate monkeys off peoples backs and lead to more impressively high sounding version numbers. :-) -Original Message- From: news [mailto:[EMAIL PROTECTED]]On Behalf Of V. Cekvenich Sent: Wednesday, October 16, 2002 08:36 To: [EMAIL PROTECTED] Subject: Re: Struts 1.1 Release [EMAIL PROTECTED] wrote: I totally understand and agree with the release policy, but I think it's worth remembering that a lot of these questions are driven by the constraints of users' environments - e.g. in corporate environments like ours, there any many people like myself continually fighting to get great open source products like Struts into the organisation so that development teams can use them, and the latest versions of them. However, this has to be done within the processes and policies that apply to any third party software, commercial or otherwise. Not trying to whine - but I fight the same battles. I work for a big, conservative company. Telling people it's a 'beta' release - regardless of what that means - makes it much more difficult to get things approved. Probably a greater percentage of your users than you realize are still using 1.02 for the sole reason that 1.1 is still called 'beta'. Worse, probably a lot of projects have started off that had to use 1.02 because it was the 'stable release' - and then the development teams struggled. I saw one project dump struts because they had trouble getting it to do what they wanted (they were forced to use 1.02). IMO, That could not possibly be a source of failure. I and others had 1.02 projects just fine! Statistically 80% of projects fail due to requirements, so that would be my first guess. (More numbers? most projects fail period, and that 99% of code in production is written by 1% of programmers) If they had tech issues, they could have gone with a experienced mentor who has had Struts code in production before, which is cost effective. And one needs to ask, why use open source? http://www.opensource.org/advocacy/case_for_business.php Because it is *better* quality is one good reason. my 2c, .V -- - This e-mail message (including attachments, if any) is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, proprietary , confidential and exempt from disclosure. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender and erase this e-mail message immediately. -- - -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Struts 1.1 Release
Ye gods! Here we go again: snip The 12th of April 2156 at 15:28 in the afternoon. Or perhaps even sooner if its ready before then... ;-) /snip Hey Craig? Any chance we can get my more specific answer for this question into the FAQ? -Original Message- From: Bachan Sadanandan [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 16, 2002 05:54 To: Struts Users Mailing List Subject: Struts 1.1 Release Hi all, Any idea when Struts 1.1 would be ready for Production .??? Thanks ! Bachan -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Struts 1.1 Release
It wouldnt matter if it was plastered on the main struts page (WITH BLINKING TEXT), someone would still askLOL. James Mitchell Software Engineer/Struts Evangelist http://www.open-tools.org -Original Message- From: Andrew Hill [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 16, 2002 12:46 AM To: Struts Users Mailing List Subject: RE: Struts 1.1 Release Ye gods! Here we go again: snip The 12th of April 2156 at 15:28 in the afternoon. Or perhaps even sooner if its ready before then... ;-) /snip Hey Craig? Any chance we can get my more specific answer for this question into the FAQ? -Original Message- From: Bachan Sadanandan [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 16, 2002 05:54 To: Struts Users Mailing List Subject: Struts 1.1 Release Hi all, Any idea when Struts 1.1 would be ready for Production .??? Thanks ! Bachan -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
[OT] RE: Struts 1.1 Release
Anyone wonder why all of a sudden this question becomes so popular? At 12:47 AM 10/16/2002 -0400, you wrote: It wouldn't matter if it was plastered on the main struts page (WITH BLINKING TEXT), someone would still askLOL. James Mitchell Software Engineer/Struts Evangelist http://www.open-tools.org -Original Message- From: Andrew Hill [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 16, 2002 12:46 AM To: Struts Users Mailing List Subject: RE: Struts 1.1 Release Ye gods! Here we go again: snip The 12th of April 2156 at 15:28 in the afternoon. Or perhaps even sooner if its ready before then... ;-) /snip Hey Craig? Any chance we can get my more specific answer for this question into the FAQ? -Original Message- From: Bachan Sadanandan [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 16, 2002 05:54 To: Struts Users Mailing List Subject: Struts 1.1 Release Hi all, Any idea when Struts 1.1 would be ready for Production .??? Thanks ! Bachan -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] Micael --- This electronic mail transmission and any accompanying documents contain information belonging to the sender which may be confidential and legally privileged. This information is intended only for the use of the individual or entity to whom this electronic mail transmission was sent as indicated above. If you are not the intended recipient, any disclosure, copying, distribution, or action taken in reliance on the contents of the information contained in this transmission is strictly prohibited. If you have received this transmission in error, please delete the message. Thank you -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
When will Struts 1.1 release
There're no mention about this. Could anyone let me know? Thanks, -Chuong = HUYNH, N. CHUONG TMA Software Solutions, Vietnam Tel: (84-8) 990 3848 - Ext: 5272 Email: [EMAIL PROTECTED] =
