Re: Running Struts Cactus tests with Ant

> As noted in a previous thread, I am hitting a wall trying to run the cactus tests in Ant. I want to commit the changes I've made to help Maven run cactus tests, and I've already had to reconcile a bunch of conflicts once... The error seems to come with the first Cactus test case (org.apach

Re: [VOTE] 1.2.0 Release Plan

Ted Husted wrote: If we use the current Validator 1.1.1 JAR, and it becomes the final release, then we could vote on whether Struts 1.2.0 can also be a "final" or "General Availability" release. If you recall I believe we came to consensus on struts-dev that Validator can't go Beta or GA w/o be

RE: Running Struts Cactus tests with Ant

Sorry.. The default target is currently set up as jar:jar That will do everything that you need it to. So all you have to do is: //step-by-step-build-struts-with-maven.readme 1) Download maven 1.0 rc1 from http://maven.apache.org 2) Add a maven_home env variable that points to where you installed

Re: Running Struts Cactus tests with Ant

--- James Mitchell <[EMAIL PROTECTED]> wrote: > Any chance someone wants to throw together a > step-by-step-build-struts-with-maven.readme? cd your-struts-dir maven build Anything much more complicated than that defeats the purpose of using Maven. David > > > > > Anyway, maybe I just need a

Re: Running Struts Cactus tests with Ant

On Tue, 16 Dec 2003, Joe Germuska wrote: > As noted in a previous thread, I am hitting a wall trying to run the > cactus tests in Ant. I want to commit the changes I've made to help > Maven run cactus tests, and I've already had to reconcile a bunch of > conflicts once... > > The error seems to c

Running Struts Cactus tests with Ant

As noted in a previous thread, I am hitting a wall trying to run the cactus tests in Ant. I want to commit the changes I've made to help Maven run cactus tests, and I've already had to reconcile a bunch of conflicts once... The error seems to come with the first Cactus test case (org.apache.s

Re: [VOTE] 1.2.0 Release Plan

+ 1 on the release plan... Note that I've left room in the release plan for the idea of multiple managers. If someone were up for sheparding the tests, especially the example application testing, I'd welcome the help. I may as well take this moment to fess up to my remedial status trying to run

Re: [VOTE] 1.2.0 Release Plan

On Tue, 16 Dec 2003, Ted Husted wrote: +1 > I've amended the date on the (now venerable) 1.2.0 release plan for this > weekend. > > http://jakarta.apache.org/struts/proposals/release-plan_1_2_0.html > > I believe the release notes are in good shape now. I already marched > through most of the

Re: [VOTE] 1.2.0 Release Plan

--- Ted Husted <[EMAIL PROTECTED]> wrote: > The mean number of milestones for a Jakarta "stable" release seems to be > > five or six. So, it would not be unusual for us to get 1.2.4 before > hitting a "General Availability" grade. That could be because products using this versioning/release sys

Re: [VOTE] 1.2.0 Release Plan

If we use the current Validator 1.1.1 JAR, and it becomes the final release, then we could vote on whether Struts 1.2.0 can also be a "final" or "General Availability" release. If this Validator 1.1.1 JAR does not make final, then the best we could do is mark ours would be "beta" (since it has

DO NOT REPLY [Bug 24516] - excessive input and javascript 'do' keyword

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: [VOTE] 1.2.0 Release Plan

Clarifying the voting guidelines is an active thread on the PMC list, so we might just want to muddle along best we can for now. Regardless of what we do for 1.2.1, we have called for a vote on a release plan for 1.2.0. The plan does call for a vote before classifying the Alpha as a Beta or Gen

Re: [VOTE] 1.2.0 Release Plan

Were we still planning on using Validator 1.1.1 when it is released ? It's getting a little confusing, since I removed it, and called for a release Vote. The vote isn't scheduled to complete until Sunday Noon. And Struts source will be frozed at Saturday Midnight. -Rob

[Validator] was Re: [VOTE] 1.2.0 Release Plan

Ok, then with 'tomcat' reading of the rules, I can put the 1.1.1 back for limited testing and then say next week call for a vote on commons-validator to classify it. I confused the issue by calling it an Alpha instead of a RC. -Rob > -Original Message- > From: Craig R. McClanahan> Quoti

Re: [VOTE] 1.2.0 Release Plan

Quoting Martin Cooper <[EMAIL PROTECTED]>: > The issue isn't so much with voting on the relesae plan, but voting on the > release itself. As you say, the HTTPD rules say that anyone can create a > release. We're not HTTPD, though, and the Jakarta rules are different. As > long as we're part of Jak

Re: [VOTE] 1.2.0 Release Plan

+1 > -Original Message- > From: Ted Husted [mailto:[EMAIL PROTECTED] > Sent: Tuesday, December 16, 2003 05:48 PM > To: 'Struts Developers List' > Subject: [VOTE] 1.2.0 Release Plan > > I've amended the date on the (now venerable) 1.2.0 release plan for this > weekend. > > http://jakart

Re: [VOTE] 1.2.0 Release Plan

The issue isn't so much with voting on the relesae plan, but voting on the release itself. As you say, the HTTPD rules say that anyone can create a release. We're not HTTPD, though, and the Jakarta rules are different. As long as we're part of Jakarta, we need to abide by the Jakarta rules. Under

Re: [VOTE] 1.2.0 Release Plan

With this proposal, I took a middle ground. The initial minor release (x.x.0) in a series called for a vote on a plan, but a plan would be optional for additional releases in the same series (1.2.1, 1.2.2, ...). So, we wouldn't have to vote on a plan again until we get to 1.3.0 or 2.0.0. The r

Re: [VOTE] 1.2.0 Release Plan

+1 I've added myself as an RM, since I'll be available to help. I can take on the tag, roll, sign and announce part, if you like. One thing I'd like to point out, because it came up in Commons, is that the HTTPD process and the Jakarta process are not 100% compatible. In particular, the Jakarta r

Re: [VOTE] 1.2.0 Release Plan

Ted Husted wrote: . If someone were up for sheparding the tests, especially the example application testing, If testing example apps, means not much more than see if the war files work and browse it, I will do it. (of course some of them had problems before, like tiles example, but not sure wh

Re: [VOTE] 1.2.0 Release Plan

+1 David --- Ted Husted <[EMAIL PROTECTED]> wrote: > I've amended the date on the (now venerable) 1.2.0 release plan for this > > weekend. > > http://jakarta.apache.org/struts/proposals/release-plan_1_2_0.html > > I believe the release notes are in good shape now. I already marched > throug

[VOTE] 1.2.0 Release Plan

I've amended the date on the (now venerable) 1.2.0 release plan for this weekend. http://jakarta.apache.org/struts/proposals/release-plan_1_2_0.html I believe the release notes are in good shape now. I already marched through most of the stale 1.0/1.1 tickets, and can mop up the rest in short

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

martinc 2003/12/16 09:13:57 Modified:doc/proposals release-plan_1_2_0.xml Log: I can help. Revision ChangesPath 1.7 +2 -2 jakarta-struts/doc/proposals/release-plan_1_2_0.xml Index: release-plan_1_2_0.xml ==

cvs commit: jakarta-struts/doc/userGuide installation.xml

husted 2003/12/16 09:12:02 Modified:doc/userGuide installation.xml Log: Remove "dev" status from Commons Validator 1.1.1 Revision ChangesPath 1.37 +1 -1 jakarta-struts/doc/userGuide/installation.xml Index: installation.xml ===

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

husted 2003/12/16 09:07:56 Modified:doc/proposals release-plan_1_2_0.xml Log: Update release plan Revision ChangesPath 1.6 +3 -3 jakarta-struts/doc/proposals/release-plan_1_2_0.xml Index: release-plan_1_2_0.xml ==

DO NOT REPLY [Bug 25561] New: - Hidden tag has wrong accesskey attribute

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