Am 08.01.2014 21:10, schrieb Gary Gregory: > On Sat, Jan 4, 2014 at 2:56 PM, Oliver Heger > <oliver.he...@oliver-heger.de>wrote: > >> Maven build works fine with Java 1.5 and 1.7 on Windows 7. The ant build >> was successful, too. Artifacts and site look good. >> >> So +1. >> >> I tried to test the build with a JDK 1.4 using the profile, but got the >> error >> java.lang.UnsupportedClassVersionError: >> org/apache/maven/surefire/booter/ForkedBooter (Unsupported major.minor >> version 49.0) >> at java.lang.ClassLoader.defineClass0(Native Method) >> at java.lang.ClassLoader.defineClass(ClassLoader.java:539) >> at >> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:12 >> 3) >> at java.net.URLClassLoader.defineClass(URLClassLoader.java:251) >> at java.net.URLClassLoader.access$100(URLClassLoader.java:55) >> at java.net.URLClassLoader$1.run(URLClassLoader.java:194) >> at java.security.AccessController.doPrivileged(Native Method) >> at java.net.URLClassLoader.findClass(URLClassLoader.java:187) >> at java.lang.ClassLoader.loadClass(ClassLoader.java:289) >> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274) >> at java.lang.ClassLoader.loadClass(ClassLoader.java:235) >> at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302) >> Exception in thread "main" >> >> Obviously, even the surefire plug-in requires a JDK > 1.4. >> >> There haven't been any changes on the site, so I repeat my comments from >> my last review: >> - The overview site needs to be updated for the new release (in the >> Releases section). >> - There are some findbugs errors, probably not that critical, but at >> least the one about inconsistent synchronization could need some >> investigation. >> - The JIRA report only shows an error. >> > > I've published the site as is for now. I see this warning: > > [INFO] Falling back to RSS for issue download: This JIRA server does not > support version 2 of the REST API, which maven-changes-plugin requires. > > Which I also see when I build the site for [codec] but there, the Jira > report is created. > > How can that be?
Sorry, no idea. I noticed that the report for [exec] shows an error while it seems to work for other components. Did you compare the plug-in configurations in different poms? Could it be that a wrong JIRA project ID is set somewhere for [exec]? Oliver > > Gary > > > >> >> Oliver >> >> Am 03.01.2014 03:39, schrieb Gary Gregory: >>> Hello All: >>> >>> This is a VOTE to release Commons Exec 1.2-RC2 >>> >>> The changes from RC1 are: >>> - Update the NOTICE.txt file fro 2014 >>> - Update the source assembly to mark .sh files as executable. >>> >>> Feature and fix release. Requires a minimum of Java 1.3. >>> >>> The Apache Commons Exec team is pleased to announce the Apache >>> commons-exec-1.2 release! >>> >>> Apache Commons Exec is a library to reliably execute external processes >>> from within the JVM. >>> >>> 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. >>> >>> This VOTE is open for at least 72 hours until January 6 2014 at 10:00 PM >>> EST. >>> >>> The files: >>> >>> https://repository.apache.org/content/repositories/orgapachecommons-038/ >>> >>> The tag: >>> >>> https://svn.apache.org/repos/asf/commons/proper/exec/tags/1.2-RC2 >>> >>> The site: >>> >>> https://people.apache.org/~ggregory/commons-exec/1.2-RC2/site/ >>> >>> Links to versions of sites and Javadocs will be live when deployed. >>> >>> Thank you, >>> Gary Gregory >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> >> > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
