DO NOT REPLY [Bug 25229] - [dbutils] Patch for extending BasicRowProcessor

2005-12-21 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=25229.
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=25229


[EMAIL PROTECTED] changed:

   What|Removed |Added

Summary|[DbUtils] Patch for |[dbutils] Patch for
   |extending BasicRowProcessor |extending BasicRowProcessor




-- 
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 29393] - [dbutils] Protected QueryRunner.close() methods

2005-12-21 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=29393.
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=29393


[EMAIL PROTECTED] changed:

   What|Removed |Added

Summary|Protected   |[dbutils] Protected
   |QueryRunner.close() methods |QueryRunner.close() methods




-- 
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 29212] - [dbutils] Allow user to provide type information for input parameters

2005-12-21 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=29212.
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=29212


[EMAIL PROTECTED] changed:

   What|Removed |Added

Summary|Allow user to provide type  |[dbutils] Allow user to
   |information for input   |provide type information for
   |parameters  |input parameters




-- 
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 28216] - [dbutils] Adding logging to quiet methods in class DbUtils

2005-12-21 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=28216.
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=28216


[EMAIL PROTECTED] changed:

   What|Removed |Added

Summary|Adding logging to quiet |[dbutils] Adding logging to
   |methods in class DbUtils.   |quiet methods in class
   ||DbUtils




-- 
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 27993] - [dbutils] Modify BasicRowProcessor to use the column label

2005-12-21 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=27993.
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=27993


[EMAIL PROTECTED] changed:

   What|Removed |Added

Summary|Modify BasicRowProcessor to |[dbutils] Modify
   |use the column label|BasicRowProcessor to use the
   ||column label




-- 
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: r358268 - /jakarta/commons/proper/dbutils/trunk/xdocs/changes.xml

2005-12-21 Thread ebourg
Author: ebourg
Date: Wed Dec 21 03:20:29 2005
New Revision: 358268

URL: http://svn.apache.org/viewcvs?rev=358268view=rev
Log:
Moved the bug ids into the 'issue' attribute of the 'action' element.

Modified:
jakarta/commons/proper/dbutils/trunk/xdocs/changes.xml

Modified: jakarta/commons/proper/dbutils/trunk/xdocs/changes.xml
URL: 
http://svn.apache.org/viewcvs/jakarta/commons/proper/dbutils/trunk/xdocs/changes.xml?rev=358268r1=358267r2=358268view=diff
==
--- jakarta/commons/proper/dbutils/trunk/xdocs/changes.xml (original)
+++ jakarta/commons/proper/dbutils/trunk/xdocs/changes.xml Wed Dec 21 03:20:29 
2005
@@ -39,23 +39,23 @@
   body
 
 release version=1.1-dev date=in CVS
-  action dev=dgraham type=add
+  action dev=dgraham type=add issue=32120
 Added protected ResultSetIterator.rethrow() method to wrap 
SQLExceptions in 
-RuntimeExceptions.  PR: 32120
+RuntimeExceptions.
   /action
-  action dev=dgraham type=update
-Added SQLState and error code to rethrown SQLExceptions.  PR: 33614
+  action dev=dgraham type=update issue=33614
+Added SQLState and error code to rethrown SQLExceptions.
   /action
-  action dev=dgraham type=add
-Added KeyedHandler to create a Map of Maps from a ResultSet. PR: 31446
+  action dev=dgraham type=add issue=31446
+Added KeyedHandler to create a Map of Maps from a ResultSet.
   /action
-  action dev=dgraham type=update
+  action dev=dgraham type=update issue=31169
 Use current class' ClassLoader instead of QueryLoader's ClassLoader
-in loadQueries().  PR: 31169
+in loadQueries().
   /action
-  action dev=dgraham type=update
+  action dev=dgraham type=update issue=31460
 Made QueryLoader.loadQueries() protected so subclasses can use query
-repositories other than properties files.  PR: 31460
+repositories other than properties files.
   /action
   action dev=dgraham type=update
 QueryRunner now calls getDataSource() internally any time it needs 
access
@@ -64,39 +64,34 @@
   action dev=dgraham type=add
 Added DbUtils.rollbackAndClose() and DbUtils.rollbackAndCloseQuietly().
   /action
-  action dev=dgraham type=update
+  action dev=dgraham type=update issue=30749
 Call ResultSet.getTimestamp() in BeanProcessor.processColumn() if 
 the bean property is a java.sql.Timestamp.  Oracle's getObject() 
 implementation returns its own incompatible Timestamp class.
-PR: 30749
   /action
-  action dev=dgraham type=update
+  action dev=dgraham type=update issue=29212
 Changed QueryRunner.fillStatement() null handling 
 to use Types.VARCHAR instead of Types.OTHER.  This works for the 
 following tested drivers: Firebird 1.5/firebirdsql 1.5RC3,
 Oracle 9/ Thin driver, MySQL 4.0/Msql Connecttor 3.0 and mm.mysql 
 2.0.4 MaxDB 7.5, HSQLDB 1.7.1, and MS Access/ODBC Bridge.
-PR# 29212
   /action
-  action dev=dgraham type=add
+  action dev=dgraham type=add issue=30032
 Added a protected QueryRunner.prepareConnection() method to
 allow subclasses to customize the Connections retrieved from
 the DataSource before they're used.
-PR# 30032
   /action
   action dev=dgraham type=add
 Refactored bean handling from BasicRowProcessor into new 
 BeanProcessor class.  This also fixes the common problem with
 Oracle NUMERIC fields not being set into bean properties.
   /action
-  action dev=dgraham type=add
+  action dev=dgraham type=add issue=27530
 Added QueryRunner.batch() methods for batch updates.
-PR# 27530
   /action
-  action dev=dgraham type=add
+  action dev=dgraham type=add issue=27377
 Added new ResultSetHandler implementation, ColumnListHandler, that 
-converts one ResultSet column into a List of Objects. 
-PR# 27377
+converts one ResultSet column into a List of Objects.
   /action
 /release
 



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



DO NOT REPLY [Bug 37987] New: - proposition for controlled copy of bean properties

2005-12-21 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=37987.
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=37987

   Summary: proposition for controlled copy of bean properties
   Product: Commons
   Version: unspecified
  Platform: Other
OS/Version: All
Status: NEW
  Severity: enhancement
  Priority: P2
 Component: Bean Utilities
AssignedTo: commons-dev@jakarta.apache.org
ReportedBy: [EMAIL PROTECTED]


IN SHORT

This request is about adding to the BeanUtils class a new method:
copyProperties(Object target, Object src, Class editable)

... that copies 'src' to 'target' as if they were declared as instances 
of 'editable'. See sections below for more details.

This request is to some extent related to the enhancement 32642.

PROBLEM DESCRIPTION

Today Commons BeanUtils offers the possibility to copy properties between
2 java beans:

static void copyProperties(Object dest, Object orig)
 
As the instrospection does not 
care about how the target variable was declared, calling such a method will
copy more properties that one wants.

To illustrate this point, let's consider the following types:

interface EditablePriceableItem {
public int getPrice();
public void setPrice(int val);
}


class PurchaseItem implements EditablePriceableItem {
//... attributes
public String getPurchaseNr() { ... }
public void setPurchaseNr(String nr) { ... }
public int getPrice() { ... } ;
public void setPrice(int val) { ... };
}

class Project implements EditablePriceableItem {
//... attributes
public String getDescription() { ... }
public void setDescription(String desc) { ... }
public int getPrice() { ... } ;
public void setPrice(int val) { ... };
}

Somewhere in a class, we have:

EditablePriceableItem priceableSrc;
EditablePriceableItem priceableTarget;

//(1)
// ...
// priceableSrc is set by some method
// ...
//
//(2)
// priceableTarget gets instanciated
// ...

//(3)
//Now I want to copy Priceable properties (and only priceable 
properties !)
//from priceableSrc to priceableTarget
BeanUtils.copyProperties(priceableTarget,priceableSrc);

Although variables are declared as EditablePriceableItem, what gets copied in 
(3)
depends on the concrete type of priceableSrc and priceableTarget.

a) When priceableSrc and priceableTarget are instances of PurchaseItem,
price and purchaseNr are copied
b) When priceableSrc and priceableTarget are instances of Project,
price and description are copied
c) When priceableSrc is an instance of PurchaseItem and priceableTarget
is an instance of Project (or the opposite) only price gets copied

As a conclusion the behaviour in (3) is not uniform.


PROPOSITION
To control the scope of properties that are copied, it would be very useful
to have a method such as:

static void copyProperties(Object target, Object source, Class editableScope)

where editableScope is an interface or class that declares the properties.
Writing (3) as:

BeanUtils.copyProperties(priceableTarget,priceableSrc,
 EditablePriceableItem.class);

would provide a consistent behaviour.

-- 
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 37987] - [beanutils] Proposition for controlled copy of bean properties

2005-12-21 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=37987.
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=37987


[EMAIL PROTECTED] changed:

   What|Removed |Added

Summary|proposition for controlled|[beanutils] Proposition for
   |copy of bean properties |controlled copy of bean
   ||properties




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



[VFS] nightly broken - why?

2005-12-21 Thread Mario Ivankovits

Hi!

Is there a log-file where I can see why the VFS nightly is broken?
Or could one please have a look at it. As far as I know Craig is the 
nightly master, no?



Thanks!
---
Mario


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



svn commit: r358269 - /jakarta/commons/proper/dbutils/trunk/project.xml

2005-12-21 Thread ebourg
Author: ebourg
Date: Wed Dec 21 03:27:34 2005
New Revision: 358269

URL: http://svn.apache.org/viewcvs?rev=358269view=rev
Log:
Added a dependency on the xdoc 1.9.2 plugin to make the site buildable with the 
latest commons-build

Modified:
jakarta/commons/proper/dbutils/trunk/project.xml

Modified: jakarta/commons/proper/dbutils/trunk/project.xml
URL: 
http://svn.apache.org/viewcvs/jakarta/commons/proper/dbutils/trunk/project.xml?rev=358269r1=358268r2=358269view=diff
==
--- jakarta/commons/proper/dbutils/trunk/project.xml (original)
+++ jakarta/commons/proper/dbutils/trunk/project.xml Wed Dec 21 03:27:34 2005
@@ -187,6 +187,14 @@
   version3.8.1/version
   urlhttp://www.junit.org//url
 /dependency
+
+dependency
+  groupIdmaven/groupId
+  artifactIdmaven-xdoc-plugin/artifactId
+  version1.9.2/version
+  urlhttp://maven.apache.org/reference/plugins/xdoc/url
+  typeplugin/type
+/dependency 
   /dependencies

   build



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



[Jakarta-commons Wiki] Update of CommonsCommitters/ReleasesInProgress by RobertBurrellDonkin

2005-12-21 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 RobertBurrellDonkin:
http://wiki.apache.org/jakarta-commons/CommonsCommitters/ReleasesInProgress

--
  
  == Current Release VOTEs ==
  
-  * FileUpload - Started 10th December 2005
+  * FileUpload RC2 - Started 21st December 2005
   * VFS - Revote started 5th December 2005
  
  

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



[Jakarta-commons Wiki] Update of CommonsCommitters/ReleasesInProgress by RobertBurrellDonkin

2005-12-21 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 RobertBurrellDonkin:
http://wiki.apache.org/jakarta-commons/CommonsCommitters/ReleasesInProgress

--
  == RobertBurrellDonkin ==
   
   * Check FileUploads
+  * Check VFS status
  
  
  

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



Re: [VOTE] Release Commons FileUpload 1.1

2005-12-21 Thread robert burrell donkin
hi martin

does fileupload required 1.4 JDK or higher?

(probably the minimum JDK is probably something we should start adding
to the release notes.)

- robert

On Mon, 2005-12-19 at 22:54 -0800, Martin Cooper wrote:
 While the vote on Release Candidate 1 passed, I have taken the time to clean
 up all of the minor issues reported against that candidate build, and to
 modify the jar manifest to adhere to recently discussed Commons conventions.
 
 This vote, therefore, is on whether or not the FileUpload 1.1-RC2 build is
 ready to become the official FileUpload 1.1 release.
 
 The distributions for FileUpload 1.1 Release Candidate 2 are available here:
 
 
 http://people.apache.org/~martinc/fileupload/v1.1-rc2/dist/http://people.apache.org/%7Emartinc/fileupload/v1.1-rc1/dist/
 
 and the updated web site is here:
 
 http://people.apache.org/~martinc/fileupload/v1.1-rc2/site/http://people.apache.org/%7Emartinc/fileupload/v1.1-rc1/site/
 
 -- --
 [ ] +1  Release Commons FileUpload 1.1-RC2 as Commons FileUpload 1.1
 [ ] +0  not too fussed, but OK
 [ ] -0  won't block, but think imperfect
 [ ] -1  not until xxx is fixed
 
 
 Here's my own +1.
 
 --
 Martin Cooper


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



svn commit: r358275 - /jakarta/commons/proper/commons-build/trunk/xdocs/releases/prepare.xml

2005-12-21 Thread rdonkin
Author: rdonkin
Date: Wed Dec 21 04:19:37 2005
New Revision: 358275

URL: http://svn.apache.org/viewcvs?rev=358275view=rev
Log:
Added recommendation about including minimum target JRE version in the release 
notes.

Modified:
jakarta/commons/proper/commons-build/trunk/xdocs/releases/prepare.xml

Modified: jakarta/commons/proper/commons-build/trunk/xdocs/releases/prepare.xml
URL: 
http://svn.apache.org/viewcvs/jakarta/commons/proper/commons-build/trunk/xdocs/releases/prepare.xml?rev=358275r1=358274r2=358275view=diff
==
--- jakarta/commons/proper/commons-build/trunk/xdocs/releases/prepare.xml 
(original)
+++ jakarta/commons/proper/commons-build/trunk/xdocs/releases/prepare.xml Wed 
Dec 21 04:19:37 2005
@@ -245,6 +245,9 @@
An introduction to the release may also be given, describing the 
component
and the release in general terms. 
/p
+p
+The release notes should contain the minimum target Java version for the 
component.
+/p
p
The release notes should be a plain text file. Take care to ensure
that the format allows easy reading on a wide variety of platforms.



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



DO NOT REPLY [Bug 37991] New: - Local filesystem provider returns 0 from URLConnection.getLastModified

2005-12-21 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=37991.
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=37991

   Summary: Local filesystem provider returns 0 from
URLConnection.getLastModified
   Product: Commons
   Version: Nightly Builds
  Platform: Macintosh
OS/Version: Mac OS X 10.4
Status: NEW
  Severity: major
  Priority: P2
 Component: VFS
AssignedTo: commons-dev@jakarta.apache.org
ReportedBy: [EMAIL PROTECTED]


You cannot get the last mod time of a file accessed via a URL that refers to a
VFS fileobject that is in the local filesystem. Mario indicated that the code
simply isn't there.

-- 
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: [feedparser] Going once, going twice...

2005-12-21 Thread Andrea Alberto
Hi,
I am willing to start contributing to some project at the
jakarta-commons and this could be a good possibility.
I have java experience but no experience as a developer on RSS (but I
think this is not a big problem).

Andrea

On 12/21/05, Phil Steitz [EMAIL PROTECTED] wrote:
 We need to make a decision on which way to go here...either demote
 back to sandbox/dormant or have someone step up to drive this
 component toward a release.

 I am happy to help getting the site fixed (seems we just need to add
 it to the nav, as http://jakarta.apache.org/commons/feedparser/ is
 there) and with build-related issues; but I have neither the time nor
 expertise to do much else.

 If we can get one knowledgeable and interested committer to step up
 and a few volunteers, we can resuscitate; otherwise we should think
 about moving it to dormant.

 Any volunteers?

 Phil

 -
 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 37987] - [beanutils] Proposition for controlled copy of bean properties

2005-12-21 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=37987.
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=37987





--- Additional Comments From [EMAIL PROTECTED]  2005-12-21 14:59 ---
I don't understand how this behavior is inconsistent.  Only the matching (same
name and type) properties can be copied.  So, case 3, IMO is fine the way it's
implemented.  A Project object doesn't have a purchaseNr property, so the
purchaseNr property can't be copied from the PurchaseItem object to the Project
object.  However, what I do think might be nice is if we had an additional
parameter to copyProperties() which specified exactly which properties to copy
(a collection/array of Strings which specified the property names).  This would
be a bit more flexible, because there could be instances where you can't use a
class/interface to specify which properties to copy (you don't want to copy the
id property for instance).  Would that work for you?  We could actually
provide both, I guess so that you wouldn't have to manually construct the
collection of property names by hand.

-- 
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 37987] - [beanutils] Proposition for controlled copy of bean properties

2005-12-21 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=37987.
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=37987





--- Additional Comments From [EMAIL PROTECTED]  2005-12-21 15:17 ---
(In reply to comment #1)
 I don't understand how this behavior is inconsistent.  Only the matching (same
 name and type) properties can be copied.  So, case 3, IMO is fine the way it's
 implemented.  A Project object doesn't have a purchaseNr property, so the
 purchaseNr property can't be copied from the PurchaseItem object to the 
Project
 object.  However, what I do think might be nice is if we had an additional
 parameter to copyProperties() which specified exactly which properties to copy
 (a collection/array of Strings which specified the property names).  This 
would
 be a bit more flexible, because there could be instances where you can't use a
 class/interface to specify which properties to copy (you don't want to copy 
the
 id property for instance).  Would that work for you?  We could actually
 provide both, I guess so that you wouldn't have to manually construct the
 collection of property names by hand.

For instance you get (EditablePriceableItem a, EditablePriceableItem b) as
parameters of a function. The only you know about it is that they are instances
 of EditablePriceableItem. Thus when copying a to b using introspections you 
don't want to alter properties that are outside of your scope: here the 
interface EditablePriceableItem.

A 3rd argument, as you propose (and as proposed in enhancement 32642), would do 
the job.
Neverthless, getting a list of property names from an interface that 
potentially extends several other interfaces is not trivial. It would then be 
very handy to have an helper method such as:

getReadableProperties(Class aclass): List/or array
getSettableProperties(Class aclass): List/or array



-- 
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][vote] APT tag library

2005-12-21 Thread robert burrell donkin
On Tue, 2005-12-20 at 09:25 -0700, Ryan Heaton wrote:
 That sounds great.  How do I get a jira account so I can add a component? 

to get a jira account just follow the sign up link

not sure whether additional karma is required to add a component

- robert


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



DO NOT REPLY [Bug 37987] - [beanutils] Proposition for controlled copy of bean properties

2005-12-21 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=37987.
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=37987





--- Additional Comments From [EMAIL PROTECTED]  2005-12-21 15:20 ---
So, how about we change this enhancement request to provide both methods:

public void copyProperties( Object src, Object dest, Class scope );
public void copyProperties( Object src, Object dest, Collection propertyNames );

-- 
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-test (in module commons-jelly) failed

2005-12-21 Thread commons-jelly 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-test has an issue affecting its community integration.
This issue affects 1 projects,
 and has been outstanding for 4 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-test :  Commons Jelly


Full details are available at:

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

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Dependency on jakarta-servletapi-5-servlet exists, no need to add for 
property maven.jar.servletapi.
 -DEBUG- Dependency on jakarta-taglibs-standard exists, no need to add for 
property maven.jar.jstl.
 -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/build.properties]
 -DEBUG- (Gump generated) Maven Properties in: 
/usr/local/gump/public/workspace/commons-jelly/build.properties
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: 
/usr/local/gump/public/workspace/commons-jelly/project.xml
 -DEBUG- Maven project properties in: 
/usr/local/gump/public/workspace/commons-jelly/project.properties
 -INFO- Project Reports in: 
/usr/local/gump/public/workspace/commons-jelly/target/test-reports



The following work was performed:
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-test/gump_work/build_commons-jelly_commons-jelly-test.html
Work Name: build_commons-jelly_commons-jelly-test (Type: Build)
Work ended in a state of : Failed
Elapsed: 2 mins 6 secs
Command Line: maven --offline jar 
[Working Directory: /usr/local/gump/public/workspace/commons-jelly]
CLASSPATH: 
/opt/jdk1.4/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-21122005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-21122005.jar:/usr/local/gump/public/workspace/jakarta-commons/discovery/dist/commons-discovery.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-21122005.jar:/usr/local/gump/public/workspace/jakarta-commons/lang/dist/commons-lang-21122005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-21122005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api-21122005.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/packages/forehead/forehead-1.0-beta-5.jar:/usr/local/gump/public/workspace/jakarta-servletapi-5/jsr154/dist/lib/servlet-api.jar:/usr/local/gump/public/workspace/jakarta-taglibs/dist/standard/lib/jstl.jar:/usr/local/gump/packages/jaxen-1.1-beta-6/jaxen-1.1-beta-6.jar:/usr/local/gump/public/workspace/dist/junit/junit.jar
-
[junit] Expected expression: ${singleSize*2}
[junit] Actual expression: ${doubleSize} File: 
file:/x1/gump/public/workspace/commons-jelly/target/test-classes/org/apache/commons/jelly/suite.jelly
 At tag test:assertEquals: line: 359 column: 75
[junit] org.apache.commons.jelly.JellyTagException: 
file:/x1/gump/public/workspace/commons-jelly/target/test-classes/org/apache/commons/jelly/suite.jelly:359:75:
 test:assertEquals  expected:[22] but was:[22]
[junit] Expected expression: ${singleSize*2}
[junit] Actual expression: ${doubleSize} File: 
file:/x1/gump/public/workspace/commons-jelly/target/test-classes/org/apache/commons/jelly/suite.jelly
 At tag test:assertEquals: line: 359 column: 75
[junit] at 
org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:712)
[junit] at 
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:282)
[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] Caused by: 
org.apache.commons.jelly.tags.junit.JellyAssertionFailedError:  expected:[22] 
but was:[22]
[junit] Expected expression: ${singleSize*2}
[junit] Actual expression: ${doubleSize} File: 
file:/x1/gump/public/workspace/commons-jelly/target/test-classes/org/apache/commons/jelly/suite.jelly
 At tag test:assertEquals: line: 359 column: 75
[junit] at 
org.apache.commons.jelly.tags.junit.AssertTagSupport.fail(AssertTagSupport.java:39)
[junit] at 
org.apache.commons.jelly.tags.junit.AssertTagSupport.failNotEquals(AssertTagSupport.java:62)
[junit] at 
org.apache.commons.jelly.tags.junit.AssertEqualsTag.doTag(AssertEqualsTag.java:55)
[junit]  

DO NOT REPLY [Bug 37987] - [beanutils] Proposition for controlled copy of bean properties

2005-12-21 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=37987.
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=37987





--- Additional Comments From [EMAIL PROTECTED]  2005-12-21 15:30 ---
(In reply to comment #3)

Parfait Monsieur! 100% agreed!
Let me know when I can test it: I have tough test cases for this feature.


-- 
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: [vfs][REVOTE] release version 1.0

2005-12-21 Thread robert burrell donkin
hi mario

On Mon, 2005-12-19 at 11:21 +0100, Mario Ivankovits wrote:
  Checked again, and it works now! So I am +1 for the release.

 No one else?
 
 
 Should I delay the release until all the discussion around how to 
 release and the maybe to come maven plugin has been settled?
 If so, I'll proceed with developing - else I'll release this week.

it looks like it'll be a while before the dust settles on how to do
better releases so i'd recommend another vote and not waiting. 

it's been very confused over the last few weeks plus folks have been
busy at javapolis and apachecon. i think that this vote has probably got
a bit lost (i certainly lost track). it's probably best just to use a
subject something like '[VOTE] release vfs version 1' since my filters
didn't recognise this as a vote thread and perhaps others haven't
either.

- robert


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



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

2005-12-21 Thread commons-jelly-tags-xml 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-xml-test has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 4 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-xml-test :  Commons Jelly


Full details are available at:

http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-xml-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/xml/build.properties]
 -DEBUG- (Gump generated) Maven Properties in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/build.properties
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/project.xml
 -DEBUG- Maven project properties in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/project.properties
 -INFO- Project Reports in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/test-reports



The following work was performed:
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-xml-test/gump_work/build_commons-jelly_commons-jelly-tags-xml-test.html
Work Name: build_commons-jelly_commons-jelly-tags-xml-test (Type: Build)
Work ended in a state of : Failed
Elapsed: 1 min 2 secs
Command Line: maven --offline jar 
[Working Directory: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml]
CLASSPATH: 
/opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-21122005.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-21122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-21122005.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-21122005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-21122005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api-21122005.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/packages/jaxen-1.1-beta-6/jaxen-1.1-beta-6.jar
-
[junit] at 
org.apache.commons.jelly.tags.junit.CaseTag$1.runTest(CaseTag.java:59)
[junit] 
[junit] 
[junit] Testcase: 
testSetSingleNodeAndAsString(org.apache.commons.jelly.tags.junit.CaseTag$1):
  Caused an ERROR
[junit] 
file:/x1/gump/public/workspace/commons-jelly/jelly-tags/xml/target/test-classes/org/apache/commons/jelly/tags/xml/suite.jelly:294:81:
 x:set You must define an attribute called 'select' for this tag.
[junit] org.apache.commons.jelly.MissingAttributeException: 
file:/x1/gump/public/workspace/commons-jelly/jelly-tags/xml/target/test-classes/org/apache/commons/jelly/tags/xml/suite.jelly:294:81:
 x:set You must define an attribute called 'select' for this tag.
[junit] at 
org.apache.commons.jelly.tags.xml.SetTag.doTag(SetTag.java:86)
[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: 
testSetStringLists(org.apache.commons.jelly.tags.junit.CaseTag$1):
Caused an ERROR
[junit] 
file:/x1/gump/public/workspace/commons-jelly/jelly-tags/xml/target/test-classes/org/apache/commons/jelly/tags/xml/suite.jelly:339:82:
 x:set You must define an attribute called 'select' for this tag.
[junit] org.apache.commons.jelly.MissingAttributeException: 
file:/x1/gump/public/workspace/commons-jelly/jelly-tags/xml/target/test-classes/org/apache/commons/jelly/tags/xml/suite.jelly:339:82:
 x:set You must define an attribute called 'select' for this tag.
[junit] at 
org.apache.commons.jelly.tags.xml.SetTag.doTag(SetTag.java:86)
[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: 
testEntities(org.apache.commons.jelly.tags.junit.CaseTag$1):  Caused an 
ERROR
[junit] 

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

2005-12-21 Thread commons-jelly-tags-xml 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-xml-test has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 4 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-xml-test :  Commons Jelly


Full details are available at:

http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-xml-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/xml/build.properties]
 -DEBUG- (Gump generated) Maven Properties in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/build.properties
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/project.xml
 -DEBUG- Maven project properties in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/project.properties
 -INFO- Project Reports in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/test-reports



The following work was performed:
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-xml-test/gump_work/build_commons-jelly_commons-jelly-tags-xml-test.html
Work Name: build_commons-jelly_commons-jelly-tags-xml-test (Type: Build)
Work ended in a state of : Failed
Elapsed: 1 min 2 secs
Command Line: maven --offline jar 
[Working Directory: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml]
CLASSPATH: 
/opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/jakarta-commons/beanutils/dist/commons-beanutils-core.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-21122005.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-21122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-21122005.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-21122005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-21122005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api-21122005.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/packages/jaxen-1.1-beta-6/jaxen-1.1-beta-6.jar
-
[junit] at 
org.apache.commons.jelly.tags.junit.CaseTag$1.runTest(CaseTag.java:59)
[junit] 
[junit] 
[junit] Testcase: 
testSetSingleNodeAndAsString(org.apache.commons.jelly.tags.junit.CaseTag$1):
  Caused an ERROR
[junit] 
file:/x1/gump/public/workspace/commons-jelly/jelly-tags/xml/target/test-classes/org/apache/commons/jelly/tags/xml/suite.jelly:294:81:
 x:set You must define an attribute called 'select' for this tag.
[junit] org.apache.commons.jelly.MissingAttributeException: 
file:/x1/gump/public/workspace/commons-jelly/jelly-tags/xml/target/test-classes/org/apache/commons/jelly/tags/xml/suite.jelly:294:81:
 x:set You must define an attribute called 'select' for this tag.
[junit] at 
org.apache.commons.jelly.tags.xml.SetTag.doTag(SetTag.java:86)
[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: 
testSetStringLists(org.apache.commons.jelly.tags.junit.CaseTag$1):
Caused an ERROR
[junit] 
file:/x1/gump/public/workspace/commons-jelly/jelly-tags/xml/target/test-classes/org/apache/commons/jelly/tags/xml/suite.jelly:339:82:
 x:set You must define an attribute called 'select' for this tag.
[junit] org.apache.commons.jelly.MissingAttributeException: 
file:/x1/gump/public/workspace/commons-jelly/jelly-tags/xml/target/test-classes/org/apache/commons/jelly/tags/xml/suite.jelly:339:82:
 x:set You must define an attribute called 'select' for this tag.
[junit] at 
org.apache.commons.jelly.tags.xml.SetTag.doTag(SetTag.java:86)
[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: 
testEntities(org.apache.commons.jelly.tags.junit.CaseTag$1):  Caused an 
ERROR
[junit] 

DO NOT REPLY [Bug 37991] - [vfs] Local filesystem provider returns 0 from URLConnection.getLastModified

2005-12-21 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=37991.
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=37991


[EMAIL PROTECTED] changed:

   What|Removed |Added

Summary|Local filesystem provider   |[vfs] Local filesystem
   |returns 0 from  |provider returns 0 from
   |URLConnection.getLastModifie|URLConnection.getLastModifie
   |d   |d




-- 
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-swing (in module commons-jelly) failed

2005-12-21 Thread JellySwing 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-swing has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 4 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-swing :  Commons Jelly


Full details are available at:

http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-swing/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-swing-21122005.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/swing/build.properties
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/swing/project.xml
 -DEBUG- Maven project properties in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/swing/project.properties
 -INFO- Project Reports in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/swing/target/test-reports
 -WARNING- No directory 
[/usr/local/gump/public/workspace/commons-jelly/jelly-tags/swing/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-swing/gump_work/build_commons-jelly_commons-jelly-tags-swing.html
Work Name: build_commons-jelly_commons-jelly-tags-swing (Type: Build)
Work ended in a state of : Failed
Elapsed: 9 secs
Command Line: maven --offline jar 
[Working Directory: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/swing]
CLASSPATH: 
/opt/jdk1.4/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-21122005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-21122005.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-21122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/define/target/commons-jelly-tags-define-21122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/interaction/target/commons-jelly-tags-interaction-21122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-21122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-21122005.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-21122005.jar:/usr/local/gump/public/workspace/jakarta-commons/lang/dist/commons-lang-21122005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-21122005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api-21122005.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/packages/jaxen-1.1-beta-6/jaxen-1.1-beta-6.jar
-
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at java.lang.Class.newInstance0(Class.java:308)
at java.lang.Class.newInstance(Class.java:261)
at 
org.apache.commons.jelly.JellyContext.getTagLibrary(JellyContext.java:432)
at 
org.apache.maven.jelly.MavenJellyContext.getTagLibrary(MavenJellyContext.java:171)
at 
org.apache.commons.jelly.parser.XMLParser.createTag(XMLParser.java:1033)
at 
org.apache.commons.jelly.parser.XMLParser.startElement(XMLParser.java:647)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown 
Source)
at 
org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown Source)
at 
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
at 
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
 Source)
at 
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown 
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown 

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

2005-12-21 Thread JellySwing 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-swing has an issue affecting its community 
integration.
This issue affects 1 projects,
 and has been outstanding for 4 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-swing :  Commons Jelly


Full details are available at:

http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-swing/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-swing-21122005.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/swing/build.properties
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/swing/project.xml
 -DEBUG- Maven project properties in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/swing/project.properties
 -INFO- Project Reports in: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/swing/target/test-reports
 -WARNING- No directory 
[/usr/local/gump/public/workspace/commons-jelly/jelly-tags/swing/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-swing/gump_work/build_commons-jelly_commons-jelly-tags-swing.html
Work Name: build_commons-jelly_commons-jelly-tags-swing (Type: Build)
Work ended in a state of : Failed
Elapsed: 9 secs
Command Line: maven --offline jar 
[Working Directory: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/swing]
CLASSPATH: 
/opt/jdk1.4/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-21122005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-21122005.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-21122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/define/target/commons-jelly-tags-define-21122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/interaction/target/commons-jelly-tags-interaction-21122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-21122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-21122005.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-21122005.jar:/usr/local/gump/public/workspace/jakarta-commons/lang/dist/commons-lang-21122005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-21122005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api-21122005.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/packages/jaxen-1.1-beta-6/jaxen-1.1-beta-6.jar
-
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at java.lang.Class.newInstance0(Class.java:308)
at java.lang.Class.newInstance(Class.java:261)
at 
org.apache.commons.jelly.JellyContext.getTagLibrary(JellyContext.java:432)
at 
org.apache.maven.jelly.MavenJellyContext.getTagLibrary(MavenJellyContext.java:171)
at 
org.apache.commons.jelly.parser.XMLParser.createTag(XMLParser.java:1033)
at 
org.apache.commons.jelly.parser.XMLParser.startElement(XMLParser.java:647)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown 
Source)
at 
org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown Source)
at 
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
at 
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
 Source)
at 
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown 
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown 

DO NOT REPLY [Bug 37994] New: - [httpclient] typo in API_CHANGES_3_0.txt

2005-12-21 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=37994.
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=37994

   Summary: [httpclient] typo in API_CHANGES_3_0.txt
   Product: Commons
   Version: 3.0 Final
  Platform: Other
OS/Version: other
Status: NEW
  Severity: trivial
  Priority: P2
 Component: Site
AssignedTo: commons-dev@jakarta.apache.org
ReportedBy: [EMAIL PROTECTED]


DigestSheme should be DigestScheme :)  Also, why is there not an httpclient
component in the list?

-- 
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-define-test (in module commons-jelly) failed

2005-12-21 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 4 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: 32 secs
Command Line: maven --offline jar 
[Working Directory: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/define]
CLASSPATH: 
/opt/jdk1.4/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-21122005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-21122005.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-21122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/dynabean/target/commons-jelly-tags-dynabean-21122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-21122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-21122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-21122005.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-21122005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-21122005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api-21122005.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/packages/jaxen-1.1-beta-6/jaxen-1.1-beta-6.jar
-
[junit] at 
org.jaxen.saxpath.base.XPathReader.unionExpr(XPathReader.java:1129)
[junit] at 
org.jaxen.saxpath.base.XPathReader.unaryExpr(XPathReader.java:1117)
[junit] at 
org.jaxen.saxpath.base.XPathReader.multiplicativeExpr(XPathReader.java:1039)
[junit] at 
org.jaxen.saxpath.base.XPathReader.additiveExpr(XPathReader.java:982)
[junit] at 
org.jaxen.saxpath.base.XPathReader.relationalExpr(XPathReader.java:902)
[junit] at 
org.jaxen.saxpath.base.XPathReader.equalityExpr(XPathReader.java:850)
[junit] at 
org.jaxen.saxpath.base.XPathReader.andExpr(XPathReader.java:826)
[junit] at 
org.jaxen.saxpath.base.XPathReader.orExpr(XPathReader.java:804)
[junit] at org.jaxen.saxpath.base.XPathReader.expr(XPathReader.java:797)
[junit] at 
org.jaxen.saxpath.base.XPathReader.parse(XPathReader.java:105)
[junit] at org.jaxen.BaseXPath.init(BaseXPath.java:126)
[junit] at org.jaxen.BaseXPath.init(BaseXPath.java:152)
[junit] at org.jaxen.dom4j.Dom4jXPath.init(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 

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

2005-12-21 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 4 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: 32 secs
Command Line: maven --offline jar 
[Working Directory: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/define]
CLASSPATH: 
/opt/jdk1.4/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-21122005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-21122005.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-21122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/dynabean/target/commons-jelly-tags-dynabean-21122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-21122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-21122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-21122005.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-21122005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-21122005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api-21122005.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/packages/jaxen-1.1-beta-6/jaxen-1.1-beta-6.jar
-
[junit] at 
org.jaxen.saxpath.base.XPathReader.unionExpr(XPathReader.java:1129)
[junit] at 
org.jaxen.saxpath.base.XPathReader.unaryExpr(XPathReader.java:1117)
[junit] at 
org.jaxen.saxpath.base.XPathReader.multiplicativeExpr(XPathReader.java:1039)
[junit] at 
org.jaxen.saxpath.base.XPathReader.additiveExpr(XPathReader.java:982)
[junit] at 
org.jaxen.saxpath.base.XPathReader.relationalExpr(XPathReader.java:902)
[junit] at 
org.jaxen.saxpath.base.XPathReader.equalityExpr(XPathReader.java:850)
[junit] at 
org.jaxen.saxpath.base.XPathReader.andExpr(XPathReader.java:826)
[junit] at 
org.jaxen.saxpath.base.XPathReader.orExpr(XPathReader.java:804)
[junit] at org.jaxen.saxpath.base.XPathReader.expr(XPathReader.java:797)
[junit] at 
org.jaxen.saxpath.base.XPathReader.parse(XPathReader.java:105)
[junit] at org.jaxen.BaseXPath.init(BaseXPath.java:126)
[junit] at org.jaxen.BaseXPath.init(BaseXPath.java:152)
[junit] at org.jaxen.dom4j.Dom4jXPath.init(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 

DO NOT REPLY [Bug 37994] - Typo in API_CHANGES_3_0.txt

2005-12-21 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=37994.
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=37994


[EMAIL PROTECTED] changed:

   What|Removed |Added

 AssignedTo|commons-|httpclient-
   |[EMAIL PROTECTED]  |[EMAIL PROTECTED]
  Component|Site|Commons HttpClient
Product|Commons |HttpClient
Summary|[httpclient] typo in|Typo in API_CHANGES_3_0.txt
   |API_CHANGES_3_0.txt |
   Target Milestone|--- |3.0.1




-- 
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-jsl-test (in module commons-jelly) failed

2005-12-21 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 4 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.
 -WARNING- Overriding Maven properties: 
[/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/build.properties]
 -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: 36 secs
Command Line: maven --offline jar 
[Working Directory: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl]
CLASSPATH: 
/opt/jdk1.4/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-21122005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-21122005.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-21122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/ant/target/commons-jelly-tags-ant-21122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-21122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-21122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-21122005.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-21122005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-21122005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api-21122005.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/packages/jaxen-1.1-beta-6/jaxen-1.1-beta-6.jar
-
[junit] at 
org.apache.commons.jelly.tags.xml.ExprTag.doTag(ExprTag.java:46)
[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:58)
[junit] at org.dom4j.rule.Mode.applyTemplates(Mode.java:79)
[junit] at org.dom4j.rule.RuleManager$1.run(RuleManager.java:171)
[junit] at org.dom4j.rule.Mode.fireRule(Mode.java:58)
[junit] at org.dom4j.rule.Stylesheet.run(Stylesheet.java:102)
[junit] at org.dom4j.rule.Stylesheet.run(Stylesheet.java:91)
[junit] at 

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

2005-12-21 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 4 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.
 -WARNING- Overriding Maven properties: 
[/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/build.properties]
 -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: 36 secs
Command Line: maven --offline jar 
[Working Directory: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl]
CLASSPATH: 
/opt/jdk1.4/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-21122005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-21122005.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-21122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/ant/target/commons-jelly-tags-ant-21122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-21122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-21122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-21122005.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-21122005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-21122005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api-21122005.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/packages/jaxen-1.1-beta-6/jaxen-1.1-beta-6.jar
-
[junit] at 
org.apache.commons.jelly.tags.xml.ExprTag.doTag(ExprTag.java:46)
[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:58)
[junit] at org.dom4j.rule.Mode.applyTemplates(Mode.java:79)
[junit] at org.dom4j.rule.RuleManager$1.run(RuleManager.java:171)
[junit] at org.dom4j.rule.Mode.fireRule(Mode.java:58)
[junit] at org.dom4j.rule.Stylesheet.run(Stylesheet.java:102)
[junit] at org.dom4j.rule.Stylesheet.run(Stylesheet.java:91)
[junit] at 

Re: DO NOT REPLY [Bug 37994] New: - [httpclient] typo in API_CHANGES_3_0.txt

2005-12-21 Thread Ortwin Glück



[EMAIL PROTECTED] wrote:

 Also, why is there not an httpclient
component in the list?



Time we move the website away from commons, folks!


-
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

2005-12-21 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 4 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-21122005.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: 30 secs
Command Line: maven --offline jar 
[Working Directory: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/html]
CLASSPATH: 
/opt/jdk1.4/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-21122005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-21122005.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-21122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/target/commons-jelly-tags-jsl-21122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-21122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-21122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-21122005.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-21122005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-21122005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api-21122005.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/packages/jaxen-1.1-beta-6/jaxen-1.1-beta-6.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:
 test:assert 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:
 test:assert 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:
 test:assert 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:
 test:assert You must define an attribute called 'test' for this tag.
[junit] at 

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

2005-12-21 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 4 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-21122005.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: 30 secs
Command Line: maven --offline jar 
[Working Directory: 
/usr/local/gump/public/workspace/commons-jelly/jelly-tags/html]
CLASSPATH: 
/opt/jdk1.4/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-21122005.jar:/usr/local/gump/public/workspace/jakarta-commons/collections/build/commons-collections-21122005.jar:/usr/local/gump/public/workspace/commons-jelly/target/commons-jelly-21122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/jsl/target/commons-jelly-tags-jsl-21122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/junit/target/commons-jelly-tags-junit-21122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/log/target/commons-jelly-tags-log-21122005.jar:/usr/local/gump/public/workspace/commons-jelly/jelly-tags/xml/target/commons-jelly-tags-xml-21122005.jar:/usr/local/gump/public/workspace/jakarta-commons/jexl/dist/commons-jexl-21122005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-21122005.jar:/usr/local/gump/public/workspace/jakarta-commons/logging/dist/commons-logging-api-21122005.jar:/usr/local/gump/public/workspace/dom4j/build/dom4j.jar:/usr/local/gump/packages/jaxen-1.1-beta-6/jaxen-1.1-beta-6.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:
 test:assert 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:
 test:assert 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:
 test:assert 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:
 test:assert You must define an attribute called 'test' for this tag.
[junit] at 

Re: [VOTE] Release Commons FileUpload 1.1

2005-12-21 Thread Martin Cooper
On 12/21/05, robert burrell donkin [EMAIL PROTECTED]
wrote:

 hi martin

 does fileupload required 1.4 JDK or higher?


From project.properties:

maven.compile.source=1.3
maven.compile.target=1.3

--
Martin Cooper


(probably the minimum JDK is probably something we should start adding
 to the release notes.)

 - robert

 On Mon, 2005-12-19 at 22:54 -0800, Martin Cooper wrote:
  While the vote on Release Candidate 1 passed, I have taken the time to
 clean
  up all of the minor issues reported against that candidate build, and to
  modify the jar manifest to adhere to recently discussed Commons
 conventions.
 
  This vote, therefore, is on whether or not the FileUpload 1.1-RC2 build
 is
  ready to become the official FileUpload 1.1 release.
 
  The distributions for FileUpload 1.1 Release Candidate 2 are available
 here:
 
 
  http://people.apache.org/~martinc/fileupload/v1.1-rc2/dist/
 http://people.apache.org/%7Emartinc/fileupload/v1.1-rc1/dist/
 
  and the updated web site is here:
 
  http://people.apache.org/~martinc/fileupload/v1.1-rc2/site/
 http://people.apache.org/%7Emartinc/fileupload/v1.1-rc1/site/
 
  -- --
  [ ] +1  Release Commons FileUpload 1.1-RC2 as Commons FileUpload 1.1
  [ ] +0  not too fussed, but OK
  [ ] -0  won't block, but think imperfect
  [ ] -1  not until xxx is fixed
  
 
  Here's my own +1.
 
  --
  Martin Cooper


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




RE: [CONFIGURATION] Conglomeration Properties file

2005-12-21 Thread Joel Trunick
I was making a very strong argument why, in fact, this functionality
(albeit trivial) should be part of commons-configuration.

J

-Original Message-
From: Emmanuel Bourg [mailto:[EMAIL PROTECTED] 
Sent: Monday, December 19, 2005 12:42 PM
To: Jakarta Commons Developers List
Subject: Re: [CONFIGURATION] Conglomeration Properties file

Joel Trunick wrote:
 How would someone specify that strategy from the xml specification of
 the search? Wouldn't it need to be part of commons-config?

You mean how to build such a configuration with the xml descriptor 
parsed by the ConfigurationFactory ? You can't, but using the 
ConfigurationFactory provided with Commons Configuration is not 
mandatory, it's just a convenient way to build a simple configuration 
from several sources.

Emmanuel Bourg

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



Re: [all] combo/ and docs/ directories

2005-12-21 Thread Rahul Akolkar
On 12/20/05, Craig McClanahan [EMAIL PROTECTED] wrote:
 On 12/20/05, Rahul Akolkar [EMAIL PROTECTED] wrote:
 
  I lack the background for a couple of directories under commons proper
  in SVN, but it will be nice to have that :-) These are not in the
  externals for trunks-proper either.
 
  * combo/


 The original theory here was that we could produce a commons-all.jar, and
 associated all Commons javadocs, for the complete set of proper Commons
 components.  The build script would let an individual developer pick which
 versions of all the point products he or she wanted, and in theory someone
 would update the checked-in version whenever there was a GA release of one
 of the packages.

 Alas, nobody really picked up on the idea, and the implementation (at least
 in Ant) is pretty messy.  I'd consider this thing to be dormant at the
 moment.

snip/

Thanks Craig, if no one adds to this thread in a few days, I'll call a
VOTE to move combo out of proper.

-Rahul



 Was this concept ever put in motion? (committer list shows Craig and Hen)
 
  * docs/
 
  Much of the stuff under docs/ is now contained in commons-build/. Does
  this serve any current purpose?


 Don't know about that one.

 Thanks!
  -Rahul


 Craig



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



Re: [VOTE] Release Commons FileUpload 1.1

2005-12-21 Thread robert burrell donkin
On Wed, 2005-12-21 at 09:09 -0800, Martin Cooper wrote:
 On 12/21/05, robert burrell donkin [EMAIL PROTECTED]
 wrote:
 
  hi martin
 
  does fileupload required 1.4 JDK or higher?
 
 
 From project.properties:
 
 maven.compile.source=1.3
 maven.compile.target=1.3

just checking since the MANIFEST says built with 1.4.2_07. (there can be
issues running 1.4 code on a 1.3 JVM unless the bootclasspath is set
right.)

- robert 


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



svn commit: r358339 - /jakarta/commons/proper/httpclient/trunk/API_CHANGES_3_0.txt

2005-12-21 Thread olegk
Author: olegk
Date: Wed Dec 21 10:41:38 2005
New Revision: 358339

URL: http://svn.apache.org/viewcvs?rev=358339view=rev
Log:
PR #37994 (Typo in API_CHANGES_3_0.txt)

Modified:
jakarta/commons/proper/httpclient/trunk/API_CHANGES_3_0.txt

Modified: jakarta/commons/proper/httpclient/trunk/API_CHANGES_3_0.txt
URL: 
http://svn.apache.org/viewcvs/jakarta/commons/proper/httpclient/trunk/API_CHANGES_3_0.txt?rev=358339r1=358338r2=358339view=diff
==
--- jakarta/commons/proper/httpclient/trunk/API_CHANGES_3_0.txt (original)
+++ jakarta/commons/proper/httpclient/trunk/API_CHANGES_3_0.txt Wed Dec 21 
10:41:38 2005
@@ -22,7 +22,7 @@
 
 * NTLM classes moved to org.apache.commons.httpclient.auth package amd made 
private
 
-* DigestSheme:
+* DigestScheme:
 the following public methods were removed, as they were only public for 
testing
 - authenticate(UsernamePasswordCredentials, Map)
 - createDigest(String, String, Map)



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



Re: [feedparser] Going once, going twice...

2005-12-21 Thread Martin van den Bemt

As I also said on the PMC list, I am not particularly interested in development 
on feedparser, though I am willing to apply patches (if they are complete with 
testcases).
Assuming dormant means you can still commit to it (else archive would have been 
a better name probably), we  can move it there and still apply patches if eg 
Andrea Alberto comes up with something. If feedparsers matures  we can always 
move it back (with an appropiate vote of course).

So willing to monitor feedparser stuff.

Mvgr,
Martin

Phil Steitz wrote:

We need to make a decision on which way to go here...either demote
back to sandbox/dormant or have someone step up to drive this
component toward a release.

I am happy to help getting the site fixed (seems we just need to add
it to the nav, as http://jakarta.apache.org/commons/feedparser/ is
there) and with build-related issues; but I have neither the time nor
expertise to do much else.

If we can get one knowledgeable and interested committer to step up
and a few volunteers, we can resuscitate; otherwise we should think
about moving it to dormant.

Any volunteers?

Phil

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



Re: [feedparser] Going once, going twice...

2005-12-21 Thread Rahul Akolkar
On 12/21/05, Andrea Alberto [EMAIL PROTECTED] wrote:
 Hi,
 I am willing to start contributing to some project at the
 jakarta-commons and this could be a good possibility.
 I have java experience but no experience as a developer on RSS (but I
 think this is not a big problem).

snip/

Thanks a lot for your interest in Commons :-) If you want to start
contributing to feedparser, please do so via mailing list discussions
and/or contributing fixes and enhancements as you deem fit. But I
wouldn't want you to invest in feedparser *only* because of Phil's
email, since I would expect someone who takes on this task to be:

 * Capable of being the release manager for feedparser 1.0 (which
means the individual probably needs to be an existing Commons
committer willing to invest time in feedparser with immediate effect).

 * Preferably, a domain expert, i.e. someone who can, without much
effort, make judgements about the correctness and improvements needed
to the codebase (not from a Java syntactic perspective, rather a
feedparser semantic perspective).

-Rahul


Andrea

 On 12/21/05, Phil Steitz [EMAIL PROTECTED] wrote:
  We need to make a decision on which way to go here...either demote
  back to sandbox/dormant or have someone step up to drive this
  component toward a release.
 
  I am happy to help getting the site fixed (seems we just need to add
  it to the nav, as http://jakarta.apache.org/commons/feedparser/ is
  there) and with build-related issues; but I have neither the time nor
  expertise to do much else.
 
  If we can get one knowledgeable and interested committer to step up
  and a few volunteers, we can resuscitate; otherwise we should think
  about moving it to dormant.
 
  Any volunteers?
 
  Phil
 
snap/

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



Re: [feedparser] Going once, going twice...

2005-12-21 Thread Rahul Akolkar
On 12/21/05, Martin van den Bemt [EMAIL PROTECTED] wrote:
 As I also said on the PMC list, I am not particularly interested in 
 development on feedparser, though I am willing to apply patches (if they are 
 complete with testcases).
snip/

Thanks for stepping forward Martin, I have no background about any PMC
thread, but I doubt thats what we are looking for. While I very much
appreciate your intent, if we are going to sustain feedparser in
proper, IMO, we really need someone to go beyond routine patches, for
starters we need a RM for 1.0.

-Rahul


 Assuming dormant means you can still commit to it (else archive would have 
 been a better name probably), we  can move it there and still apply patches 
 if eg Andrea Alberto comes up with something. If feedparsers matures  we can 
 always move it back (with an appropiate vote of course).

 So willing to monitor feedparser stuff.

 Mvgr,
 Martin

 Phil Steitz wrote:
  We need to make a decision on which way to go here...either demote
  back to sandbox/dormant or have someone step up to drive this
  component toward a release.
 
  I am happy to help getting the site fixed (seems we just need to add
  it to the nav, as http://jakarta.apache.org/commons/feedparser/ is
  there) and with build-related issues; but I have neither the time nor
  expertise to do much else.
 
  If we can get one knowledgeable and interested committer to step up
  and a few volunteers, we can resuscitate; otherwise we should think
  about moving it to dormant.
 
  Any volunteers?
 
  Phil
snap/

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



svn commit: r358355 - /jakarta/commons/proper/math/trunk/xdocs/issue-tracking.xml

2005-12-21 Thread psteitz
Author: psteitz
Date: Wed Dec 21 11:33:36 2005
New Revision: 358355

URL: http://svn.apache.org/viewcvs?rev=358355view=rev
Log:
Added issue tracking page.

Added:
jakarta/commons/proper/math/trunk/xdocs/issue-tracking.xml   (with props)

Added: jakarta/commons/proper/math/trunk/xdocs/issue-tracking.xml
URL: 
http://svn.apache.org/viewcvs/jakarta/commons/proper/math/trunk/xdocs/issue-tracking.xml?rev=358355view=auto
==
--- jakarta/commons/proper/math/trunk/xdocs/issue-tracking.xml (added)
+++ jakarta/commons/proper/math/trunk/xdocs/issue-tracking.xml Wed Dec 21 
11:33:36 2005
@@ -0,0 +1,61 @@
+?xml version=1.0?
+!--
+Copyright 2005 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.
+--
+document
+ properties
+  titleIssue tracking/title
+  author email=commons-dev@jakarta.apache.orgCommons Documentation 
Team/author
+ /properties
+body
+!-- == --
+section name=Issue tracking
+p
+  Commons Math uses a href=http://issues.apache.org/bugzilla/;ASF 
Bugzilla/a for tracking issues.
+  To use Bugzilla you may need to a 
href=http://issues.apache.org/bugzilla/createaccount.cgi;create an 
account/a.
+/p
+p
+  If you would like to report a bug, or raise an enhancement request with
+  Commons Math please do the following:
+  ol
+  lia 
href=http://issues.apache.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMEDamp;bug_status=NEWamp;bug_status=ASSIGNEDamp;bug_status=REOPENEDamp;bug_status=NEEDINFOamp;product=Commonsamp;component=Math;Search
 existing open bugs/a.
+  If you find your issue listed then please add a comment with your 
details./li
+  lia 
href=http://mail-archives.apache.org/mod_mbox/jakarta-commons-dev/;Search the 
mailing list archive/a.
+  You may find your issue or idea has already been discussed./li
+  lia 
href=http://issues.apache.org/bugzilla/enter_bug.cgi?product=Commonsamp;version=unspecifiedamp;component=Mathamp;rep_platform=Allamp;op_sys=Allamp;priority=P1amp;bug_severity=normalamp;bug_status=NEWamp;assigned_to=commons-dev%40jakarta.apache.orgamp;short_desc=%5Bmath%5D%20%22Your%20subject%20heading%20here%22amp;comment=Please%20provide%20details%20here.%20Its%20best%20to%20submit%20patches%20that%20alter%0D%0Aexisting%20file%20content%20in%20%22unified%20cvs%20diff%22%20format.%20%0D%0A%0D%0ASubmissions%20that%20provide%20new%20files%20can%20be%20supplied%20as%20direct%20file%0D%0Aattachments%20or%20archives%20in%20zip%20or%20tar.gz%20format.%20please%20be%20kind%20%0D%0Aenough%20to%20identify%20the%20format%20of%20the%20attached%20archive%20as%20bugzilla%0D%0Atends%20to%20strip%20these%20characterstics%20by%20removing%20the%20files%20extension.amp;commentprivacy=0amp;form_name=enter_bug;Submit
 a bug report or enhancement request/a.
+  Please prefix all new issues with [math] in the summary line.
+  /li
+  /ol
+/p
+p
+  Please also remember these points:
+  ul
+  lithe more information you provide, the better we can help you/li
+  litest cases are vital, particularly for any proposed enhancements/li
+  lithe developers of Commons Math are all unpaid volunteers/li
+  /ul
+/p
+p
+  You may also find these links useful:
+  ul
+  lia 
href=http://issues.apache.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMEDamp;bug_status=NEWamp;bug_status=ASSIGNEDamp;bug_status=REOPENEDamp;bug_status=NEEDINFOamp;product=Commonsamp;component=Math;All
 Open Math bugs/a/li
+  lia 
href=http://issues.apache.org/bugzilla/buglist.cgi?bug_status=RESOLVEDamp;bug_status=VERIFIEDamp;bug_status=CLOSEDamp;product=Commonsamp;component=Math;All
 Closed Math bugs/a/li
+  lia 
href=http://issues.apache.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMEDamp;bug_status=NEWamp;bug_status=ASSIGNEDamp;bug_status=REOPENEDamp;bug_status=NEEDINFOamp;bug_status=RESOLVEDamp;bug_status=VERIFIEDamp;bug_status=CLOSEDamp;product=Commonsamp;component=Math;All
 Math bugs/a/li
+  /ul
+/p
+/section
+!-- == --
+/body
+/document

Propchange: jakarta/commons/proper/math/trunk/xdocs/issue-tracking.xml
--
svn:eol-style = native

Propchange: jakarta/commons/proper/math/trunk/xdocs/issue-tracking.xml
--
svn:keywords = Date Author Id Revision HeadURL

Propchange: jakarta/commons/proper/math/trunk/xdocs/issue-tracking.xml

Re: [feedparser] Going once, going twice...

2005-12-21 Thread Henri Yandell
On 12/20/05, Phil Steitz [EMAIL PROTECTED] wrote:
 We need to make a decision on which way to go here...either demote
 back to sandbox/dormant or have someone step up to drive this
 component toward a release.

 I am happy to help getting the site fixed (seems we just need to add
 it to the nav, as http://jakarta.apache.org/commons/feedparser/ is
 there) and with build-related issues; but I have neither the time nor
 expertise to do much else.

 If we can get one knowledgeable and interested committer to step up
 and a few volunteers, we can resuscitate; otherwise we should think
 about moving it to dormant.

 Any volunteers?

The big one for me is to know why we'd want to have such a project.
Rome exists, it has a good license and it's getting used. There's no
reason to not develop redundant components if the itch is there, but
why work at creating the itch?

Hen

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



Re: [all] combo/ and docs/ directories

2005-12-21 Thread Henri Yandell
On 12/21/05, Rahul Akolkar [EMAIL PROTECTED] wrote:
 On 12/20/05, Craig McClanahan [EMAIL PROTECTED] wrote:
  On 12/20/05, Rahul Akolkar [EMAIL PROTECTED] wrote:
  
   I lack the background for a couple of directories under commons proper
   in SVN, but it will be nice to have that :-) These are not in the
   externals for trunks-proper either.
  
   * combo/
 
 
  The original theory here was that we could produce a commons-all.jar, and
  associated all Commons javadocs, for the complete set of proper Commons
  components.  The build script would let an individual developer pick which
  versions of all the point products he or she wanted, and in theory someone
  would update the checked-in version whenever there was a GA release of one
  of the packages.
 
  Alas, nobody really picked up on the idea, and the implementation (at least
  in Ant) is pretty messy.  I'd consider this thing to be dormant at the
  moment.
 
 snip/

 Thanks Craig, if no one adds to this thread in a few days, I'll call a
 VOTE to move combo out of proper.

+1. :)

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



Re: [jelly][vote] APT tag library

2005-12-21 Thread Paul Libbrecht

robert burrell donkin wrote:

not sure whether additional karma is required to add a component
  

Oh well, you need to be a committer if you want to maintain such in svn.

I think I'd summarize the things as follows:
- Ryan indicated he had this tag-library and would like to propose it
- Dion indicated he'd rather have help at committership to maintain such 
a tag-library as we (jelly committers tend to loose responsiveness a bit 
too often nowadays)

- a kind of informal vote was requested
- some votes, some comments on the informallity
- you (Robert) came to say that committership seemed a bit heavy to 
request for such a new contribution which I tend to understand 
(basically, all the committerships I've known, except for the sandbox 
fresh-components, have started with a live participation to commons-dev, 
commons-users, and jira, with advise to existing committers).
- thus I suggested Ryan to make one in jira and we start looking at it, 
horribly realizing that jira is not clickable from the jelly 
web-pages and that the life as an active community member 
contribution starts


So the suggestion is for Ryan to get a jira account (as Robert said, 
just click register), then post, there, an archive with a candidate 
library, receive comments, repost, see it arrive inside svn, and evolve 
etc...


hoping it'll have clarified things

paul

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



Re: [feedparser] Going once, going twice...

2005-12-21 Thread Stephen Colebourne

Phil Steitz wrote:

We need to make a decision on which way to go here...either demote
back to sandbox/dormant or have someone step up to drive this
component toward a release.


This is a clear case of demote to dormant IMHO.

Stephen

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



Re: [feedparser] Going once, going twice...

2005-12-21 Thread Martin van den Bemt



Rahul Akolkar wrote:

On 12/21/05, Martin van den Bemt [EMAIL PROTECTED] wrote:


As I also said on the PMC list, I am not particularly interested in development 
on feedparser, though I am willing to apply patches (if they are complete with 
testcases).


snip/

Thanks for stepping forward Martin, I have no background about any PMC
thread, but I doubt thats what we are looking for. While I very much
appreciate your intent, if we are going to sustain feedparser in
proper, IMO, we really need someone to go beyond routine patches, for
starters we need a RM for 1.0.


Yeah I know... Was just assuming dormant mode already for my offer, since no 
one stepped up already for months (though I did a little work on feedparser to 
get a nightly build). A dormant project will however never see a release, so to 
be blunt : from where I stand currently there is no need for a release manager, 
since there is not any activity on feedparser and even if there someone is 
stepping up as a release manager, we should have serious doubts about making an 
actual release, since currently no one is supporting feedparser and feedparser 
will slip into dormant mode pretty quickly again, because of the lack of 
support.
So there is nothing more to it then trying to fix issues that are in bugzilla (just 3 of them) and sending/committing patches to improve feedparser and get it in shape. 


I am just volunteering to commit them (with some review) and keep an eye on 
what the project is doing.

Mvgr,
Martin

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



Re: [feedparser] Going once, going twice...

2005-12-21 Thread Martin van den Bemt



The big one for me is to know why we'd want to have such a project.
Rome exists, it has a good license and it's getting used. There's no
reason to not develop redundant components if the itch is there, but
why work at creating the itch?



Good point indeed. I just stepped to volunteer helping out when people provide 
(complete) patches.
The way it currently is with feedparser though, is that I think I won't have 
much work on that.
(this is not a note for you Hen..)
It's not about finding a release manager, but about activity and you don't have 
to be a committer to be active with coding. :)

In short, +1 on a move to dormant mode, but I am willing to apply patches to it 
when people send them.

Mvgr,
Martin



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



svn commit: r358396 - in /jakarta/commons/sandbox/scxml/trunk/src/main/java/org/apache/commons/scxml: SCXMLDigester.java env/jsp/Standalone.java

2005-12-21 Thread rahul
Author: rahul
Date: Wed Dec 21 14:12:28 2005
New Revision: 358396

URL: http://svn.apache.org/viewcvs?rev=358396view=rev
Log:
1) Configured SCXML digester instances can now be obtained via public methods. 
This allows users to customize the digester ruleset further, if necessary. 
Nudge by Mike Sparr.

2) Change the digest() methods to declare throws clauses for underlying 
exceptions related to digester parsing. Intercept runtime exceptions to provide 
a sensible message in the logs.

Unfortunately, the second point might break some existing code. I'll probably 
send out a note about it to the user list later in the week.

Modified:

jakarta/commons/sandbox/scxml/trunk/src/main/java/org/apache/commons/scxml/SCXMLDigester.java

jakarta/commons/sandbox/scxml/trunk/src/main/java/org/apache/commons/scxml/env/jsp/Standalone.java

Modified: 
jakarta/commons/sandbox/scxml/trunk/src/main/java/org/apache/commons/scxml/SCXMLDigester.java
URL: 
http://svn.apache.org/viewcvs/jakarta/commons/sandbox/scxml/trunk/src/main/java/org/apache/commons/scxml/SCXMLDigester.java?rev=358396r1=358395r2=358396view=diff
==
--- 
jakarta/commons/sandbox/scxml/trunk/src/main/java/org/apache/commons/scxml/SCXMLDigester.java
 (original)
+++ 
jakarta/commons/sandbox/scxml/trunk/src/main/java/org/apache/commons/scxml/SCXMLDigester.java
 Wed Dec 21 14:12:28 2005
@@ -17,7 +17,7 @@
  */
 package org.apache.commons.scxml;
 
-//import java.io.IOException;
+import java.io.IOException;
 import java.net.URL;
 import java.text.MessageFormat;
 import java.util.Iterator;
@@ -64,6 +64,7 @@
 import org.xml.sax.Attributes;
 import org.xml.sax.ErrorHandler;
 import org.xml.sax.InputSource;
+import org.xml.sax.SAXException;
 
 /**
  * pThe SCXMLDigester provides the ability to digest a SCXML document into
@@ -71,6 +72,8 @@
  * pThe SCXMLDigester can be used for:/p
  * ol
  *  liDigest a SCXML file into the Commons SCXML Java object model./li
+ *  liObtain a SCXML Digester for further customization of the default
+ *  ruleset./li
  *  liSerialize an SCXML object (primarily for debugging)./li
  * /ol
  */
@@ -95,6 +98,9 @@
  *
  * @return SCXML The SCXML object corresponding to the file argument
  *
+ * @throws IOException Underlying Digester parsing threw an IOException
+ * @throws SAXException Underlying Digester parsing threw a SAXException
+ *
  * @see Context
  * @see ErrorHandler
  * @see Evaluator
@@ -102,7 +108,8 @@
  */
 public static SCXML digest(final URL scxmlURL,
 final ErrorHandler errHandler, final Context evalCtx,
-final Evaluator evalEngine) {
+final Evaluator evalEngine)
+throws IOException, SAXException {
 
 SCXML scxml = null;
 Digester scxmlDigester = SCXMLDigester
@@ -111,12 +118,15 @@
 
 try {
 scxml = (SCXML) scxmlDigester.parse(scxmlURL.toString());
-} catch (Exception e) {
+} catch (RuntimeException rte) {
+// Intercept runtime exceptions, only to log them with a
+// sensible error message about failure in document parsing
 MessageFormat msgFormat = new MessageFormat(ERR_DOC_PARSE_FAIL);
 String errMsg = msgFormat.format(new Object[] {
-scxmlURL.toString(), e.getMessage()
+String.valueOf(scxmlURL), rte.getMessage()
 });
-log.error(errMsg, e);
+log.error(errMsg, rte);
+throw rte;
 }
 
 if (scxml != null) {
@@ -148,6 +158,9 @@
  *
  * @return SCXML The SCXML object corresponding to the file argument
  *
+ * @throws IOException Underlying Digester parsing threw an IOException
+ * @throws SAXException Underlying Digester parsing threw a SAXException
+ *
  * @see Context
  * @see ErrorHandler
  * @see Evaluator
@@ -155,7 +168,8 @@
  */
 public static SCXML digest(final String documentRealPath,
 final ErrorHandler errHandler, final Context evalCtx,
-final Evaluator evalEngine, final PathResolver pathResolver) {
+final Evaluator evalEngine, final PathResolver pathResolver)
+throws IOException, SAXException {
 
 SCXML scxml = null;
 Digester scxmlDigester = SCXMLDigester.newInstance(null, pathResolver);
@@ -163,12 +177,15 @@
 
 try {
 scxml = (SCXML) scxmlDigester.parse(documentRealPath);
-} catch (Exception e) {
+} catch (RuntimeException rte) {
+// Intercept runtime exceptions, only to log them with a
+// sensible error message about failure in document parsing
 MessageFormat msgFormat = new MessageFormat(ERR_DOC_PARSE_FAIL);
 String errMsg = msgFormat.format(new Object[] {
-documentRealPath, e.getMessage()
+documentRealPath, rte.getMessage()
 });
-

DO NOT REPLY [Bug 37985] - unit tests fail for commons-net-1.4.1 with NullPointerException

2005-12-21 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=37985.
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=37985


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||INVALID




--- Additional Comments From [EMAIL PROTECTED]  2005-12-21 23:17 ---
disconnect should not be called on a SocketClient instance that has not
been successfully connected.  If there's a problem, it would be
with the unit test, not SocketClient. In other words, the test code should be
  if(client.isConnected())
client.disconnect();
instead of
  client.disconnect();

However, if you do that, then the unit test doesn't fail when a connection
is not established.  So you could write
  if(client.isConnected())
client.disconnect();
  else
throw SomeAppropriateException(Connection failed.);

But since client.disconnect() already throws an exception, I have to assume
the test writer opted for the shorter
   client.disconnect();

In short, the test is supposed to fail if it can't connect.

-- 
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 37985] - unit tests fail for commons-net-1.4.1 with NullPointerException

2005-12-21 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=37985.
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=37985





--- Additional Comments From [EMAIL PROTECTED]  2005-12-21 23:24 ---
(In reply to comment #1)
 This patch solves the problem. I'm going to go ahead with packaging 1.4.1 
 using
 this patch, unless there's some overwhelming reason not to.

I don't mean to speak for the rest of the Commons Net developers, but I think
we'd rather you package it by bypassing the unit tests during packaging.
Applying your patch may cause more bug reports from people who call disconnect()
improperly.  With the patch, they'll have no indication they did something 
wrong.
We can discuss this further on commons-dev.

-- 
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: [feedparser] Going once, going twice...

2005-12-21 Thread Rahul Akolkar
On 12/21/05, Martin van den Bemt [EMAIL PROTECTED] wrote:

snip/

 Yeah I know... Was just assuming dormant mode already for my offer,
snap/

OK, I did miss that critical point earlier :-)


On 12/21/05, Martin van den Bemt [EMAIL PROTECTED] wrote:
 It's not about finding a release manager, but about activity and you don't 
 have to be a committer to be active with coding. :)

snip/

True. I now see how some of my statements could be misread, it was
never my intent to discourage anyone. Oh well ...

-Rahul

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



[Jakarta-commons Wiki] Update of SCXML/1.0.0ReleasePlan by RahulAkolkar

2005-12-21 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/1%2e0%2e0ReleasePlan

The comment on the change is:
Mark resolved issue, add severity column to issues table

--
  
  I have till date assigned myself to SCXML bugs and enhancements based on 
discussions on the mailing lists. This is a practice that I do not intend to 
continue anymore, but for a better perspective, here are the issues that have 
been discussed on the Commons mailing lists:
  
- ||'''Issue'''||'''Reporter'''||'''Status'''||
+ ||'''Issue'''||'''Severity'''||'''Reporter'''||'''Status'''||
- ||SCXML send element body content is not parsed||Mike Sparr|| (./) ||
+ ||SCXML send element body content is not parsed||nor||Mike Sparr|| (./) ||
- ||Alignment of time model of execution with spec||James Barnett|| - ||
+ ||Alignment of time model of execution with spec||nor||James Barnett|| - ||
- ||Digester instances are not available for further customization||Mike 
Sparr|| - ||
+ ||Digester instances are not available for further customization||enh||Mike 
Sparr|| (./) ||
- ||API docs on website need to be improved||Rahul Akolkar|| - ||
+ ||API docs on website need to be improved||enh||Rahul Akolkar|| - ||
  
  = Check Compatibility =
  

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



DO NOT REPLY [Bug 37985] - unit tests fail for commons-net-1.4.1 with NullPointerException

2005-12-21 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=37985.
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=37985


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|INVALID |




--- Additional Comments From [EMAIL PROTECTED]  2005-12-21 23:38 ---

(In reply to comment #2)
 disconnect should not be called on a SocketClient instance that has not
 been successfully connected.  If there's a problem, it would be
 with the unit test, not SocketClient. In other words, the test code should be
   if(client.isConnected())
 client.disconnect();
 instead of
   client.disconnect();
 However, if you do that, then the unit test doesn't fail when a connection
 is not established.  So you could write
   if(client.isConnected())
 client.disconnect();
   else
 throw SomeAppropriateException(Connection failed.);
 
 But since client.disconnect() already throws an exception, I have to assume
 the test writer opted for the shorter
client.disconnect();

Fair enough. However, I think that some exception should be thrown (maybe
IllegalStateException?) that indicates that the object is in an invalid state,
instead of letting a NullPointerException occur.

 
 In short, the test is supposed to fail if it can't connect.
I can accept that the test would fail if it can't connect. However, it really
shouldn't be because of a NullPointerException.


(In reply to comment #3)
 I don't mean to speak for the rest of the Commons Net developers, but I think
 we'd rather you package it by bypassing the unit tests during packaging.

I concurr about not including the patch. We actually prefer to keep packages as
close to upstream as possible.

 Applying your patch may cause more bug reports from people who call 
 disconnect()
 improperly.  With the patch, they'll have no indication they did something 
 wrong.
 We can discuss this further on commons-dev.

The current code doesn't give much better of an indication that something went
wrong, so perhaps throwing an exception, like I mentioned above, is more
appropriate?

-- 
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: r358408 - /jakarta/commons/sandbox/scxml/trunk/xdocs/api-notes/core-digester.xml

2005-12-21 Thread rahul
Author: rahul
Date: Wed Dec 21 14:50:14 2005
New Revision: 358408

URL: http://svn.apache.org/viewcvs?rev=358408view=rev
Log:
Update API notes based on today's changes to the static methods in 
SCXMLDigester class.

Modified:
jakarta/commons/sandbox/scxml/trunk/xdocs/api-notes/core-digester.xml

Modified: jakarta/commons/sandbox/scxml/trunk/xdocs/api-notes/core-digester.xml
URL: 
http://svn.apache.org/viewcvs/jakarta/commons/sandbox/scxml/trunk/xdocs/api-notes/core-digester.xml?rev=358408r1=358407r2=358408view=diff
==
--- jakarta/commons/sandbox/scxml/trunk/xdocs/api-notes/core-digester.xml 
(original)
+++ jakarta/commons/sandbox/scxml/trunk/xdocs/api-notes/core-digester.xml Wed 
Dec 21 14:50:14 2005
@@ -35,15 +35,26 @@
  pThe primary convenience method exposed by the 
codeSCXMLDigester/code
  is:/p
  pre
+//import java.io.IOException;
 //import java.net.URL;
 //import org.apache.commons.scxml.Context;
 //import org.apache.commons.scxml.Evaluator;
 //import org.apache.commons.scxml.SCXMLDigester;
 //import org.apache.commons.scxml.model.SCXML;
 //import org.xml.sax.ErrorHandler;
+//import org.xml.sax.SAXException;
 
-SCXML scxml = SCXMLDigester.digest(lt;URLgt;, lt;ErroHandlergt;,
+SCXML scxml = null;
+
+try {
+  scxml = SCXMLDigester.digest(lt;URLgt;, lt;ErroHandlergt;,
 lt;Contextgt;, lt;Evaluatorgt;);
+} catch (IOException ioe) {
+  // IOException while parsing
+} catch (SAXException se) {
+  // SAXException while parsing
+}
+  
 
 if (scxml == null) {
   // Digestion failed



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



DO NOT REPLY [Bug 37971] - [net] NTFTPEntryParser doesn't parse NT ftp server list correctly.

2005-12-21 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=37971.
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=37971


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||DUPLICATE




--- Additional Comments From [EMAIL PROTECTED]  2005-12-22 01:15 ---
Yes, but the original regexp: you're talking about has ALREADY been changed in
the code as part of the fix of defect 35346.

*** This bug has been marked as a duplicate of 35346 ***

-- 
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 35346] - [net] NTFTPEntryParser parses directory names starting with a number followed by space incorrectly.

2005-12-21 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=35346.
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=35346


[EMAIL PROTECTED] changed:

   What|Removed |Added

 CC||[EMAIL PROTECTED]




--- Additional Comments From [EMAIL PROTECTED]  2005-12-22 01:15 ---
*** Bug 37971 has been marked as a duplicate of this bug. ***

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



logging, TCCL JCL 1.0.5 alpha

2005-12-21 Thread Voytenko, Dmytro
Hi,

I'm sorry for repeating the subject if it was discussed already, but I couldn't 
find an archive search. 

This email is regarding numerous problems with JCL in multi-class-loader 
environments. This seems to be a rather critical issue. I just got a chance to 
take a look into changes for JCL 1.0.5 currently in the alpha stage. 
Unfortunetely, these changes resolve a very small percent of all the problems 
associated with TCCL. If I understand correctly changes mostly targeted to make 
sure ClassLoaders are released, thus eliminating memory leaks related to hot 
deployment. Other issues (arguably more critical) remain unresolved. 

One of the issues I often run into is confusion b/w web application and shared 
loggers in the servlet container environment (Tomcat). Here's the small 
description of the situation:
There're two applications: app1 and app2. Both define logging configuration for 
outputing into different files (logfile1 and logfile2). These two applications 
use shared library (shared.jar). Classes in app1, app2 and shared.jar use JCL 
for logging. In this case the sequence is the following:
1) app1 is invoked first (for instance ServletInApp1)
2) code in app1 invokes class/method in the shared library (for instance 
SharedUtils.getInfo())
3) Log in the shared class (SharedUtils) is initialized using LogFactory for 
app1
4) At this point, any logs produced by SharedUtils will got to logfile1
5) app2 is invoked
6) code in app2 invokes the same SharedUtils
7) all logs in the SharedUtils still go to logfile1

Such a behaviour is rather confusing and basically jeopardizes any advantages 
of configuring LogFactory-s for each TCCL. This also brings system into the 
uncertain state. If app1 is redeployed, it's not clear what will happen to the 
SharedUtils.log, especially if LogFactory itself will be weak-referenced (as in 
1.0.5). 

These all problems could be resolved by simply disabling use of TCCL in the 
LogFactory. I entered this request in the bug database while ago: 
http://issues.apache.org/bugzilla/show_bug.cgi?id=36927

This problem seems to be rather critical to me, so I was wondering if you have 
other plans to resolve these problems, or if you believe the solution described 
in the bug report is appropriate. If you're persuing other ways to resolve the 
issue, could you please point me to the documents or bug reports describing 
them? In either case, do you have information on when the fix could be released?

thanks,
Dimitry E Voytenko



  

- ABOUT REVERE -

Revere provides finance and business professionals with superior data and 
analytics on companies traded publicly in the U.S. Our approach is based on 
precise classification and identification of key business relationships. The 
Revere Complete product suite combines the Revere Research analysis platform 
and the Revere RealTime market data application. Revere Complete integrates 
comprehensive financial and market information - real-time quotes, sector and 
option analytics, charts, news, fundamental data, and sophisticated screening - 
with unique content derived from Revere's own independent research: 

- The Revere Hierarchy, a patented classification system that provides 
unmatched detail in specifying a company's business activities and identifying 
exact competitors

- Revere Relationships, a database mapping a company to its key competitors, 
customers, suppliers, and strategic partners
 
www.reveredata.com



Re: [VOTE] Release Commons FileUpload 1.1

2005-12-21 Thread Niall Pemberton
-- --
[X] +1  Release Commons FileUpload 1.1-RC2 as Commons FileUpload 1.1
[ ] +0  not too fussed, but OK
[ ] -0  won't block, but think imperfect
[ ] -1  not until xxx is fixed


The only comments I have are a couple of reminders when you cut the release:

1) Same comment I made on RC1 -  IMO it would be worth mentioning the new
Commons IO dependency in the official announcement.

2) Fileupload's home/index page will need changing to refer to version 1.1
in the downloading section.

Niall




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



[PROPOSAL] Move SCXML to Commons Proper

2005-12-21 Thread Rahul Akolkar
As Robert has indicated before [1], it seems appropriate that sandbox
graduation proposals surface on the dev list before any formal VOTE
thread.

I'd like to propose moving SCXML to Commons Proper. Various data
points that motivate me -- in no particular order -- are:

 * Commons SCXML is being used

 * There has been a question about version 1.0

 * An Apache project uses Commons SCXML, some others could use Commons
SCXML if they please (see usecases on website - though I haven't
proposed any enhancements against unreleased code)

 * The codebase is ready for the final paces, and the known issues are
being actively resolved (see release plan below)

A release plan is taking shape here:

http://wiki.apache.org/jakarta-commons/SCXML/1.0.0ReleasePlan

At this point, I'd like to open the floor for a discussion about
anything and all things Commons SCXML. The code, website, wiki are all
in the expected place for a sandbox project.

I think we'll leave this thread open for atleast a couple of weeks,
to give any interested folks a few days on the other side of the
holiday break. Indeed, speaking for myself, my response time is bound
to vary over the next couple of weeks.

Opinions / comments / questions ?

-Rahul

P.S.-Needless to say, everyone is welcome to comment -- developers,
users, lurkers.

[1] http://marc.theaimsgroup.com/?l=jakarta-commons-devm=112937138601530w=2

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



svn commit: r358471 - /jakarta/commons/sandbox/scxml/trunk/xdocs/changes.xml

2005-12-21 Thread rahul
Author: rahul
Date: Wed Dec 21 19:33:28 2005
New Revision: 358471

URL: http://svn.apache.org/viewcvs?rev=358471view=rev
Log:
Today's entries to the change history.

Modified:
jakarta/commons/sandbox/scxml/trunk/xdocs/changes.xml

Modified: jakarta/commons/sandbox/scxml/trunk/xdocs/changes.xml
URL: 
http://svn.apache.org/viewcvs/jakarta/commons/sandbox/scxml/trunk/xdocs/changes.xml?rev=358471r1=358470r2=358471view=diff
==
--- jakarta/commons/sandbox/scxml/trunk/xdocs/changes.xml (original)
+++ jakarta/commons/sandbox/scxml/trunk/xdocs/changes.xml Wed Dec 21 19:33:28 
2005
@@ -35,6 +35,17 @@
 release version=1.0 date=Pending
  description=Project nearing promotion vote to Commons Proper
 
+  action dev=rahul type=update
+   [12-21-2005] SCXML digester instances are now available for further
+   customization of the default digester ruleset.
+  /action
+
+  action dev=rahul type=update
+   [12-21-2005] The static digest() methods of the SCXMLDigester class
+   now throw the same exceptions as the underlying ones from
+   Digester#parse().
+  /action
+
   action dev=rahul type=add
[12-10-2005] Make digester namespace aware, and capture arbitrary 
namespace
children of SCXML lt;sendgt; element.



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



svn commit: r358472 - /jakarta/commons/sandbox/id/trunk/src/media/logo.xcf

2005-12-21 Thread brett
Author: brett
Date: Wed Dec 21 19:34:40 2005
New Revision: 358472

URL: http://svn.apache.org/viewcvs?rev=358472view=rev
Log:
remove text properties on binary file

Modified:
jakarta/commons/sandbox/id/trunk/src/media/logo.xcf   (props changed)

Propchange: jakarta/commons/sandbox/id/trunk/src/media/logo.xcf
('svn:eol-style' removed)

Propchange: jakarta/commons/sandbox/id/trunk/src/media/logo.xcf
('svn:keywords' removed)



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



svn commit: r358475 - in /jakarta/commons: sandbox/openpgp/trunk/src/site/site.xml trunks-sandbox/pom.xml trunks-sandbox/src/ trunks-sandbox/src/site/ trunks-sandbox/src/site/apt/ trunks-sandbox/src/s

2005-12-21 Thread brett
Author: brett
Date: Wed Dec 21 19:38:32 2005
New Revision: 358475

URL: http://svn.apache.org/viewcvs?rev=358475view=rev
Log:
setting up site inheritance sample

Added:
jakarta/commons/trunks-sandbox/src/
jakarta/commons/trunks-sandbox/src/site/
jakarta/commons/trunks-sandbox/src/site/apt/
jakarta/commons/trunks-sandbox/src/site/apt/index.apt
  - copied, changed from r356049, 
jakarta/commons/proper/commons-build/trunk/xdocs/sandbox/index.xml
jakarta/commons/trunks-sandbox/src/site/site.xml   (with props)
Modified:
jakarta/commons/sandbox/openpgp/trunk/src/site/site.xml
jakarta/commons/trunks-sandbox/pom.xml

Modified: jakarta/commons/sandbox/openpgp/trunk/src/site/site.xml
URL: 
http://svn.apache.org/viewcvs/jakarta/commons/sandbox/openpgp/trunk/src/site/site.xml?rev=358475r1=358474r2=358475view=diff
==
--- jakarta/commons/sandbox/openpgp/trunk/src/site/site.xml (original)
+++ jakarta/commons/sandbox/openpgp/trunk/src/site/site.xml Wed Dec 21 19:38:32 
2005
@@ -10,7 +10,7 @@
 
 !--  TODO: proper menu --
 
-menu name=Quick Links
+menu name=Subproject menu
   item name=Introduction href=/index.html /
   item name=Usage href=/usage.html /
 /menu

Modified: jakarta/commons/trunks-sandbox/pom.xml
URL: 
http://svn.apache.org/viewcvs/jakarta/commons/trunks-sandbox/pom.xml?rev=358475r1=358474r2=358475view=diff
==
--- jakarta/commons/trunks-sandbox/pom.xml (original)
+++ jakarta/commons/trunks-sandbox/pom.xml Wed Dec 21 19:38:32 2005
@@ -2,6 +2,8 @@
  xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/maven-v4_0_0.xsd;
   modelVersion4.0.0/modelVersion
   groupIdorg.apache.commons/groupId
+  artifactIdcommons-sandbox-parent/artifactId
+  packagingpom/packaging
   !-- TODO: dummy version. In Maven 2.1, this will be auto-versioned being a 
generic parent --
   version1.0-SNAPSHOT/version
   nameJakarta Commons Sandbox/name
@@ -89,21 +91,30 @@
   jdkLevel1.3/jdkLevel
 /configuration
   /plugin
+  plugin
+artifactIdmaven-site-plugin/artifactId
+executions
+  execution
+goals
+  goalattach-descriptor/goal
+/goals
+  /execution
+/executions
+  /plugin
 /plugins
   /build
   reporting
 plugins
   !-- TODO: should be omitted when there are no tests to run --
   plugin
-groupIdorg.apache.maven.plugins/groupId
-artifactIdmaven-clover-plugin/artifactId
-!-- TODO: why are these needed? --
-configuration
-  flushPolicythreaded/flushPolicy
-  flushInterval100/flushInterval
-/configuration
+groupIdorg.codehaus.mojo/groupId
+artifactIdcobertura-maven-plugin/artifactId
   /plugin
 /plugins
   /reporting
+  modules
+moduleexec/module
+moduleopenpgp/module
+  /modules
 /project
 

Copied: jakarta/commons/trunks-sandbox/src/site/apt/index.apt (from r356049, 
jakarta/commons/proper/commons-build/trunk/xdocs/sandbox/index.xml)
URL: 
http://svn.apache.org/viewcvs/jakarta/commons/trunks-sandbox/src/site/apt/index.apt?p2=jakarta/commons/trunks-sandbox/src/site/apt/index.aptp1=jakarta/commons/proper/commons-build/trunk/xdocs/sandbox/index.xmlr1=356049r2=358475rev=358475view=diff
==
--- jakarta/commons/proper/commons-build/trunk/xdocs/sandbox/index.xml 
(original)
+++ jakarta/commons/trunks-sandbox/src/site/apt/index.apt Wed Dec 21 19:38:32 
2005
@@ -1,68 +1,60 @@
-?xml version=1.0 ?
-!DOCTYPE org.apache.commons.parts SYSTEM '../../parts/parts.dtd'
-!--
-   Copyright 2001-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.
---
-
-document
-  properties
-titleSandbox/title
-author email=commons-dev@jakarta.apache.orgCommons Documentation 
Team/author
-  /properties
-  body
-section name=The Jakarta Commons Sandbox
-  p
-The Sandbox is a Subversion repository for Commons committers to
-function as an open workspace for sharing and collaboration.
-The Sandbox serves as a staging ground for project which are
-destined for what is known as the Commons Proper.
-  /p
-
-sandbox-table;
-
-/section
-
-section name=Status of the Sandbox 

Re: [PROPOSAL] Move SCXML to Commons Proper

2005-12-21 Thread Rahul Akolkar
On 12/21/05, Dion Gillard [EMAIL PROTECTED] wrote:
 How many active developers are there for SCXML?

snip/

I believe you mean Commons committers?

I have done most of the development since Commons SCXML was created.

Other Commons committers who have expressed interest in participating
(in the past or in the future), include:
 * Martin Cooper (see Project team page, played a key role in the
creation of the SCXML component)
 * Niall Pemberton (Future components interest, CommonsPeople wiki page)

Ofcourse, I do not speak for either of them, or their current stand on
this proposal :-)

There have been users who have helped with development in terms of
ideas and code (Jaroslav Gergic, James Barnett, Mike Sparr). There are
others users who have done development to suit their needs that I'm
aware of (but have not contributed back to Commons).

-Rahul

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



svn commit: r358510 - /jakarta/commons/proper/fileupload/tags/FILEUPLOAD_1_1_RC2/

2005-12-21 Thread martinc
Author: martinc
Date: Wed Dec 21 22:09:47 2005
New Revision: 358510

URL: http://svn.apache.org/viewcvs?rev=358510view=rev
Log:
Tagging Commons FileUpload 1.1-RC2, somewhat belatedly

Added:
jakarta/commons/proper/fileupload/tags/FILEUPLOAD_1_1_RC2/
  - copied from r358509, jakarta/commons/proper/fileupload/trunk/


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