Re: [VOTE] 1.2.0 Release Plan

One possible question is from the new boilerplate: Copyright [] [name of copyright owner] Is it just "The Apache Software Foundation", like in the 1.1 license? That would be my guess. The one reference to Struts in the previous license version was related to the section on use of the tradem

RE: [VOTE] 1.2.0 Release Plan

The exact license details can be found here: http://www.apache.org/dev/apply-license.html David --- "Karr, David" <[EMAIL PROTECTED]> wrote: > Does this involve changing the file header comment to replace the > existing license with the new license? That's something that I can > relatively easi

Re: [VOTE] 1.2.0 Release Plan

Besides changing header, there's also maintaining copyrights and moving them to a new location and then updating a Checkstyle version of the license. I did the last major license update and I'd be willing to do it as well this weekend. Just let me know. Paul Sundling Karr, David wrote: Doe

RE: [VOTE] 1.2.0 Release Plan

Does this involve changing the file header comment to replace the existing license with the new license? That's something that I can relatively easily script in elisp macros. If someone can confirm that's all this is, and show me exactly what needs to change, I can get that done this weekend. --

Re: [VOTE] 1.2.0 Release Plan

At 1:49 PM -0600 2/20/04, Joe Germuska wrote: > Just a few things: * What about the new Apache license? Technically, it doesn't need to change if we release before March 1st, but we're mighty close to that, so > perhaps we should switch now? +1 from me too; wasn't someone offering to do it a f

Re: [VOTE] 1.2.0 Release Plan

> Just a few things: * What about the new Apache license? Technically, it doesn't need to change if we release before March 1st, but we're mighty close to that, so > perhaps we should switch now? +1 from me too; wasn't someone offering to do it a few weeks ago? At this point I don't see any r

Re: [VOTE] 1.2.0 Release Plan

> contrib Personally, I've been defining what is released by what is generated by the release target. :) For Struts 1.1, Struts-El was released coincident with the Struts 1.1 release, but they were separate events. If someone wants to also roll a struts-el release, or struts-jsf release, pleas

Re: [VOTE] 1.2.0 Release Plan

--- Martin Cooper <[EMAIL PROTECTED]> wrote: > On Fri, 20 Feb 2004, Ted Husted wrote: > > > Assuming it was all right with everyone, I'm setting the freeze date > for 1.2.0 for tomorrow (Saturday) night. > > > > I'm updating the release plan. There are still a lot of enhancement > patches that we

Re: [VOTE] 1.2.0 Release Plan

On Fri, 20 Feb 2004, Ted Husted wrote: > Assuming it was all right with everyone, I'm setting the freeze date for 1.2.0 for > tomorrow (Saturday) night. > > I'm updating the release plan. There are still a lot of enhancement patches that we > haven't applied, but I think those can wait for later

Re: [VOTE] 1.2.0 Release Plan

At 9:37 AM -0500 2/20/04, Ted Husted wrote: Assuming it was all right with everyone, I'm setting the freeze date for 1.2.0 for tomorrow (Saturday) night. I'm updating the release plan. There are still a lot of enhancement patches that we haven't applied, but I think those can wait for later in

cvs commit: jakarta-struts/doc/proposals release-plan_1_2_0.xml

husted 2004/02/20 09:03:20 Modified:doc project.xml releases.xml status.xml doc/proposals release-plan_1_2_0.xml Log: Correct hyperlinks. Revision ChangesPath 1.47 +4 -4 jakarta-struts/doc/project.xml Index: project.xml ==

Re: Status of struts-examples

> -Original Message- > From: Ted Husted [mailto:[EMAIL PROTECTED]> If there aren't any strong objections, > then, I'd like to remove them and make a clean break with the things we did for the > sake of the 1.1 march. +1 sounds good ! --

cvs commit: jakarta-struts/doc/userGuide release-notes.xml

husted 2004/02/20 08:35:17 Modified:doc/userGuide release-notes.xml Log: Update release notes. Revision ChangesPath 1.49 +3 -0 jakarta-struts/doc/userGuide/release-notes.xml Index: release-notes.xml ===

DO NOT REPLY [Bug 26413] - Indexed Field Date Validation Allows Invalid Dates

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

cvs commit: jakarta-struts/src/share/org/apache/struts/validator FieldChecks.java

husted 2004/02/20 08:16:05 Modified:src/share/org/apache/struts/validator FieldChecks.java Log: Apply #26413 "Indexed Field Date Validation Allows Invalid Dates" submitted by Niall Pemberton. Revision ChangesPath 1.17 +93 -76 jakarta-struts/src/share/org/apache

DO NOT REPLY [Bug 26413] - Indexed Field Date Validation Allows Invalid Dates

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 26413] - Indexed Field Date Validation Allows Invalid Dates

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: [GUMP@lsd]: jakarta-struts/jakarta-struts failed

On Fri, 20 Feb 2004, Ted Husted <[EMAIL PROTECTED]> wrote: > we are currently using LICENSE.txt rather than LICENSE. > > Is that a problem? No, it's just that Struts' Gump descriptor didn't know that. It's already fixed in CVS. Cheers Stefan -

cvs commit: jakarta-struts/doc status.xml

husted 2004/02/20 06:47:01 Modified:doc status.xml Log: Routine update. Revision ChangesPath 1.59 +3 -3 jakarta-struts/doc/status.xml Index: status.xml === RCS file: /home/cvs/jakarta

Re: [GUMP@lsd]: jakarta-struts/jakarta-struts failed

In regard to http://lsd.student.utwente.nl/gump/jakarta-struts/jakarta-struts.html we are currently using LICENSE.txt rather than LICENSE. Is that a problem? -Ted. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional c

cvs commit: jakarta-struts/doc/proposals release-plan_1_2_0.xml

husted 2004/02/20 06:41:23 Modified:doc/proposals release-plan_1_2_0.xml Log: Revise date, postpone remaining patches. Revision ChangesPath 1.8 +5 -7 jakarta-struts/doc/proposals/release-plan_1_2_0.xml Index: release-plan_1_2_0.xml =

Re: [VOTE] 1.2.0 Release Plan

Assuming it was all right with everyone, I'm setting the freeze date for 1.2.0 for tomorrow (Saturday) night. I'm updating the release plan. There are still a lot of enhancement patches that we haven't applied, but I think those can wait for later in the 1.2.x series. I do intend to start march

DO NOT REPLY [Bug 26413] - Indexed Field Date Validation Allows Invalid Dates

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 27089] - doubleRange missing from validator-rules.xml

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

[GUMP@lsd]: jakarta-struts/jakarta-struts failed

-Dbuild.sysclasspath=only -Dcommons-beanutils.jar=/data3/gump/jakarta-commons/beanutils/dist/commons-beanutils.jar -Djdbc20ext.jar=/data3/gump/opt/jdbc2_0/jdbc2_0-stdext.jar -Dantlr.jar=/data3/gump/opt/antlr-2.7.2/antlr.jar -Dcommons-lang.jar=/data3/gump/jakarta-commons/lang/dist/commons-lan