DO NOT REPLY [Bug 39550] New: - Add equals(type[]) to NumberUtils

2006-05-10 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=39550

   Summary: Add equals(type[]) to NumberUtils
   Product: Commons
   Version: Nightly Builds
  Platform: Other
OS/Version: other
Status: NEW
  Severity: enhancement
  Priority: P2
 Component: Lang
AssignedTo: commons-dev@jakarta.apache.org
ReportedBy: [EMAIL PROTECTED]


It would be useful to add an equals() method like the current min and max
methods which take an array type and determine if all the values are equal.

I have found myself in need of this often. I have to retrieve objects from
multiple data sources in parallel to build an array of complex object. To ensure
validity, I always compare that my sub-retrievals returned the same number of
objects as expected.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

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

DO NOT REPLY [Bug 39477] - [beanutils] StringLocaleConverter uses same pattern for numbers and dates

2006-05-10 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=39477





--- Additional Comments From [EMAIL PROTECTED]  2006-05-11 04:40 ---
The problem is that if your target is String, which is a sort of catch-all
target, you may have both numbers and dates that need to be converted to a
String.  I think the primary use case that was envisioned for BeanUtils was to
copy *from* Strings *to* specific types.  However, I've found it quite common
that I want to prepopulate an ActionForm from a business object, which means I'm
copying all the various specific types to Strings.  If there are numbers and
dates, they'll need different formats.

I'll work on putting a junit test together for it -- may not get to it until
this weekend.  

Thanks!

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

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

RE: [jelly] taglibs lead distribution ?

2006-05-10 Thread Hans Gilde 
I can do bug fixes and such and I'm definitely in favor of cleaning up the
Jira assignments. If you'd like to assign me some stuff, I'll fix it. But
I'm not in a position to really lead anything at the moment.

-Original Message-
From: Paul Libbrecht [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, May 10, 2006 4:17 AM
To: Jakarta Commons Developers List
Subject: [jelly] taglibs lead distribution ?


Hi,


I was fiddling with Jira jelly project administration because 
interaction didn't have a component and realized that some components 
have been assigned to dion... which is good.
I'd like it if we could distribute the lead of all components, also so 
that James Strachan is not anymore the default assignee!!

I'd be willing to take over xml and swing tag-libs... maybe some others.
Would anyone wish those ? Would anyone be ready to take over others ?
Some taglibs are not in urgent need but some really have a need and this 
way we could react better to requests which keep coming as jelly, even 
though it tastes unfinished, still has a good attraction, I feel.

paul

-
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]

DO NOT REPLY [Bug 39548] - [configuration] use a Strategy pattern for locating resources

2006-05-10 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=39548





--- Additional Comments From [EMAIL PROTECTED]  2006-05-10 21:24 ---
Created an attachment (id=18253)
 --> (http://issues.apache.org/bugzilla/attachment.cgi?id=18253&action=view)
locator-strategy.patch

This patch is against trunk from a month or two ago. I would have updated, but
for some reason the repository can't be found.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

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

DO NOT REPLY [Bug 39548] New: - [configuration] use a Strategy pattern for locating resources

2006-05-10 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=39548

   Summary: [configuration] use a Strategy pattern for locating
resources
   Product: Commons
   Version: unspecified
  Platform: Other
OS/Version: other
Status: NEW
  Severity: enhancement
  Priority: P2
 Component: Configuration
AssignedTo: commons-dev@jakarta.apache.org
ReportedBy: [EMAIL PROTECTED]


Currently, the method for locating resources (ie ConfigurationUtils.locate )
uses a few means of finding the resource. However, the ways of finding resources
are set in stone.

At times, it would be useful to be able to pick and choose how resources are
located. Here's an example:

I have a webapp that builds a CompositeConfiguration composed of several
PropertiesConfigurations (we'll say my.properties and default.properties) via
spring. So, I go to kick off tomcat. If the current directory I'm in has a
my.properties or default.properties those files get used instead of the ones
on the classpath that I intended to be used. As a result, unexpected behavior of
the webapp ensues.

The solution to this is to encapsulate each algorithm for locating resoucess,
and be able to pick and choose. To me, this screamed of the strategy pattern.

A patch is forthcoming...

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

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

Re: [PROPOSAL] Move Commons Proxy to Proper

2006-05-10 Thread robert burrell donkin 
On Mon, 2006-05-08 at 20:30 +0200, Joerg Hohwiller wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Hi there,
> 
> James Carman wrote:
> > Outside projects (currently my Syringe project and the "Crispy" project
> > at sourceforge) are beginning to want to use Commons Proxy, but are finding
> > it difficult since it's in the sandbox and no releases are available.  I
> > believe Proxy's API is close to being ready for a release candidate.
> > Moving it to the proper will help us prepare it for an
> > official release.  There are some classes that I might remove altogether,
> > since they feel rather "frameworky" (the CachedProvider is one of them).
> > I've cut/signed a mock 1.0 release and it can be found in my home directory
> > (/home/jcarman/commons-proxy-1.0-release) on www.apache.org.  Can you folks
> > take a look at it and let me know what you think?
> A little late on this but anyways...
> Just to meantion that the framework of my open-source project at sourceforge
> is also looking at commons-proxy. I would apreciate if proxy would move to
> proper. It looks quite stable and ready to use for me...

i'm generally in favour

- robert



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

[Jakarta-commons Wiki] Update of "SCXML/Upgrades/ChangesBeforeFirstRC" by RahulAkolkar

2006-05-10 Thread Apache Wiki 
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jakarta-commons Wiki" 
for change notification.

The following page has been changed by RahulAkolkar:
http://wiki.apache.org/jakarta-commons/SCXML/Upgrades/ChangesBeforeFirstRC

The comment on the change is:
New page for API changes before going to RC1 (should be easy porting atleast)

New page:
This page contains notes about changes made before proposing the first release 
candidate of Commons SCXML. While attempts are made to maintain backwards 
compatibility even for unreleased code to minimize user inconvenience, some 
changes are best made before a first release, when the API gets locked (until 
the next major version atleast). Each change is described in terms of the 
motivation and the migration path for affected users.



Contents:
[[TableOfContents]]



=== Custom actions and the SCXML digester ===

''Changed since: 05/11/2006 nightly''

''Affected users: Those who use custom actions''

The earlier approach of adding custom actions, one at a time, after a SCXML 
digester was instantiated has been replaced by an approach where all custom 
actions are now passed at once while instantiating the SCXML digester. The 
earlier approach:

 * Was not processing custom actions in external documents (that were pulled in 
via the  "src" attribute, for instance).
 * Had a more error-prone API (needed a call to updateSCXML() method)

Here is an example code snippet and the changes needed (note that the custom 
action class itself can be reused, so no additional development is needed for 
custom actions):

''Before:''
{{{
  // (1) Get Digester with "default" rules for parsing SCXML documents
  Digester digester = SCXMLDigester.newInstance(null, null);

  // (2) Register the "custom" action(s)
  SCXMLDigester.addCustomAction(digester,
   "http://my.custom-actions.domain/CUSTOM";, "hello", Hello.class);

  // (3) Repeat 2 for other custom actions 

  // (4) Parse the SCXML document containing the custom action(s)
  SCXML scxml = null;
  try {
  scxml = (SCXML) digester.parse(url.toString());
  // url points to SCXML document
  } catch (Exception e) {
  // bad document, take necessary action
  }

  // (5) Wire up the object model for the SCXMLExecutor
  SCXMLDigester.updateSCXML(scxml);

  // (6) Continue creating an SCXMLExecutor etc.
}}}


''After:''
{{{
  // (1) Create a list of custom actions, add as many as are needed
  List customActions = new ArrayList();
  CustomAction ca =
new CustomAction("http://my.custom-actions.domain/CUSTOM";,
 "hello", Hello.class);
  customActions.add(ca);

  // (2) Add other custom actions to list

  // (3) Parse the SCXML document containing the custom action(s)
  SCXML scxml = null;
  try {
  scxml = SCXMLDigester.digest(url, errorHandler, customActions);
  // url points to SCXML document, errorHandler is SAX ErrorHandler
  } catch (Exception e) {
  // bad document, take necessary action
  }

  // (4) Continue creating an SCXMLExecutor etc.
}}}

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

[Jakarta-commons Wiki] Update of "SCXML/HomePage" by RahulAkolkar

2006-05-10 Thread Apache Wiki 
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jakarta-commons Wiki" 
for change notification.

The following page has been changed by RahulAkolkar:
http://wiki.apache.org/jakarta-commons/SCXML/HomePage

The comment on the change is:
Remove dead-end link added by Fasih.

--
   * ["../Tutorials/Templating"] 
  SCXML allows for defining of a certain FSM externally which can be re-used 
for convenience. This tutorial briefly covers the use-cases and the 
implementation of the Templating Pattern. 
  
-  BridgingPatterns 
- 
-  * ["../Tutorials/BridgingPatterns"]
- 
  
  
  === Evolution ===

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

[Jakarta-commons Wiki] Update of "SCXML/HomePage" by RahulAkolkar

2006-05-10 Thread Apache Wiki 
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jakarta-commons Wiki" 
for change notification.

The following page has been changed by RahulAkolkar:
http://wiki.apache.org/jakarta-commons/SCXML/HomePage

The comment on the change is:
Page for the couple of API tweaks expected before RC1

--
  
  
  
+ === Evolution ===
+ 
+ This is a section to document the evolution of the Commons SCXML library, 
most importantly a placeholder to note any API changes and upgrade notes.
+ 
+  * ["../Upgrades/ChangesBeforeFirstRC"]
+ Document contains notes about changes made before proposing the first release 
candidate of Commons SCXML.
+ 
+ 
+ 
  === From The Archives ===
  
   * ../ProjectProposal

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

DO NOT REPLY [Bug 39534] - [scxml] External Digester does not addCustomActions

2006-05-10 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=39534





--- Additional Comments From [EMAIL PROTECTED]  2006-05-10 20:04 ---
That will definitely be a larger change for the users, but also conceptually, 
since the custom actions are meant to be in other XML namespaces, the approach 
used is similar to how Mozilla does XTF for its plugins (you define a backing 
bean for each element in the namespace). If we take the POJO approach, then it 
does imply higher reflection overheads (at runtime, reflection is our bread-n-
butter at parsing time) and is probably strange as an XML namespace. After 
all, the actions are called custom actions since their utility and 
implementation preferences are subjective.

As a library, Commons SCXML provides opportunities to customize most of its 
internals, be it parsing, custom actions or engine semantics. Together, these 
should allow users to build atop with their ideas (and the useful ones can 
hopefully come back in to Commons SCXML). There is only so much that will come 
out of the box, especially for the first release. I have some cleanup done 
that fixes this issue about not parsing custom actions in "src'ed in" 
documents, but the repository seems down ATM.


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

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

DO NOT REPLY [Bug 39537] - [dbcp] BasicDataSource.getConnection() Connections don't work as hashtable keys -- test case provided

2006-05-10 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=39537





--- Additional Comments From [EMAIL PROTECTED]  2006-05-10 16:38 ---
Skimming the source I think this may stem from DelegatingConnection having
equals() and hashCode() implementations that don't obey the equals & hashCode
contracts. My initial impressions is those methods should just be removed but
I'm not sure if this will have a negative side effects elsewhere.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

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

svn commit: r405769 - in /jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/cookie: Cookie2.java CookieAttributeHandler.java CookieOrigin.java CookiePathComparator.java

2006-05-10 Thread olegk 
Author: olegk
Date: Wed May 10 08:12:04 2006
New Revision: 405769

URL: http://svn.apache.org/viewcvs?rev=405769&view=rev
Log:
Some javadoc tweaks

Modified:

jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/cookie/Cookie2.java

jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/cookie/CookieAttributeHandler.java

jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/cookie/CookieOrigin.java

jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/cookie/CookiePathComparator.java

Modified: 
jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/cookie/Cookie2.java
URL: 
http://svn.apache.org/viewcvs/jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/cookie/Cookie2.java?rev=405769&r1=405768&r2=405769&view=diff
==
--- 
jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/cookie/Cookie2.java
 (original)
+++ 
jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/cookie/Cookie2.java
 Wed May 10 08:12:04 2006
@@ -1,7 +1,7 @@
 /*
  * $Header: 
/cvsroot/httpc-cookie2/httpc-cookie2/httpcookie2SVN-patch.082805-2100.diff,v 
1.1 2005/08/29 05:01:58 sjain700 Exp $
- * $Revision$
- * $Date$
+ * $Revision:400312 $
+ * $Date:2006-05-06 14:49:41 +0200 (Sat, 06 May 2006) $
  *
  * 
  *
@@ -41,6 +41,8 @@
  * 
  *
  * @author Samit Jain ([EMAIL PROTECTED])
+ * 
+ * @since 3.1
  */
 public class Cookie2 extends Cookie {
 

Modified: 
jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/cookie/CookieAttributeHandler.java
URL: 
http://svn.apache.org/viewcvs/jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/cookie/CookieAttributeHandler.java?rev=405769&r1=405768&r2=405769&view=diff
==
--- 
jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/cookie/CookieAttributeHandler.java
 (original)
+++ 
jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/cookie/CookieAttributeHandler.java
 Wed May 10 08:12:04 2006
@@ -1,7 +1,7 @@
 /*
- * $HeadURL$
- * $Revision$
- * $Date$
+ * 
$HeadURL:https://svn.apache.org/repos/asf/jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/cookie/CookieAttributeHandler.java
 $
+ * $Revision:400312 $
+ * $Date:2006-05-06 14:49:41 +0200 (Sat, 06 May 2006) $
  *
  * 
  *
@@ -32,14 +32,16 @@
 
 /**
  * Ths interface represents a cookie attribute handler responsible
- * for parsing, validating, matching and formatting a specific
- * cookie attribute, such as path, domain, port, etc.
+ * for parsing, validating, and matching a specific cookie attribute, 
+ * such as path, domain, port, etc.
  *
  * Different cookie specifications can provide a specific
  * implementation for this class based on their cookie handling
  * rules.
  *
  * @author [EMAIL PROTECTED] (Samit Jain)
+ * 
+ * @since 3.1
  */
 public interface CookieAttributeHandler {
 

Modified: 
jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/cookie/CookieOrigin.java
URL: 
http://svn.apache.org/viewcvs/jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/cookie/CookieOrigin.java?rev=405769&r1=405768&r2=405769&view=diff
==
--- 
jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/cookie/CookieOrigin.java
 (original)
+++ 
jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/cookie/CookieOrigin.java
 Wed May 10 08:12:04 2006
@@ -1,7 +1,7 @@
 /*
- * $HeadURL$
- * $Revision$
- * $Date$
+ * 
$HeadURL:https://svn.apache.org/repos/asf/jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/cookie/CookieOrigin.java
 $
+ * $Revision:400312 $
+ * $Date:2006-05-06 14:49:41 +0200 (Sat, 06 May 2006) $
  *
  * 
  *
@@ -28,6 +28,14 @@
  */
 package org.apache.commons.httpclient.cookie;
 
+/**
+ * CookieOrigin class incapsulates details of an origin server that 
+ * are relevant when parsing, validating or matching HTTP cookies.
+ * 
+ * @author mailto:oleg at ural.ru">Oleg Kalnichevski
+ * 
+ * @since 3.1
+ */
 public final class CookieOrigin {
 
private final String host;

Modified: 
jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/cookie/CookiePathComparator.java
URL: 
http://svn.apache.org/viewcvs/jakarta/commons/proper/httpclient/trunk/src/java/org/apache/commons/httpclient/cookie/CookiePathComparator.java?rev=405769&r1=40576

DO NOT REPLY [Bug 39538] - [collections] Support parametized classes with commons.collections.

2006-05-10 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=39538





--- Additional Comments From [EMAIL PROTECTED]  2006-05-10 14:47 ---
Someone has already ported it.  There's a sourceforge project
(http://collections15.sourceforge.net/) out there that does it.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

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

[EMAIL PROTECTED]: Project commons-jelly-tags-html (in module commons-jelly) failed

2006-05-10 Thread commons-jelly-tags-html development 
To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project commons-jelly-tags-html has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 9 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-jelly-tags-html :  Commons Jelly


Full details are available at:

http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-html/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [commons-jelly-tags-html-10052006.jar] identifier set to 
project name
 -DEBUG- Dependency on xml-xerces exists, no need to add for property 
maven.jar.xerces.
 -DEBUG- (Gump generated) Maven Properties in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/html/build.properties
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/html/project.xml
 -DEBUG- Maven project properties in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/html/project.properties
 -INFO- Project Reports in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/html/target/test-reports
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-html/gump_work/build_commons-jelly_commons-jelly-tags-html.html
Work Name: build_commons-jelly_commons-jelly-tags-html (Type: Build)
Work ended in a state of : Failed
Elapsed: 12 secs
Command Line: maven --offline jar 
[Working Directory: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/html]
CLASSPATH: 
/opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-10052006.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-10052006.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-10052006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/target/commons-jelly-tags-jsl-10052006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-10052006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-10052006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-10052006.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-10052006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-10052006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-10052006.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/packages/jaxen-1.1-beta-4/jaxen-1.1-beta-4.jar:/usr/local/gump/packages/nekohtml-0.9.5/nekohtml.jar
-
[junit] at 
org.apache.commons.jelly.tags.junit.CaseTag$1.runTest(CaseTag.java:59)
[junit] 
[junit] 
[junit] Testcase: 
testLowerCase(org.apache.commons.jelly.tags.junit.CaseTag$1): Caused an 
ERROR
[junit] 
file:/x1/gump/public/workspace/commons-jelly/jelly-tags/html/target/test-classes/org/apache/commons/jelly/html/suite.jelly:40:48:
  You must define an attribute called 'test' for this tag.
[junit] org.apache.commons.jelly.MissingAttributeException: 
file:/x1/gump/public/workspace/commons-jelly/jelly-tags/html/target/test-classes/org/apache/commons/jelly/html/suite.jelly:40:48:
  You must define an attribute called 'test' for this tag.
[junit] at 
org.apache.commons.jelly.tags.junit.AssertTag.doTag(AssertTag.java:54)
[junit] at 
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:262)
[junit] at 
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
[junit] at 
org.apache.commons.jelly.tags.junit.CaseTag$1.runTest(CaseTag.java:59)
[junit] 
[junit] 
[junit] Testcase: 
testMixedCase(org.apache.commons.jelly.tags.junit.CaseTag$1): Caused an 
ERROR
[junit] 
file:/x1/gump/public/workspace/commons-jelly/jelly-tags/html/target/test-classes/org/apache/commons/jelly/html/suite.jelly:47:48:
  You must define an attribute called 'test' for this tag.
[junit] org.apache.commons.jelly.MissingAttributeException: 
file:/x1/gump/public/workspace/commons-jelly/jelly-tags/html/target/test-classes/org/apache/commons/jelly/html/suite.jelly:47:48:
  You must define an attribute called 'test' for this tag.
[junit] at 
org.apache.commons.jelly.tags.junit.AssertTag.doTag(AssertTag.java:54)

[EMAIL PROTECTED]: Project commons-jelly-tags-html (in module commons-jelly) failed

2006-05-10 Thread commons-jelly-tags-html development 
To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project commons-jelly-tags-html has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 9 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-jelly-tags-html :  Commons Jelly


Full details are available at:

http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-html/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Sole output [commons-jelly-tags-html-10052006.jar] identifier set to 
project name
 -DEBUG- Dependency on xml-xerces exists, no need to add for property 
maven.jar.xerces.
 -DEBUG- (Gump generated) Maven Properties in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/html/build.properties
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/html/project.xml
 -DEBUG- Maven project properties in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/html/project.properties
 -INFO- Project Reports in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/html/target/test-reports
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-html/gump_work/build_commons-jelly_commons-jelly-tags-html.html
Work Name: build_commons-jelly_commons-jelly-tags-html (Type: Build)
Work ended in a state of : Failed
Elapsed: 12 secs
Command Line: maven --offline jar 
[Working Directory: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/html]
CLASSPATH: 
/opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-10052006.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-10052006.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-10052006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/target/commons-jelly-tags-jsl-10052006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-10052006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-10052006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-10052006.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-10052006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-10052006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-10052006.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/packages/jaxen-1.1-beta-4/jaxen-1.1-beta-4.jar:/usr/local/gump/packages/nekohtml-0.9.5/nekohtml.jar
-
[junit] at 
org.apache.commons.jelly.tags.junit.CaseTag$1.runTest(CaseTag.java:59)
[junit] 
[junit] 
[junit] Testcase: 
testLowerCase(org.apache.commons.jelly.tags.junit.CaseTag$1): Caused an 
ERROR
[junit] 
file:/x1/gump/public/workspace/commons-jelly/jelly-tags/html/target/test-classes/org/apache/commons/jelly/html/suite.jelly:40:48:
  You must define an attribute called 'test' for this tag.
[junit] org.apache.commons.jelly.MissingAttributeException: 
file:/x1/gump/public/workspace/commons-jelly/jelly-tags/html/target/test-classes/org/apache/commons/jelly/html/suite.jelly:40:48:
  You must define an attribute called 'test' for this tag.
[junit] at 
org.apache.commons.jelly.tags.junit.AssertTag.doTag(AssertTag.java:54)
[junit] at 
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:262)
[junit] at 
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
[junit] at 
org.apache.commons.jelly.tags.junit.CaseTag$1.runTest(CaseTag.java:59)
[junit] 
[junit] 
[junit] Testcase: 
testMixedCase(org.apache.commons.jelly.tags.junit.CaseTag$1): Caused an 
ERROR
[junit] 
file:/x1/gump/public/workspace/commons-jelly/jelly-tags/html/target/test-classes/org/apache/commons/jelly/html/suite.jelly:47:48:
  You must define an attribute called 'test' for this tag.
[junit] org.apache.commons.jelly.MissingAttributeException: 
file:/x1/gump/public/workspace/commons-jelly/jelly-tags/html/target/test-classes/org/apache/commons/jelly/html/suite.jelly:47:48:
  You must define an attribute called 'test' for this tag.
[junit] at 
org.apache.commons.jelly.tags.junit.AssertTag.doTag(AssertTag.java:54)

DO NOT REPLY [Bug 39538] - [collections] Support parametized classes with commons.collections.

2006-05-10 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=39538





--- Additional Comments From [EMAIL PROTECTED]  2006-05-10 14:09 ---
You should definitely branch out.  Support for non-parametric classes must be 
maintained for a long time to come.  I suggest starting the newer branch as 
commons.collections v5 to copy the Java 1.5 (also called Java 5 by some).

Taking the plunge is the best way to go.  I did and was suprised to how quickly 
things go.  The team should agree on a few basic principle which are also 
outlined in a PDF document distributed by Sun on their website (named generics-
tutorial.pdf).

I suggest starting with the abstract classes.  Have a review between developers 
to catch oversights.  Then go on to modify 2 or 3 containers and format testing 
(JUnit).  The tests should be straightforward.  It's a matter of testing 
derived type compatibility.  Once the first 2 or 3 containers done and tested, 
the rest will go very quickly.  

This project can be done in less than 1 month confortably.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

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

[jira] Commented: (JELLY-226) Upgrade dom4j and jaxen

2006-05-10 Thread Lukas Theussl (JIRA) 
[ 
http://issues.apache.org/jira/browse/JELLY-226?page=comments#action_12378924 ] 

Lukas Theussl commented on JELLY-226:
-

Please read the recent comments at http://jira.codehaus.org/browse/MAVEN-1345 
(hey, you opened this one! ;) ), I have currently resolved (AFAICT) all 
problems with dom4j/jaxen in Maven by using a development/branch version of 
dom4j (unfortunately with the current cvs problems on sourceforge it doesn't 
seem like this will be released too soon). The only issue I see here is the 
licensing problem pointed out by E.R. Harold: you shouldn't use any dom4j 
earlier than 1.5.2.

Cheers,
Lukas

> Upgrade dom4j and jaxen
> ---
>
>  Key: JELLY-226
>  URL: http://issues.apache.org/jira/browse/JELLY-226
>  Project: Jelly
> Type: Wish

>   Components: core / taglib.core, taglib.jsl, taglib.xml
> Reporter: Lukas Theussl

>
> I am struggling with upgrading dom4j and jaxen for our upcoming maven-1.1 
> release (see http://jira.codehaus.org/browse/MAVEN-1345 and 
> http://jira.codehaus.org/browse/JAXEN-67 for some chunks of discussion). Part 
> of the problem seems to be some kind of binary incompatibility in project 
> dependencies of jelly. I tried to rebuild jelly with the latest dom4j-1.6.1 
> and jaxen-1.1-beta-8 but failed due to several broken test cases, in 
> particular in the jsl tag library. It would be nice if we had a jelly release 
> with unified dependencies, even though I am not sure it will solve our 
> problem of dropped CDATA sections that I described in JAXEN-67.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

DO NOT REPLY [Bug 39538] - [collections] Support parametized classes with commons.collections.

2006-05-10 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=39538


[EMAIL PROTECTED] changed:

   What|Removed |Added

Summary|Support parametized classes |[collections] Support
   |with commons.collections.   |parametized classes with
   ||commons.collections.




-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

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

DO NOT REPLY [Bug 39537] - [dbcp] BasicDataSource.getConnection() Connections don't work as hashtable keys -- test case provided

2006-05-10 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=39537


[EMAIL PROTECTED] changed:

   What|Removed |Added

Summary|BasicDataSource.getConnectio|[dbcp]
   |n() Connections don't work  |BasicDataSource.getConnectio
   |as hashtable keys -- test   |n() Connections don't work
   |case provided   |as hashtable keys -- test
   ||case provided




-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

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

DO NOT REPLY [Bug 39543] - file size

2006-05-10 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=39543


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||INVALID




--- Additional Comments From [EMAIL PROTECTED]  2006-05-10 13:56 ---
This is a question for the commons-user@jakarta.apache.org mailing list, not
something that should go in Bugzilla.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

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

[jira] Commented: (JELLY-229) Add list of possible completions to jelly-tags-interaction

2006-05-10 Thread Lukas Theussl (JIRA) 
[ 
http://issues.apache.org/jira/browse/JELLY-229?page=comments#action_12378920 ] 

Lukas Theussl commented on JELLY-229:
-

Fantastic! Thanks so much for your quick response!

-Lukas

> Add list of possible completions to jelly-tags-interaction
> --
>
>  Key: JELLY-229
>  URL: http://issues.apache.org/jira/browse/JELLY-229
>  Project: Jelly
> Type: New Feature

>   Components: taglib.interaction
> Versions: 1.0
>  Environment: Linux FC3, jdk-14.2_10, Maven-1.1-beta-3-SNAPSHOT
> Reporter: Lukas Theussl
> Assignee: Paul Libbrecht
>  Fix For: 1.1
>  Attachments: JELLY-229.patch
>
> This is a follow-up of JELLY-175. I added a method setCompletor(list) 
> allowing to set a list of strings that is used by jline for tab completion. 
> Use it like: . The list of 
> tab-completion strings is added to the history list, ie new goals typed in 
> console mode will always be tab-completed afterwards.
> Please note that I have bumped the jline dependency to the latest 0.9.5. This 
> is not on ibiblio yet, I have created an upload request ( 
> http://jira.codehaus.org/browse/MAVENUPLOAD-883 ), if it is not found, you 
> will have to put the jline-0.9.5.jar into your local repo by hand.
> To test it: I have deployed a snapshot of the maven 1 console plugin:
> maven plugin:download 
> -Dmaven.repo.remote=http://www.ibiblio.org/maven,http://cvs.apache.org/repository/
>  -DgroupId=maven -DartifactId=maven-console-plugin -Dversion=1.2-SNAPSHOT
> The default value for the completor list is 
> "clean,java:compile,jar,test,xdoc,site,quit,help", but you can define your 
> own custom list using the maven.console.completor.goals property.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[EMAIL PROTECTED]: Project commons-jelly-tags-define-test (in module commons-jelly) failed

2006-05-10 Thread commons-jelly-tags-define development 
To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project commons-jelly-tags-define-test has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 9 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-jelly-tags-define-test :  Commons Jelly


Full details are available at:

http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-define-test/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Dependency on xml-xerces exists, no need to add for property 
maven.jar.xerces.
 -WARNING- Overriding Maven properties: 
[/usr/local/gump/public/workspace/commons-jelly/jelly-tags/define/build.properties]
 -DEBUG- (Gump generated) Maven Properties in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/define/build.properties
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/define/project.xml
 -DEBUG- Maven project properties in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/define/project.properties
 -INFO- Project Reports in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/define/target/test-reports



The following work was performed:
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-define-test/gump_work/build_commons-jelly_commons-jelly-tags-define-test.html
Work Name: build_commons-jelly_commons-jelly-tags-define-test (Type: Build)
Work ended in a state of : Failed
Elapsed: 15 secs
Command Line: maven --offline jar 
[Working Directory: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/define]
CLASSPATH: 
/opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-10052006.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-10052006.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-10052006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/dynabean/target/commons-jelly-tags-dynabean-10052006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-10052006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-10052006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-10052006.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-10052006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-10052006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-10052006.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/packages/jaxen-1.1-beta-4/jaxen-1.1-beta-4.jar
-
[junit] at junit.framework.TestResult.runProtected(TestResult.java:124)
[junit] at junit.framework.TestResult.run(TestResult.java:109)
[junit] at junit.framework.TestCase.run(TestCase.java:118)
[junit] at junit.framework.TestSuite.runTest(TestSuite.java:208)
[junit] at junit.framework.TestSuite.run(TestSuite.java:203)
[junit] at 
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:325)
[junit] at 
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:536)
[junit] May 10, 2006 6:36:57 AM 
org.apache.commons.jelly.expression.xpath.XPathExpression evaluate
[junit] SEVERE: Error constructing xpath
[junit] org.jaxen.XPathSyntaxException: Node-set expected
[junit] at org.jaxen.BaseXPath.(BaseXPath.java:131)
[junit] at org.jaxen.BaseXPath.(BaseXPath.java:156)
[junit] at org.jaxen.dom4j.Dom4jXPath.(Dom4jXPath.java:101)
[junit] at 
org.apache.commons.jelly.expression.xpath.XPathExpression.evaluate(XPathExpression.java:78)
[junit] at 
org.apache.commons.jelly.expression.ExpressionSupport.evaluateRecurse(ExpressionSupport.java:61)
[junit] at 
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:256)
[junit] at 
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
[junit] at 
org.apache.commons.jelly.tags.junit.CaseTag$1.runTest(CaseTag.java:59)
[junit] at junit.framework.TestCase.runBare(TestCase.java:127)
[junit] at junit.framework.TestResult$1.protect(TestResult.java:106)
[junit] at junit.framework.TestResult.runProtected(TestResult.java:124)
[junit] at junit.framework.

[EMAIL PROTECTED]: Project commons-jelly-tags-define-test (in module commons-jelly) failed

2006-05-10 Thread commons-jelly-tags-define development 
To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project commons-jelly-tags-define-test has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 9 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-jelly-tags-define-test :  Commons Jelly


Full details are available at:

http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-define-test/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Dependency on xml-xerces exists, no need to add for property 
maven.jar.xerces.
 -WARNING- Overriding Maven properties: 
[/usr/local/gump/public/workspace/commons-jelly/jelly-tags/define/build.properties]
 -DEBUG- (Gump generated) Maven Properties in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/define/build.properties
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/define/project.xml
 -DEBUG- Maven project properties in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/define/project.properties
 -INFO- Project Reports in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/define/target/test-reports



The following work was performed:
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-define-test/gump_work/build_commons-jelly_commons-jelly-tags-define-test.html
Work Name: build_commons-jelly_commons-jelly-tags-define-test (Type: Build)
Work ended in a state of : Failed
Elapsed: 15 secs
Command Line: maven --offline jar 
[Working Directory: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/define]
CLASSPATH: 
/opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-10052006.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-10052006.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-10052006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/dynabean/target/commons-jelly-tags-dynabean-10052006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-10052006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-10052006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-10052006.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-10052006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-10052006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-10052006.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/packages/jaxen-1.1-beta-4/jaxen-1.1-beta-4.jar
-
[junit] at junit.framework.TestResult.runProtected(TestResult.java:124)
[junit] at junit.framework.TestResult.run(TestResult.java:109)
[junit] at junit.framework.TestCase.run(TestCase.java:118)
[junit] at junit.framework.TestSuite.runTest(TestSuite.java:208)
[junit] at junit.framework.TestSuite.run(TestSuite.java:203)
[junit] at 
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:325)
[junit] at 
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:536)
[junit] May 10, 2006 6:36:57 AM 
org.apache.commons.jelly.expression.xpath.XPathExpression evaluate
[junit] SEVERE: Error constructing xpath
[junit] org.jaxen.XPathSyntaxException: Node-set expected
[junit] at org.jaxen.BaseXPath.(BaseXPath.java:131)
[junit] at org.jaxen.BaseXPath.(BaseXPath.java:156)
[junit] at org.jaxen.dom4j.Dom4jXPath.(Dom4jXPath.java:101)
[junit] at 
org.apache.commons.jelly.expression.xpath.XPathExpression.evaluate(XPathExpression.java:78)
[junit] at 
org.apache.commons.jelly.expression.ExpressionSupport.evaluateRecurse(ExpressionSupport.java:61)
[junit] at 
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:256)
[junit] at 
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
[junit] at 
org.apache.commons.jelly.tags.junit.CaseTag$1.runTest(CaseTag.java:59)
[junit] at junit.framework.TestCase.runBare(TestCase.java:127)
[junit] at junit.framework.TestResult$1.protect(TestResult.java:106)
[junit] at junit.framework.TestResult.runProtected(TestResult.java:124)
[junit] at junit.framework.

[EMAIL PROTECTED]: Project commons-jelly-tags-jsl-test (in module commons-jelly) failed

2006-05-10 Thread commons-jelly-tags-jsl development 
To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project commons-jelly-tags-jsl-test has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 9 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-jelly-tags-jsl-test :  Commons Jelly


Full details are available at:

http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jsl-test/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Dependency on ant exists, no need to add for property 
maven.jar.ant-optional.
 -DEBUG- Dependency on xml-xerces exists, no need to add for property 
maven.jar.xerces.
 -DEBUG- (Gump generated) Maven Properties in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/build.properties
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/project.xml
 -DEBUG- Maven project properties in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/project.properties
 -INFO- Project Reports in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/target/test-reports



The following work was performed:
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jsl-test/gump_work/build_commons-jelly_commons-jelly-tags-jsl-test.html
Work Name: build_commons-jelly_commons-jelly-tags-jsl-test (Type: Build)
Work ended in a state of : Failed
Elapsed: 17 secs
Command Line: maven --offline jar 
[Working Directory: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl]
CLASSPATH: 
/opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-10052006.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-10052006.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-10052006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/ant/target/commons-jelly-tags-ant-10052006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-10052006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-10052006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-10052006.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-10052006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-10052006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-10052006.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/packages/jaxen-1.1-beta-4/jaxen-1.1-beta-4.jar
-
[junit] at 
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:262)
[junit] at 
org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:186)
[junit] at 
org.apache.commons.jelly.TagSupport.getBodyText(TagSupport.java:234)
[junit] at 
org.apache.commons.jelly.tags.core.SetTag.doTag(SetTag.java:90)
[junit] at 
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:262)
[junit] at 
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
[junit] at 
org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:186)
[junit] at 
org.apache.commons.jelly.tags.jsl.TemplateTag$1.run(TemplateTag.java:160)
[junit] at org.dom4j.rule.Mode.fireRule(Mode.java:59)
[junit] at org.dom4j.rule.Mode.applyTemplates(Mode.java:80)
[junit] at org.dom4j.rule.RuleManager$1.run(RuleManager.java:171)
[junit] at org.dom4j.rule.Mode.fireRule(Mode.java:59)
[junit] at org.dom4j.rule.Stylesheet.run(Stylesheet.java:102)
[junit] at org.dom4j.rule.Stylesheet.run(Stylesheet.java:91)
[junit] at org.dom4j.rule.Stylesheet.run(Stylesheet.java:78)
[junit] at org.dom4j.rule.Stylesheet.run(Stylesheet.java:71)
[junit] at 
org.apache.commons.jelly.tags.jsl.StylesheetTag.doTag(StylesheetTag.ja

[EMAIL PROTECTED]: Project commons-jelly-tags-jsl-test (in module commons-jelly) failed

2006-05-10 Thread commons-jelly-tags-jsl development 
To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project commons-jelly-tags-jsl-test has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 9 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-jelly-tags-jsl-test :  Commons Jelly


Full details are available at:

http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jsl-test/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Dependency on ant exists, no need to add for property 
maven.jar.ant-optional.
 -DEBUG- Dependency on xml-xerces exists, no need to add for property 
maven.jar.xerces.
 -DEBUG- (Gump generated) Maven Properties in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/build.properties
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/project.xml
 -DEBUG- Maven project properties in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/project.properties
 -INFO- Project Reports in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/target/test-reports



The following work was performed:
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jsl-test/gump_work/build_commons-jelly_commons-jelly-tags-jsl-test.html
Work Name: build_commons-jelly_commons-jelly-tags-jsl-test (Type: Build)
Work ended in a state of : Failed
Elapsed: 17 secs
Command Line: maven --offline jar 
[Working Directory: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl]
CLASSPATH: 
/opt/jdk1.5/lib/tools.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/cli/target/commons-cli-10052006.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-10052006.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-10052006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/ant/target/commons-jelly-tags-ant-10052006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-10052006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-10052006.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-10052006.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-10052006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-10052006.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/target/commons-logging-api-10052006.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/packages/jaxen-1.1-beta-4/jaxen-1.1-beta-4.jar
-
[junit] at 
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:262)
[junit] at 
org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:186)
[junit] at 
org.apache.commons.jelly.TagSupport.getBodyText(TagSupport.java:234)
[junit] at 
org.apache.commons.jelly.tags.core.SetTag.doTag(SetTag.java:90)
[junit] at 
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:262)
[junit] at 
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
[junit] at 
org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:186)
[junit] at 
org.apache.commons.jelly.tags.jsl.TemplateTag$1.run(TemplateTag.java:160)
[junit] at org.dom4j.rule.Mode.fireRule(Mode.java:59)
[junit] at org.dom4j.rule.Mode.applyTemplates(Mode.java:80)
[junit] at org.dom4j.rule.RuleManager$1.run(RuleManager.java:171)
[junit] at org.dom4j.rule.Mode.fireRule(Mode.java:59)
[junit] at org.dom4j.rule.Stylesheet.run(Stylesheet.java:102)
[junit] at org.dom4j.rule.Stylesheet.run(Stylesheet.java:91)
[junit] at org.dom4j.rule.Stylesheet.run(Stylesheet.java:78)
[junit] at org.dom4j.rule.Stylesheet.run(Stylesheet.java:71)
[junit] at 
org.apache.commons.jelly.tags.jsl.StylesheetTag.doTag(StylesheetTag.ja

DO NOT REPLY [Bug 39543] New: - file size

2006-05-10 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=39543

   Summary: file size
   Product: Commons
   Version: 1.1.0
  Platform: Other
OS/Version: Windows 2000
Status: NEW
  Severity: major
  Priority: P2
 Component: Net
AssignedTo: commons-dev@jakarta.apache.org
ReportedBy: [EMAIL PROTECTED]


I am using commons net package version 1.1.0 (which is pretty old, I know) to 
write data using FTP into a remote dataset residing on a MVS system. Now, my 
requirement is, I need to find out the size of the dataset before I write and 
if the dataset is full I need to throw a message in my program that the remote 
file I am trying to append is full and cannot further append data into it. 
I have had a look at commons-net-1.4.1 package, which has the new addition of 
MVSFTPParser class to the parser package. It would be helpful if you could let 
me know how to go about using it. Probably a sample code will be useful.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

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

svn commit: r405668 - /jakarta/commons/proper/jelly/trunk/jelly-tags/interaction/src/test/org/apache/commons/jelly/tags/interaction/sample.jelly

2006-05-10 Thread polx 
Author: polx
Date: Wed May 10 00:52:22 2006
New Revision: 405668

URL: http://svn.apache.org/viewcvs?rev=405668&view=rev
Log:
Added "born before the 20th century" into the question...
(really non serious change)
paul

Modified:

jakarta/commons/proper/jelly/trunk/jelly-tags/interaction/src/test/org/apache/commons/jelly/tags/interaction/sample.jelly

Modified: 
jakarta/commons/proper/jelly/trunk/jelly-tags/interaction/src/test/org/apache/commons/jelly/tags/interaction/sample.jelly
URL: 
http://svn.apache.org/viewcvs/jakarta/commons/proper/jelly/trunk/jelly-tags/interaction/src/test/org/apache/commons/jelly/tags/interaction/sample.jelly?rev=405668&r1=405667&r2=405668&view=diff
==
--- 
jakarta/commons/proper/jelly/trunk/jelly-tags/interaction/src/test/org/apache/commons/jelly/tags/interaction/sample.jelly
 (original)
+++ 
jakarta/commons/proper/jelly/trunk/jelly-tags/interaction/src/test/org/apache/commons/jelly/tags/interaction/sample.jelly
 Wed May 10 00:52:22 2006
@@ -24,7 +24,7 @@
   ${x.add('Pascal')}${x.add('Einstein')}
 
 
-  
 Your answer was: ${answer}
   



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

Re: [jelly] taglibs lead distribution ?

2006-05-10 Thread Dion Gillard 

I'm happy to take over a few too.

On 5/10/06, Paul Libbrecht <[EMAIL PROTECTED]> wrote:



Hi,


I was fiddling with Jira jelly project administration because
interaction didn't have a component and realized that some components
have been assigned to dion... which is good.
I'd like it if we could distribute the lead of all components, also so
that James Strachan is not anymore the default assignee!!

I'd be willing to take over xml and swing tag-libs... maybe some others.
Would anyone wish those ? Would anyone be ready to take over others ?
Some taglibs are not in urgent need but some really have a need and this
way we could react better to requests which keep coming as jelly, even
though it tastes unfinished, still has a good attraction, I feel.

paul

-
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

Re: [logging] JCL 1.1 FC available for final checks

2006-05-10 Thread Simon Kitching 
On Tue, 2006-05-09 at 17:44 -0700, Wendy Smoak wrote:
> On 5/9/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> 
> > The Log4jFactory class appears to be missing.
> 
> Never mind, it's in the release notes.  Sorry, I expected 1.1 to be a
> drop-in replacement and was surprised by the error.
> 
> I don't recall any deprecation warnings, though.  I've had this in
> commons-logging.properties for as long as I can remember:
>
> org.apache.commons.logging.LogFactory=org.apache.commons.logging.impl.Log4jFactory
> 
> Off to read the documentation for 1.0.4 to see what I missed. :)

The deprecation info is indeed in the release notes, starting with the
1.0.3 release (April 2003). Three years seems a reasonable phase-out
period.

Regards,

Simon


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

[jelly] taglibs lead distribution ?

2006-05-10 Thread Paul Libbrecht 


Hi,


I was fiddling with Jira jelly project administration because 
interaction didn't have a component and realized that some components 
have been assigned to dion... which is good.
I'd like it if we could distribute the lead of all components, also so 
that James Strachan is not anymore the default assignee!!


I'd be willing to take over xml and swing tag-libs... maybe some others.
Would anyone wish those ? Would anyone be ready to take over others ?
Some taglibs are not in urgent need but some really have a need and this 
way we could react better to requests which keep coming as jelly, even 
though it tastes unfinished, still has a good attraction, I feel.


paul

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

[jira] Commented: (JELLY-226) Upgrade dom4j and jaxen

2006-05-10 Thread Paul Libbrecht (JIRA) 
[ 
http://issues.apache.org/jira/browse/JELLY-226?page=comments#action_12378851 ] 

Paul Libbrecht commented on JELLY-226:
--

The current dependency is jaxen 1.1-beta8 and dom4j 1.5.
Is that sufficient for you ?
Do you need 1.5.2 or 1.6 ?
paul

> Upgrade dom4j and jaxen
> ---
>
>  Key: JELLY-226
>  URL: http://issues.apache.org/jira/browse/JELLY-226
>  Project: Jelly
> Type: Wish

>   Components: core / taglib.core, taglib.jsl, taglib.xml
> Reporter: Lukas Theussl

>
> I am struggling with upgrading dom4j and jaxen for our upcoming maven-1.1 
> release (see http://jira.codehaus.org/browse/MAVEN-1345 and 
> http://jira.codehaus.org/browse/JAXEN-67 for some chunks of discussion). Part 
> of the problem seems to be some kind of binary incompatibility in project 
> dependencies of jelly. I tried to rebuild jelly with the latest dom4j-1.6.1 
> and jaxen-1.1-beta-8 but failed due to several broken test cases, in 
> particular in the jsl tag library. It would be nice if we had a jelly release 
> with unified dependencies, even though I am not sure it will solve our 
> problem of dropped CDATA sections that I described in JAXEN-67.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[validator] [patch-38133 Enhancement] commiter help needed

2006-05-10 Thread taabpr 

Hi all,
I've submited some time ago an enhancement patch for validator - 
'Enhance form to handle nested forms (beans)' with patch, test, etc. Is 
any commiter willing to have a look? (this feature is very often 
requested by Struts users). See 
http://issues.apache.org/bugzilla/show_bug.cgi?id=38133

Thanks a lot,
   Tom

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

[jira] Commented: (JELLY-229) Add list of possible completions to jelly-tags-interaction

2006-05-10 Thread Paul Libbrecht (JIRA) 
[ 
http://issues.apache.org/jira/browse/JELLY-229?page=comments#action_12378850 ] 

Paul Libbrecht commented on JELLY-229:
--

I changed the question to "born before the 20th century" ;-).

For release to happen is just to get a vote on commons-dev which I opened 
yesterday and expect to close on Friday 12:00 GMT.
Is that ok for you ?
paul

> Add list of possible completions to jelly-tags-interaction
> --
>
>  Key: JELLY-229
>  URL: http://issues.apache.org/jira/browse/JELLY-229
>  Project: Jelly
> Type: New Feature

>   Components: taglib.interaction
> Versions: 1.0
>  Environment: Linux FC3, jdk-14.2_10, Maven-1.1-beta-3-SNAPSHOT
> Reporter: Lukas Theussl
> Assignee: Paul Libbrecht
>  Fix For: 1.1
>  Attachments: JELLY-229.patch
>
> This is a follow-up of JELLY-175. I added a method setCompletor(list) 
> allowing to set a list of strings that is used by jline for tab completion. 
> Use it like: . The list of 
> tab-completion strings is added to the history list, ie new goals typed in 
> console mode will always be tab-completed afterwards.
> Please note that I have bumped the jline dependency to the latest 0.9.5. This 
> is not on ibiblio yet, I have created an upload request ( 
> http://jira.codehaus.org/browse/MAVENUPLOAD-883 ), if it is not found, you 
> will have to put the jline-0.9.5.jar into your local repo by hand.
> To test it: I have deployed a snapshot of the maven 1 console plugin:
> maven plugin:download 
> -Dmaven.repo.remote=http://www.ibiblio.org/maven,http://cvs.apache.org/repository/
>  -DgroupId=maven -DartifactId=maven-console-plugin -Dversion=1.2-SNAPSHOT
> The default value for the completor list is 
> "clean,java:compile,jar,test,xdoc,site,quit,help", but you can define your 
> own custom list using the maven.console.completor.goals property.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[jira] Updated: (JELLY-229) Add list of possible completions to jelly-tags-interaction

2006-05-10 Thread Paul Libbrecht (JIRA) 
 [ http://issues.apache.org/jira/browse/JELLY-229?page=all ]

Paul Libbrecht updated JELLY-229:
-

  Component: taglib.interaction
Fix Version: 1.1
 (was: 1.1-beta-1)
Version: 1.0

Fixed components and versions.

> Add list of possible completions to jelly-tags-interaction
> --
>
>  Key: JELLY-229
>  URL: http://issues.apache.org/jira/browse/JELLY-229
>  Project: Jelly
> Type: New Feature

>   Components: taglib.interaction
> Versions: 1.0
>  Environment: Linux FC3, jdk-14.2_10, Maven-1.1-beta-3-SNAPSHOT
> Reporter: Lukas Theussl
> Assignee: Paul Libbrecht
>  Fix For: 1.1
>  Attachments: JELLY-229.patch
>
> This is a follow-up of JELLY-175. I added a method setCompletor(list) 
> allowing to set a list of strings that is used by jline for tab completion. 
> Use it like: . The list of 
> tab-completion strings is added to the history list, ie new goals typed in 
> console mode will always be tab-completed afterwards.
> Please note that I have bumped the jline dependency to the latest 0.9.5. This 
> is not on ibiblio yet, I have created an upload request ( 
> http://jira.codehaus.org/browse/MAVENUPLOAD-883 ), if it is not found, you 
> will have to put the jline-0.9.5.jar into your local repo by hand.
> To test it: I have deployed a snapshot of the maven 1 console plugin:
> maven plugin:download 
> -Dmaven.repo.remote=http://www.ibiblio.org/maven,http://cvs.apache.org/repository/
>  -DgroupId=maven -DartifactId=maven-console-plugin -Dversion=1.2-SNAPSHOT
> The default value for the completor list is 
> "clean,java:compile,jar,test,xdoc,site,quit,help", but you can define your 
> own custom list using the maven.console.completor.goals property.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[jira] Resolved: (JELLY-175) patch for jelly-tags-interaction

2006-05-10 Thread Paul Libbrecht (JIRA) 
 [ http://issues.apache.org/jira/browse/JELLY-175?page=all ]
 
Paul Libbrecht resolved JELLY-175:
--

Resolution: Fixed

This in the current version about to be released (I think).
paul

> patch for jelly-tags-interaction
> 
>
>  Key: JELLY-175
>  URL: http://issues.apache.org/jira/browse/JELLY-175
>  Project: Jelly
> Type: Improvement

>   Components: taglib.interaction
> Versions: 1.0
>  Environment: I've tested this in windows with and without cygwin.
> Reporter: Ryan Christanson
> Assignee: Paul Libbrecht
> Priority: Minor
>  Fix For: 1.1
>  Attachments: interaction.patch, patch.txt
>
> I've attached a patch to the commons-jelly-tags-interaction jar. This
> patch makes it so the interaction task will try to use jline:
> http://jline.sourceforge.net/
> Jline makes it so a java console will have tab completion, and
> history, and other goodies.
> This is great, because the maven-console plugin uses the
> commons-jelly-tags-interaction jar. So if you update the
> commons-jelly-tags-interaction jar, and then tell the maven console
> plugin to use the new jar, then your maven console will have history,
> and tab completion.
> I've set it up to remember all of the commands typed in any console,
> further it uses that history as the tab completion source - so you can
> tab complete past commands.
> I've tested this in windows and it works great, but in windows with
> cygwin, it doesn't do the fancy completion, but still works.
> By the way, in windows, jline's lib doesn't support arrows for
> history, so use CONTROL+P and CONTROL+N.
> Its possible that there might be a better way to integrate jline into
> this lib, i've just done what looked like the quickest way to get it
> working so my maven console would have history and tab completion.
> Maybe this feature could be enabled with a tag attribute?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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

[jira] Updated: (JELLY-175) patch for jelly-tags-interaction

2006-05-10 Thread Paul Libbrecht (JIRA) 
 [ http://issues.apache.org/jira/browse/JELLY-175?page=all ]

Paul Libbrecht updated JELLY-175:
-

  Component: taglib.interaction
Fix Version: 1.1
Version: 1.0
  Assign To: Paul Libbrecht

Fixed versions component.

> patch for jelly-tags-interaction
> 
>
>  Key: JELLY-175
>  URL: http://issues.apache.org/jira/browse/JELLY-175
>  Project: Jelly
> Type: Improvement

>   Components: taglib.interaction
> Versions: 1.0
>  Environment: I've tested this in windows with and without cygwin.
> Reporter: Ryan Christanson
> Assignee: Paul Libbrecht
> Priority: Minor
>  Fix For: 1.1
>  Attachments: interaction.patch, patch.txt
>
> I've attached a patch to the commons-jelly-tags-interaction jar. This
> patch makes it so the interaction task will try to use jline:
> http://jline.sourceforge.net/
> Jline makes it so a java console will have tab completion, and
> history, and other goodies.
> This is great, because the maven-console plugin uses the
> commons-jelly-tags-interaction jar. So if you update the
> commons-jelly-tags-interaction jar, and then tell the maven console
> plugin to use the new jar, then your maven console will have history,
> and tab completion.
> I've set it up to remember all of the commands typed in any console,
> further it uses that history as the tab completion source - so you can
> tab complete past commands.
> I've tested this in windows and it works great, but in windows with
> cygwin, it doesn't do the fancy completion, but still works.
> By the way, in windows, jline's lib doesn't support arrows for
> history, so use CONTROL+P and CONTROL+N.
> Its possible that there might be a better way to integrate jline into
> this lib, i've just done what looked like the quickest way to get it
> working so my maven console would have history and tab completion.
> Maybe this feature could be enabled with a tag attribute?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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