...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
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 kno
+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 b
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
+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 b
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 p
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.apac
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/conte
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
pro
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 t
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/st
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
con
12 matches
Mail list logo
