Re: [VOTE] Struts Action Framework v1.3.4 Quality
On 5/10/06, Niall Pemberton <[EMAIL PROTECTED]> wrote: I missed the discussion where the 1.3 dtd was added - seems like its actually identical to the 1.1 dtd - which IMO serves no purpose. I would rather it was removed. I remember being involved -- it had to do with the version numbers not matching. It seems odd to use Struts Tiles 1.3 with a version 1.1 DTD. Here's the commit message. The registration was changed instead of a new one being added. I see no reason not to add it back. http://marc.theaimsgroup.com/?l=struts-dev&m=113098757610401&w=2 I don't have much time available at the moment, but I was hoping to try and check out this version by the weekend. Whether I'll get round to that I'm not sure, but it looks pretty academic since it'll have probably been voted GA by then :-( Especially with minotaur being down (so no one can download the test build) I'm fine with holding the vote open longer. In fact I was going to ask if there was anyone who _does_ intend to test it but needs more time. I doubt this build is perfect. Based on my testing, I think it's good enough for GA. However, the *last* thing I want to do is have to recall a release, so I'd rather wait until everyone has had a chance to test it. Assuming the vote is successful, I think Don would like to announce it at JavaOne. I'm not sure what kind of access I'll have from there, so if we let the vote go past the weekend, I might need help getting the distribution moved over to www.apache.org/dist and the download page updated. I definitely need help with the release announcement. And we still have to figure out how to get the jars from the "snapshot and test build" Maven repo over to www.apache.org/dist/maven-repository. (It's not as simple as copying them over, and I'm uncomfortable with the idea of re-building them, which Maven would do if I changed the in the pom and re-'mvn deploy'ed them.) Niall, does Monday give you enough time? Calling the vote immediately was intended to encourage testing and evaluation, not to lock people out of the process by rushing it through. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
how to highlight 2 passwords fields in case validwhen fails?
I am using struts 1.1. I have two fields in a form: pwd, retypePwd. I use validwhen to validate whether these two fields are exactly same. It works fine. But I want to highlight these two fields in case validation fails. I use a javascript function to get failed fields from session, but it always empty. could anyone help me out? thank you - Posted via Jive Forums http://forums.opensymphony.com/thread.jspa?threadID=30376&messageID=58793#58793 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Struts Action Framework v1.3.4 Quality
Normally, I'd agree with you but: a) This is the latest in a succession of very recent releases so little has changed (last one was Sunday) b) Theoretically people test during that week, but in practice few do. Seems people don't pay attention until a vote is called We can always recall a release or throw out a new one if a major issue has been found, but as I've said, this is the same code that has been there for months and yes, I dare say years. We've been spending all our time (way too much porportionally, IMO) on the build and site, but the code has been very stable. For the next significant release, I'm fine with waiting the extra week. Don Niall Pemberton wrote: In the past we've made a new version available for people to check out for a period of time (my preference is at least a week) before calling a vote. I'm against this process of publishing and calling a vote immediately as I believe it increases the chance of a build with problems being voted GA. I don't have much time available at the moment, but I was hoping to try and check out this version by the weekend. Whether I'll get round to that I'm not sure, but it looks pretty academic since it'll have probably been voted GA by then :-( Niall On 5/10/06, Wendy Smoak <[EMAIL PROTECTED]> wrote: The Struts Action Framework 1.3.4 Test Build is available to evaluate for release quality. The release plan is available on the wiki: http://wiki.apache.org/struts/StrutsActionRelease134 The test build, including checksums and signatures, has been deployed to: http://svn.apache.org/dist/struts/action/v1.3.4 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 Since 1.3.3, the following issues have been resolved: * [STR-2795] - Postback Forms - Caching and Modules * [STR-2866] - Struts Tiles jar is missing dtd, tld and chain config files * [STR-2867] - Dependency problems in faces-example2 sample app (using Tiles) * [STR-2870] - The Specification-Title in the jar file manifests is corrupted * [STR-2872] - Section "4.3.3 Map-backed ActionForms" of User's Manual contains a dead link * [STR-2871] - Rename the release notes so that the filename contains a single period Known issues in 1.3.4: * struts-faces-example2 deploys but the links do 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. My vote is for GA quality. I've had 1.3 in production for eight months with no problems, and I believe we've resolved all of the packaging issues discovered since converting to Maven 2 and reorganizing the project. -- Wendy Smoak - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Struts Action Framework v1.3.4 Quality
In the past we've made a new version available for people to check out for a period of time (my preference is at least a week) before calling a vote. I'm against this process of publishing and calling a vote immediately as I believe it increases the chance of a build with problems being voted GA. I don't have much time available at the moment, but I was hoping to try and check out this version by the weekend. Whether I'll get round to that I'm not sure, but it looks pretty academic since it'll have probably been voted GA by then :-( Niall On 5/10/06, Wendy Smoak <[EMAIL PROTECTED]> wrote: The Struts Action Framework 1.3.4 Test Build is available to evaluate for release quality. The release plan is available on the wiki: http://wiki.apache.org/struts/StrutsActionRelease134 The test build, including checksums and signatures, has been deployed to: http://svn.apache.org/dist/struts/action/v1.3.4 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 Since 1.3.3, the following issues have been resolved: * [STR-2795] - Postback Forms - Caching and Modules * [STR-2866] - Struts Tiles jar is missing dtd, tld and chain config files * [STR-2867] - Dependency problems in faces-example2 sample app (using Tiles) * [STR-2870] - The Specification-Title in the jar file manifests is corrupted * [STR-2872] - Section "4.3.3 Map-backed ActionForms" of User's Manual contains a dead link * [STR-2871] - Rename the release notes so that the filename contains a single period Known issues in 1.3.4: * struts-faces-example2 deploys but the links do 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. My vote is for GA quality. I've had 1.3 in production for eight months with no problems, and I believe we've resolved all of the packaging issues discovered since converting to Maven 2 and reorganizing the project. -- Wendy Smoak - 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: [VOTE] Struts Action Framework v1.3.4 Quality
On 5/10/06, Joe Germuska <[EMAIL PROTECTED]> wrote: At 11:21 AM -0700 5/10/06, Wendy Smoak wrote: >On 5/10/06, Joe Germuska <[EMAIL PROTECTED]> wrote: > >>This seems like the smallest of things, but the distribution includes >>struts-core-1.3.4.jar and not struts-action-1.3.4.jar. >> >>I thought we'd decided to change that? The upgrade notes wiki page >>refers to struts-action: >>http://wiki.apache.org/struts/StrutsUpgradeNotes12to13 > >We decided to call the entire subproject "Struts Action" (rather than >Struts Core or Struts Classic). > >That individual artifactId was changed back to struts-core during the >Maven reorganization. I'm fairly sure I mentioned it on the list, but >I'm having trouble finding messages that talk about struts-core and >struts-action among all the commit messages in the archives. > >In summary, struts-core.jar contains the core of the Action framework. >Eventually, I would like to have a 'struts-action.jar' that contains >the _entire_ framework, the equivalent of 'struts.jar' from the 1.2 >branch, or the Spring framework's full 'spring.jar'. I'm fine on this -- in fact, I think that "struts-action" implies what you described, and it's better to keep what's now known as "struts-core" from "usurping" that name! >Can I count you as +1, or does this need further discussion? +1 GA But I just noticed something else; for some reason the registration of the Tiles 1.1 DTD was removed, even though I don't know of anything that makes Tiles unable to function if one has a valid-according-to-that-DTD tiles-definitions.xml. I missed the discussion where the 1.3 dtd was added - seems like its actually identical to the 1.1 dtd - which IMO serves no purpose. I would rather it was removed. Given that at this moment we appear to be having systems problems with apache.org machines, this is annoying; is there any reason not to restore that registration? The 1.1 DTD is included in the JAR; it's just not registered in XmlParser. Since only the new identical 1.3 dtd is registered, looks like were going to force any tiles users whose apps don't have www access into an unecessary upgrade. For those with www access who don't upgrade, its going to mean more load on the Apache servers. I don't think this qualifies as a reason not to grant GA status. Maybe not, but it doesn't make us look v.smart when we explain that "...there isn't anything new/changed in the 1.3 dtd, but you should upgrade, otherwise it won't use the local copy in the jar". Niall Joe - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Struts-Faces: Is this a bug?
On 5/9/06, A. Alonso Dominguez <[EMAIL PROTECTED]> wrote: Hi there! I'm trying to use the new struts-action framework, version 1.3.3 with tiles and faces. I'm following the example applications but I found possibly a bug when rendering a struts-based FormBean. The jsp code that I was using is as follows: but when it's rendered to the view, the HTML form's "action" attribute references "/common/skin/default/layout/base.do". There is not any action in my application with that url. Instead there is a file "/common/skin/default/layout/base.jsp" which is the base file for the tiles definitions: I dived inside "the org.apache.struts.faces.renderer.FormRenderer" code and I found this code (line 280): protected String action(FacesContext context, UIComponent component) { String actionURL = context.getApplication().getViewHandler(). getActionURL(context, context.getViewRoot().getViewId()); if (log.isTraceEnabled()) { log.trace("getActionURL(" + context.getViewRoot().getViewId() + ") --> " + actionURL); } return (context.getExternalContext().encodeActionURL(actionURL)); } which really does nothing with the actionURL, It just takes de ViewRootId and returns it to the caller. Playing with this code I have now the following: protected String action(FacesContext context, UIComponent component, ModuleConfig moduleConfig) { //String actionURL = //context.getApplication ().getViewHandler(). //getActionURL(context, context.getViewRoot().getViewId()); FormComponent form = (FormComponent) component; String actionURL = context.getApplication().getViewHandler(). getActionURL(context, moduleConfig.getPrefix() + form.getAction()); if (log.isTraceEnabled()) { log.trace("getActionURL(" + context.getViewRoot().getViewId() + ") --> " + actionURL); } return (context.getExternalContext().encodeActionURL(actionURL)); } I don't know if this is the correct way for retrieving the real actionURL but It works now and I'm using it. Should this be posted as a bug?? Yes, this does sound like a bug. Could you please file an issue on it, using project name "Struts Action 1" and component "Faces"? http://issues.apache.org/struts/ Craig
[Struts Wiki] Update of "StrutsMaintenanceMaven" 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/StrutsMaintenanceMaven The comment on the change is: Note that the instructions apply to snapshots and distributions as well as svn. -- Maven 2 does not use .properties files. Per-developer and per-system configuration is done in '''~/.m2/settings.xml'''. (Where '~' represents the user's home directory.) For more information, refer to the [http://maven.apache.org/maven-settings/settings.html settings model] and the Suggested Settings section below. + == Acquiring the Source Code == + - == Checkout Source from Subversion == + === Checkout Source from Subversion === The Struts Subversion repository is organized into sub-projects. You can check out Struts Action 1 alone using this URL: {{{ @@ -20, +22 @@ {{{ svn co https://svn.apache.org/repos/asf/struts/current current }}} + + === Snapshot or Distribution === + + The following instructions should work equally well from the 'src' directory of a Struts Action snapshot or distribution. If they don't, let us know! == Building with Maven == - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Struts Action Framework v1.3.4 Quality
At 11:21 AM -0700 5/10/06, Wendy Smoak wrote: On 5/10/06, Joe Germuska <[EMAIL PROTECTED]> wrote: This seems like the smallest of things, but the distribution includes struts-core-1.3.4.jar and not struts-action-1.3.4.jar. I thought we'd decided to change that? The upgrade notes wiki page refers to struts-action: http://wiki.apache.org/struts/StrutsUpgradeNotes12to13 We decided to call the entire subproject "Struts Action" (rather than Struts Core or Struts Classic). That individual artifactId was changed back to struts-core during the Maven reorganization. I'm fairly sure I mentioned it on the list, but I'm having trouble finding messages that talk about struts-core and struts-action among all the commit messages in the archives. In summary, struts-core.jar contains the core of the Action framework. Eventually, I would like to have a 'struts-action.jar' that contains the _entire_ framework, the equivalent of 'struts.jar' from the 1.2 branch, or the Spring framework's full 'spring.jar'. I'm fine on this -- in fact, I think that "struts-action" implies what you described, and it's better to keep what's now known as "struts-core" from "usurping" that name! Can I count you as +1, or does this need further discussion? +1 GA But I just noticed something else; for some reason the registration of the Tiles 1.1 DTD was removed, even though I don't know of anything that makes Tiles unable to function if one has a valid-according-to-that-DTD tiles-definitions.xml. Given that at this moment we appear to be having systems problems with apache.org machines, this is annoying; is there any reason not to restore that registration? The 1.1 DTD is included in the JAR; it's just not registered in XmlParser. I don't think this qualifies as a reason not to grant GA status. Joe -- Joe Germuska [EMAIL PROTECTED] * http://blog.germuska.com "You really can't burn anything out by trying something new, and even if you can burn it out, it can be fixed. Try something new." -- Robert Moog - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Struts Action Framework v1.3.4 Quality
On 5/10/06, Joe Germuska <[EMAIL PROTECTED]> wrote: This seems like the smallest of things, but the distribution includes struts-core-1.3.4.jar and not struts-action-1.3.4.jar. I thought we'd decided to change that? The upgrade notes wiki page refers to struts-action: http://wiki.apache.org/struts/StrutsUpgradeNotes12to13 We decided to call the entire subproject "Struts Action" (rather than Struts Core or Struts Classic). That individual artifactId was changed back to struts-core during the Maven reorganization. I'm fairly sure I mentioned it on the list, but I'm having trouble finding messages that talk about struts-core and struts-action among all the commit messages in the archives. In summary, struts-core.jar contains the core of the Action framework. Eventually, I would like to have a 'struts-action.jar' that contains the _entire_ framework, the equivalent of 'struts.jar' from the 1.2 branch, or the Spring framework's full 'spring.jar'. Like Wendy, I've had 1.3 based code in production for months, so I'm GA on the code -- as for whether the above is an important packaging problem or just something that needs to be updated in docs, I'll defer. IMO we just need to fix the upgrade notes. Can I count you as +1, or does this need further discussion? Don, I think the Maven build is fine; the artifactId has been struts-core for quite a while. I'd say how long, but minotaur seems to be down again so I can't check the svn log. :( Thanks, -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: What's the goal of SAF 2.0? (was Public API first draft )
Ted Husted wrote: 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. The people mentioned above surely do use Webwork. However, they are not regular users in the sense of this discussion. When you know something and its internal logic and so on as well as these people do, things that are unintuitive and confusing to regular end &users may come naturally to you. There is a real hazard in this, I think. In some recent private correspondence, somebody commented to me that a lot of ASF projects seemed to be "developer-centric", rather than "user-centric" and that this had some very negative consequences in practice. Well, is this dichotomy between a "developer-centric" and "user-centric" really a legitimate difference of viewpoint? It seems to me that any software development project should be user-centric. Similarly, a book writing project should be reader-centric and the development of a consumer device should be consumer-centric. It is my considered opinion that, without that kind of relentless focus on what is useable by and helpful to other people, a project is at extreme risk of degrading into some kind of exercise in intellectual masturbation. In any case, I (unlike some people ;-)) do not presume to know everything there is to know about open source software development. However, I have certain basic beliefs about this and some experience to know whereof I speak. On the basis of this, my sincere advice is that, if you want to do something that's useful, focus on convenience for the broad user base, not your own convenience. Regards, Jonathan Revusky -- lead developer, FreeMarker project, http://freemarker.org/ -Ted. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Struts Action Framework v1.3.4 Quality
I didn't know we decided to change that, as it has repercussions all throughout the Maven build. I'm fine with us changing it for the next release, but I certainly don't think it should stand in the way of this one. Don Joe Germuska wrote: This seems like the smallest of things, but the distribution includes struts-core-1.3.4.jar and not struts-action-1.3.4.jar. I thought we'd decided to change that? The upgrade notes wiki page refers to struts-action: http://wiki.apache.org/struts/StrutsUpgradeNotes12to13 Like Wendy, I've had 1.3 based code in production for months, so I'm GA on the code -- as for whether the above is an important packaging problem or just something that needs to be updated in docs, I'll defer. Joe - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN] Struts BOF Wednesday, 5:30 PM, at JavaOne in the Pavilion
Yep, I'll post a recap. However, don't worry, all decisions will discussed and possibly voted on on the list for them to be "official". Don tm jee wrote: Sounds like a lot of fun. Unfortunately I can't make it. :-( Is it possible to post a summary about what has been discussed and the conclusion arrived at. That would really help people who can't make it catch-up. Thx rgds - Original Message From: Don Brown <[EMAIL PROTECTED]> To: Struts Developers List Sent: Thursday, 11 May, 2006 12:18:02 AM Subject: [ANN] Struts BOF Wednesday, 5:30 PM, at JavaOne in the Pavilion We will be having an "unofficial" Struts BOF at JavaOne with the purpose of discussing the technical directions of the Struts project. I intend this to be more of a working group meeting and discussion than a presentation, so please come prepared to discuss roadmaps and hammer out feature ideas and implementations. If we get too many people, we'll probably split into smaller groups for at least part of the BOF. When: Wednesday, May 17 at 5:30 PM till 6:30 Where: Pavilion, in the back by the luncheon area as the initial gathering area What: Technical discussion of Struts' near to mid-term roadmap Who: Open to anyone Why: A lot of ideas floated around, time to take it to the next level How: We'll have scouted out a free area with chairs and hopefully tables. By that time, the pavilion might be more empty Don - 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: [VOTE] Struts Action Framework v1.3.4 Quality
This seems like the smallest of things, but the distribution includes struts-core-1.3.4.jar and not struts-action-1.3.4.jar. I thought we'd decided to change that? The upgrade notes wiki page refers to struts-action: http://wiki.apache.org/struts/StrutsUpgradeNotes12to13 Like Wendy, I've had 1.3 based code in production for months, so I'm GA on the code -- as for whether the above is an important packaging problem or just something that needs to be updated in docs, I'll defer. Joe -- Joe Germuska [EMAIL PROTECTED] * http://blog.germuska.com "You really can't burn anything out by trying something new, and even if you can burn it out, it can be fixed. Try something new." -- Robert Moog - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN] Struts BOF Wednesday, 5:30 PM, at JavaOne in the Pavilion
Sounds like a lot of fun. Unfortunately I can't make it. :-( Is it possible to post a summary about what has been discussed and the conclusion arrived at. That would really help people who can't make it catch-up. Thx rgds - Original Message From: Don Brown <[EMAIL PROTECTED]> To: Struts Developers List Sent: Thursday, 11 May, 2006 12:18:02 AM Subject: [ANN] Struts BOF Wednesday, 5:30 PM, at JavaOne in the Pavilion We will be having an "unofficial" Struts BOF at JavaOne with the purpose of discussing the technical directions of the Struts project. I intend this to be more of a working group meeting and discussion than a presentation, so please come prepared to discuss roadmaps and hammer out feature ideas and implementations. If we get too many people, we'll probably split into smaller groups for at least part of the BOF. When: Wednesday, May 17 at 5:30 PM till 6:30 Where: Pavilion, in the back by the luncheon area as the initial gathering area What: Technical discussion of Struts' near to mid-term roadmap Who: Open to anyone Why: A lot of ideas floated around, time to take it to the next level How: We'll have scouted out a free area with chairs and hopefully tables. By that time, the pavilion might be more empty Don - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Struts BOF Wednesday, 5:30 PM, at JavaOne in the Pavilion
We will be having an "unofficial" Struts BOF at JavaOne with the purpose of discussing the technical directions of the Struts project. I intend this to be more of a working group meeting and discussion than a presentation, so please come prepared to discuss roadmaps and hammer out feature ideas and implementations. If we get too many people, we'll probably split into smaller groups for at least part of the BOF. When: Wednesday, May 17 at 5:30 PM till 6:30 Where: Pavilion, in the back by the luncheon area as the initial gathering area What: Technical discussion of Struts' near to mid-term roadmap Who: Open to anyone Why: A lot of ideas floated around, time to take it to the next level How: We'll have scouted out a free area with chairs and hopefully tables. By that time, the pavilion might be more empty Don - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Struts Wiki] Update of "UserPreferences" by GeorgeDinwiddie
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 GeorgeDinwiddie: http://wiki.apache.org/struts/UserPreferences -- - 第ä¸æ¬¡ä½¿ç¨ + ##language:en + [[UserPreferences]] + If you are coming to this page for the first time, you'll see the form into which you can enter your username and some other settings (password is stored, in plaintext, but currently not used). It is best to choose a WikiName (like Firstname``Lastname) as username to get your changes and signatures link back to your Wiki``Homepage. Entering your email will enable you to get notifications on page changes. + + If you click on '''Create Profile''', a user profile will be created for you. With the response, a HTTP cookie will be sent that contains your user ID, which enables the system to recognize you. + + /!\ ''This "ID", shown in the response page, can be used to send the same cookie to other machines you might use. So jot it down! Or cut and paste the URL shown above, after you created your profile.'' + + '''Logout''' clears the cookie. As described above, '''Login''' enables you to gain access to your user profile if you somehow lost the cookie or are on another machine. '''Save''' just updates your profile. + - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Struts Build v1.0.1
+1 too, while there are always improvements to be made, this looks good enough for a release. Thanks again! Don On 5/10/06, Greg Reddin <[EMAIL PROTECTED]> wrote: +1. Thanks for all your hard work on this build stuff :-) Greg On May 10, 2006, at 3:24 AM, Wendy Smoak wrote: > In advance of a Struts Action 1.3.x release, we need to release > version 1.0.1 of the struts-build jar. A test build has been deployed > here: > > * http://cvs.apache.org/maven-snapshot-repository/org/apache/struts/ > struts-build/1.0.1/ > > This jar contains Checkstyle and Jalopy config files, and is declared > in the struts-action-parent pom as an . Each module can > then access the config files on the classpath. > > Version 1.0.0 was retired due to an invalid jar manifest. This will > be the first release of struts-build. > > Here's my +1. > > -- > Wendy Smoak > > - > 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Struts Action Framework v1.3.4 Quality
GA - This looks really good Wendy, thanks again for the hard work! Don Wendy Smoak wrote: The Struts Action Framework 1.3.4 Test Build is available to evaluate for release quality. The release plan is available on the wiki: http://wiki.apache.org/struts/StrutsActionRelease134 The test build, including checksums and signatures, has been deployed to: http://svn.apache.org/dist/struts/action/v1.3.4 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 Since 1.3.3, the following issues have been resolved: * [STR-2795] - Postback Forms - Caching and Modules * [STR-2866] - Struts Tiles jar is missing dtd, tld and chain config files * [STR-2867] - Dependency problems in faces-example2 sample app (using Tiles) * [STR-2870] - The Specification-Title in the jar file manifests is corrupted * [STR-2872] - Section "4.3.3 Map-backed ActionForms" of User's Manual contains a dead link * [STR-2871] - Rename the release notes so that the filename contains a single period Known issues in 1.3.4: * struts-faces-example2 deploys but the links do 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. My vote is for GA quality. I've had 1.3 in production for eight months with no problems, and I believe we've resolved all of the packaging issues discovered since converting to Maven 2 and reorganizing the project. -- Wendy Smoak - 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: [VOTE] Release Struts Build v1.0.1
+1. Thanks for all your hard work on this build stuff :-) Greg On May 10, 2006, at 3:24 AM, Wendy Smoak wrote: In advance of a Struts Action 1.3.x release, we need to release version 1.0.1 of the struts-build jar. A test build has been deployed here: * http://cvs.apache.org/maven-snapshot-repository/org/apache/struts/ struts-build/1.0.1/ This jar contains Checkstyle and Jalopy config files, and is declared in the struts-action-parent pom as an . Each module can then access the config files on the classpath. Version 1.0.0 was retired due to an invalid jar manifest. This will be the first release of struts-build. Here's my +1. -- Wendy Smoak - 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: [VOTE] Release Struts Build v1.0.1
I don't see a license file in either the root directory or META-INF, they're 'hidden' away down next in org/apache/struts/build. Also, the notice.txt includes: "This product includes the ANTLR parsing library, developed by JGuru.com (http://www.antlr.org and http://www.jguru.com)." Which I couldn't find a reason to be included. The included pom.xml and pom.properties have no license header. On 5/10/06, Wendy Smoak <[EMAIL PROTECTED]> wrote: In advance of a Struts Action 1.3.x release, we need to release version 1.0.1 of the struts-build jar. A test build has been deployed here: * http://cvs.apache.org/maven-snapshot-repository/org/apache/struts/struts-build/1.0.1/ This jar contains Checkstyle and Jalopy config files, and is declared in the struts-action-parent pom as an . Each module can then access the config files on the classpath. Version 1.0.0 was retired due to an invalid jar manifest. This will be the first release of struts-build. Here's my +1. -- Wendy Smoak - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- http://www.multitask.com.au/people/dion/ Chuck Norris sleeps with a night light. Not because Chuck Norris is afraid of the dark, but because the dark is afraid of Chuck Norris
[Struts Wiki] Update of "StrutsActionRelease134" 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/StrutsActionRelease134 -- || '''#''' || '''Description''' || '''Completed''' || || A0. || Update all pom.xml files to omit "-SNAPSHOT" || (./) || || A1. || Tag release in svn: STRUTS_ACTION_1_3_4 || (./) || - || 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 || || + || 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.4 || || + || A4. || Upload Distribution to people.apache.org:/www/cvs.apache.org/dist/struts/action/v1.3.4 || (./) || || A5. || Update all pom.xml files to "1.3.5-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] Release Struts Build v1.0.1
In advance of a Struts Action 1.3.x release, we need to release version 1.0.1 of the struts-build jar. A test build has been deployed here: * http://cvs.apache.org/maven-snapshot-repository/org/apache/struts/struts-build/1.0.1/ This jar contains Checkstyle and Jalopy config files, and is declared in the struts-action-parent pom as an . Each module can then access the config files on the classpath. Version 1.0.0 was retired due to an invalid jar manifest. This will be the first release of struts-build. Here's my +1. -- Wendy Smoak - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE] Struts Action Framework v1.3.4 Quality
The Struts Action Framework 1.3.4 Test Build is available to evaluate for release quality. The release plan is available on the wiki: http://wiki.apache.org/struts/StrutsActionRelease134 The test build, including checksums and signatures, has been deployed to: http://svn.apache.org/dist/struts/action/v1.3.4 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 Since 1.3.3, the following issues have been resolved: * [STR-2795] - Postback Forms - Caching and Modules * [STR-2866] - Struts Tiles jar is missing dtd, tld and chain config files * [STR-2867] - Dependency problems in faces-example2 sample app (using Tiles) * [STR-2870] - The Specification-Title in the jar file manifests is corrupted * [STR-2872] - Section "4.3.3 Map-backed ActionForms" of User's Manual contains a dead link * [STR-2871] - Rename the release notes so that the filename contains a single period Known issues in 1.3.4: * struts-faces-example2 deploys but the links do 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. My vote is for GA quality. I've had 1.3 in production for eight months with no problems, and I believe we've resolved all of the packaging issues discovered since converting to Maven 2 and reorganizing the project. -- Wendy Smoak - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Struts Wiki] Update of "UserPreferences" by wujiegao
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 wujiegao: http://wiki.apache.org/struts/UserPreferences -- + 第ä¸æ¬¡ä½¿ç¨ - ##language:en - [[UserPreferences]] - If you are coming to this page for the first time, you'll see the form into which you can enter your username and some other settings (password is stored, in plaintext, but currently not used). It is best to choose a WikiName (like Firstname``Lastname) as username to get your changes and signatures link back to your Wiki``Homepage. Entering your email will enable you to get notifications on page changes. - - If you click on '''Create Profile''', a user profile will be created for you. With the response, a HTTP cookie will be sent that contains your user ID, which enables the system to recognize you. - - /!\ ''This "ID", shown in the response page, can be used to send the same cookie to other machines you might use. So jot it down! Or cut and paste the URL shown above, after you created your profile.'' - - '''Logout''' clears the cookie. As described above, '''Login''' enables you to gain access to your user profile if you somehow lost the cookie or are on another machine. '''Save''' just updates your profile. - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Struts Wiki] Update of "StrutsActionRelease134" 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/StrutsActionRelease134 -- || '''#''' || '''Description''' || '''Completed''' || || A0. || Update all pom.xml files to omit "-SNAPSHOT" || (./) || - || A1. || Tag release in svn: STRUTS_ACTION_1_3_4 || || + || A1. || Tag release in svn: STRUTS_ACTION_1_3_4 || (./) || || 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.4 || || - || A5. || Update all pom.xml files to "1.3.5-SNAPSHOT" || || + || A5. || Update all pom.xml files to "1.3.5-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@ list |||| - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]