[Struts Wiki] Update of "StrutsActionRelease133" by WendySmoak

Dear Wiki user, You have subscribed to a wiki page or wiki category on "Struts Wiki" for change notification. The following page has been changed by WendySmoak: http://wiki.apache.org/struts/StrutsActionRelease133 --

[VOTE] Struts Action Framework v1.3.3 Quality

The Struts Action Framework 1.3.3 Test Build is available to evaluate for release quality. The release plan is available on the wiki: http://wiki.apache.org/struts/StrutsActionRelease133 The test build, including signatures and checksums, has been deployed to: http://svn.apache.org/dist/str

[Struts Wiki] Update of "StrutsActionRelease133" by WendySmoak

Dear Wiki user, You have subscribed to a wiki page or wiki category on "Struts Wiki" for change notification. The following page has been changed by WendySmoak: http://wiki.apache.org/struts/StrutsActionRelease133 --

[Struts Wiki] Update of "StrutsMavenRelease" by WendySmoak

Dear Wiki user, You have subscribed to a wiki page or wiki category on "Struts Wiki" for change notification. The following page has been changed by WendySmoak: http://wiki.apache.org/struts/StrutsMavenRelease The comment on the change is: Combine deploy, site, and site:deploy

[Struts Wiki] Update of "StrutsMavenRelease" by WendySmoak

Dear Wiki user, You have subscribed to a wiki page or wiki category on "Struts Wiki" for change notification. The following page has been changed by WendySmoak: http://wiki.apache.org/struts/StrutsMavenRelease -- 1.

[Struts Wiki] Update of "StrutsActionRelease133" by WendySmoak

Dear Wiki user, You have subscribed to a wiki page or wiki category on "Struts Wiki" for change notification. The following page has been changed by WendySmoak: http://wiki.apache.org/struts/StrutsActionRelease133 --

[Struts Wiki] Update of "StrutsActionRelease133" by WendySmoak

Dear Wiki user, You have subscribed to a wiki page or wiki category on "Struts Wiki" for change notification. The following page has been changed by WendySmoak: http://wiki.apache.org/struts/StrutsActionRelease133 --

[Struts Wiki] Update of "StrutsActionRelease133" by WendySmoak

Dear Wiki user, You have subscribed to a wiki page or wiki category on "Struts Wiki" for change notification. The following page has been changed by WendySmoak: http://wiki.apache.org/struts/StrutsActionRelease133 --

Re: [shale] Sun JSF 1.1 Binaries now available on Maven 1 repo (was: Re: [shale] JSF 1.2 binaries now pure CDDL (no Sun Binary Code License))

>From: Ed Burns <[EMAIL PROTECTED]> > > > On Wed, 08 Mar 2006 06:41:32 -0800, Ed Burns said: > > EB> Hello Shale Developers, > EB> I'm happy to report that, after Craig's prompting, we have removed the > EB> Sun Binary Code License encumbrance on the Sun JSF 1.2 implementation > EB> binar

Re: JIRA links to Subversion commits

On Thu, May 04, 2006 at 07:37:26AM -0700, Martin Cooper wrote: ... > > Only the incubator (webwork) svn tree is being parsed. I'll update the > > config file so that the rest of struts is parsed too. > > > Aha! Of course - I was forgetting we have two SVN trees right now. Thanks, > Jeff! As you'

Re: svn commit: r404856 - /struts/action2/

Wendy Smoak wrote: I organized action2 into the usual branches/tags/trunk structure, and added it to the 'current' external. Then I noticed a few jar files as things scrolled by during an update. Can any of these be removed? ~/svn/struts/current/action2 $ find . -name *.jar ./apps/portlet/src/m

Bug report for Struts [2006/05/07]

+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

[shale] Sun JSF 1.1 Binaries now available on Maven 1 repo (was: Re: [shale] JSF 1.2 binaries now pure CDDL (no Sun Binary Code License))

> On Wed, 08 Mar 2006 06:41:32 -0800, Ed Burns <[EMAIL PROTECTED]> said: EB> Hello Shale Developers, EB> I'm happy to report that, after Craig's prompting, we have removed the EB> Sun Binary Code License encumbrance on the Sun JSF 1.2 implementation EB> binaries at

Re: svn commit: r404856 - /struts/action2/

I organized action2 into the usual branches/tags/trunk structure, and added it to the 'current' external. Then I noticed a few jar files as things scrolled by during an update. Can any of these be removed? ~/svn/struts/current/action2 $ find . -name *.jar ./apps/portlet/src/main/etc/gridsphere/g

Re: [Action2] STATUS - Documentation

Thanks, but almost everything was already there. I'm just making a refactoring pass to ensure consistency and completeness. The snippet macro does work with absolute URIs, but once the codebase comes over from the incubator, setting up the short-cuts Toby mentioned would certainly help. -Ted. O

Re: Struts JIRA -- top level 'ALL' and/or 'SITE' project?

On 5/7/06, Ted Husted <[EMAIL PROTECTED]> wrote: I'd prefer site, since it keeps the focus on the deliverables. I agree. After thinking about it for a while I couldn't really come up with a justification for 'all'. If it's important enough to have issues, it can have its own JIRA project. -

Re: Struts JIRA -- top level 'ALL' and/or 'SITE' project?

I'd prefer site, since it keeps the focus on the deliverables. On 5/7/06, Wendy Smoak <[EMAIL PROTECTED]> wrote: What do you think of having a JIRA project for 'ALL' and/or 'SITE'? (Do we need to be concerned with the eventual merge of all the Apache JIRAs and possible duplicate project codes?)

Re: Struts JIRA -- top level 'ALL' and/or 'SITE' project?

I vote for a SITE project. --- Wendy Smoak <[EMAIL PROTECTED]> wrote: > As part of his review of the 1.3.3 snapshot, Paul suggested changing > the downloads page. This is actually part of the top-level site. > > We currently don't have anywhere to record issues for the > struts.apache.org site,

Re: [Action2] STATUS - Documentation

Wow, Ted this is looking great! I really like the new organization, as it is very easy to follow. I especially appreciate the work you've put into the Tutorial section, as that has always been a weak area in the WW docs. Patrick, we need to get that snippet macro working with the new reposi

Re: Struts JIRA -- top level 'ALL' and/or 'SITE' project?

Good idea, and AFAIK, we don't have to be worried about a JIRA merger. ALL or SITE works for me, probably ALL would be more flexible. Don Wendy Smoak wrote: As part of his review of the 1.3.3 snapshot, Paul suggested changing the downloads page. This is actually part of the top-level site.

Re: Struts Action 1.3.3 release will be going for GA, need feedback now

Paul Benedict wrote: Very nice job. I am extremely impressed with how 1.3 is organized. Ted is totally right for saying 2006 is a "hotbed of activity" for Struts :) Some things to consider. #1) The Development milestones haven't been updated since 1.2.6. If you don't care about documenting anyt

Re: Struts Action 1.3.3 release will be going for GA, need feedback now

On 5/7/06, Don Brown <[EMAIL PROTECTED]> wrote: > I think Don worked on these already (after that snapshot). Does this > look better? > http://struts.apache.org/struts-action/milestones.html Actually, I removed this page, merging its content into the roadmap page. Check the live website for

Re: Struts Action 1.3.3 release will be going for GA, need feedback now

Wendy Smoak wrote: On 5/7/06, Paul Benedict <[EMAIL PROTECTED]> wrote: #2) Milestone page links to "Struts Classic Release Plan 1.3.0" which I think is no longer a relevant proposal, as it is under the Relevant Proposal section. We've consolidated all those libraries back into one numbered ver

Re: Struts Action 1.3.3 release will be going for GA, need feedback now

On 5/7/06, Paul Benedict <[EMAIL PROTECTED]> wrote: #1) The Development milestones haven't been updated since 1.2.6. If you don't care about documenting anything else in 1.2.x, at least split off 1.3.x into 1.3.3 and 1.3.x, so that the notes are official. There's a couple of "TODO" items still l

Struts JIRA -- top level 'ALL' and/or 'SITE' project?

As part of his review of the 1.3.3 snapshot, Paul suggested changing the downloads page. This is actually part of the top-level site. We currently don't have anywhere to record issues for the struts.apache.org site, or for things that affect more than one of the sub-projects. What do you think

Re: [action][Proposal] Architecture plan for Struts Action 2.0

I am a bit surprised that this was not all pretty well worked out in detail before the merger. Why not first take the time to see what will need to be done and what the result will look like before deciding to do it? That should not be a daunting task. A list of what the result will take and wh

Re: What's the goal of SAF 2.0? (was Public API first draft )

On 5/6/06, Don Brown <[EMAIL PROTECTED]> wrote: Please don't judge until we are done. Silence can be taken to imply consent, and if people with questions don't speak up now, then other people might be disappointed later, when a binding veto lands on the table. We need to first agree on our des

Re: [action][Proposal] Architecture plan for Struts Action 2.0

On 5/6/06, Bob Lee <[EMAIL PROTECTED]> wrote: The new API should be simpler, cleaner, better separated from the implementation, more intuitive, and better organized. If you understand WW2, you'll have no problem understanding the new API. If you haven't learned WW2 yet, it will be easier to learn

[Action2] STATUS - Documentation

I've been trudging through the SAF2 wiki, updating the links, nomenclature, and formatting for an Action 2 distribution. Aside from the mechanical work, I've also been filling in the TODOs and smoothing over other rough spots. I should be able to get through the rest of the Reference section thi

Re: Struts Action 1.3.3 release will be going for GA, need feedback now

Very nice job. I am extremely impressed with how 1.3 is organized. Ted is totally right for saying 2006 is a "hotbed of activity" for Struts :) Some things to consider. #1) The Development milestones haven't been updated since 1.2.6. If you don't care about documenting anything else in 1.2.x, at

Struts Action 1.3.3 release will be going for GA, need feedback now

Wendy is planning to roll the Struts Action 1.3.3 release tomorrow, and I think it is about time for a GA release. Since the last 1.3.2 beta release, we've: - Cleaned up the website - Fixed 19 tickets (below) - Vastly improved the build and examples We aim to be asking for GA for this next rel