Re: Question about Apache-Extras

[Dave Brondsema]

On 1/7/14 11:15 AM, Andrea Pescetti wrote:
> On 22/12/2013 Jacques Le Roux wrote:
>> OFBiz is concerned as well. We have several components there and we
>> would like to know if a replacement solution has been planned?
>> https://code.google.com/a/apache-extras.org/hosting/search?q=label%3aOFBiz
> 
> Another round of Board reports, so I'm asking if there is any update too. The
> original post http://s.apache.org/hzJ stated January 15 as a deadline. So, any
> news on the following two questions?
> 
> 1) Does the Google Code change affect Apache Extras?
> 
> 2) Are there plans to make the lost functionality available in some other 
> ways?
> 
> Infra clearly stated that this is "a ComDev issue".
> 
> Thanks,
>   Andrea.
> 

If moving away from Google Code is desired, an option to consider would be using
Apache Allura (podling) and/or SourceForge (which runs Allura).  Allura has
importers for Google Code wikis, tickets and source repos.  For files, Allura
itself doesn't have download system, but SourceForge does (AOO uses it too) and
SourceForge has implemented a Google Code files importer for it.  SourceForge's
docs about it are at
https://sourceforge.net/p/forge/documentation/Google%20Code%20Importer/

Note: these importers currently choke on the extra "/a/apache-extras.org" in the
URL.  I'm sure that would be easy enough for us to fix if anyone wanted to
proceed in this direction.

I'm a member of the Allura PPMC and a SourceForge employee.


-- 
Dave Brondsema : d...@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
  <><

[ANNOUNCEMENT] Apache Commons Exec 1.2 Released

[Gary Gregory]

The Apache Commons Exec team is pleased to announce the 1.2 release!

Apache Commons Exec is a library to reliably execute external processes
from within the JVM.

This is a mostly a maintenance release after a long absence from new
releases and still requires a only minimum of Java 1.3.

Changes in this version include:

New features:

o Set names for started threads.  Issue: EXEC-55. Thanks to Dominik
Stadler.

Fixed Bugs:

o Issue: EXEC-68.
  Watchdog kills process immediately if timeout is too large.
  Thanks to Joel McCance.

o Issue: EXEC-57.
  Applied the patch from Nickolay Martinov but the timeout disguises the
fact that the process might be still running.
  Therefore added a sanity check in order to throw an exception if the the
timeout for join() was exceeded.
  Thanks to Nickolay Martinov.

o Issue: EXEC-60.
  Fixed dead lock by calling the timeout observers outside of the
synchronized block thereby removing on pre-requisite of a deadlock.
  Also added a test case to demonstrate that this problem is fixed (which
of course can not guarantee the absence of a dead lock).
  Thanks to Peter Kofler.

o Issue: EXEC-52.
  Tests fail on HP-UX, because it uses a different syntax for the ping
command.
  Thanks to Nickolay Martinov.

o Issue: EXEC-49.
  "Write dead end" IOException when using Piped streams w/PumpStreamHandler.
  When encountering a PipedOutputStream we will automatically close it to
avoid the exception.
  Thanks to Kevin Telford.

o Issue: EXEC-34.
  Race condition prevent watchdog working using ExecuteStreamHandler.
  Patch submittd by Kristian Rosenvold.
  Thanks to Marco Ferrante.

For complete information on Commons Exec, including instructions on how to
submit bug reports, patches, or suggestions for improvement, see the Apache
Commons Exec website:

Site: http://commons.apache.org/proper/commons-exec/

Download: http://commons.apache.org/exec/download_codec.cgi

Enjoy,
Gary Gregory on behalf of the Apache Commons Exec team

-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition
JUnit in Action, Second Edition 
Spring Batch in Action 
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory