Wiki cleanup

Hi we have: 1) http://wiki.apache.org/struts 2) https://cwiki.apache.org/WW/ 3) https://cwiki.apache.org/S2WIKI/ 4) https://cwiki.apache.org/S2PLUGINS/ Our homepage links to #3 (which currently looks as it would not have a stylesheet, btw) I know #1 is not maintained. What about the other 2 wi

Re: Wiki cleanup

2013/3/19 Christian Grobmeier : > 1) http://wiki.apache.org/struts > 2) https://cwiki.apache.org/WW/ > 3) https://cwiki.apache.org/S2WIKI/ > 4) https://cwiki.apache.org/S2PLUGINS/ > > Our homepage links to #3 (which currently looks as it would not have a > stylesheet, btw) Started auto-export by h

Re: Wiki cleanup

Thanks for taking the time and explain the situation to me. I appreciate it. i am still behind spam-protecting #1. On Tue, Mar 19, 2013 at 8:48 AM, Lukasz Lenart wrote: > 2013/3/19 Christian Grobmeier : >> 1) http://wiki.apache.org/struts >> 2) https://cwiki.apache.org/WW/ >> 3) https://cwiki.ap

Re: parse or not

2013/3/18 Matt Raible : > I believe the ${} is enough of an indicator that it's an expression. So I > guess that's +1 for parsing. I think I have to explain it a bit more: before there was a dedicated param called "parse" to enable parsing or not the validator's params, like below: @IntRangeFiel

Jenkins build is back to stable : Struts2-JDK6 » Struts 2 Core #668

See - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org

Jenkins build is back to stable : Struts2-JDK6 #668

See - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org

Re: Wiki cleanup

Should we think of filing an Infra ticket rather than mail request regarding spam protection for #1? Am 19.03.2013 09:26 schrieb "Christian Grobmeier" : > Thanks for taking the time and explain the situation to me. I appreciate > it. > > i am still behind spam-protecting #1. > > On Tue, Mar 19, 20

Re: Wiki cleanup

On Tue, Mar 19, 2013 at 11:31 AM, Rene Gielen wrote: > Should we think of filing an Infra ticket rather than mail request > regarding spam protection for #1? I have seen others doing this by simple mail request. I looked for an appropriate Jira module, but was unsure where to file it. Suggestion

Re: Wiki cleanup

Am 19.03.13 11:36, schrieb Christian Grobmeier: > On Tue, Mar 19, 2013 at 11:31 AM, Rene Gielen wrote: >> Should we think of filing an Infra ticket rather than mail request >> regarding spam protection for #1? > > I have seen others doing this by simple mail request. I looked for an > appropriate

Re: [VOTE] Formally end support for Struts 1

Note to everybody following this thread: when this Vote passes, all the documentation and source code of S1 will still be available, no one is going to remove it, erase and whatsoever Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ -

Re: Support for Convention-Plugin through the Junit-Plugin

2013/3/18 Christian Grobmeier : > I debugged a good while and figured out how it can be done, basically. > > The trick is, you give it a special config: > > @Override > protected String getConfigPath() { > return "struts-convention.xml"; > } > > This config above contains more or le

Re: Struts 3 package name

2013/3/18 Paul Benedict : > I professionally work on a huge project where S1 is used everywhere. The > best upgrade path for us is to put S2 in the web container, write new > actions in S2, and convert the old S1 actions during maintenance. This > scheme is only possible because S2 uses a different

Re: Struts 3 package name

If we name the Java package "org.apache.struts3", we will keep a migration path open for *both* S1 and S2. The perspective we should have, I think, is that we are one of many front-end technologies and it's *necessary* for multiple versions of Struts to be used at the same time. Even if it is not n

Re: Struts 3 package name

2013/3/19 Paul Benedict : > If we name the Java package "org.apache.struts3", we will keep a migration > path open for *both* S1 and S2. The perspective we should have, I think, is > that we are one of many front-end technologies and it's *necessary* for > multiple versions of Struts to be used at

Re: Struts 3 package name

It's a good thought, but if you do that, then there's no incremental migration path between S2 and S3. On Tue, Mar 19, 2013 at 10:02 AM, Lukasz Lenart wrote: > 2013/3/19 Paul Benedict : > > If we name the Java package "org.apache.struts3", we will keep a > migration > > path open for *both* S1 an

Re: Struts 3 package name

2013/3/19 Paul Benedict : > It's a good thought, but if you do that, then there's no incremental > migration path between S2 and S3. I don't know if is needed, as we just said that the S3 should be better S2 - migrating between them should be easy. Regards -- Łukasz + 48 606 323 122 http://www.

Re: Struts 3 package name

Good point! If it is that easy, then sure. On Tue, Mar 19, 2013 at 10:11 AM, Lukasz Lenart wrote: > 2013/3/19 Paul Benedict : > > It's a good thought, but if you do that, then there's no incremental > > migration path between S2 and S3. > > I don't know if is needed, as we just said that the S3 s

Re: Struts 3 package name

My thoughts its a good way to keep a separate package name ? One question Do the S3 architecture will change ? Sent from my BlackBerry® smartphone -Original Message- From: Paul Benedict Sender: paulus.benedic...@gmail.com Date: Mon, 18 Mar 2013 14:17:34 To: Struts Developers List Repl

Re: Struts 3 package name

2013/3/19 : > My thoughts its a good way to keep a separate package name ? One question Do > the S3 architecture will change ? No, it will be the same as S2. The plan is ti just remove deprecated parts and cleanup the code base Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ -

Re: Struts 3 package name

Don't you think it will raise questions (and eyebrows) why Struts 3 has a struts 2 package name? Paul On Tue, Mar 19, 2013 at 4:29 PM, Lukasz Lenart wrote: > 2013/3/19 : > > My thoughts its a good way to keep a separate package name ? One > question Do the S3 architecture will change ? > > No

Re: Struts 3 package name

2013/3/19 Paul Benedict : > Don't you think it will raise questions (and eyebrows) why Struts 3 has a > struts 2 package name? That's why we should call it S2.5, in other words when package name remains unchanged it shouldn't be called S3 ;) Regards -- Łukasz + 48 606 323 122 http://www.lenart.

Re: Struts 3 package name

Ah, well, the only unfortunate problem with calling it 2.5 is that you already have a 2.3. No one is going to realize you intend it as a half-jump release (like Tomcat 5.0 and 5.5). There will likely be confusion why a point release dropped so much support, but if we advertise in big bold letters t

Re: Struts 3 package name

2013/3/20 Paul Benedict : > Ah, well, the only unfortunate problem with calling it 2.5 is that you > already have a 2.3. No one is going to realize you intend it as a half-jump > release (like Tomcat 5.0 and 5.5). There will likely be confusion why a > point release dropped so much support, but if