On 7/4/06, Wendy Smoak [EMAIL PROTECTED] wrote:
The struts-master v3 pom is available in the snapshot repo, so as long
as it looks good, the parent tag in struts1/pom.xml can be changed:
3-SNAPSHOT - 3.
Done.
The repository ids for distributionManagement have been
consolidated. If you're
+1
--
James Mitchell
On Jul 5, 2006, at 1:05 AM, Wendy Smoak wrote:
It's time to release version 3 of the struts-master pom:
* http://svn.apache.org/repos/asf/struts/maven/trunk/pom/pom.xml
This is the master pom from which struts-parent inherits, and it needs
to be released prior to
On 7/1/06, Don Brown (JIRA) [EMAIL PROTECTED] wrote:
Rename Struts Action 1 to Struts 1
If we are using struts1 and struts2 for the repository folders
(which is fine with me), why are we using 1.x and 2.0 for the
website folders?
* http://struts.apache.org/1.x/
* http://struts.apache.org/2.0/
On 7/5/06, Wendy Smoak [EMAIL PROTECTED] wrote:
Ted is threatening to roll 1.3.5 any day now
Yes, I'm reviewing the release plans for 1.3.5 and 2.0 today, and
wrapping up any outstanding issues (especially STR-2898).
I'm glad to see how busy everyone has been over the weekend. It looks
like a
See
* http://issues.apache.org/struts/browse/STR-2898
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Right now, only the Struts Dev forum is available as a OS Forum.
The best place to post a question like this is the Struts User list,
where there are more people to help and the answers are archived.
* http://struts.apache.org/mail.html
-Ted.
On 7/3/06, Ashok Kumar Y [EMAIL PROTECTED] wrote:
+1
James Mitchell wrote:
+1
--
James Mitchell
On Jul 5, 2006, at 1:05 AM, Wendy Smoak wrote:
It's time to release version 3 of the struts-master pom:
* http://svn.apache.org/repos/asf/struts/maven/trunk/pom/pom.xml
This is the master pom from which struts-parent inherits, and it needs
I chose 1.x and 2.0 because I think it fits better with the other archived web
sites. The struts1 and struts2 names are more for internal use and in
particular, struts1 is only used in svn due to the maven workaround. I think
1.x and 2.0, as well as the past 1.2.9 and so on, is easier for the
it is configured, it doesn't help
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=36323messageID=71456#71456
-
To unsubscribe,
I hate to bring this question back, but do we have a final decision on
how 1.x and 2.x codebases are treated name-wise and what is the
official way to refer to a product/version?
Because seems that Don, for example, have a different idea on naming:
I think it is as simple as Struts 1.3, Struts
I think you are over-thinking this one. Struts is a single product with
multiple versions. Since both are still developed, at times, it is helpful to
refer to Struts 2.0 as Struts 2 and Struts 1.x as Struts 1, but these names are
really optional and a tool to help clarify versions. In the
I think that there should be ONE strict naming system that every
commiter has to obey whether writing a high-profile article or an
informan email. Such a system will indeed serve as a tool to help
clarify versions. After all, when I say for example Struts 2 I do
not want to explain later have I
On 7/5/06, Michael Jouravlev [EMAIL PROTECTED] wrote:
Having a system is usually a good thing.
Perhaps it would help to define these terms, which I think many people
use naturally.
Struts 2 - The product represented by the repository head.
Struts 2.x - The product that the repository head is
On 7/5/06, Don Brown [EMAIL PROTECTED] wrote:
I chose 1.x and 2.0 because I think it fits better with the other archived web
sites. The struts1 and struts2 names are more for internal use and in
particular, struts1 is only used in svn due to the maven workaround. I think
1.x and 2.0, as well
It would be better to take this thead to the user list.
* http://struts.apache.org/mail.html
(Perhaps it is time to setup a OS forum for the Struts user list too.)
-Ted.
On 7/5/06, ninavagyan [EMAIL PROTECTED] wrote:
it is configured, it doesn't help
So in your terms Struts 2 == SAF2. This does not tell me much ;-) Is
it strictly WW2.x or anything starting from WW2.x codebase onwards? I
guess the latter considering that Struts 2 is represented by the
repository head.
See, your definition is not clear enough for an end user while being
too
Well, that raises an interesting problem. When a user goes to the Struts site,
they expect to see documentation covering the latest released version, but when
developers maintain the site, they are documenting the latest code in development.
I like the idea of automatically versioned sites as
On 7/5/06, Michael Jouravlev [EMAIL PROTECTED] wrote:
So in your terms Struts 2 == SAF2. This does not tell me much ;-) Is
it strictly WW2.x or anything starting from WW2.x codebase onwards?
I guess the latter considering that Struts 2 is represented by the
repository head.
Yes, I think the
IMHO Struts means the latest/current developmentin other
words...SAF2, struts2, 2.x,
I think we should just say Struts, but clarify only if we mean an
older version. I mean, we do that now with everything else. If
someone has a question about Struts, and it happens to pertain to 1.0
On 7/5/06, Don Brown [EMAIL PROTECTED] wrote:
Well, that raises an interesting problem. When a user goes to the Struts site,
they expect to see documentation covering the latest released version, but when
developers maintain the site, they are documenting the latest code in
development.
Yes,
That assumes all the development and support effort go towards one
framework, Struts 2. If we're still actively supporting and
developing the Struts 1.x line, then references to Struts should
include a qualification of which Struts framework is meant.
Hubert
On 7/5/06, James Mitchell [EMAIL
On 7/2/06, Wendy Smoak [EMAIL PROTECTED] wrote:
Does the JasperReports dependency [2] need to be commented out by
default? I thought it was under a non-ASL-compatible license, and
couldn't be included in any 'default' build. I'm not exactly sure how
that applies to an archetype, but wanted to
Yes, I think we should avoid confusion with QuickStart.
I haven't looked at all of these closely yet. Can we go back to
calling it blank, or is there already another by that name?
-Ted.
On 7/2/06, Wendy Smoak [EMAIL PROTECTED] wrote:
Another thought on the Struts 2 archetype:
Is there
I respectfully disagree. I think having to clarify Struts as 1
or 2 is just as bad as having to say Struts Action 1 vs. Struts
Action 2 vs. Shale.
Believe me, I'm not trying to discount the 1.x development. I have
stated as much on several threads. Also, I have many 1.x apps to
On 7/5/06, James Mitchell [EMAIL PROTECTED] wrote:
Your thoughts?
I think we are dangerously closed to discussion what is is :)
So, lets have that discussion and get it over with.
First, in practice, the committers uniformly cite what version we are
talking about. I don't think we have a
On 7/5/06, James Mitchell [EMAIL PROTECTED] wrote:
Believe me, I'm not trying to discount the 1.x development. I have
stated as much on several threads. Also, I have many 1.x apps to
support, and I think my recent work on getting the 1.2.x and 1.3.x
nightlies back online proves my commitment
See
* http://issues.apache.org/struts/browse/SITE-8
-T.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This is question for the user list, but I can mention that switching
between http and https is not fun to do in Struts 1, but the SSL Ext
taglib may help.
* http://sslext.sourceforge.net/
-Ted.
On 6/28/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Hi ,
Iam developing application in struts
On 7/5/06, Ted Husted [EMAIL PROTECTED] wrote:
On 7/5/06, James Mitchell [EMAIL PROTECTED] wrote:
Your thoughts?
I think we are dangerously closed to discussion what is is :)
So, lets have that discussion and get it over with.
skipped
Other people are going to refer to Struts the same way
So people know, I just did:
svn move -m Moving Shale to TLP
https://svn.apache.org/repos/asf/struts/shale https://svn
.apache.org/repos/asf/shale
Committed revision 419348.
You'll need to use svn switch to change your svn checkout to the new location.
( svn switch
On 7/5/06, Michael Jouravlev [EMAIL PROTECTED] wrote:
The disagreement and confusion is having and publicly using 1 and
2 labels. Do we use them internally? Do we use them publicly?
Everything we do is public. There aren't any secret internal-use labels.
What do these labels mean? Do they
On 7/5/06, Michael Jouravlev [EMAIL PROTECTED] wrote:
The disagreement and confusion is having and publicly using 1 and
2 labels. Do we use them internally? Do we use them publicly? What
do these labels mean? Do they identify generations like Java and Java2
or Win9x and WinNT, or do they
A thought occured to me today. If we ever want to share code between struts 1
and struts 2c (ie: locale resolution), having the org.apache.struts package
structure being the neutral place makes sense, with action (1.x) and action2
(2.x) being specific implementations.
Well, not that the
I do not think Struts connotates 1.x, or 2.x, or the current production
release, or whatever. It's just a title for our line of products. If you need
to talk about a version, just say so. I am content and agree with James.
James Mitchell [EMAIL PROTECTED] wrote: I respectfully disagree. I
Everything we do is public. There aren't any secret internal use labels.
Ted, then you are obviously not in on the secret. :)
Ted Husted [EMAIL PROTECTED] wrote: On 7/5/06, Michael Jouravlev wrote:
The disagreement and confusion is having and publicly using 1 and
2 labels. Do we use them
Good question. Here are the options of the top of my head:
- Jakarta Commons project
- Put it in Struts 1.x, since Struts 2 will probably have 1 has a dep for
migration code
- Create new Struts Commons
- Just have two copies of the code
To be honest, I lean towards the last option, unless
On 7/5/06, Don Brown [EMAIL PROTECTED] wrote:
Good question. Here are the options of the top of my head:
- Jakarta Commons project
- Put it in Struts 1.x, since Struts 2 will probably have 1 has a dep
for
migration code
- Create new Struts Commons
- Just have two copies of the code
On 7/5/06, Ted Husted [EMAIL PROTECTED] wrote:
Yes, I think we should avoid confusion with QuickStart.
I haven't looked at all of these closely yet. Can we go back to
calling it blank, or is there already another by that name?
Toby, is the archetype patterned more after the struts2-blank or
On Jul 5, 2006, at 2:33 AM, Wendy Smoak wrote:
Ted is threatening to roll 1.3.5 any day now, so here are updated
snapshots of the assemblies:
http://people.apache.org/builds/struts/1.3.x/assembly/
Looks great Wendy!
I took a quick look around, and noticed that both the myfaces-api and
I think it would be more towards starter, i guess. It is runnable and have a
simple action in it with validation and conversion as well.
rgds.
- Original Message
From: Wendy Smoak [EMAIL PROTECTED]
To: Struts Developers List dev@struts.apache.org
Cc: [EMAIL PROTECTED]
Sent:
40 matches
Mail list logo
