On Fri, Jul 20, 2012 at 1:12 AM, Lukasz Lenart <[email protected]> wrote: > Hi, > > What do you thinking about adding small example apps to Struts 2 ?
Who will maintain them, and keep them up to date when the core framework changes? How will we ensure that they continue to represent best practices when new features or mechanisms are introduced into the framework? > I was thinking about adding some example how to use more advanced > futures of Struts 2 - mostly extension points. It would be a new Maven > module next to core / apps so on. > > Why inside the Struts 2 ? It's better to test and check if it works. > With separated project, I must build Struts 2, build project and test > it. So the RM would be responsible for manually testing all of these apps to ensure that they are working before a build could be considered ready to put to a vote? If they're "inside" S2, that would have to be true. You couldn't release if the apps were broken. Don't get me wrong - I'm all for having examples. But they need to be maintained, and that takes sustained effort over time. And as the RM for many releases of S1, I'll point out that manual testing of examples as part of every build is not a trivial task either - especially when you find that something over the last few months broke an app, nobody discovered the breakage until now, and now you can't release until you've fixed it. -- Martin Cooper > Regards > -- > Łukasz > + 48 606 323 122 http://www.lenart.org.pl/ > > --------------------------------------------------------------------- > 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]
