Re: Demoting older Struts releases

Its more on encouraging users to move to releases where bug fixes and security vulnerability fixes have been made. From the ancient Struts 1.2.0 release notes: The /vote/ may also serve to /reclassify/ the /release/ to be of /Beta/ or /General Availability/ (/GA/) quality, as defined by the Ap

Re: Revert the trunk

In most projects the latest and greatest code is in the trunk, See Subversion Red-Bean Book . What Wes suggests is going to be the easiest to follow. Recall when all those reverse merges are performed they are

FindBugs is being run against WebWork and not Struts ?

Hi, I am on the findbugs list and the FindBugs Team announced that they will be running FindBugs against WebWork and a number of other projects.. Does that make sense or would the Struts committers rather that be switched over to Struts 2 code base ? Here is the link. http://findbugs.cs.umd.e

Re: Woes trying to release

Have you ever considered taking this out of the pom,xml entirely and moving it to the settings.xml ? This would allow you to add a password, for continuous build stuff if that's required when fetching the code. In addition not having the branch explicitly hard coded in the pom.xml might make wo

Re: Struts 2 GUI tools

James, You may want to try and team up with Yann Cébron who wrote the Struts 2 plugin for IntelliJ. http://plugins.intellij.net/plugin/?id=1698 http://www.jetbrains.net/confluence/display/CONTEST/Struts2PluginChangeNotes#Struts2PluginChangeNotes-IDEA7 I have only played with it since I am no

Re: Feature sponsorship proposal

e's a prize at the end will be the first ones to dump your a## when you really need them, but don't have an incentive to offer. If Struts (or any project) doesn't have enough volunteers to keep the work going, then we have bigger issues. Just my $0.02! On Mon, Apr 7, 2008 at 1

Re: Feature sponsorship proposal

Don I have a few questions 1) I agree that this contribution has to be valuable to the contributing company both technically and marketing. Back in 2003 when I obtained free IntelliJ licenses from Jetbrains for the Struts Committers all they wanted was acknowledgment on our web page and that w

Re: [action2] Leveraging known constructs (was Public API first draft)

Eric Molitor wrote: The new Messages API could easily be mapped onto an implementation similar to that of Log4J. Why not embrace that idea and utilize familiar methods to provide access. such as... msgs.info("some.key"); msgs.warn("some.warn.key"); msgs.error("some.error.key"); Why not just:

Re: Versioning work-in-development (Re: svn commit: r125632 - /struts/el/trunk/project.xml)

For the in between official releases for our project at work I created a 'all-versioned' target that uses ants 'propertyFile' task to automatically increment a build number. This build number is stored in the ant generated manifest file of the built jar/war file. For the first 'versioned' build,

Re: [VOTE] Move minimum to 2.3 (was Re: Changing how CommonsMultipartRequestHandler handles text parameters?)

+1 , 2.3 +1, 2.4 - Since we seem to take 18mo between releases, (that's just the way it is) we may as well go for 2.4. > -Original Message- > From: Ted Husted [mailto:[EMAIL PROTECTED] > Sent: Monday, August 30, 2004 10:09 AM > To: 'Struts Developers List', 'Struts

Re: Struts 1.2.2 Release Notes

Niall Pemberton wrote: I'm going to take a look at doing the release notes later. Do we need 1.2.2 release notes that document the changes since Struts 1.1 or do we just need release notes with the changes since the Struts 1.2.1 beta? You could use what maven produces when you type: mave

Re: [VOTE] - Bill Siggelkow for committer

+0, As David said I don't know Bill, but look forward to changing that. James Mitchell wrote: I have known Bill for a few years and he is definitely committer material. He has contributed in numerous ways to this community and others. I owe him a great deal for his help with our local Struts Users

Re: Tonight's Nightly Build Dependencies

Comment below Craig McClanahan wrote: I've updated my nightly build script (effective with the 20040706 build) to use the following dependnet libraries, which I'm assuming corresponds to what we'll actually use in a Struts 1.2.1 release. Can whoever is going to be release manager for this confi

Re: i've just moved validator meterial from old to new wiki

robert burrell donkin wrote: just to let everyone here know that jakarta commons now has a shiny new wiki :) http://wiki.apache.org/jakarta-commons i've just moved all the content i could find on validator from the old wiki to the new. i don't know if there's anything here in strutsland that ne

Re: Managing the commons-validator dependency (Re: DO NOT REPLY [Bug 29004] - ActionValidatorForms cause badly formed validator javascript)

At the very least I'll take time to look into the multiple form Javascript problem. Robert Leland wrote: Joe Germuska wrote: I thought that the release of Struts 1.2.1 was blocked pending a release of commons-validator 1.1.3 ? If that's true, is it right to change the nightly build

Re: Managing the commons-validator dependency (Re: DO NOT REPLY [Bug 29004] - ActionValidatorForms cause badly formed validator javascript)

Joe Germuska wrote: I thought that the release of Struts 1.2.1 was blocked pending a release of commons-validator 1.1.3 ? If that's true, is it right to change the nightly builds to use a different dependency? might not have been clear. The version in my hoime directory is from the 1.1.3 branc

Re: Contacting Husted dot Com

Ted/All: You can place messages from '[EMAIL PROTECTED]' on your perminate list of email to delete. This is an old mail address that I used with Bugzilla several years ago, that has been co-opted by the email Virus going around. [EMAIL PROTECTED] wrote: Thank you for your inquiry. To

Re: cvs commit: jakarta-struts/xdocs/userGuide building_controller.xml

I didn't notice if you also updated the version under docs or not ? I synced these docs about 4 months ago, bit I am sure they are out of sync. > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Tuesday, April 27, 2004 10:34 PM > To: [EMAIL PROTECTED] > Subjec

Re: Struts-Chain App [was TilesServlet deleted]

> -Original Message- > From: Ted Husted [mailto:[EMAIL PROTECTED]> > Once we bring Chain down from contrib, I'd like to bring that one over here. > > I am planning to do a "generic" sample app for Commons Chain. Doing the Struts one > first was simply a convenience. > > It would be

Re: Url Validation Configuration Options

Ted Husted wrote: Any thoughts on this one? http://issues.apache.org/bugzilla/show_bug.cgi?id=28148 "The current url validation in struts (validateUrl method in FieldChecks) only uses the default url configuration options. "I am attaching a patch that will allow the following options to be set

Re: rsync commons-validator-1.1.2 to iBiblio? (Re: Problem building Struts with Maven)

Thanks for tracking down the info. Joe Germuska wrote: OK, so I brought this up over on commons-dev, and here's what I learned: At 3:16 PM -0400 4/13/04, Mark R. Diggory wrote: I can tell you we have the following directory available /www/cvs.apache.org/repository/ with a few builds within it t

Re: rsync commons-validator-1.1.2 to iBiblio? (Re: Problem building Struts with Maven)

> Sergio, the immediate problem is simply that that version of > commons-validator is not available from the iBiblio repository > (because it's a dev version). There are a variety of solutions to > the problem, but since Validator has cut a 1.1.2 release, I think the > best solution would be

Re: [Validator] call for testers.

> -Original Message- > From: Adam Hardy > Rob, > how does this validation inheritance work? Is it documented anywhere? Yes, when Nacho G. Mac Dowell provided the patch, in Bug 27870, he also provided a unit test. This is from the validator.xml file in the unit tests: http://jakarta.apa

Re: Should we require wiki logins?

> -Original Message- > From: Ted Husted [mailto:[EMAIL PROTECTED]> > It would be nice if we could encourage people to login. Not so much so we can > watchdog people. But so we know who deserves the kudos. :) Ok your's and Martins point, +1.

[Validator] call for testers.

I would like to entice developers to give the Struts Nightly and/or the commons-validator a try. I am announcing this only on the 'dev' list in the belief that since you subscribed to the 'dev' list you are generally more advanced. Also since I will be in a crunch for the next few days I can't pr

Re: Should we require wiki logins?

I am -0 on logins. Correcting malicious changes to the pages hopefully won't be to hard as long as there is a history trail we can roll back to. Also if a login account only requires a verified email account, if someone wanted to hack the page, they would still do it. Where it would get hard to pol

Validator and Struts 1.2.1 rollout

This directly impacts the Struts 1.2.1 release. Now that the Validation of Validator is turned on we now know that Struts 1.2.1 will not work with any currently released version of Validator including 1.1.2 because of a faultly DTD. I have checked in fixes to both the Main Trunk of Validator a

Re: Validator Plugin

[EMAIL PROTECTED] wrote: One issue with this is to make sure the validator DTD is up to date. The reason I say this is because the DTD appears to be missing the var-jstype sub-element of the var element. Even the 1.2.0 version of the DTD on CVS is missing this. I assume it is a valid element,

Re: Validator Plugin

[EMAIL PROTECTED] wrote: One issue with this is to make sure the validator DTD is up to date. The reason I say this is because the DTD appears to be missing the var-jstype sub-element of the var element. Even the 1.2.0 version of the DTD on CVS is missing this. I assume it is a valid element,

Re: 2.3 for 1.3? (was Counting down to 1.2.1)

Joe Germuska wrote: Struts 1.x then remains Servlet 2.2, JSP 1.1, Java 1.2. Struts 2.x (fka 1.3.x) can then be Servlet 2.3, JSP 1.2, and Java 1.3. Struts 3.x (fka 2.x) can then be Servlet 2.4 and JSP 2.0, as planned. If we are going to depend on Servlet 2.3, then I think it's probably worth c

Re: TLP conversion status

Martin Cooper wrote: Here's an update on where we are on getting everything morphed over into Struts TLP status. First off, this is taking *much* longer than I'd expected. Part of it is that there are a lot of things to do, but much of it is because I don't have enough permission to do things myse

Re: 2.3 for 1.3? (was Counting down to 1.2.1)

Ted Husted wrote: So, I'm going to knuckle down and do whatever we need to do to get 1.2.1 ready to cut this week. In the meantime, I'm wondering if we want to just bite the bullet and move the minimum to servlet 2.3 for the Struts 1.3.x series? I have been thinking this for a long time. Folks

Re: JavaScriptTag and multiple forms.

> -Original Message- > From: Joe Germuska > At 4:35 PM + 4/3/04, Robert Leland wrote: > >Every since I applied the patch to allow the validator to work, > >with multiple forms, there has been one thing that has bothered me: > > > >The JavaScript

JavaScriptTag and multiple forms.

Every since I applied the patch to allow the validator to work, with multiple forms, there has been one thing that has bothered me: The JavaScriptTag requires the name of the form. So now both the form name and the action name are required in the JSP, and this increases the coupling. How about

Why struts-documentation ?

Why does struts-documentation include all the jar files for struts when it contains no JSP's or struts-config.xml ? Not having to run tomcat to view the DOCS is a big Plus. -ROb - To unsubscribe, e-mail: [EMAIL PROTECTED] For

Re: Fw: UrlValidator() takes options - but how?

Comments In Line. > -Original Message- > From: Niall Pemberton [mailto:[EMAIL PROTECTED]> While I was testing this I did have > another thought - UrlValidator just > returns true or false when it validates and gives no indication of what bit > of the validation failed. What do you think

Validator Plugin

Currently the Validator PlugIn doesnât validate the XML file. I have updated it to remove the deprecated methods and to validate the XML files. Here is the question: Currently, the validator plugin fails by logging a message but doesnât take advantage of throwing an exception. I believe it shoul

[Validator] release(was : Re: Counting down to the 1.2.1 release)

Martin Cooper wrote: >There have been some Validator discussions going on on commons-dev, >related to JavaScript, so I'm going to wait for a green light from someone >(David G?) before I roll Validator 1.1.2. Ok, Validator is now using DOM Level 1 compatable calls to resolve the form name. Thank