[Struts Wiki] Update of "StrutsActionRelease133" by WendySmoak

[Apache Wiki]

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

--
   * Wait about five minutes for Maven to download and build everything
   ** If you see any error messages, please do a quick search of the mail 
archives and/or post them on the Dev list, and if they appear to be newly 
introduced issues, a Jira tickets will need to be created so we can track and 
resolve the issue as quickly as possible.  Oh, and THANK YOU for your help.
  
- == Outstanding Bugs ==
+ == Outstanding Issues ==
  
  
http://issues.apache.org/struts/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10121&fixfor=21710
+ 
+ == Resolved Issues ==
+ 
+ 
http://issues.apache.org/struts/secure/ReleaseNote.jspa?version=21710&styleName=Text&projectId=10121&Create=Create
  
  == TO DO ==
  
@@ -90, +94 @@

  || A4. || Upload Distribution to 
people.apache.org:/www/cvs.apache.org/dist/struts/action/v1.3.3 || (./) ||
  || A5. || Update all pom.xml files to "1.3.4-SNAPSHOT" || (./) ||
  || A6. || Announce the Test Build on dev@ and user@ lists (optional) || -- ||
- || A7. || Post release-quality vote on dev@ list  ||  ||
+ || A7. || Post release-quality vote on dev@ list  || (./)  ||
  
  
  == Vote (A) ==

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[VOTE] Struts Action Framework v1.3.3 Quality

[Wendy Smoak]

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/struts/action/v1.3.3

In addition, all jars, webapps, sources and javadocs are available in
Apache's Maven snapshot repository under groupId
'org.apache.struts.action'.
http://cvs.apache.org/maven-snapshot-repository

Known issues:
* struts-faces-example2 does not work

Once you have had a chance to review this test build, please respond
with a vote on its quality:

[ ] Alpha
[ ] Beta
[ ] General Availability (GA)

We welcome votes from all community members, however, only the votes
of Struts PMC members are binding.

--
Wendy Smoak

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[Struts Wiki] Update of "StrutsActionRelease133" by WendySmoak

[Apache Wiki]

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

--
  || A0. || Update all pom.xml files to omit "-SNAPSHOT" || (./)  ||
  || A1. || Tag release in svn: STRUTS_ACTION_1_3_3 || (./)  ||
  || A2. || Check out a clean copy using the 'tag' created in A1 and 
see StrutsMavenRelease || (./) ||
- || A3. || Deploy Test Build to cvs.apache.org/maven-snapshot-repository ||  ||
+ || A3. || Deploy Test Build to cvs.apache.org/maven-snapshot-repository || 
(./)  ||
- || A4. || Upload Distribution to 
people.apache.org:/www/cvs.apache.org/dist/struts/action/v1.3.3 ||  ||
+ || A4. || Upload Distribution to 
people.apache.org:/www/cvs.apache.org/dist/struts/action/v1.3.3 || (./) ||
- || A5. || Update all pom.xml files to "1.3.4-SNAPSHOT" ||  ||
+ || A5. || Update all pom.xml files to "1.3.4-SNAPSHOT" || (./) ||
- || A6. || Announce the Test Build on dev@ and user@ lists (optional) ||  ||
+ || A6. || Announce the Test Build on dev@ and user@ lists (optional) || -- ||
- || A7. || Post release-quality vote on dev@ and user@ lists ||  ||
+ || A7. || Post release-quality vote on dev@ list  ||  ||
  
  
  == Vote (A) ==

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[Struts Wiki] Update of "StrutsMavenRelease" by WendySmoak

[Apache Wiki]

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

--
  {{{
  ~/svn/struts/STRUTS_ACTION_1_3_X
  $ rm -rf $M2_REPO/org/apache/struts/action
- $ mvn deploy -P pre-assembly,perform-itest
+ $ mvn deploy site site:deploy -P pre-assembly,perform-itest
  {about 20 minutes later...}
- $ mvn site site:deploy
  $ cd assembly
  $ mvn assembly:assembly
  $ scp target/assembly/out/* 
people.apache.org:/www/cvs.apache.org/dist/struts/action/v1.3.x

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[Struts Wiki] Update of "StrutsMavenRelease" by WendySmoak

[Apache Wiki]

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. Create and upload signatures for all .jar and .pom files in 
maven-snapshot-repository, and the .zip assembly file.
  
  {{{
- ~/svn/struts/current/action
+ ~/svn/struts/STRUTS_ACTION_1_3_X
  $ rm -rf $M2_REPO/org/apache/struts/action
  $ mvn deploy -P pre-assembly,perform-itest
  {about 20 minutes later...}

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[Struts Wiki] Update of "StrutsActionRelease133" by WendySmoak

[Apache Wiki]

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

--
  || '''#''' || '''Description''' || '''Completed''' ||
  || 1. || Run Unit Test targets  || (./) ||
  || 2. || Run Cactus Tests (see below) || n/a ||
- || 3. || Play test examples application (TC 5.0.x) ||  ||
+ || 3. || Play test examples application (TC 5.0.x) || (./) ||
  
  
  '''Note:''' Cactus tests are not working and have been moved to the sandbox.
@@ -84, +84 @@

  
  || '''#''' || '''Description''' || '''Completed''' ||
  || A0. || Update all pom.xml files to omit "-SNAPSHOT" || (./)  ||
- || A1. || Tag release in svn: STRUTS_ACTION_1_3_3 ||  ||
+ || A1. || Tag release in svn: STRUTS_ACTION_1_3_3 || (./)  ||
- || A2. || Check out a clean copy using the 'tag' created in A1 and 
see StrutsMavenRelease ||  ||
+ || A2. || Check out a clean copy using the 'tag' created in A1 and 
see StrutsMavenRelease || (./) ||
  || A3. || Deploy Test Build to cvs.apache.org/maven-snapshot-repository ||  ||
  || A4. || Upload Distribution to 
people.apache.org:/www/cvs.apache.org/dist/struts/action/v1.3.3 ||  ||
  || A5. || Update all pom.xml files to "1.3.4-SNAPSHOT" ||  ||

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[Struts Wiki] Update of "StrutsActionRelease133" by WendySmoak

[Apache Wiki]

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

--
  === Testing Summary ===
  
  || '''#''' || '''Description''' || '''Completed''' ||
- || 1. || Run Unit Test targets  ||  ||
+ || 1. || Run Unit Test targets  || (./) ||
- || 2. || Run Cactus Tests (see below) ||  ||
+ || 2. || Run Cactus Tests (see below) || n/a ||
  || 3. || Play test examples application (TC 5.0.x) ||  ||
  
  
+ '''Note:''' Cactus tests are not working and have been moved to the sandbox.
- === Cactus Tests ===
- 
- || '''#''' || '''J2SE Version''' || '''Tomcat Version''' ||  '''Status''' ||
- || 1. || J2SE 1.3.1_04 || Tomcat 4.1.30 ||  ||
- || 2. || J2SE 1.4.2_07 || Tomcat 4.1.30 ||  ||
- || 3. || J2SE 1.3.1_04 || Tomcat 5.0.28 ||  ||
- || 4. || J2SE 1.4.2_07 || Tomcat 5.0.28 ||  ||
- 
  
  == Test Build Checklist (A) ==
  
  See also Commons [http://jakarta.apache.org/commons/releases/release.html 
Step-by-Step Guide]
  
  || '''#''' || '''Description''' || '''Completed''' ||
- || A0. || Update all pom.xml files to omit "-SNAPSHOT" ||  ||
+ || A0. || Update all pom.xml files to omit "-SNAPSHOT" || (./)  ||
  || A1. || Tag release in svn: STRUTS_ACTION_1_3_3 ||  ||
  || A2. || Check out a clean copy using the 'tag' created in A1 and 
see StrutsMavenRelease ||  ||
  || A3. || Deploy Test Build to cvs.apache.org/maven-snapshot-repository ||  ||

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[Struts Wiki] Update of "StrutsActionRelease133" by WendySmoak

[Apache Wiki]

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

--
  == Preparation Checklist ==
  
  || '''#''' || '''Description''' || '''Status''' ||
- || 1. || Announce plan to dev@ list ||  ||
+ || 1. || Announce plan to dev@ list || (discussed) ||
- || 2. || Review/Resolve Outstanding Bugs ||  ||
+ || 2. || Review/Resolve Outstanding Bugs || (./) ||
- || 3. || Update Release Notes ||  ||
+ || 3. || Update Release Notes || (./) ||
- || 4. || Check Dependencies ||  ||
+ || 4. || Check Dependencies || (./) ||
  
  The Commons [http://jakarta.apache.org/commons/releases/prepare.html 
Preparation Guide] is a helpful preparation backgrounder, but Commons
  uses the "beta/release-candidate/final" process.
@@ -63, +63 @@

  || Commons Logging || 1.0.4 || Released || core (logging all over) ||
  || Commons Validator || 1.3.0 || Released || Struts Validator ||
  || Jakarta Oro || 2.0.8 || Released || Commons Validator ||
+ 
+ '''Note:''' This release of Struts Action depends on Struts Build 1.0.0 for 
the Checkstyle config file.
  
  == Testing Checklist ==
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

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))

[Gary VanMatre]

>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> binaries at . 
> EB> This is a maven 1.x repo, but you can use the backwards compatibility 
> EB> mechanism of maven 2 by including the legacy element in 
> EB> your declaration for the above repo. 
> 
> Well, two months later, I'm happy to report that JSF 1.1 has now been 
> released under the CDDL [1]. I have just uploaded some jars for this, 
> and now the repository at the above URL has the following. 
> 

That's most excellent news! Thanks Ed.

Gary


> group-id: javax.faces 
> 
> artifact-id: jsf-api 
> artifact-id: jsf-impl 
> 
> version: 1.1_02 
> 
> description: The final build of JSF 1.1_02 
> 
> version: 1.1_03-SNAPSHOT 
> 
> description: a snapshot taken today of the JSF_1_1_ROLLING branch 
> 
> version: 1.2-b20-SNAPSHOT 
> 
> description: a snapshot taken yesterday of the HEAD branch 
> 
> 
> [1] http://blogs.sun.com/roller/page/rlubke?entry=jsf_1_1_is_now 
> 
> Ed 
> 
> -- 
> | [EMAIL PROTECTED] | {home: 407 869 9587, office: 408 884 9519 OR x31640} 
> | homepage: | http://purl.oclc.org/NET/edburns/ 
> | aim: edburns0sunw | iim: [EMAIL PROTECTED] 
> | 06 Business Days until JavaOne SF 2006 
> 
> 
> - 
> To unsubscribe, e-mail: [EMAIL PROTECTED] 
> For additional commands, e-mail: [EMAIL PROTECTED] 
> 

Re: JIRA links to Subversion commits

[Jeff Turner]

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 back to one tree, I've updated the JIRA plugin:

http://issues.apache.org/struts/browse/STR-2852?page=all


--Jeff

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

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

[Don Brown]

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/main/etc/gridsphere/gridsphere-ui-tags-2.1.2.jar
./apps/portlet/src/main/webapp/WEB-INF/lib/batik-awt-util.jar
./apps/portlet/src/main/webapp/WEB-INF/lib/batik-svggen.jar
./apps/portlet/src/main/webapp/WEB-INF/lib/batik-util.jar
./apps/portlet/src/main/webapp/WEB-INF/lib/cewolf.jar
./apps/shopping-cart/src/main/webapp/WEB-INF/lib/sitemesh-2.2.1.jar

Yes, these should be removed.


./lib/bootstrap/clover-license.jar
./lib/bootstrap/commons-cli.jar
./lib/bootstrap/commons-httpclient.jar
./lib/bootstrap/commons-logging.jar
./lib/bootstrap/ivy-1.1.jar

No, these need to stay for the Ant build.

Thanks for the help,

Don


--
Wendy

On 5/7/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:

Author: bayard
Date: Sun May  7 14:29:56 2006
New Revision: 404856

URL: http://svn.apache.org/viewcvs?rev=404856&view=rev
Log:
Moving Webwork out of the Incubator and over to Struts as per Jira 
issue: #INFRA-791


Added:
struts/action2/
  - copied from r404855, incubator/webwork2/




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Bug report for Struts [2006/05/07]

[bugzilla]

+---+
| Bugzilla Bug ID   |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned|
| | OPN=ReopenedVER=Verified(Skipped Closed/Resolved)   |
| |   +-+
| |   | Severity: BLK=Blocker CRI=CriticalMAJ=Major |
| |   |   MIN=Minor   NOR=Normal  ENH=Enhancement   |
| |   |   +-+
| |   |   | Date Posted |
| |   |   |  +--+
| |   |   |  | Description  |
| |   |   |  |  |
| 5739|Opn|Enh|2002-01-08|Struts fails silently in too many places  |
| 5937|New|Enh|2002-01-21|[taglib] html:form trims all extensions   |
| 6847|New|Enh|2002-03-04|Multiple file upload not possible due to MultiPart|
| 7902|Opn|Enh|2002-04-10|The exception handling declaration in the DTD does|
| 8240|Ver|Min|2002-04-18|Data-Source configuration in examples is outdated |
| 9088|Opn|Enh|2002-05-15|FormTag.getActionMappingURL() assumes 1 servlet ma|
| 9616|New|Enh|2002-06-05|Some more Struts docs |
| 9748|New|Enh|2002-06-10|[taglib] attribute labelKeyProperty for Options ta|
|10550|New|Enh|2002-07-08|Delegate path-management to ActionForwards|
|10552|New|Enh|2002-07-08|create helper objects in struts-config|
|10867|Opn|Enh|2002-07-16|[taglib] Add indexedProperty attribute in html tag|
|11154|Opn|Enh|2002-07-25|[taglib] html:link tag extension for multiple para|
|11733|Opn|Enh|2002-08-15|Make error keys more specific |
|12170|Opn|Enh|2002-08-29|Added functionality when extending another definit|
|12301|Opn|Enh|2002-09-04|[taglib] nested:messages Tag does not work as expe|
|12600|New|Enh|2002-09-12|[taglib] html:form tag always prepends context pat|
|13125|Opn|Enh|2002-09-30|[taglib] Lack of character-set while using   forwardPattern should support differe|
|16708|New|Enh|2003-02-03|I18N on ActionForwards|
|16764|Opn|Enh|2003-02-04|No inheritance of html:html xhtml="true" in includ|
|16792|Ass|Enh|2003-02-05|Migrate to commons-resources for message resources|
|16814|New|Enh|2003-02-05|Add a generalized utililty class to expose informa|
|16946|Opn|Enh|2003-02-10|SwitchAction not setting context properly for tile|
|16971|New|Enh|2003-02-11|[taglib] "multiple" attribute on select tag should|
|17368|Opn|Enh|2003-02-25|[taglib]  multiple does not populate |
|17449|New|Enh|2003-02-26|[taglib] Allow relative URL in action attribute of|
|17473|New|Enh|2003-02-27|[taglib] Problem to include a jsp into an iterate |
|17530|New|Enh|2003-02-28|RequestUtils.computeURL should use the session ass|
|17559|New|Enh|2003-03-01|[tiles] key attribute for tiles (put & item)  |
|17600|New|Enh|2003-03-03|[taglib] key property for html:optionsCollection t|
|17698|Opn|Enh|2003-03-05|The value(key) form name pattern doesn't work with|
|18015|Opn|Enh|2003-03-14|[taglib] New  custom tag to write form|
|18017|Opn|Enh|2003-03-14|[tiles] extends fails in JSP-based Definitions|
|18022|New|Enh|2003-03-14|HttpSessionBindingListener.valueUnbound() called o|
|18032|Opn|Enh|2003-03-16|[taglib]  tag appending session doesn't |
|18194|Opn|Enh|2003-03-20|[resources] Enhance MessageResources to enable sev|
|18237|Opn|Enh|2003-03-21|[tiles] excessive memory usage|
|18293|New|Enh|2003-03-24|Loading language files does not use Resource Bundl|
|18788|New|Enh|2003-04-07|Multiple input hook for multipage forms in process|
|18981|New|Enh|2003-04-13|[upload] File upload maximum size validator   |
|19346|New|Enh|2003-04-26|Errors and Messages should be easier to manage|
|19539|New|Enh|2003-05-02|Add checks for List and Map-backed properties in D|
|19631|New|Enh|2003-05-04|Enhancements to RequestUtils tests|
|19812|New|Enh|2003-05-10|[taglib] BaseFieldTag don't use ConvertUtils as St|
|19903|New|Enh|2003-05-13|Field considered valid if no ActionError created  |
|19925|New|Enh|2003-05-14|Server side solution for DispatchAction and : Make value optional when id|
|21508|New|Enh|2003-07-11|[tiles]  element too restrictive|
|21512|New|Enh|2003-07-11|exception tag's path attribute accepts only web re|
|21514|New|Enh|2003-07-11|[taglib] html:form focus function could be more po|
|21517|New|Enh|2003-07-11|[tiles] definition's put tag works in non-standard|
|21575|New|Enh|2003-07-14|RequestProcessor : Populating non-String Bean fiel|
|21624|Opn|Enh|2003-07-15|Extend TokenProcessor to handle a list of tra

[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))

[Ed Burns]

> 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 .
EB> This is a maven 1.x repo, but you can use the backwards compatibility
EB> mechanism of maven 2 by including the legacy element in
EB> your  declaration for the above repo.

Well, two months later, I'm happy to report that JSF 1.1 has now been
released under the CDDL [1].  I have just uploaded some jars for this,
and now the repository at the above URL has the following.

group-id: javax.faces

  artifact-id: jsf-api
  artifact-id: jsf-impl

version: 1.1_02

  description: The final build of JSF 1.1_02

version: 1.1_03-SNAPSHOT

  description: a snapshot taken today of the JSF_1_1_ROLLING branch

version: 1.2-b20-SNAPSHOT

  description: a snapshot taken yesterday of the HEAD branch


[1] http://blogs.sun.com/roller/page/rlubke?entry=jsf_1_1_is_now

Ed

-- 
| [EMAIL PROTECTED]  | {home: 407 869 9587, office: 408 884 9519 OR x31640}
| homepage: | http://purl.oclc.org/NET/edburns/
| aim: edburns0sunw | iim: [EMAIL PROTECTED]
| 06 Business Days until JavaOne SF 2006


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

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

[Wendy Smoak]

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/gridsphere-ui-tags-2.1.2.jar
./apps/portlet/src/main/webapp/WEB-INF/lib/batik-awt-util.jar
./apps/portlet/src/main/webapp/WEB-INF/lib/batik-svggen.jar
./apps/portlet/src/main/webapp/WEB-INF/lib/batik-util.jar
./apps/portlet/src/main/webapp/WEB-INF/lib/cewolf.jar
./apps/shopping-cart/src/main/webapp/WEB-INF/lib/sitemesh-2.2.1.jar
./lib/bootstrap/clover-license.jar
./lib/bootstrap/commons-cli.jar
./lib/bootstrap/commons-httpclient.jar
./lib/bootstrap/commons-logging.jar
./lib/bootstrap/ivy-1.1.jar

--
Wendy

On 5/7/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:

Author: bayard
Date: Sun May  7 14:29:56 2006
New Revision: 404856

URL: http://svn.apache.org/viewcvs?rev=404856&view=rev
Log:
Moving Webwork out of the Incubator and over to Struts as per Jira issue: 
#INFRA-791

Added:
struts/action2/
  - copied from r404855, incubator/webwork2/




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Action2] STATUS - Documentation

[Ted Husted]

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.

On 5/7/06, Don Brown <[EMAIL PROTECTED]> wrote:

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
repository.  I think we should use struts/action2/trunk as that will be
the new home once Infrastructure moves the project from incubation.

Don

Ted Husted wrote:
> 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 this
> week. The next step would be to update the Javadocs and corresponding
> "snippet" paths. (The wiki utilizes a nifty macro that lets you
> incorporate portions of the Javadocs into the wiki text.)
>
> Once we get through the Javadoc snippets, I expect that we could
> generate a preliminary HTML version for the Apache Struts website. We
> might then follow the convention of maintaining the "nightly build"
> version on the wiki, and generating a HTML version for the website as
> part of the release process.
>
> -Ted.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

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

[Wendy Smoak]

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.

--
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

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

[Ted Husted]

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?)


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

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

[Paul Benedict]

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, or for things that affect more than one of the
> sub-projects.
> 
> 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?)
> 
> --
> Wendy
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Action2] STATUS - Documentation

[Don Brown]

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 
repository.  I think we should use struts/action2/trunk as that will be 
the new home once Infrastructure moves the project from incubation.


Don

Ted Husted wrote:

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 this
week. The next step would be to update the Javadocs and corresponding
"snippet" paths. (The wiki utilizes a nifty macro that lets you
incorporate portions of the Javadocs into the wiki text.)

Once we get through the Javadoc snippets, I expect that we could
generate a preliminary HTML version for the Apache Struts website. We
might then follow the convention of maintaining the "nightly build"
version on the wiki, and generating a HTML version for the website as
part of the release process.

-Ted.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

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

[Don Brown]

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.

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 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?)

--
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

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

[Don Brown]

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 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 listed there :)
  

Done

#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 version, haven't we?
  

Fixed.

#3) Consider listing links to the latest of previous GA releases
on the download page, one per minor-version:
* General Availability (GA) Releases
  o Struts 1.3.3
  o Struts Scripting 1.0.1
* Previous Releases
  o Struts 1.2.9
  o Struts 1.1
  o Struts 1.0.2
* Alpha Releases
  o Struts Shale 1.0.2
* Older Releases are available from the
  o Archive Site

#4a) Why do the Table of Contents for the User Guide
list out the release notes for all 1.1 version? Looks a bit
odd. I'd either remove them or add links to the other
versions. I'd prefer the latter.
  

Done

#4b) Page header is for 1.3.2.
#4c) Page title is 1.3.1.
  

Actually, once says "since 1.3.1", and the other 1.3.2, which is correct.

Thanks again for the feedback, and let us know if you see anything else.

Don

#5) 40M is a hefty download. Here's a breakdown of each piece
in compressed size:
* docs = 10MB
* lib = 3MB
* src = 6MB
* webapp = 20MB

I hope there is a "lib" only version release too.
In fact, I would go even further and only include struts
libraries and no dependencies (1MB!). Spring does it this way. You
can download only the spring libraries, or the entire library
with all the dependencies (what we have now in this snapshot).
I vote for a struts-only lib artifact too.

-- Paul

--- Don Brown <[EMAIL PROTECTED]> wrote:

  
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 release, so please voice any 
concerns now so we can _finally_ push out a 1.3.x GA release.  There are 
only 10 outstanding "bugs", five of which are Faces and the rest are 
minor and mostly unconfirmed and shouldn't hold up a GA release, in my 
opinion.  If you feel differently, please let us know ASAP. 


http://cvs.apache.org/builds/struts/maven/trunk/nightly/struts-action/

Thanks in advice,

Don

Release Notes - Struts Action 1 - Version 1.3.3

** Bug
* [STR-2509] - [struts-faces] - core-library and example1-webapp patches
* [STR-2698] - Struts API - MultipartRequestHandler documentation error
* [STR-2724] - Fix Min/Max Length Validator for different line endings
* [STR-2741] - [site] Broken Links
* [STR-2752] - forwardPattern implementation missing
* [STR-2805] - java.lang.NullPointerException
* [STR-2809] - ImportAttribute does not  import all attribute with 
ignore=true
* [STR-2826] - If a field's display property is set to 'none' using 
CSS or JavaScript, the focus code fails.

* [STR-2831] - error in nested:options web-documentation
* [STR-2837] - Fix the site build
* [STR-2843] - PropertyMessageResources.loadLocale(String localeKey) 
has a problem!
* [STR-2851] - The Struts Tiles jar is missing from the 1.3.2 
distribution

* [STR-2854] - mask validator error
* [STR-2855] - Invalid path to source Java files in Struts Cookbook

** Improvement
* [STR-1546] - [apps] Add validateLongRange and validateDoubleRange 
to validator web app

* [STR-2846] - Move source directories to standard Maven 2 format
* [STR-2850] - Add tests to confirm that example apps work
* [STR-2852] - Move the non-working integration tests to the sandbox 
for review.



** Task
* [STR-2860] - Change DOCTYPE in validator config files to v1.3.0






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


  



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

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

[Wendy Smoak]

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 the latest.


That is the live website. :)  Both roadmap and milestones were there,
published yesterday. But from the timestamps on the html pages, it
looked like an old version was in target/site and got published after
you removed it from svn.  I deleted it from minotaur.

Here's the new, improved roadmap page:
  http://struts.apache.org/struts-action/roadmap.html

--
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

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

[Don Brown]

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 version, haven't we?


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 the latest.


Don


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

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

[Wendy Smoak]

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 listed there :)

#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 version, haven't we?


I think Don worked on these already (after that snapshot).  Does this
look better?
  http://struts.apache.org/struts-action/milestones.html


#3) Consider listing links to the latest of previous GA releases
on the download page,


The download page is part of the top-level Struts site, so this can be
addressed separately from 1.3.3.


#4a) Why do the Table of Contents for the User Guide
list out the release notes for all 1.1 version? Looks a bit
odd. I'd either remove them or add links to the other
versions. I'd prefer the latter.
#4b) Page header is for 1.3.2.
#4c) Page title is 1.3.1.


I thought we were going to accumulate release notes for 1.3 until we
hit GA.  IMO we shouldn't have a "release notes" page for 1.3.1, which
was only a test build, nor should we refer to it on the 1.3.2 page as
"Release Notes (since 1.3.1)".

I'm going to drop that page and go from1.2.9 to 1.3.3, but it likely
will not be complete.  Not everything is marked 'fixed' in JIRA with
the correct release number.  If anyone would like to go through JIRA
tickets and figure out which version they belong to, that would be
great.


#5) 40M is a hefty download. ...I hope there is a "lib" only version release 
too.


Good suggestion.  I opened STR-2863 for this.  As long as the assembly
plugin cooperates, I think it can be done for 1.3.3.

Thanks for taking the time to review the snapshot!

--
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

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

[Wendy Smoak]

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 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?)

--
Wendy

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

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

[Dakota Jack]

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 what
the result will look like would be worth having before taking a vote on
this.  To just a make a decision and to start coding blindly before knowing
what the parameters of the situation are would be just to return to past
"throw it against the wall and see what sticks" sort of decision making.

The continuing introduction of "Ti" into these conversations is confusing to
me.  I am not sure what Ted means by that.  I know Ted and I know it is an
agenda for sure, but I don't know what that agenda is.

I also don't see the arguments (reasons) for evolution now revolution later
decisions.  Are there any that have been gathered, arranged, collated, etc?
This all seems a bit out of control and not well-planned.  These sorts of
discussion, by the way, have nothing to do with "architecture".

On 5/7/06, Ted Husted <[EMAIL PROTECTED]> wrote:


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 the new API
> than WW2.

All of which seems to imply that the "new API" might be the equivalent of
WW 3.

We've always planned to consider signficant API changes for "SAF 2.0
Next" as Ti Phase 2, but we need to set modest, achievable
expectations for SAF 2.0 (aka WW 2.3). The first phase is an
evolutionary transition. The second phase is meant to be
revolutionary.

Of course, without code on the table, it's too soon to say yes, no, or
maybe. No matter what anyone plans to do, the implementation has to
pass muster. The most anyone here can say is "Looks cool, show us the
code" or "Here's the code, how do you like it?".

-Ted.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
"You can lead a horse to water but you cannot make it float on its back."
~Dakota Jack~

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

[Ted Husted]

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
design goals, then we can pick through implementations.  The proposal is
about agreeing to the laid out design goals, but it is too early to say
that we are or aren't meeting them.  First cuts are never put into
production as is, and this API is no different.  Besides, even if we did
finally go with something more sweeping, to make it acceptable under the
original agreed upon proposal, we'd have to ensure existing apps would
be able to migrate in hours so you can be sure the end user will have a
smooth migration.  Otherwise, we'd have to move the API to a new version.


+1

Under the original proposal, the community agreed that the goal is for
Action 2.0 to be a smooth *transition* for WebWork developers and as
smooth a migration as we can make it for Action 1 developers.

Of course, we all want to continue to improve the framework, and under
the original proposal we agreed that more ambitious improvements are
to take place in a second phase, which may be a 2.1 or 3.0 series.

It's healthy to have these discussions, but we do not want to create
unrealistic expectations of what can be accomplished in the SAF 2.0
timeframe.



What we need here is cooperation and a willingness to compromise and
follow a common path that may not be exactly what everyone wants, but it
is what the community agreed is best for the project and its users.


True, and the community has already agreed that Action 2.0 will be a
transitional release. If we agree that some or all of the proposed API
changes are transitional, and if someone actually comes up with a
patch, and if we accept the patch, then fine. But there is no
shortages of *ifs* in that statement. We do *not* want to give people
the impression that by having these discussions, we have decided to
change course and revoke the original agreement.



My
guess is you will always think a new API goes too far, Bob will think it
doesn't go far enough, and the rest of the developers will lie along
that spectrum.  We could either fight every step of the way to force our
point of view, or we could work together to find a common vision.  I
think we owe it to our users to do the latter.


Hmmm, I can't think of a *user* to whom we owe more than Jason -- or
Patrick -- or Toby -- or Rainer  -- or anyone else who not only *uses*
the framework but also makes concrete contributions to the code and
documentation. We all are users.

-Ted.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

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

[Ted Husted]

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 the new API
than WW2.


All of which seems to imply that the "new API" might be the equivalent of WW 3.

We've always planned to consider signficant API changes for "SAF 2.0
Next" as Ti Phase 2, but we need to set modest, achievable
expectations for SAF 2.0 (aka WW 2.3). The first phase is an
evolutionary transition. The second phase is meant to be
revolutionary.

Of course, without code on the table, it's too soon to say yes, no, or
maybe. No matter what anyone plans to do, the implementation has to
pass muster. The most anyone here can say is "Looks cool, show us the
code" or "Here's the code, how do you like it?".

-Ted.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[Action2] STATUS - Documentation

[Ted Husted]

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 this
week. The next step would be to update the Javadocs and corresponding
"snippet" paths. (The wiki utilizes a nifty macro that lets you
incorporate portions of the Javadocs into the wiki text.)

Once we get through the Javadoc snippets, I expect that we could
generate a preliminary HTML version for the Apache Struts website. We
might then follow the convention of maintaining the "nightly build"
version on the wiki, and generating a HTML version for the website as
part of the release process.

-Ted.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

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

[Paul Benedict]

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 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 listed there :)

#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 version, haven't we?

#3) Consider listing links to the latest of previous GA releases
on the download page, one per minor-version:
* General Availability (GA) Releases
  o Struts 1.3.3
  o Struts Scripting 1.0.1
* Previous Releases
  o Struts 1.2.9
  o Struts 1.1
  o Struts 1.0.2
* Alpha Releases
  o Struts Shale 1.0.2
* Older Releases are available from the
  o Archive Site

#4a) Why do the Table of Contents for the User Guide
list out the release notes for all 1.1 version? Looks a bit
odd. I'd either remove them or add links to the other
versions. I'd prefer the latter.
#4b) Page header is for 1.3.2.
#4c) Page title is 1.3.1.

#5) 40M is a hefty download. Here's a breakdown of each piece
in compressed size:
* docs = 10MB
* lib = 3MB
* src = 6MB
* webapp = 20MB

I hope there is a "lib" only version release too.
In fact, I would go even further and only include struts
libraries and no dependencies (1MB!). Spring does it this way. You
can download only the spring libraries, or the entire library
with all the dependencies (what we have now in this snapshot).
I vote for a struts-only lib artifact too.

-- Paul

--- Don Brown <[EMAIL PROTECTED]> wrote:

> 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 release, so please voice any 
> concerns now so we can _finally_ push out a 1.3.x GA release.  There are 
> only 10 outstanding "bugs", five of which are Faces and the rest are 
> minor and mostly unconfirmed and shouldn't hold up a GA release, in my 
> opinion.  If you feel differently, please let us know ASAP. 
> 
> http://cvs.apache.org/builds/struts/maven/trunk/nightly/struts-action/
> 
> Thanks in advice,
> 
> Don
> 
> Release Notes - Struts Action 1 - Version 1.3.3
> 
> ** Bug
> * [STR-2509] - [struts-faces] - core-library and example1-webapp patches
> * [STR-2698] - Struts API - MultipartRequestHandler documentation error
> * [STR-2724] - Fix Min/Max Length Validator for different line endings
> * [STR-2741] - [site] Broken Links
> * [STR-2752] - forwardPattern implementation missing
> * [STR-2805] - java.lang.NullPointerException
> * [STR-2809] - ImportAttribute does not  import all attribute with 
> ignore=true
> * [STR-2826] - If a field's display property is set to 'none' using 
> CSS or JavaScript, the focus code fails.
> * [STR-2831] - error in nested:options web-documentation
> * [STR-2837] - Fix the site build
> * [STR-2843] - PropertyMessageResources.loadLocale(String localeKey) 
> has a problem!
> * [STR-2851] - The Struts Tiles jar is missing from the 1.3.2 
> distribution
> * [STR-2854] - mask validator error
> * [STR-2855] - Invalid path to source Java files in Struts Cookbook
> 
> ** Improvement
> * [STR-1546] - [apps] Add validateLongRange and validateDoubleRange 
> to validator web app
> * [STR-2846] - Move source directories to standard Maven 2 format
> * [STR-2850] - Add tests to confirm that example apps work
> * [STR-2852] - Move the non-working integration tests to the sandbox 
> for review.
> 
> 
> ** Task
> * [STR-2860] - Change DOCTYPE in validator config files to v1.3.0
> 
> 
> 
> 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

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

[Don Brown]

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 release, so please voice any 
concerns now so we can _finally_ push out a 1.3.x GA release.  There are 
only 10 outstanding "bugs", five of which are Faces and the rest are 
minor and mostly unconfirmed and shouldn't hold up a GA release, in my 
opinion.  If you feel differently, please let us know ASAP. 


http://cvs.apache.org/builds/struts/maven/trunk/nightly/struts-action/

Thanks in advice,

Don

Release Notes - Struts Action 1 - Version 1.3.3

** Bug
   * [STR-2509] - [struts-faces] - core-library and example1-webapp patches
   * [STR-2698] - Struts API - MultipartRequestHandler documentation error
   * [STR-2724] - Fix Min/Max Length Validator for different line endings
   * [STR-2741] - [site] Broken Links
   * [STR-2752] - forwardPattern implementation missing
   * [STR-2805] - java.lang.NullPointerException
   * [STR-2809] - ImportAttribute does not  import all attribute with 
ignore=true
   * [STR-2826] - If a field's display property is set to 'none' using 
CSS or JavaScript, the focus code fails.

   * [STR-2831] - error in nested:options web-documentation
   * [STR-2837] - Fix the site build
   * [STR-2843] - PropertyMessageResources.loadLocale(String localeKey) 
has a problem!
   * [STR-2851] - The Struts Tiles jar is missing from the 1.3.2 
distribution

   * [STR-2854] - mask validator error
   * [STR-2855] - Invalid path to source Java files in Struts Cookbook

** Improvement
   * [STR-1546] - [apps] Add validateLongRange and validateDoubleRange 
to validator web app

   * [STR-2846] - Move source directories to standard Maven 2 format
   * [STR-2850] - Add tests to confirm that example apps work
   * [STR-2852] - Move the non-working integration tests to the sandbox 
for review.



** Task
   * [STR-2860] - Change DOCTYPE in validator config files to v1.3.0






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]