date:20041023

[Apache Struts Wiki] Updated: StrutsRelease125

2004-10-23 Thread dev

   Date: 2004-10-23T03:02:30
   Editor: TedHusted <[EMAIL PROTECTED]>
   Wiki: Apache Struts Wiki
   Page: StrutsRelease125
   URL: http://wiki.apache.org/struts/StrutsRelease125

   Tickets, tickets, who's  fixing the tickets? :)

Change Log:

--
@@ -24,7 +24,7 @@
 See on the Commons [http://jakarta.apache.org/commons/releases/prepare.html 
Preparation Guide]
 
 || '''#''' || '''Description''' || '''Completed''' ||
-|| 1. || Review/Resolve Outstanding Bugs || (do we actually still do this?) ||
+|| 1. || Review/Resolve Outstanding Bugs || As to Problem tickets, yes we should, or 
state the reason why. How can we say its "ready for primetime", when we know that 
there are unaddressed problems. If we can't fix the problems, we must at least 
acknowledge the tickets.||
 || 2. || Update Release Notes || done ||
 || 3. || Check Dependencies || done ||
 || 4. || Update to version 1.2.5 build.xml, project.xml, and the MANIFEST.MF || done 
||

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

[Apache Struts Wiki] Updated: StrutsRelease125

2004-10-23 Thread dev

   Date: 2004-10-23T03:17:21
   Editor: TedHusted <[EMAIL PROTECTED]>
   Wiki: Apache Struts Wiki
   Page: StrutsRelease125
   URL: http://wiki.apache.org/struts/StrutsRelease125

   Tweak language to agree with dev@ discussions. Add new step A6.

Change Log:

--
@@ -24,7 +24,7 @@
 See on the Commons [http://jakarta.apache.org/commons/releases/prepare.html 
Preparation Guide]
 
 || '''#''' || '''Description''' || '''Completed''' ||
-|| 1. || Review/Resolve Outstanding Bugs || As to Problem tickets, yes we should, or 
state the reason why. How can we say its "ready for primetime", when we know that 
there are unaddressed problems. If we can't fix the problems, we must at least 
acknowledge the tickets.||
+|| 1. || Review/Resolve Outstanding Bugs || As to Problem tickets, yes we should 
resolve or problems, or at least state the reason why. If we can't fix the problems, 
we *must* at least acknowledge the outstanding problem tickets.||
 || 2. || Update Release Notes || done ||
 || 3. || Check Dependencies || done ||
 || 4. || Update to version 1.2.5 build.xml, project.xml, and the MANIFEST.MF || done 
||
@@ -53,7 +53,7 @@
 || 2. || Run Cactus Tests (see below) || done ||
 || 3. || Play test bundled applications (latest GA release of Tomcat) || done ||
 
-Note - would be nice to have a set of Struts test cases to run against these apps ;)
+Note - would be nice to have a set of Struts test cases (or WebTest cases) to run 
against these apps ;)
 
 === Cactus Tests ===
 
@@ -68,14 +68,18 @@
 See also Commons [http://jakarta.apache.org/commons/releases/release.html 
Step-by-Step Guide]
 
 || '''#''' || '''Description''' || '''Completed''' ||
-|| A1. || Tag release in svn: STRUTS_1_2_5 || done ||
-|| A2. || Run Distribution Target (ant release) || done ||
-|| A3. || Upload Distribution to 
cvs.apache.org:/www/cvs.apache.org/dist/struts/v1.2.5 || done ||
-|| A4. || Deploy JAR to Apache Java-Repository || _ ||
-|| A5. || Update "Acquiring" page on website || done ||
-|| A6. || Post release-quality vote on dev@ list || (should be sent 10/20/2004) ||
+|| A1. || Tag distribution in svn: STRUTS_1_2_5 || done ||
+|| A2. || Run build release target (ant release) || done ||
+|| A3. || Upload test build to cvs.apache.org:/www/cvs.apache.org/dist/struts/v1.2.5 
|| done ||
+|| A4. || Announce test-build on dev@ and pmc@ lists only || done: 17-oct-2004 ||
+|| A5. || Post release-quality vote on dev@ list || (may be sent 20-oct-2004) ||
 
 == Vote ==
+
+|| A6. || If vote fails (including lack of quorum), remove test-build cvs.apache.org 
|| _ ||
+|| A7. || If vote passes, update "Acquiring" page on website || done ||
+|| A8. || If vote passes, deploy JAR to Apache Java-Repository || _ ||
+
 
 == General Availability Checklist (B) ==
 

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

[Apache Struts Wiki] Updated: StrutsRelease125

2004-10-23 Thread dev

   Date: 2004-10-23T03:20:35
   Editor: TedHusted <[EMAIL PROTECTED]>
   Wiki: Apache Struts Wiki
   Page: StrutsRelease125
   URL: http://wiki.apache.org/struts/StrutsRelease125

   As a rule, better to publicize only beta and GAs on website.

Change Log:

--
@@ -77,7 +77,7 @@
 == Vote ==
 
 || A6. || If vote fails (including lack of quorum), remove test-build cvs.apache.org 
|| _ ||
-|| A7. || If vote passes, update "Acquiring" page on website || done ||
+|| A7. || If vote passes, update "Acquiring" page on website || _ ||
 || A8. || If vote passes, deploy JAR to Apache Java-Repository || _ ||
 
 

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

[Apache Struts Wiki] Updated: StrutsRelease125

2004-10-23 Thread dev

   Date: 2004-10-23T03:25:09
   Editor: TedHusted <[EMAIL PROTECTED]>
   Wiki: Apache Struts Wiki
   Page: StrutsRelease125
   URL: http://wiki.apache.org/struts/StrutsRelease125

   Add step 0 to announce and link release plan.

Change Log:

--
@@ -24,6 +24,7 @@
 See on the Commons [http://jakarta.apache.org/commons/releases/prepare.html 
Preparation Guide]
 
 || '''#''' || '''Description''' || '''Completed''' ||
+|| 0. || Announce plan to dev@ list; link from roadmap page || done ||
 || 1. || Review/Resolve Outstanding Bugs || As to Problem tickets, yes we should 
resolve or problems, or at least state the reason why. If we can't fix the problems, 
we *must* at least acknowledge the outstanding problem tickets.||
 || 2. || Update Release Notes || done ||
 || 3. || Check Dependencies || done ||

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

svn commit: rev 55366 - struts/trunk/doc

2004-10-23 Thread husted

Author: husted
Date: Sat Oct 23 03:28:17 2004
New Revision: 55366

Modified:
   struts/trunk/doc/acquiring.xml
   struts/trunk/doc/bylaws.xml
   struts/trunk/doc/releases.xml
   struts/trunk/doc/roadmap.xml
Log:
Updates to synch website with discussions on Struts Dev list.

Modified: struts/trunk/doc/acquiring.xml
==
--- struts/trunk/doc/acquiring.xml  (original)
+++ struts/trunk/doc/acquiring.xml  Sat Oct 23 03:28:17 2004
@@ -57,9 +57,6 @@
 When a build is judged "ready for prime time", it is promoted to "General
 Availability" status and may be made the "Best Available" release.
 
-
-The current development build is Struts v1.2.5 and is available http://svn.apache.org/dist/struts/v1.2.5/";>here
-
 
 
 

Modified: struts/trunk/doc/bylaws.xml
==
--- struts/trunk/doc/bylaws.xml (original)
+++ struts/trunk/doc/bylaws.xml Sat Oct 23 03:28:17 2004
@@ -275,30 +275,27 @@
 
 
   
-  A release plan may be used to keep all volunteers aware of when a
-  release is desired, who will be the release manager, when the
-  repository will be tagged to create a release, and other assorted
-  information to keep volunteers from tripping over each other. Lazy
-  majority decides each issue in a release plan.
+  A release plan must be used to keep all volunteers aware of when a
+  release is desired, whether it will be a major, minor, or
+  milestone release, who will be the release manager, when the
+  repository will be tagged to create the distribution, and other assorted
+  information to keep volunteers from tripping over each other. A release
+  plan must be announced to the DEV list. Lazy majority decides each issue
+  in a release plan.
   
 
-  
+
 
 
 
 
-After a new release is built, it must be tested and classified before
-being released to the general public. A release is automatically
-assigned an "Alpha" status. The release grade may be changed to
-"Beta" or "General Availability" by majority vote. Once a release is
-classified by the PMC Members, it can be distributed to the general
-public on behalf of the Foundation.
-
-
-
-Once a release is tagged and built (or "rolled"), it should not be
-rebuilt. If a problem is found, that release may be left at Alpha
-or Beta status and the next release created.
+After a proposed release is built, it must be tested and classified before
+being released to the general public. The proposed release may be assigned
+"Alpha", "Beta" or "General Availability" classifications by majority vote.
+Once a release is classified by the PMC Members, it may be distributed to
+the general public on behalf of the Foundation. Distributions may be
+reclassified or withdrawn by majority vote, but the release number may not
+be reused by another distribution.
 
 
 

Modified: struts/trunk/doc/releases.xml
==
--- struts/trunk/doc/releases.xml   (original)
+++ struts/trunk/doc/releases.xml   Sat Oct 23 03:28:17 2004
@@ -15,47 +15,36 @@
   available for download.
 
 
-  A 
-  http://jakarta.apache.org/commons/versioning.html";>point release 
should be made before and after any product change that is not a "fully-compatible 
change" (see link). This includes moving a dependency from an internal package to an 
external product, including products distributed through the Jakarta Commons. We 
should place any fully-compatible changes in the hands of the community before 
starting on a change that is only "interface" or "external-interface" compatible.
-  A fully-compatible point release does not always need a "preview" beta or 
milestone release. If appropriate, a Release Candidate can be cut, uploaded to the 
development distribution directories on svn.apache.org 
(/www/svn.apache.org/dist/struts/ and http://svn.apache.org/repository/struts/), and 
voted to be released to the general public from there. 
-  Any release should follow the same general process used by the Jakarta 
Commons and the Apache HTTP Server project.
-  
-
-  http://jakarta.apache.org/commons/releases/";>Releasing Common 
Components
-
-
-  http://nagoya.apache.org/wiki/apachewiki.cgi?SigningReleases";>Signing a release 
version
-  
-
-  The MD5 tool is installed on daedalus, and you can create the 
digests for Struts releases there.
-
-  
-
-
-  http://httpd.apache.org/dev/release.html";>Apache HTTPD Server 
Release Guidelines
-
-  
-http://apache.org/dev/";>Apache Developer Resources
-  
-  
+  A
+  http://jakarta.apa

Re: [VOTE] HTTPD or Tomcat (once more with feeling) [was Adopt ...]

2004-10-23 Thread Ted Husted

I don't agree that it makes any practical difference whether we use Tomcat or HTTPD. 
Most people won't even notice the difference. (I didn't at first.) I'd still prefer 
going with HTTPD "out of the box" for the sake of standardization.

My own feelings aside, I updated the website to coincide with what we discussed here.

Most of the issues raised in this thread should be resolved as part of the release 
plan, rather than after the distribution (or proposed release) has been rolled. If 
posting a release plan is *required* before tagging the repository, then a lot of 
these concerns go away.

If a release plan is not enough to save us from "committers gone wild", then we have 
problems that a "test build" phase won't fix. :)

Accordingly, I strengthened the need for a formal plan in the Release Guidelines and 
Bylaws, and I also tweaked the Release Plan checklist for 1.2.5 to clarify the 
terminology and sequence of events. The changes are in the repository and posted to 
the site, subject to lazy consensus.

-Ted.


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

RE: non-standard attributes in taglib

2004-10-23 Thread Ted Husted

On Wed, 20 Oct 2004 09:37:32 -0500, Joe Germuska wrote:
> Personally, I don't think I'd even
> object to making it a Struts sub-project that was available but
> clearly distinct from the core and the base taglib

+1

We can keep the original Struts taglib subproject, that observes on the HTML 
specification, and still have fancier implementations -- if that's what the community 
wants AND if there are volunteers to do the work.

Personally, I'd love to see a proposal for a gee-whiz taglib subproject, like Struts 
Layout. But as to the existing taglibs, I'd agree they should stay in the scope of the 
4.01 specification. There are product manager who love the fact that the existing 
taglibs sticks to the spec, and the original taglib serves them well.

But sticking to 4.01 for the original taglibs subproject doesn't preclude other 
extensions that go beyond 4.01, like we have for JSTL and Faces.

-Ted.

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

svn commit: rev 55393 - struts/trunk/contrib/struts-chain/src/java/org/apache/struts/chain/legacy

2004-10-23 Thread craigmcc

Author: craigmcc
Date: Sat Oct 23 11:30:37 2004
New Revision: 55393

Added:
   
struts/trunk/contrib/struts-chain/src/java/org/apache/struts/chain/legacy/ChainAction.java
   
struts/trunk/contrib/struts-chain/src/java/org/apache/struts/chain/legacy/DispatchAction.java
Log:
Add a couple of ways that an Action can delegate its business logic
processing to a Chain (or Command):

* ChainAction - Name of the chain is configured in the  element

* DispatchAction - Name of the chain is specified by a request parameter
  (analogous to the standard org.apache.struts.actions.DispatchAction)


Added: 
struts/trunk/contrib/struts-chain/src/java/org/apache/struts/chain/legacy/ChainAction.java
==
--- (empty file)
+++ 
struts/trunk/contrib/struts-chain/src/java/org/apache/struts/chain/legacy/ChainAction.java
  Sat Oct 23 11:30:37 2004
@@ -0,0 +1,152 @@
+/*
+ * Copyright 1999-2004 The Apache Software Foundation.
+ * 
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ * 
+ *  http://www.apache.org/licenses/LICENSE-2.0
+ * 
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.struts.chain.legacy;
+
+import javax.servlet.http.HttpServletRequest;
+import javax.servlet.http.HttpServletResponse;
+
+import org.apache.commons.chain.Catalog;
+import org.apache.commons.chain.CatalogFactory;
+import org.apache.commons.chain.Command;
+import org.apache.commons.chain.Context;
+import org.apache.commons.chain.web.servlet.ServletWebContext;
+
+import org.apache.struts.action.Action;
+import org.apache.struts.action.ActionForm;
+import org.apache.struts.action.ActionForward;
+import org.apache.struts.action.ActionMapping;
+
+/**
+ * An Action implementation that delegates to a
+ * configured Chain (or Command) for performing the actual business
+ * logic related to a request.  The name of the chain to be executed
+ * is specified by setting the parameter attribute of
+ * the  element configuring this action.
+ * For example:
+ *
+ * 
+ *

DO NOT REPLY [Bug 18169] - Resource attribute of msg tag in the validation.xml doesn't work as anticipated

2004-10-23 Thread bugzilla

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://issues.apache.org/bugzilla/show_bug.cgi?id=18169

Resource attribute of msg tag in the validation.xml doesn't work as anticipated





--- Additional Comments From [EMAIL PROTECTED]  2004-10-24 03:07 ---
Is this an issue within Struts or Commons Validator?  If this issue is with the 
JavaScript generated for client-side error reporting, you might have better 
luck opening a ticket against Commons Validator.

If you opt to file against Commons Validator, and there is no problem with the 
way Commons Validator is integrated within Struts, please close this ticket 
when you open the other one.

Thanks :-)

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

Bugzilla

2004-10-23 Thread Eddie Bush

Hey Y'all,

Is there some way I can change the email address used by Bugzilla?  I looked into the 
"prefs", but don't see a way to modify this.  Seeing as how I no longer use that email 
address, I should really see about getting it changed.  Must I create a new Bugzilla 
account to effect this change?

Thanks!

Eddie


---
avast! Antivirus: Outbound message clean.
Virus Database (VPS): 0443-3, 10/22/2004
Tested on: 10/23/2004 10:10:55 PM
avast! - copyright (c) 2000-2004 ALWIL Software.
http://www.avast.com

DO NOT REPLY [Bug 30876] - While using File Upload, getting ClassCastException when returning from a FormBean/Action Class

2004-10-23 Thread bugzilla

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://issues.apache.org/bugzilla/show_bug.cgi?id=30876

While using File Upload, getting ClassCastException when returning from a 
FormBean/Action Class





--- Additional Comments From [EMAIL PROTECTED]  2004-10-24 03:28 ---
Is this still an issue, or may it be closed?

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

DO NOT REPLY [Bug 31731] - ClassCastException from ActionServlet.getRequestProcessor()

2004-10-23 Thread bugzilla

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://issues.apache.org/bugzilla/show_bug.cgi?id=31731

ClassCastException from ActionServlet.getRequestProcessor()





--- Additional Comments From [EMAIL PROTECTED]  2004-10-24 03:34 ---
Adam,

Have you attempted resolution of this issue with Kris' suggestion?  It sounds 
to me like this is a case of a container not adhering to the spec and not an 
issue with Struts.  It's not Struts' fault that your container elected to use a 
different classloader to load new copies of your classes - thereby rendering 
them incompatible.

Regards,

Eddie

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

Bugs in dependencies

2004-10-23 Thread Eddie Bush

Howdy Y'all,

Just wondering how we wish to address bugs in things Struts is dependant upon, such as 
validator, file-upload, etc.  Should these bugs remain filed against Struts?  It seems 
more apropriate to me that they be closed with an FYI that the issue is with something 
we're dependant upon and not with Struts itself, as well as a tactful request that the 
filer go file against the project we're dependant on.

Does that rub anyone wrong?  Why?  I'm curious about protocol here.

Perhaps we should close the bug and file the new one on their behalf, including their 
email on the newly-filed bug?

Thanks!

Eddie



---
avast! Antivirus: Outbound message clean.
Virus Database (VPS): 0443-3, 10/22/2004
Tested on: 10/23/2004 10:45:46 PM
avast! - copyright (c) 2000-2004 ALWIL Software.
http://www.avast.com

DO NOT REPLY [Bug 31836] - Non-wildcard mapped actions cause 's action render to fail

2004-10-23 Thread bugzilla

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://issues.apache.org/bugzilla/show_bug.cgi?id=31836

Non-wildcard mapped actions cause 's action render to fail

[EMAIL PROTECTED] changed:

   What|Removed |Added

   Severity|Normal  |Enhancement
 Status|NEW |RESOLVED
 Resolution||INVALID



--- Additional Comments From [EMAIL PROTECTED]  2004-10-24 04:06 ---
This isn't a Struts bug.  If you read the documentation, you'll find that you 
may either map actions to the *.do pattern or do do/*.  For module support, it 
is required that you use extension mapping (*.do).

See http://struts.apache.org/userGuide/configuration.html#dd_config_mapping

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

Re: Bugzilla

2004-10-23 Thread Martin Cooper

On Sat, 23 Oct 2004 22:10:53 -0500, Eddie Bush <[EMAIL PROTECTED]> wrote:
> Hey Y'all,
> 
> Is there some way I can change the email address used by Bugzilla?  I looked into 
> the "prefs", but don't see a way to modify this.  Seeing as how I no longer use that 
> email address, I should really see about getting it changed.  Must I create a new 
> Bugzilla account to effect this change?
> 
You'll need to create a new e-mail account. Once you've done that, you
can use the Email Settings tab on User Preferences to "watch" your old
e-mail account, meaning that any mail that would have been sent to
that should be sent to your new account.

--
Martin Cooper


> Thanks!
> 
> Eddie
> 
> ---
> avast! Antivirus: Outbound message clean.
> Virus Database (VPS): 0443-3, 10/22/2004
> Tested on: 10/23/2004 10:10:55 PM
> avast! - copyright (c) 2000-2004 ALWIL Software.
> http://www.avast.com
> 
>

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

Re: Bugs in dependencies

2004-10-23 Thread Martin Cooper

On Sat, 23 Oct 2004 22:45:44 -0500, Eddie Bush <[EMAIL PROTECTED]> wrote:
> Howdy Y'all,
> 
> Just wondering how we wish to address bugs in things Struts is dependant upon, such 
> as validator, file-upload, etc.  Should these bugs remain filed against Struts?  It 
> seems more apropriate to me that they be closed with an FYI that the issue is with 
> something we're dependant upon and not with Struts itself, as well as a tactful 
> request that the filer go file against the project we're dependant on.
> 

If you're positive that the bug is in the external component, and not
in the glue code for that in Struts, then you can change the Bugzilla
product and component to that of the external component in question.
(Be aware that this is a two step process - you'll need to change the
product first, before you'll get the appropriate component list to
choose from.)

If there is some question about whether it's in the external component
or in the glue, I think the bug should be left here until that is
determined.

--
Martin Cooper

> Does that rub anyone wrong?  Why?  I'm curious about protocol here.
> 
> Perhaps we should close the bug and file the new one on their behalf, including 
> their email on the newly-filed bug?
> 
> Thanks!
> 
> Eddie
> 
> ---
> avast! Antivirus: Outbound message clean.
> Virus Database (VPS): 0443-3, 10/22/2004
> Tested on: 10/23/2004 10:45:46 PM
> avast! - copyright (c) 2000-2004 ALWIL Software.
> http://www.avast.com
> 
>

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

Re: Bugs in dependencies

2004-10-23 Thread Eddie Bush

in-line ...
- Original Message - 
From: "Martin Cooper" <[EMAIL PROTECTED]>
To: "Struts Developers List" <[EMAIL PROTECTED]>
Sent: Saturday, October 23, 2004 11:16 PM
Subject: Re: Bugs in dependencies

On Sat, 23 Oct 2004 22:45:44 -0500, Eddie Bush <[EMAIL PROTECTED]> wrote:
Howdy Y'all,
Just wondering how we wish to address bugs in things Struts is dependant 
upon, such as validator, file-upload, etc.  Should these bugs remain 
filed against Struts?  It seems more apropriate to me that they be closed 
with an FYI that the issue is with something we're dependant upon and not 
with Struts itself, as well as a tactful request that the filer go file 
against the project we're dependant on.

If you're positive that the bug is in the external component, and not
in the glue code for that in Struts, then you can change the Bugzilla
product and component to that of the external component in question.
(Be aware that this is a two step process - you'll need to change the
product first, before you'll get the appropriate component list to
choose from.)
Fantastic.  Thanks Martin :-)
If there is some question about whether it's in the external component
or in the glue, I think the bug should be left here until that is
determined.
I wholeheartedly agree!  It's annoying to see bugs filed against Struts that 
aren't rightfully Struts bugs though :-)

--
Martin Cooper

Does that rub anyone wrong?  Why?  I'm curious about protocol here.
Perhaps we should close the bug and file the new one on their behalf, 
including their email on the newly-filed bug?

Thanks!
Eddie 

---
avast! Antivirus: Outbound message clean.
Virus Database (VPS): 0443-3, 10/22/2004
Tested on: 10/23/2004 11:21:48 PM
avast! - copyright (c) 2000-2004 ALWIL Software.
http://www.avast.com

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

Invalid Email Addresses

2004-10-23 Thread Eddie Bush

Would it be inappropriate to remove email addresses that come back invalid from bugs?  
I wouldn't want to create the perception that we're trying to take someone out of the 
loop, but I find bounce messages annoying ...

Thanks! :-)


---
avast! Antivirus: Outbound message clean.
Virus Database (VPS): 0443-3, 10/22/2004
Tested on: 10/23/2004 11:26:34 PM
avast! - copyright (c) 2000-2004 ALWIL Software.
http://www.avast.com

Re: Invalid Email Addresses

2004-10-23 Thread Martin Cooper

On Sat, 23 Oct 2004 23:26:32 -0500, Eddie Bush <[EMAIL PROTECTED]> wrote:
> Would it be inappropriate to remove email addresses that come back invalid from 
> bugs?  I wouldn't want to create the perception that we're trying to take someone 
> out of the loop, but I find bounce messages annoying ...
> 

I think that's fine as long as you add a comment to that effect in the
bug report.

--
Martin Cooper


> Thanks! :-)
> 
> ---
> avast! Antivirus: Outbound message clean.
> Virus Database (VPS): 0443-3, 10/22/2004
> Tested on: 10/23/2004 11:26:34 PM
> avast! - copyright (c) 2000-2004 ALWIL Software.
> http://www.avast.com
> 
>

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

SVN Commits

2004-10-23 Thread Eddie Bush

Howdy Y'all,

I seem to be having some issues with SVN commits.  The client continually re-prompts 
me for my username/password -- and I even tried including them on the command line.

Example:

C:\Work\sub-version\struts-trunk\doc>svn commit --username [EMAIL PROTECTED] 
--password XX --message "Updated to reflect that I am now active again"
Sendingdoc\volunteers.xml
Authentication realm:  ASF Committers
Username: [EMAIL PROTECTED]
Password for '[EMAIL PROTECTED]': **
Authentication realm:  ASF Committers
Username: svn: Commit failed (details follow):
svn: CHECKOUT of '/repos/asf/!svn/ver/51684/struts/trunk/doc/volunteers.xml': 
authorization failed (https://svn.apache.org)

Are you familiar with this at all?  I was able to check things out (anonymously) using 
SVN without a hitch.

I have tried multiple forms of my username - all have met with equal lack of success.

I've managed to test a patch for ActionServlet I'd like to apply soon-ish too.

Thanks!

Eddie



---
avast! Antivirus: Outbound message clean.
Virus Database (VPS): 0443-3, 10/22/2004
Tested on: 10/24/2004 1:15:39 AM
avast! - copyright (c) 2000-2004 ALWIL Software.
http://www.avast.com

Re: SVN Commits

2004-10-23 Thread Eddie Bush

FYI - I can login to the CVS box and I'm pretty sure this is just an alias 
for that one, so that shouldn't be an issue.  I'm very open to suggestions 
as to how I may resolve this :-)

Thanks!
- Original Message - 
From: "Eddie Bush" <[EMAIL PROTECTED]>
To: "Struts Developers List" <[EMAIL PROTECTED]>
Sent: Sunday, October 24, 2004 1:15 AM
Subject: SVN Commits

Howdy Y'all,
I seem to be having some issues with SVN commits.  The client continually 
re-prompts me for my username/password -- and I even tried including them on 
the command line.

Example:
C:\Work\sub-version\struts-trunk\doc>svn commit --username 
[EMAIL PROTECTED] --password XX --message "Updated to reflect that I 
am now active again"
Sendingdoc\volunteers.xml
Authentication realm:  ASF Committers
Username: [EMAIL PROTECTED]
Password for '[EMAIL PROTECTED]': **
Authentication realm:  ASF Committers
Username: svn: Commit failed (details follow):
svn: CHECKOUT of 
'/repos/asf/!svn/ver/51684/struts/trunk/doc/volunteers.xml': authorization 
failed (https://svn.apache.org)

Are you familiar with this at all?  I was able to check things out 
(anonymously) using SVN without a hitch.

I have tried multiple forms of my username - all have met with equal lack of 
success.

I've managed to test a patch for ActionServlet I'd like to apply soon-ish 
too.

Thanks!
Eddie

---
avast! Antivirus: Outbound message clean.
Virus Database (VPS): 0443-3, 10/22/2004
Tested on: 10/24/2004 1:15:39 AM
avast! - copyright (c) 2000-2004 ALWIL Software.
http://www.avast.com

---
avast! Antivirus: Outbound message clean.
Virus Database (VPS): 0443-3, 10/22/2004
Tested on: 10/24/2004 1:22:28 AM
avast! - copyright (c) 2000-2004 ALWIL Software.
http://www.avast.com

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

Re: SVN Commits

2004-10-23 Thread Martin Cooper

On Sun, 24 Oct 2004 01:15:38 -0500, Eddie Bush <[EMAIL PROTECTED]> wrote:
> Howdy Y'all,
> 
> I seem to be having some issues with SVN commits.  The client continually re-prompts 
> me for my username/password -- and I even tried including them on the command line.
> 
> Example:
> 
> C:\Work\sub-version\struts-trunk\doc>svn commit --username [EMAIL PROTECTED] 
> --password XX --message "Updated to reflect that I am now active again"
> Sendingdoc\volunteers.xml
> Authentication realm:  ASF Committers
> Username: [EMAIL PROTECTED]
> Password for '[EMAIL PROTECTED]': **
> Authentication realm:  ASF Committers
> Username: svn: Commit failed (details follow):
> svn: CHECKOUT of '/repos/asf/!svn/ver/51684/struts/trunk/doc/volunteers.xml': 
> authorization failed (https://svn.apache.org)
> 
> Are you familiar with this at all?  I was able to check things out (anonymously) 
> using SVN without a hitch.
> 

Just guessing, but this (your anonymous checkout) might be the
problem. If you didn't check out using the HTTPS URL, then you won't
be able to  check in changes.

--
Martin Cooper


> I have tried multiple forms of my username - all have met with equal lack of success.
> 
> I've managed to test a patch for ActionServlet I'd like to apply soon-ish too.
> 
> Thanks!
> 
> Eddie
> 
> ---
> avast! Antivirus: Outbound message clean.
> Virus Database (VPS): 0443-3, 10/22/2004
> Tested on: 10/24/2004 1:15:39 AM
> avast! - copyright (c) 2000-2004 ALWIL Software.
> http://www.avast.com
> 
>

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

Re: SVN Commits

2004-10-23 Thread Eddie Bush

Well, I did the checkout just as it's described in :
http://www.apache.org/dev/version-control.html
In fact, that's what I patterned my commit after as well.  Must one be 
purposefully setup to use SVN for commits, or should a person who previously 
had CVS access auto-magically have SVN commit access as well?

- Original Message - 
From: "Martin Cooper" <[EMAIL PROTECTED]>
To: "Struts Developers List" <[EMAIL PROTECTED]>
Sent: Sunday, October 24, 2004 1:39 AM
Subject: Re: SVN Commits

On Sun, 24 Oct 2004 01:15:38 -0500, Eddie Bush <[EMAIL PROTECTED]> wrote:
Howdy Y'all,
I seem to be having some issues with SVN commits.  The client continually 
re-prompts me for my username/password -- and I even tried including them 
on the command line.

Example:
C:\Work\sub-version\struts-trunk\doc>svn commit --username 
[EMAIL PROTECTED] --password XX --message "Updated to reflect 
that I am now active again"
Sendingdoc\volunteers.xml
Authentication realm:  ASF Committers
Username: [EMAIL PROTECTED]
Password for '[EMAIL PROTECTED]': **
Authentication realm:  ASF Committers
Username: svn: Commit failed (details follow):
svn: CHECKOUT of 
'/repos/asf/!svn/ver/51684/struts/trunk/doc/volunteers.xml': 
authorization failed (https://svn.apache.org)

Are you familiar with this at all?  I was able to check things out 
(anonymously) using SVN without a hitch.

Just guessing, but this (your anonymous checkout) might be the
problem. If you didn't check out using the HTTPS URL, then you won't
be able to  check in changes.
--
Martin Cooper

I have tried multiple forms of my username - all have met with equal lack 
of success.

I've managed to test a patch for ActionServlet I'd like to apply soon-ish 
too.

Thanks!
Eddie 

---
avast! Antivirus: Outbound message clean.
Virus Database (VPS): 0443-3, 10/22/2004
Tested on: 10/24/2004 1:46:01 AM
avast! - copyright (c) 2000-2004 ALWIL Software.
http://www.avast.com

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

Re: SVN Commits

2004-10-23 Thread Eddie Bush

I'm able to get on the CVS box just fine:
login as: ekbush
Sent username "ekbush"
[EMAIL PROTECTED]'s password:
Last login: Fri Oct 15 21:10:46 2004 from minotaur.apache
Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994
   The Regents of the University of California.  All rights reserved.
FreeBSD 4.10-STABLE (turbo) #6: Sat Jun  5 10:27:02 PDT 2004
Welcome to FreeBSD!
This is an Apache Software Foundation server.
For more information please see:
 http://www.apache.org/dev/
In order to support national characters for European languages in tools like
less without creating other nationalisation aspects, set the environment
variable LC_ALL to 'en_US.ISO8859-1'.

... however nothing I have tried, as of yet, has enabled me to experience 
success at committing via SVN:

C:\Work\sub-version\struts-trunk\doc>svn commit --username ekbush --message 
"Re-added myself as active." volunteers.xml
Sendingvolunteers.xml
Authentication realm:  ASF Committers
Password for 'ekbush': **
Authentication realm:  ASF Committers
Username: [EMAIL PROTECTED]
Password for '[EMAIL PROTECTED]': **
Authentication realm:  ASF Committers
Username: svn: Commit failed (details follow):
svn: CHECKOUT of 
'/repos/asf/!svn/ver/51684/struts/trunk/doc/volunteers.xml': authorization 
failed (https://svn.apache.org)

I re-checked-out the tree, and even specified my username this time when 
doing so.  No luck :-(

I'll surf around and see what I can find that might be helpful.  I'm open to 
suggestions.

Thanks for trying, Martin :-)
Eddie
- Original Message - 
From: "Eddie Bush" <[EMAIL PROTECTED]>
To: "Struts Developers List" <[EMAIL PROTECTED]>; "Martin Cooper" 
<[EMAIL PROTECTED]>
Sent: Sunday, October 24, 2004 1:45 AM
Subject: Re: SVN Commits


Well, I did the checkout just as it's described in :
http://www.apache.org/dev/version-control.html
In fact, that's what I patterned my commit after as well.  Must one be 
purposefully setup to use SVN for commits, or should a person who 
previously had CVS access auto-magically have SVN commit access as well?

- Original Message - 
From: "Martin Cooper" <[EMAIL PROTECTED]>
To: "Struts Developers List" <[EMAIL PROTECTED]>
Sent: Sunday, October 24, 2004 1:39 AM
Subject: Re: SVN Commits


On Sun, 24 Oct 2004 01:15:38 -0500, Eddie Bush <[EMAIL PROTECTED]> wrote:
Howdy Y'all,
I seem to be having some issues with SVN commits.  The client 
continually re-prompts me for my username/password -- and I even tried 
including them on the command line.

Example:
C:\Work\sub-version\struts-trunk\doc>svn commit --username 
[EMAIL PROTECTED] --password XX --message "Updated to reflect 
that I am now active again"
Sendingdoc\volunteers.xml
Authentication realm:  ASF Committers
Username: [EMAIL PROTECTED]
Password for '[EMAIL PROTECTED]': **
Authentication realm:  ASF Committers
Username: svn: Commit failed (details follow):
svn: CHECKOUT of 
'/repos/asf/!svn/ver/51684/struts/trunk/doc/volunteers.xml': 
authorization failed (https://svn.apache.org)

Are you familiar with this at all?  I was able to check things out 
(anonymously) using SVN without a hitch.

Just guessing, but this (your anonymous checkout) might be the
problem. If you didn't check out using the HTTPS URL, then you won't
be able to  check in changes.
--
Martin Cooper

I have tried multiple forms of my username - all have met with equal 
lack of success.

I've managed to test a patch for ActionServlet I'd like to apply 
soon-ish too.

Thanks!
Eddie

---
avast! Antivirus: Outbound message clean.
Virus Database (VPS): 0443-3, 10/22/2004
Tested on: 10/24/2004 1:46:01 AM
avast! - copyright (c) 2000-2004 ALWIL Software.
http://www.avast.com

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

---
avast! Antivirus: Outbound message clean.
Virus Database (VPS): 0443-3, 10/22/2004
Tested on: 10/24/2004 1:58:18 AM
avast! - copyright (c) 2000-2004 ALWIL Software.
http://www.avast.com

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

[Apache Struts Wiki] Updated: StrutsRelease125

[Apache Struts Wiki] Updated: StrutsRelease125

[Apache Struts Wiki] Updated: StrutsRelease125

[Apache Struts Wiki] Updated: StrutsRelease125

svn commit: rev 55366 - struts/trunk/doc

Re: [VOTE] HTTPD or Tomcat (once more with feeling) [was Adopt ...]

RE: non-standard attributes in taglib

svn commit: rev 55393 - struts/trunk/contrib/struts-chain/src/java/org/apache/struts/chain/legacy

DO NOT REPLY [Bug 18169] - Resource attribute of msg tag in the validation.xml doesn't work as anticipated

Bugzilla

DO NOT REPLY [Bug 30876] - While using File Upload, getting ClassCastException when returning from a FormBean/Action Class

DO NOT REPLY [Bug 31731] - ClassCastException from ActionServlet.getRequestProcessor()

Bugs in dependencies

DO NOT REPLY [Bug 31836] - Non-wildcard mapped actions cause 's action render to fail

Re: Bugzilla

Re: Bugs in dependencies

Re: Bugs in dependencies

Invalid Email Addresses

Re: Invalid Email Addresses

SVN Commits

Re: SVN Commits

Re: SVN Commits

Re: SVN Commits

Re: SVN Commits

24 matches

Site Navigation

Mail list logo

Footer information