Re: Plan for Struts 3

2013/3/19 Rene Gielen : > +1 for removing anything deprecated and unmaintained Argh ... but can it be version 2.4.x/2.5.x? Or should we wait till 3.x ? ;-) Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ - To unsu

Jenkins build is still unstable: Struts2-JDK6 #667

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 » XWork: Core #667

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

Jenkins build became unstable: Struts2-JDK6 » Struts 2 Core #667

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

Re: Plan for Struts 3

+1 for removing anything deprecated and unmaintained Am 18.03.13 15:04, schrieb Paul Benedict: > Yes, S3 should be a clean break from anything deprecated. Remove anything > no longer supported. > > Paul > > On Mon, Mar 18, 2013 at 8:12 AM, Christian Grobmeier > wrote: > >> On Mon, Mar 18, 2013

Re: parse or not

I believe the ${} is enough of an indicator that it's an expression. So I guess that's +1 for parsing. On Mar 18, 2013, at 2:52 PM, Lukasz Lenart wrote: > Have a question > > https://issues.apache.org/jira/browse/WW-4018 > > > Regards > -- > Łukasz > + 48 606 323 122 http://www.lenart.org.p

parse or not

Have a question https://issues.apache.org/jira/browse/WW-4018 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...@s

Re: Plan for Struts 3

2013/3/18 Paul Benedict : > Oh, I see what you mean. Sure, why support something you already have a > replacement for? Just take it out of the build and move them to an "extras" > distribution for others to get -- they should no longer come as part of the > standard distribution. Good point, extra

Re: Struts 3 package name

Using the Shade plugin is an option as long as I can shade everything appropriately. I don't know if that's a really good choice as opposed to a separate package name. Paul On Mon, Mar 18, 2013 at 12:48 PM, Maurizio Cucchiara wrote: > Before reading Lukasz's message [1], probably I would have sa

Re: Plan for Struts 3

Oh, I see what you mean. Sure, why support something you already have a replacement for? Just take it out of the build and move them to an "extras" distribution for others to get -- they should no longer come as part of the standard distribution. BTW... Right now, the plugins are part of S2 releas

Re: [VOTE] Formally end support for Struts 1

2013/3/18 : > I see most of user are using S1 . I give to support to S1 . > > Thoughts ? The same as previous - there is now will to support S1 - and this just constitute the current situation. Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ --

Re: Plan for Struts 3

2013/3/18 Paul Benedict : > Ah, that wouldn't be nice to Struts 2 users :-) Just let Struts 2 be as it > is. Perhaps add notes to the documentation and call it quits for those > plugins. Yes I know, but with S2 versioning policy in place it should be already S4. What I mean is that the plugin will

Re: [VOTE] Formally end support for Struts 1

I see most of user are using S1 . I give to support to S1 . Thoughts ? --Original Message-- From: Rainer Hermanns To: Struts Developers List ReplyTo: Struts Developers List Subject: Re: [VOTE] Formally end support for Struts 1 Sent: Mar 18, 2013 7:44 PM +1 (binding) cheers, Rainer Raine

Re: Struts 3 package name

Before reading Lukasz's message [1], probably I would have said that changing the package name to struts3 would have been a good idea. After all, many Apache Commons projects have chosen this schema. As you know, you can use two versions of commons lang without experiencing any problem. However, I

Struts 3 package name

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 package name. If S3 is going to

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

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 less everything which is also contained in struts-p

Re: Plan for Struts 3

Ah, that wouldn't be nice to Struts 2 users :-) Just let Struts 2 be as it is. Perhaps add notes to the documentation and call it quits for those plugins. Paul On Mon, Mar 18, 2013 at 9:30 AM, Lukasz Lenart wrote: > 2013/3/18 Paul Benedict : > > Yes, S3 should be a clean break from anything depr

Re: Plan for Struts 3

2013/3/18 Paul Benedict : > Yes, S3 should be a clean break from anything deprecated. Remove anything > no longer supported. But I would like to do it before we start with S3, to be precise :-) Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ ---

Re: [VOTE] Formally end support for Struts 1

+1 (binding) cheers, Rainer Rainer Hermanns aixcept Willibrordstraße 82 52134 Herzogenrath - Germany w: http://aixcept.de/ t: +49 - 2406 - 979 22 11 f: +49 - 2406 - 979 22 13 m: +49 - 170 - 343 29 12

Re: Plan for Struts 3

+1 On Mon, Mar 18, 2013 at 10:04 AM, Paul Benedict wrote: > Yes, S3 should be a clean break from anything deprecated. Remove anything > no longer supported. > > Paul > > On Mon, Mar 18, 2013 at 8:12 AM, Christian Grobmeier >wrote: > > > On Mon, Mar 18, 2013 at 9:46 AM, Lukasz Lenart > > wrote:

Re: Plan for Struts 3

Yes, S3 should be a clean break from anything deprecated. Remove anything no longer supported. Paul On Mon, Mar 18, 2013 at 8:12 AM, Christian Grobmeier wrote: > On Mon, Mar 18, 2013 at 9:46 AM, Lukasz Lenart > wrote: > > As S1 is going to be emeritus soon, what do you think about removing > >

Jenkins build became unstable: Struts2-JDK6 #666

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

Jenkins build became unstable: Struts2-JDK6 » XWork: Core #666

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

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

Interesting. Thanks Martin and Lukasz, maybe i have more luck with these hints. I will let you know :-) Christian 2013/3/17 Martin Gainty : > Christian > > check out MockStrutsTestCase > http://strutstestcase.sourceforge.net/api/servletunit/struts/MockStrutsTestCase.html#setConfigFile(java.lang.S

Re: Plan for Struts 3

On Mon, Mar 18, 2013 at 9:46 AM, Lukasz Lenart wrote: > As S1 is going to be emeritus soon, what do you think about removing > the Struts 1 plugin from Struts 2? Also we could remove other > deprecated plugins like Dojo, Zero Configuration and JSF? +1 It was yesterday when I was looking at them

Jenkins build is back to normal : Struts2-JDK6 #663

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

Build failed in Jenkins: Struts2-JDK6 #662

See Changes: [Lukasz Lenart] WW-4006 Improves ExpressionValidator annotation to match ExpressionValidator class [Lukasz Lenart] WW-4005 Improves EmailValidator annotation to match EmailValidator class ---

Re: Plan for Struts 3

As S1 is going to be emeritus soon, what do you think about removing the Struts 1 plugin from Struts 2? Also we could remove other deprecated plugins like Dojo, Zero Configuration and JSF? Thus would be covered in 2.4.x release and with cleaned a bit code base we could switch to Git and start work