[BeanUtils] 1.8.0 RC2 available for review

BeanUtils 1.8.0 RC2 is available for review here:
http://people.apache.org/~niallp/beanutils-1.8.0-rc2/

I have tested this with JDK 1.3, 1.4, 1.5 and 1.6. This RC is built with JDK 1.5
(Ibuilding with JDK 1.4, has the following problem:
 http://commons.markmail.org/message/wqqs67eyi6hq3mcq )

The tag is here:
http://svn.apache.org/viewvc/commons/proper/beanutils/tags/BEANUTILS_1_8_0_RC2/

Release Notes:
http://people.apache.org/~niallp/beanutils-1.8.0-rc2/RELEASE-NOTES.txt

Site:
http://people.apache.org/~niallp/beanutils-1.8.0-rc2/site/
(note some links are broken since the 1.8.0 directories are not yet created)

Clirr Report (compared to 1.8.0 Beta)
http://people.apache.org/~niallp/beanutils-1.8.0-rc2/site/clirr-report.html
(note breaking compatibility with 1.8.0 Beta was discussed here:
 http://commons.markmail.org/message/xpeify7dioksg7xg )

I'm going to be away (and offline) from Thursday for a week - so
there'll be a delay in me responding to any feedback.

tia

Niall

[GUMP <at> vmgump]: Project commons-configuration-test (in module apache-commons) failed

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 general <at> gump.apache.org.

Project commons-configuration-test has an issue affecting its community integration.
This issue affects 1 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
    - commons-configuration-test :  Apache Commons

Full details are available at:
    http://vmgump.apache.org/gump/public/apache-commons/commons-configuration-test/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were provided:
 -WARNING- Overriding Maven2 settings: [/srv/gump/public/workspace/apache-commons/configuration/gump_mvn_settings.xml]
 -DEBUG- (Gump generated) Maven2 Settings in: /srv/gump/public/workspace/apache-commons/configuration/gump_mvn_settings.xml
 -INFO- Failed with reason build failed
 -DEBUG- Maven POM in: /srv/gump/public/workspace/apache-commons/configuration/pom.xml

The following work was performed:
http://vmgump.apache.org/gump/public/apache-commons/commons-configuration-test/gump_work/build_apache-commons_commons-configuration-test.html
Work Name: build_apache-commons_commons-configuration-test (Type: Build)
Work ended in a state of : Failed
Elapsed: 2 mins 16 secs
Command Line: mvn --batch-mode --settings
/srv/gump/public/workspace/apache-commons/configuration/gump_mvn_settings.xml test 

[VOTE] Accept flatfile codebase for new sandbox component

The codebase is available for perusal at:

http://people.apache.org/~mbenson/flatfile-proposal/

The IP clearance template has been started and is
available at:

http://svn.apache.org/repos/asf/incubator/public/trunk/site-author/ip-clearance/commons-flatfile.xml

This vote will be open for 72 hours.

Thanks,
Matt

deadlocks in dbcp?

Hello,

I'm developing a static deadlock checking tool for Java and am
evaluating it on open-source programs.  I ran it on the latest dbcp
source code (from svn) using the latest pool source code (also from
svn) and here are the results:

http://chord.stanford.edu/dbcp1.3/deadlocks.html

The first three reports, under groups 1-3, point to the deadlock
reported in DBCP-44 (https://issues.apache.org/jira/browse/DBCP-44).
I presume this problem is still unresolved?

The remaining reports all seem to point to a previously unknown
deadlock, and they all seem to occur because the close() method in
PoolableConnection is synchronized.  Can a dbcp developer confirm if
any of these reports points to a real deadlock (or whether they are
all false positives)?  Also, it seems like they are related to DBCP-49
(https://issues.apache.org/jira/browse/DBCP-49) which is where the
close() method was first synchronized.

If you want me to run the deadlock checker more extensively, let me
know.  The test case I currently have
(http://chord.stanford.edu/dbcp1.3/T.java.html) excludes many usage
scenarios.  Anyone who knows scenarios I'm missing or has test cases
exercising those scenarios can point them out to me.  They don't have
to be too "concrete": the tool does static analysis which ignores
specific values of timers, flags, etc.  So even one "abstract" test
case like the above one actually covers several concrete test cases.

[ANN] Commons JXPath 1.3 Released

The Apache Commons team is pleased to announce the release of Apache Commons JXPath version 1.3.

The org.apache.commons.jxpath package defines a simple interpreter of an expression language called
XPath. JXPath applies XPath expressions to graphs of objects of all kinds: JavaBeans, Maps, Servlet
contexts, DOM etc, including mixtures thereof.

Commons JXPath 1.3 contains a substantial number of bug fixes as well as a number of new features. Details
can be found in the release notes:

    http://commons.apache.org/jxpath/release-notes-1.3.html

Commons JXPath is available in either binary or source form from the following downloads page:

    http://commons.apache.org/jxpath/download_jxpath.cgi

For more information on Commons JXPath, visit the project homepage:

    http://commons.apache.org/jxpath/

-Matt Benson
 on behalf of the Apache Commons Community

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe <at> commons.apache.org
For additional commands, e-mail: dev-help <at> commons.apache.org

[Commons Wiki] Update of "CommonsOsgi" by NiallPemberton

Dear Wiki user,

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

The following page has been changed by NiallPemberton:
http://wiki.apache.org/commons/CommonsOsgi

The comment on the change is:
Add JXPath 1.3

------------------------------------------------------------------------------
  || jci             ||  1.0               ||                          ||                        ||
  || jelly           ||  1.0               ||                          || No m2 build            ||
  || jexl            ||  1.1               ||                          ||                        ||
- || jxpath          ||  1.2               ||                          || See
[http://svn.apache.org/repos/asf/felix/trunk/commons/commons-jxpath/pom.xml Felix Bundle] ||
+ || jxpath          ||  1.2               || 1.3                      || See
[http://svn.apache.org/repos/asf/felix/trunk/commons/commons-jxpath/pom.xml Felix Bundle] ||
  || lang            ||  2.3               || 2.4                      ||                        ||
  || launcher        ||  1.1               ||                          ||                        ||
  || logging         ||  1.1.1             ||                          || OSGi is N/A; See Below ||

[GUMP <at> vmgump]: Project commons-configuration (in module apache-commons) failed

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 general <at> gump.apache.org.

Project commons-configuration has an issue affecting its community integration.
This issue affects 14 projects,
 and has been outstanding for 13 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
    - commons-configuration :  Apache Commons
    - commons-jelly-tags-ojb :  Commons Jelly
    - db-ojb-from-packages-1-0-release :  ObjectRelationalBridge
    - db-torque :  Persistence Layer
    - fulcrum-cache :  Services Framework
    - fulcrum-configuration-impl :  Services Framework
    - fulcrum-intake :  Services Framework
    - fulcrum-parser :  Services Framework
    - fulcrum-security-memory :  Services Framework
    - fulcrum-security-nt :  Services Framework
    - fulcrum-template :  Services Framework
    - jakarta-turbine-jcs :  Cache
    - test-ojb-from-packages-1-0-release :  ObjectRelationalBridge
    - turbine-core :  A servlet based framework.

Full details are available at:
    http://vmgump.apache.org/gump/public/apache-commons/commons-configuration/index.html

That said, some information snippets are provided here.

[continuum] BUILD FAILURE: Commons - Commons IO - Build Def:

Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=107937&projectId=155

Build statistics:
  State: Failed
  Previous State: Failed
  Started at: Mon 11 Aug 2008 05:59:58 -0700
  Finished at: Mon 11 Aug 2008 06:01:02 -0700
  Total time: 1m 4s
  Build Trigger: Schedule
  Build Number: 82
  Exit code: 1
  Building machine hostname: vmbuild.apache.org
  Operating system : Linux(unknown)
  Java Home version : 
          java version "1.5.0_12"
          Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04)
          Java HotSpot(TM) Client VM (build 1.5.0_12-b04, mixed mode, sharing)

  Builder version :
          Maven version: 2.0.8
          Java version: 1.5.0_12
          OS name: "linux" version: "2.6.20-16-server" arch: "i386" Family: "unix"

****************************************************************************
SCM Changes:
****************************************************************************
Changed: niallp @ Mon 11 Aug 2008 04:21:38 -0700
Comment: Fix IO-168 Symbolic links (symlinks) followed when deleting directory - reported by Apostolos
Lerios, thanks to Attila Szegedi for the solution and Brydie McCoy for the patch
Files changed:

[GUMP <at> vmgump]: Project commons-configuration (in module apache-commons) failed

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 general <at> gump.apache.org.

Project commons-configuration has an issue affecting its community integration.
This issue affects 14 projects,
 and has been outstanding for 11 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
    - commons-configuration :  Apache Commons
    - commons-jelly-tags-ojb :  Commons Jelly
    - db-ojb-from-packages-1-0-release :  ObjectRelationalBridge
    - db-torque :  Persistence Layer
    - fulcrum-cache :  Services Framework
    - fulcrum-configuration-impl :  Services Framework
    - fulcrum-intake :  Services Framework
    - fulcrum-parser :  Services Framework
    - fulcrum-security-memory :  Services Framework
    - fulcrum-security-nt :  Services Framework
    - fulcrum-template :  Services Framework
    - jakarta-turbine-jcs :  Cache
    - test-ojb-from-packages-1-0-release :  ObjectRelationalBridge
    - turbine-core :  A servlet based framework.

Full details are available at:
    http://vmgump.apache.org/gump/public/apache-commons/commons-configuration/index.html

That said, some information snippets are provided here.

[GUMP <at> vmgump]: Project commons-cli (in module apache-commons) failed

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 general <at> gump.apache.org.

Project commons-cli has an issue affecting its community integration.
This issue affects 51 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
    - apollo :  Apollo Project
    - cargo :  Cargo provides a Java API to manipulate Java Containers
    - checkstyle :  Java style checker
    - commons-cli :  Commons CLI Package
    - commons-javaflow :  Commons Javaflow
    - commons-jelly :  Commons Jelly
    - commons-jelly-tags-ant :  Commons Jelly
    - commons-jelly-tags-antlr :  Commons Jelly
    - commons-jelly-tags-avalon :  Commons Jelly
    - commons-jelly-tags-bean :  Commons Jelly
    - commons-jelly-tags-beanshell :  Commons Jelly
    - commons-jelly-tags-betwixt :  Commons Jelly
    - commons-jelly-tags-bsf :  Commons Jelly
    - commons-jelly-tags-define :  Commons Jelly
    - commons-jelly-tags-define-test :  Commons Jelly
    - commons-jelly-tags-dynabean :  Commons Jelly
    - commons-jelly-tags-email :  Commons Jelly
    - commons-jelly-tags-fmt :  Commons Jelly
    - commons-jelly-tags-fmt-test :  Commons Jelly
    - commons-jelly-tags-html :  Commons Jelly

[GUMP <at> vmgump]: Project commons-configuration (in module apache-commons) failed

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 general <at> gump.apache.org.

Project commons-configuration has an issue affecting its community integration.
This issue affects 14 projects,
 and has been outstanding for 9 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
    - commons-configuration :  Apache Commons
    - commons-jelly-tags-ojb :  Commons Jelly
    - db-ojb-from-packages-1-0-release :  ObjectRelationalBridge
    - db-torque :  Persistence Layer
    - fulcrum-cache :  Services Framework
    - fulcrum-configuration-impl :  Services Framework
    - fulcrum-intake :  Services Framework
    - fulcrum-parser :  Services Framework
    - fulcrum-security-memory :  Services Framework
    - fulcrum-security-nt :  Services Framework
    - fulcrum-template :  Services Framework
    - jakarta-turbine-jcs :  Cache
    - test-ojb-from-packages-1-0-release :  ObjectRelationalBridge
    - turbine-core :  A servlet based framework.

Full details are available at:
    http://vmgump.apache.org/gump/public/apache-commons/commons-configuration/index.html

That said, some information snippets are provided here.