Struts 1 - what does the future hold?
Hi all, In 2010 we finished a 6 year project of redeveloping our complete application from COBOL and a bit of Java to a totally Java application using Struts 1. We have tens of thousands of classes and millions of lines of code. A new kind of "one off/stand alone" application has been requested by the business, and the Analyst in charge is looking at different frameworks and even languages ( ie Grails, Spring MVC ) for completing this project. I asked why they weren't just going to use our current environment (Struts 1 and Java). They expressed concerns about how long Java and Struts 1 would remain viable. I don't happen to share these concerns but am looking for some sort of confirmation from the development team that my thinking is correct on this subject and that Struts 1 will be maintained enough to keep it compliant and relevant. My feeling is that if anything they should maybe switch to Struts 2 for this project to remain in the same realm as the rest of our apps. My question is: As Java SE and EE and all things java, continue to evolve will Struts 1 be maintained in order to remain compliant and usable? Not expecting any new features or anything but just wondering if we need to be thinking about a possible end of life type situation for Struts 1. -------- Brian Holzer IT Analyst Saskatchewan Government Insurance email: bhol...@sgi.sk.ca phone: (306) 751-1573 fax: (306) 569-7683 This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the named addressee, 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. If you are not the intended recipient you are notified that using, disclosing, copying or distributing the contents of this information is strictly prohibited. - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Struts 1 - what does the future hold?
Hi Paul, I agree with you that any new development we do, we should be doing with Struts 2 ( I hope to convince them of that ) but my question is more about Struts 1 and it's maintenance going forward. With our application being as large as it is, I am just looking for some confirmation from the development team about (below) My question is: As Java SE and EE and all things java, continue to evolve and new versions keep coming out, will Struts 1 be maintained enough in order to remain compliant and usable? Just wondering if we need to be thinking about a possible end of life type situation for Struts 1 in the future. Brian >>> Paul Benedict 11/15/2012 1:13 PM >>> Go with Struts 2. End of story :-) I did make some really big enhancements to 1.4 but Struts 2 is well and above any new enhancements for 1.x Paul On Thu, Nov 15, 2012 at 12:56 PM, Brian Holzer wrote: > Hi all, > In 2010 we finished a 6 year project of redeveloping our complete > application from COBOL and a bit of Java to a totally Java application > using Struts 1. We have tens of thousands of classes and millions of lines > of code. A new kind of "one off/stand alone" application has been > requested by the business, and the Analyst in charge is looking at > different frameworks and even languages ( ie Grails, Spring MVC ) for > completing this project. I asked why they weren't just going to use our > current environment (Struts 1 and Java). They expressed concerns about how > long Java and Struts 1 would remain viable. I don't happen to share these > concerns but am looking for some sort of confirmation from the development > team that my thinking is correct on this subject and that Struts 1 will be > maintained enough to keep it compliant and relevant. > >My feeling is that if anything they should maybe switch to Struts 2 for > this project to remain in the same realm as the rest of our apps. > >My question is: As Java SE and EE and all things java, continue to > evolve will Struts 1 be maintained in order to remain compliant and usable? > Not expecting any new features or anything but just wondering if we need > to be thinking about a possible end of life type situation for Struts 1. > > > > > > > Brian Holzer > IT Analyst > Saskatchewan Government Insurance > email: bhol...@sgi.sk.ca > phone: (306) 751-1573 > fax: (306) 569-7683 > > This e-mail and any files transmitted with it are confidential and > intended solely for the use of the individual or entity to whom they are > addressed. If you are not the named addressee, 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. If you are not the intended recipient > you are notified that using, disclosing, copying or distributing the > contents of this information is strictly prohibited. > > - > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > For additional commands, e-mail: dev-h...@struts.apache.org > > This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the named addressee, 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. If you are not the intended recipient you are notified that using, disclosing, copying or distributing the contents of this information is strictly prohibited. - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Plan for Struts 3
Hi all, If you drop support for S1, what about those people still using S1? I'm guessing there are a lot of them out there. Brian >>> Lukasz Lenart 3/5/2013 2:22 PM >>> Hi, I have few additional thoughts about S3 and the future. First with should drop support of S1 and use simple Struts as a project name - no more Struts2, Struts3, Struts4, ... Simple Struts and version 3.0.1, 4.1.0.1, etc. We should just keep support for one version back, so when we release 3.x, we should support just the latest version of 2.x branch (and drop support for S1) - critical issues and security vulnerabilities. Versioning: x.y.z.s x - major API changes, breaks backward compatibility y - minor API changes, can break backward compatibility (minor, one method replaced other, should be simple to adopt) z - maintenance, no API changes, no backward compatibility breaks s - security release With these two in mind we can more flexible handle changes and adopt new requirements. Also website can be keep much clearer, just /current and /previous ;-) Regards -- *ukasz + 48 606 323 122 http://www.lenart.org.pl/ This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the named addressee, 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. If you are not the intended recipient you are notified that using, disclosing, copying or distributing the contents of this information is strictly prohibited. - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Plan for Struts 3
Fair enough, I'm hopeful as well that the docs will still be available. I realize there hasn't been a release in ages, but I always assumed that if there was a security issue that it would be patched. If someone wants to migrate they could use some version of Struts2 2.? to slowly migrate pieces of a super large project and then move onto 3 once totally migrated to 2. To any of you that are still around thanks for your work on Struts1. Brian >>> Dave Newton 3/5/2013 4:28 PM >>> I don't think anybody was talking about removing all traces of it, just making the lack of support official. Dave This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the named addressee, 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. If you are not the intended recipient you are notified that using, disclosing, copying or distributing the contents of this information is strictly prohibited. - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Fwd: Re: Docs: Working on Struts main
I checked out that staging site and one thing I found is that on the Documentation dropdown on the main page, the links to the Struts 2.3X and Struts 1.3X were both broken. Not sure that's what you were going for. Brian >>> Rene Gielen 13/09/2013 11:22 AM >>> http://struts.staging.apache.org/ Am 13.09.2013 18:35 schrieb "Paul Benedict" : > Where can I see the "new" website before it goes live? > > > On Fri, Sep 13, 2013 at 2:22 AM, Rene Gielen > wrote: > > > As this a major change, a formal vote might be a valid option. > > Am 12.09.2013 11:26 schrieb "Lukasz Lenart" : > > > > > Can we go live? > > > > > > 2013/9/11 Lukasz Lenart : > > > > I think we can go live with the new website even now - it looks much > > > > better the old one and the rest can be improved in meantime. > > > > > > > > 2013/9/10 Christian Grobmeier : > > > >> Am 10.09.13 18:11, schrieb Rene Gielen: > > > >>> If I'd use [Publish Site] now in the Bookmarklet, the site gets - > > well > > > - > > > >>> published. So better nobody would hit this unless we are sure to > > > launch the > > > >>> reworked site. Also, we are currently not able to publish "small > > > changes" > > > >>> such as release announcements without rolling out the full new > site. > > I > > > just > > > >>> want to make sure anybody is aware of this (as long as I'm not > > missing > > > >>> something here). > > > >> Ah yes, thats right. Luckily the old page is already much worse then > > the > > > >> half completed one now. > > > >> We have a lot of outdated links and information there. If somebody > > reads > > > >> that he would be totally done. > > > >> If it is really an emergency problem we can branch the trunk, > rollback > > > >> things on trunk and push a change. > > > >> Not nice and well thought, but would work in case of fire. > > > >> > > > >> > > > >>> - René > > > >>> > > > >>> > > > >>> 2013/9/10 Christian Grobmeier > > > >>> > > > Am 10.09.13 14:40, schrieb Lukasz Lenart: > > > > 2013/9/10 Rene Gielen : > > > >> You guys are aware that we cannot publish to live anymore now? > We > > > would > > > >> rollout the new site then. > > > If you mean that "view diff" gives a "no result", this was prior > the > > > changes. I thought it was a hickup at infra. > > > I have tried that via the cms bookmarklet. Or did you mean > something > > > else? > > > > What you mean by that? > > > > > > > > > > > > Regards > > > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > > > For additional commands, e-mail: dev-h...@struts.apache.org > > > > > > > > > >> > > > >> > > > >> > - > > > >> To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > > > >> For additional commands, e-mail: dev-h...@struts.apache.org > > > >> > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > > > For additional commands, e-mail: dev-h...@struts.apache.org > > > > > > > > > > > > -- > Cheers, > Paul > This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the named addressee, 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. If you are not the intended recipient you are notified that using, disclosing, copying or distributing the contents of this information is strictly prohibited. - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Fwd: Re: We are live :-)
X 2 >>> Paul Benedict 17/09/2013 2:16 PM >>> Nice work. On Tue, Sep 17, 2013 at 3:15 PM, Philip Luppens wrote: > On Tue, Sep 17, 2013 at 9:11 PM, Christian Grobmeier >wrote: > > > Hey all, > > > > we have a new main site, I just pulled the trigger :-) > > > > http://struts.apache.org > > > > Thanks to all who corrected a lot of things when I was piled under work > > the past days. Keep on doing that. It's only for our own best to keep on > > improving the docs on all pages of our main site. > > > > Sweet! Great job y'all! > > -Phil > > > > > > Cheers > > Christian > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > > For additional commands, e-mail: dev-h...@struts.apache.org > > > > > > > -- > "We cannot change the cards we are dealt, just how we play the hand." - > Randy Pausch > -- Cheers, Paul This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the named addressee, 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. If you are not the intended recipient you are notified that using, disclosing, copying or distributing the contents of this information is strictly prohibited. - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Fwd: Re: Re-organise docs
I'm in agreement with Paul on this one. >>> Paul Benedict 05/11/2013 9:13 AM >>> I usually find it a life-saver to see the docs of previous versions. Not everyone upgrades and it's impossible to compare latest syntax and features to what was before. I think we definitely need to keep the docs of the previously published versions around. If you don't want to do that, then I think the latest docs need to contain some sort of history on feature changes/upgrades. On Tue, Nov 5, 2013 at 1:34 AM, Lukasz Lenart wrote: > I'm wondering what is wrong with exposing only the latest Draft docs > and just forget about publishing docs on each release? Thus will > simplify keeping page update-2-date and reduce amount of time spend on > preparing new release. > > > Regards > -- > *ukasz > + 48 606 323 122 http://www.lenart.org.pl/ > > 2013/10/30 Lukasz Lenart : > > There is one problem - to include docs in the assemblies they must be > > downloaded with wget (there is no support for SiteExporter in > > Jenkins). > > So, I must add a task which will export docs from Confluence and put > > them under /docs and then with wget they can be downloaded to Jenkins > > and assembled :\ > > > > ech... bit messy solution, but I don't see other option. > > > > > > Regards > > -- > > *ukasz > > + 48 606 323 122 http://www.lenart.org.pl/ > > > > 2013/9/10 : > >> +1 for that > >> It will reduce a lot of confusion > >> --Original Message-- > >> From: Lukasz Lenart > >> To: Struts Developers List > >> ReplyTo: Struts Developers List > >> Subject: Re-organise docs > >> Sent: Sep 10, 2013 12:18 PM > >> > >> Hi, > >> > >> I thought a bit about our docs - for each main branch we provide docs, > >> i.e. /release/2.3.x/, /release/2.2.x/ etc. We also expose draft docs > >> as /development/2.x - all thus leads to mess when we must update > >> something or so. > >> > >> So maybe just instead of many places with docs we should expose the > >> latest related to last release under path /docs and redirect to > >> Confluence in case of draft docs? > >> > >> > >> Regards > >> -- > >> *ukasz > >> + 48 606 323 122 http://www.lenart.org.pl/ > >> > >> - > >> To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > >> For additional commands, e-mail: dev-h...@struts.apache.org > >> > >> > >> > >> Sent from BlackBerry* on Airtel > > - > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > For additional commands, e-mail: dev-h...@struts.apache.org > > -- Cheers, Paul This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the named addressee, 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. If you are not the intended recipient you are notified that using, disclosing, copying or distributing the contents of this information is strictly prohibited. - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
