Re: Using fluido once available

2012-11-27 Thread Rene Gielen
Am 28.11.12 06:14, schrieb Martin Cooper: > On Tue, Nov 27, 2012 at 1:55 PM, Johannes Geppert wrote: > >> It looks there is a broad agreement related to the projects links and the >> Roadmap FAQ. >> So i have dropped it from the site. >> >> Also I have added a Facebook and G+ Integration beside

Re: Plan for Struts 3

2012-11-27 Thread Paul Benedict
Well I know that XWork had its only dependency injection support, but now that Java has a standard dependency injection mechanism, we should definitely go with that. Also it keeps on getting developed with each new EE so it's something we should support as a first-class citizen. On Wed, Nov 28, 20

Re: Using fluido once available

2012-11-27 Thread Lukasz Lenart
2012/11/28 Martin Cooper : > Why are we supporting commercial enterprises from our site? As a 501(c)3 > organisation, are we allowed to do that? Hmmm we should ask somebody as I have no idea how it works in US. Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ --

Re: Plan for Struts 3

2012-11-27 Thread Lukasz Lenart
2012/11/28 Paul Benedict : > What about dropping XWork injection support for JSR 330 (Commons DI)? You mean what we have now and use Guice as an internal DI mechanism ? Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/

Re: Plan for Struts 3

2012-11-27 Thread Paul Benedict
What about dropping XWork injection support for JSR 330 (Commons DI)? On Wed, Nov 28, 2012 at 12:41 AM, Lukasz Lenart wrote: > I've updated the plan :-) > > Request Git repo from INFRA > Import project > Remove deprecated plugins > Drop support for Struts 1 (remove plugin) > Remove deprecated API

Re: Plan for Struts 3

2012-11-27 Thread Lukasz Lenart
I've updated the plan :-) Request Git repo from INFRA Import project Remove deprecated plugins Drop support for Struts 1 (remove plugin) Remove deprecated APIs Switch to Java 1.6 Rename XWork packages to org.apache.struts.xwork Rename Struts 2 packages to org.apache.struts Prepare the first releas

Re: Plan for Struts 3

2012-11-27 Thread Lukasz Lenart
2012/11/28 Dave Newton : > Part of the question regarded org.apache.struts v. org.apache.struts2. > > I don't know how many (if any) conflicts there are. > > I'm not a fan of embedding version info in package names. I'd hate to > see org.apache.struts3, and IMO it'd be confusing to have Struts 3 >

Re: Using fluido once available

2012-11-27 Thread Martin Cooper
On Tue, Nov 27, 2012 at 1:55 PM, Johannes Geppert wrote: > It looks there is a broad agreement related to the projects links and the > Roadmap FAQ. > So i have dropped it from the site. > > Also I have added a Facebook and G+ Integration beside the Twitter > Integration. > Looks like this is our

Build failed in Jenkins: Struts2-JDK6 #569

2012-11-27 Thread Apache Jenkins Server
See Changes: [Lukasz Lenart] WW-3928 Adds deprecation warning to don't use ActionContextCleanUp any more -- [...truncated 5824 lines...] at org.apache.maven.surefire.booter.SurefireBooter.m

Re: Plan for Struts 3

2012-11-27 Thread Dave Newton
Part of the question regarded org.apache.struts v. org.apache.struts2. I don't know how many (if any) conflicts there are. I'm not a fan of embedding version info in package names. I'd hate to see org.apache.struts3, and IMO it'd be confusing to have Struts 3 have a struts2 package name component

Re: Plan for Struts 3

2012-11-27 Thread Paul Benedict
Perhaps I don't understand, but you can run Struts 1 and Struts 2 simultaneously. They have different Maven artifacts and Java package names. The discussion was about whether to continue supporting the Struts 1 Plugin in S3. I am of the opinion "no" because it provides such limited capabilities. I

RE: Plan for Struts 3

2012-11-27 Thread Martin Gainty
Matt makes a good pointone of the primary reasons to select Struts MVC Framework over Spring is the ability of Struts2 to work with previous Struts versions (Struts1) +1 for Matt Martin __ Please do not alter or disrupt this transmission...Thank You

Re: Plan for Struts 3

2012-11-27 Thread Matt Raible
If it breaks backwards-compatibility, I'd suggest not doing it. I've always been impressed with projects like Spring that've maintained backwards compatibility w/o making a breaking change such as this. On Nov 27, 2012, at 3:54 PM, Jeff Black wrote: > Never mind. > > I suppose it makes sense

Re: Plan for Struts 3

2012-11-27 Thread Jeff Black
Never mind. I suppose it makes sense to some extent; however I'm with Dave when it comes to incorporating the version number in the package name. Just my two cents. From: Jeff Black To: Struts Developers List Sent: Tuesday, November 27, 2012 4:50 PM Subjec

Re: Plan for Struts 3

2012-11-27 Thread Jeff Black
Is it really necessary to alter the package name? From: Lukasz Lenart To: Struts Developers List Sent: Thursday, November 22, 2012 5:35 AM Subject: Re: Plan for Struts 3 2012/11/22 Dave Newton : > How useful is the Struts 1 plugin? It's mentioned as a migr

Re: svn commit: r1414413 - /struts/site/branches/site2fluidomigration/src/site/site.xml

2012-11-27 Thread Lukasz Lenart
Works when accessed via http://localhost, thanks! 2012/11/27 Lukasz Lenart : > e... my fault ;-) I'm testing from file system, so by default protocol > will be file:// > > 2012/11/27 Lukasz Lenart : >> But this time, error is more complicated: >> >> FB.getLoginStatus() called before calling FB.ini

Re: svn commit: r1414413 - /struts/site/branches/site2fluidomigration/src/site/site.xml

2012-11-27 Thread Lukasz Lenart
e... my fault ;-) I'm testing from file system, so by default protocol will be file:// 2012/11/27 Lukasz Lenart : > But this time, error is more complicated: > > FB.getLoginStatus() called before calling FB.init(). all.js:52 > GET > file://www.facebook.com/plugins/like.php?api_key=&locale=en_US&s

Re: svn commit: r1414413 - /struts/site/branches/site2fluidomigration/src/site/site.xml

2012-11-27 Thread Lukasz Lenart
But this time, error is more complicated: FB.getLoginStatus() called before calling FB.init(). all.js:52 GET file://www.facebook.com/plugins/like.php?api_key=&locale=en_US&sdk=joey&channel_url=http%3A%2F%2Fstatic.ak.facebook.com%2Fconnect%2Fxd_arbiter.php%3Fversion%3D17%23cb%3Df11ac4a7fc%26origin

Re: svn commit: r1414413 - /struts/site/branches/site2fluidomigration/src/site/site.xml

2012-11-27 Thread Lukasz Lenart
It didn't help, but maybe it's related to OSX ? Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ 2012/11/27 : > Author: jogep > Date: Tue Nov 27 21:49:42 2012 > New Revision: 1414413 > > URL: http://svn.apache.org/viewvc?rev=1414413&view=rev > Log: > Add missing http to facebook in

Re: Using fluido once available

2012-11-27 Thread Johannes Geppert
It looks there is a broad agreement related to the projects links and the Roadmap FAQ. So i have dropped it from the site. Also I have added a Facebook and G+ Integration beside the Twitter Integration. Looks like this is our current News Section. ;-) On the bottom of our Welcome Page are some Bo

Re: svn commit: r1414349 - in /struts/site/branches/site2fluidomigration: ./ src/site/site.xml src/site/xdoc/index.xml

2012-11-27 Thread Lukasz Lenart
2012/11/27 Johannes Geppert : > Hmm, I see now a buttons for twitter, g+ and facebook. > Currently tested with Chrome and Firefox. > > Any JavaScript Errors in your Console? Failed to load file://connect.facebook.net/en_US/all.js#xfbml=1 Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.

Re: Plan for Struts 3

2012-11-27 Thread Paul Benedict
No, I support dropping the plugin. I was only echoing the previous point, which was the S1 plugin gives you very limited S1 reuse -- you get the actions but not the taglibs. On Tue, Nov 27, 2012 at 2:56 PM, Lukasz Lenart wrote: > 2012/11/27 Paul Benedict : > > Lukasz, you can... but the S1 plugin

Re: Plan for Struts 3

2012-11-27 Thread Lukasz Lenart
2012/11/27 Paul Benedict : > Lukasz, you can... but the S1 plugin allows people to forgo the S1 jar. You > don't gain much in terms of the presentation layer since you can't use the > S1 taglibs anymore, but the S1 action can still be called. So you mean we should keep support for S1 in S3 ? And u

Re: svn commit: r1414332 - in /struts/site/branches/site2fluidomigration/src/site: resources/css/site.css site.xml

2012-11-27 Thread Łukasz Lenart
It overwrite link on the right: Apache | Struts 2 | Struts 1 Regards -- Łukasz mobile +48 606 323 122 http://www.lenart.org.pl/ Warszawa JUG conference - Confitura http://confitura.pl/ 2012/11/27 : > Author: jogep > Date: Tue Nov 27 19:26:45 2012 > New Revision: 1414332 > > URL: http://svn.apa

Re: Using fluido once available

2012-11-27 Thread Rene Gielen
Am 26.11.12 22:41, schrieb Martin Cooper: > On Mon, Nov 26, 2012 at 12:41 PM, Lukasz Lenart > wrote: > >> 2012/11/25 Johannes Geppert : >>> What others think about shrinking a little bit the menu and some Content? >> >> +1 :-) >> > > Depends on what you mean by "shrink". We have people (e.g. Lin

Re: Using fluido once available

2012-11-27 Thread Rene Gielen
Changing it to Apache Struts, Struts, Apache, the Apache feather logo, and the Apache Struts project logos are trademarks of The Apache Software Foundation. imo looks more appropriate - there still seems to be some css weirdness though... Am 26.11.12 23:28, schrieb Joh

Re: Using fluido once available

2012-11-27 Thread Rene Gielen
I applied the moves suggested in my former mail. Am 27.11.12 16:08, schrieb Rene Gielen: > Indeed it looks a bit awkward having trunk/branches besides > forms/legacy. But it just indicates that the latter directories seem to > be misplaced so far. > > I'd suggest moving the contents of legacy to

Re: Using fluido once available

2012-11-27 Thread Rene Gielen
Indeed it looks a bit awkward having trunk/branches besides forms/legacy. But it just indicates that the latter directories seem to be misplaced so far. I'd suggest moving the contents of legacy to ../archive, and introduce a new folder ../resources where we move the forms directory to. - René A