Re: Plan for Struts 3
...should have said projects instead of code ;-) Markus Fischer Am 18.04.2013 08:58, schrieb i...@flyingfischer.ch: There is a lot of code out there still relying on Java 6. If there is no urgent need to use Java 7, it is no good idea to make the framework dependent on Java 7: We should keep a minimal backward compatibility regarding Java. Markus Fischer Am 18.04.2013 08:46, schrieb Johannes Geppert: Hi, Switch to Java 1.6 when starting a new major release why not start with Java 7? I mean Java 6 is already in the end of life cycle. :-) Johannes # web: http://www.jgeppert.com twitter: http://twitter.com/jogep 2013/4/18 Lukasz Lenart A new plan :D Plan for Struts 2.5: 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 Prepare the first release Plan for Struts 3: Rename Struts 2 packages to org.apache.struts 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 - 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
Moving docs from the source
Hi, Right now we have a small mismatch where the docs are kept. They are partially in Confluence and partially in a source code of a class. Take look on that page [1] and you will find a nice looking sections messed up with a bit ugly inlined code. The problem is that to correct that I have to know the source code, I mean which class is included by a snippet to render given section. So basically I must hit Edit on the page, check the name of the class, go to IDE, change class, commit, etc very long path to improve just a typo :\ My idea is to move all the descriptions into wiki and left just a brief description of a class with a link to the docs. [1] http://struts.apache.org/development/2.x/docs/actionmapper.html 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
Re: Moving docs from the source
+1 On Thu, Apr 18, 2013 at 1:10 PM, Lukasz Lenart wrote: > Hi, > > Right now we have a small mismatch where the docs are kept. They are > partially in Confluence and partially in a source code of a class. > Take look on that page [1] and you will find a nice looking sections > messed up with a bit ugly inlined code. The problem is that to correct > that I have to know the source code, I mean which class is included by > a snippet to render given section. So basically I must hit Edit on the > page, check the name of the class, go to IDE, change class, commit, > etc very long path to improve just a typo :\ > > My idea is to move all the descriptions into wiki and left just a > brief description of a class with a link to the docs. > > [1] http://struts.apache.org/development/2.x/docs/actionmapper.html > > > 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 > > -- With Regards Umesh Awasthi http://www.travellingrants.com/
Re: Plan for Struts 3
Am 18.04.13 08:00, schrieb Lukasz Lenart: > A new plan :D > > Plan for Struts 2.5: > 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 > Prepare the first release > > Plan for Struts 3: > Rename Struts 2 packages to org.apache.struts What is the added value to expect Struts users to go through the pain of package renaming two times within a foreseeable time period? How about this big picture: 2.5 - intermediate step requiring users to cleanup their projects - switch to Git, remove all deprecated stuff, switch to J6 3.0 - new features and API with added value for users to switch to new API - includes alignment of all package names Regarding adoption I'm pretty sure that J6 should still be the way to go. J7 adoption seems to be around 15% right now as I read lately, maybe the next year helps to increase this rate. At least for 2.5 and start of development on 3.0 we should stay with J6 *sigh* > > > Regards > - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Moving docs from the source
+1 On Thu, Apr 18, 2013 at 9:40 AM, Lukasz Lenart wrote: > Hi, > > Right now we have a small mismatch where the docs are kept. They are > partially in Confluence and partially in a source code of a class. > Take look on that page [1] and you will find a nice looking sections > messed up with a bit ugly inlined code. The problem is that to correct > that I have to know the source code, I mean which class is included by > a snippet to render given section. So basically I must hit Edit on the > page, check the name of the class, go to IDE, change class, commit, > etc very long path to improve just a typo :\ > > My idea is to move all the descriptions into wiki and left just a > brief description of a class with a link to the docs. > > [1] http://struts.apache.org/development/2.x/docs/actionmapper.html > > > 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 > -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Plan for Struts 3
Good point! Plan for Struts 2.5: 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 Prepare the first release Plan for Struts 3: Rename XWork packages to org.apache.struts.xwork Rename Struts 2 packages to org.apache.struts Switch to Java 1.7 https://cwiki.apache.org/confluence/display/WW/Struts+Next 2013/4/18 Rene Gielen : > Am 18.04.13 08:00, schrieb Lukasz Lenart: >> A new plan :D >> >> Plan for Struts 2.5: >> 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 >> Prepare the first release >> >> Plan for Struts 3: >> Rename Struts 2 packages to org.apache.struts > > What is the added value to expect Struts users to go through the pain of > package renaming two times within a foreseeable time period? > > How about this big picture: > 2.5 - intermediate step requiring users to cleanup their projects - > switch to Git, remove all deprecated stuff, switch to J6 > 3.0 - new features and API with added value for users to switch to new > API - includes alignment of all package names > > Regarding adoption I'm pretty sure that J6 should still be the way to > go. J7 adoption seems to be around 15% right now as I read lately, maybe > the next year helps to increase this rate. At least for 2.5 and start of > development on 3.0 we should stay with J6 *sigh* > >> >> >> Regards >> > - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
[docs] Change site target task
Hi guys, I've just realized that "Change site target" [1] is outdated. Is there still a need of it? Can I delete the whole paragraph? ATM distribution management points to the url: scm:svn:https://svn.apache.org/repos/infra/websites/production/struts/content/release/2.3.x/ [1] https://cwiki.apache.org/confluence/display/WW/Building+Struts+2+-+Fast+track+release#BuildingStruts2-Fasttrackrelease-Changesitetarget Twitter :http://www.twitter.com/m_cucchiara G+ :https://plus.google.com/107903711540963855921 Linkedin:http://www.linkedin.com/in/mauriziocucchiara VisualizeMe: http://vizualize.me/maurizio.cucchiara?r=maurizio.cucchiara Maurizio Cucchiara - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: [docs] Change site target task
2013/4/18 Maurizio Cucchiara : > Hi guys, > I've just realized that "Change site target" [1] is outdated. Is there > still a need of it? Can I delete the whole paragraph? > > ATM distribution management points to the url: > scm:svn:https://svn.apache.org/repos/infra/websites/production/struts/content/release/2.3.x/ Right now I don't have a good idea how to automatically push a new version of docs. Right now I'm simply checking out the whole site, update it manually base on target/checkout/ (here you have tagged version) with the command below: mvn site:site site:stage -DstagingDirectory=/Users/lukaszlenart/Sites/struts/release/2.3.x/ then I'm updating docs by expanding target/checkout/assembly/target/assembly/out/struts-X.X.X.X-docs.zip into /Users/lukaszlenart/Sites/struts/release/2.3.x/docs then svn add --force * and svn commit But this is far from optimal :\ 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
Re: Plan for Struts 3
I know it's a bit contentious, but I would really like the package name to be org.apache.struts3 so that people migrate from struts 1 progressively. i am actually in the process of doing this now with struts 2.3 (1000 some actions) and it's a life-saver. It will take several years in our team's product life cycle to complete the transition. On Thu, Apr 18, 2013 at 1:00 AM, Lukasz Lenart wrote: > A new plan :D > > Plan for Struts 2.5: > 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 > Prepare the first release > > Plan for Struts 3: > Rename Struts 2 packages to org.apache.struts > > > 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 > >
Example of hard coded based struts2 configuration for Configuration Manager Impl.
Are there any examples that show struts2 configuration without reading content from an XML file? The purpose of this is I'm tracing though all this code to understand how the configuration is assembled and it isn't clear yet. The goal is to produce a new configuration manager, I was wondering if there were tests that have needed to manually create such configuration. Also if anyone has some detailed documentation on how the different components fit together. Obviously some of this can be derived from interpretation of the XML but still an explanation directly from the API level of how the assembly works would be really nice.
Re: svn commit: r1469387 - /struts/struts2/tags/STRUTS_2_3_14_1/
For some weird reason, the maven release plugin tag the wrong version (struts/struts2/tags/STRUTS_2_3_14 instead of struts/struts2/branches/STRUTS_2_3_14.X). My guess is that this happen because the wrong info into the scm connections: This: scm:svn:http://svn.apache.org/repos/asf/struts/struts2/tags/STRUTS_2_3_14 scm:svn:https://svn.apache.org/repos/asf/struts/struts2/tags/STRUTS_2_3_14 http://svn.apache.org/viewcvs.cgi/struts/struts2/tags/STRUTS_2_3_14 Should be: scm:svn:http://svn.apache.org/repos/asf/struts/struts2/branches/STRUTS_2_3_14_X scm:svn:https://svn.apache.org/repos/asf/struts/struts2/branches/STRUTS_2_3_14_X http://svn.apache.org/viewcvs.cgi/struts/struts2/branches/STRUTS_2_3_14_X I'm going to update fast track release guide. Twitter :http://www.twitter.com/m_cucchiara G+ :https://plus.google.com/107903711540963855921 Linkedin:http://www.linkedin.com/in/mauriziocucchiara VisualizeMe: http://vizualize.me/maurizio.cucchiara?r=maurizio.cucchiara Maurizio Cucchiara On 18 April 2013 17:55, wrote: > Author: mcucchiara > Date: Thu Apr 18 15:55:44 2013 > New Revision: 1469387 > > URL: http://svn.apache.org/r1469387 > Log: > [maven-release-plugin] copy for tag STRUTS_2_3_14_1 > > Added: > struts/struts2/tags/STRUTS_2_3_14_1/ (props changed) > - copied from r1469386, struts/struts2/tags/STRUTS_2_3_14/ > > Propchange: struts/struts2/tags/STRUTS_2_3_14_1/ > -- > reviewboard:url = https://reviews.apache.org > > Propchange: struts/struts2/tags/STRUTS_2_3_14_1/ > -- > --- svn:ignore (added) > +++ svn:ignore Thu Apr 18 15:55:44 2013 > @@ -0,0 +1,10 @@ > +.classpath > +.project > +.settings > +*.ipr > +*.iml > +*.iws > +target > +.idea > + > +test-output > > Propchange: struts/struts2/tags/STRUTS_2_3_14_1/ > -- > --- svn:mergeinfo (added) > +++ svn:mergeinfo Thu Apr 18 15:55:44 2013 > @@ -0,0 +1,2 @@ > +/struts/struts2/branches/STRUTS_2_2_1_1:1037870-1053416 > +/struts/struts2/tags/STRUTS_2_2_1:965062-1037869 > > - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: Moving docs from the source
Don't really understand. In a bit of a rush if I reread it maybe it would sink in: If you mean to prevent the code from updating the developer guide then great. The developer guide should contain links to the javadoc where appropriate which of course does need to stay in sync with the code. No content should be removed from the source files. Although adding links to the dev guide would certainly help. BTW if you search "sturts2 javadoc" the first page is: http://struts.apache.org/javadoc.html -> http://struts.apache.org/development/2.x/struts2-core/apidocs/index.html (Broken, kind of annoying) On Thu, Apr 18, 2013 at 2:00 AM, Christian Grobmeier wrote: > +1 > > > On Thu, Apr 18, 2013 at 9:40 AM, Lukasz Lenart > wrote: > > Hi, > > > > Right now we have a small mismatch where the docs are kept. They are > > partially in Confluence and partially in a source code of a class. > > Take look on that page [1] and you will find a nice looking sections > > messed up with a bit ugly inlined code. The problem is that to correct > > that I have to know the source code, I mean which class is included by > > a snippet to render given section. So basically I must hit Edit on the > > page, check the name of the class, go to IDE, change class, commit, > > etc very long path to improve just a typo :\ > > > > My idea is to move all the descriptions into wiki and left just a > > brief description of a class with a link to the docs. > > > > [1] http://struts.apache.org/development/2.x/docs/actionmapper.html > > > > > > 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 > > > > > > -- > http://www.grobmeier.de > https://www.timeandbill.de > > - > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > For additional commands, e-mail: dev-h...@struts.apache.org > >
