On 6/28/06, Michael Jouravlev wrote:
You mean, Struts 2.0 version 2.0, then Struts 2.0 version 2.1, Struts
2.0 version 2.2, ..., Struts 2.0 version 3.0, ..., Struts 2.0 version
4.0
:-)
2.0 is a version number, while we are choosing project names (Are we?)
Do we treat Struts2 as the next version, or do we treat Struts and
Struts2 as separate subprojects like Win9x/Me vs. WinNT/2K/XP ?
(Obviously I prefer the latter)
How version numbers correspond to project names?
Can Struts 2 subproject have version number higher than 2.x? (I think yes)
Can Struts [implied: 1] have version numbers higher than 1.x?
(theoretically yes, but that would be bizzare)
this
and
https://svn.apache.org/repos/asf/struts/actionsubversion
the
which
can
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
You mean, Struts 2.0 version 2.0, then Struts 2.0 version 2.1, Struts
2.0 version 2.2, ..., Struts 2.0 version 3.0, ..., Struts 2.0 version
4.0
:-)
2.0 is a version number, while we are choosing project names (Are we?)
Do we treat Struts2 as the next version, or do we treat Struts and
Struts2 as separate subprojects like Win9x/Me vs. WinNT/2K/XP ?
(Obviously I prefer the latter)
How version numbers correspond to project names?
Can Struts 2 subproject have version number higher than 2.x? (I think yes)
Can Struts [implied: 1] have version numbers higher than 1.x?
(theoretically yes, but that would be bizzare)
On 6/28/06, Bob Lee wrote:
+1 for Struts 2.0
Bob
the+1 for Struts 2.0
Bob
On 6/28/06, Don Brown wrote:
With the departure of Struts Shale, I think it is time we return to
With the departure of Struts Shale, I think it is time we return to
idea of
Struts as a single, unified framework. While I had hoped we could do
Struts as a single, unified framework. While I had hoped we could do
by
including Shale, everyone involved felt Shale deserved its own project
including Shale, everyone involved felt Shale deserved its own project
so
I'm adjusting my original Struts 2.0 proposal to simply rename Struts
Action as
Struts.
The ramifications of such a renaming up for discussion:
1. Struts Action 1.3 becomes Struts 1.3 and Struts Action 2.0becomes
Struts 2.0
2. We rename the
I'm adjusting my original Struts 2.0 proposal to simply rename Struts
Action as
Struts.
The ramifications of such a renaming up for discussion:
1. Struts Action 1.3 becomes Struts 1.3 and Struts Action 2.0becomes
Struts 2.0
2. We rename the
directory as https://svn.apache.org/repos/asf/struts/framework, keep
other
top level directories the same
3. The org.apache.struts.action2 package becomes org.apache.struts2
4. action.* and struts-action.* configuration files become struts.*
5. The SAF acronym in the documentation would return to Struts
Given all the product naming changes in the last few years (much of
top level directories the same
3. The org.apache.struts.action2 package becomes org.apache.struts2
4. action.* and struts-action.* configuration files become struts.*
5. The SAF acronym in the documentation would return to Struts
Given all the product naming changes in the last few years (much of
was my
fault, I admit), I'd like to have these changes decided on soon, so we
fault, I admit), I'd like to have these changes decided on soon, so we
move
on to getting Struts 2.0 out the door.
Don
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
on to getting Struts 2.0 out the door.
Don
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
--
"You can lead a horse to water but you cannot make it float on its back."
~Dakota Jack~
