Re: [scxml-js] working toward a release
Hi Rahul, So far, I have not found any technical shortcomings that would seem to indicate that Maven2 with AntRun will not work. I feel the main challenge is the Maven community's reluctance to support such solutions, which makes it difficult for me to obtain answers to my questions. In any case, I am making progress and will commit today. Thanks, Jake On 10-08-27 04:47 PM, Rahul Akolkar wrote: Right, ideal scenario is where the build and release mechanics of [scxml-js] are no different than other Commons Proper components (which use Maven2 for build+release tasks). By necessity, Commons is more focused on standardizing how components are built, sites are deployed, releases are cut etc. Having said that, if there are technical reasons why the ant run plugin won't work for [scxml-js], then lets make those reasons clear, confirm they can't be fixed (or fixed without much effort) and explore other avenues. Do you have changes to the pom to get closer to the goal of using m2 for build+release (incomplete as they may be)? If so, can you commit it? That way the rest of us can take a look -- I don't think I'll have time immediately for this, but I will take a look when I can. -Rahul Let me know what you think. Thanks, Jake On 10-08-26 05:24 PM, Rahul Akolkar wrote: On Thu, Aug 26, 2010 at 4:52 PM, Jacob Beardjbea...@cs.mcgill.cawrote: Hi, I've brought up a question on the maven list which I was wondering if others could weigh on. Basically, the question is what is the best way to deal with JavaScript library dependencies for which no Maven repository exists. One person has encouraged me to set up a Maven repository on my personal server using Apache Archiva, and provide these libraries there, then simply link to them as dependencies in the main project pom.xml. Another person has said that I can simply call AntRun from an early phase to download these dependencies using my current Ant script. snip/ The latter will work better. The former sets you up to do an undue amount of work, serve as a point of distribution as well as failure and relies on adding a reference to the repo you host into the project pom -- downsides galore. I will make some general comments about feedback from Maven lists in this context: * While figuring out how the Maven central repo (or some other) should host popular JavaScript libraries of the day is a good goal in itself, for the purpose of the [scxml-js] build that is not the problem we are trying to solve for everyone else. * More generally, the lists are understandably drunk on Maven cool-aid (very well-intended too, no doubt) to the point where the pragmatic view of getting the [scxml-js] build set up using the Commons release infrastructure could get lost in the theoretical arguments of the Maven way. * Many of the proposed solutions will make more sense for work type settings (such as setting up a maven repo manager etc.) but are not very applicable to Apache Commons components. After talking to Maven lists, its best to make final Maven-related decisions on the Commons list as with this thread. So thanks for asking here. -Rahul I'd appreciate hearing others' opinions on this. Thanks, Jake On 10-08-25 06:58 PM, Rahul Akolkar wrote: On Wed, Aug 25, 2010 at 6:13 PM, sebbseb...@gmail.com wrote: On 25 August 2010 22:23, Rahul Akolkarrahul.akol...@gmail.com wrote: On Wed, Aug 25, 2010 at 4:51 PM, Jacob Beardjbea...@cs.mcgill.ca wrote: Hi, I've completed initial integration of Maven with the Ant build script. Maven's compile phase now builds the combined js file and the single class file. The package phase is then able to successfully create an executable jar. snip/ Cool. My next question is, is it important to phase out getDeps.xml, the ant script that downloads required JavaScript and Java libraries for the project, in favor of a Maven solution? Many of the required libraries downloaded in getDeps.xml do not have a maven repository, but at the same time, many do, including commons-cli and xalan. These could perhaps be downloaded by Maven. Is a hybrid solution the best approach? snap/ I'd say so, there is value to having the Java deps listed in the pom rather than elsewhere, so they get taken care of as part of the Maven's management of dependencies. The binaries distros in Commons don't actually contain dependency jars so there is no need to download (beyond being in the m2 local repo) or copy them into distros. Seems like the JavaScript deps that aren't in the repo will necessitate the hybrid approach. One way would be to fetch these during another antrun execution tied to one of the earlier phases. Maybe also add the dependencies to the POM as provided? snip/ If you're talking about the JS deps, no. These aren't on central (and
Re: [math] unit tests for FastMath
Luc Maisonobe wrote: Hi all, I have started integrating the FastMath class from MATH-375. I have not committed anything for now as I am first fixing numerous checkstyle errors (more than 300) and wanted to have one clean commit to simplify patching both trunk for 3.0 and branch 2.X. One less obvious problem is unit tests. The current tests (which I converted to Junit 4) depend on a few external classes that themselve depend on a LGPL library, and this library doesn seem to be available in maven repositories. This imply that we cannot include the library in the release, and we cannot either use it as an optional dependency for tests. I would suggest to completely remove this library and create tests simply by storing reference values in files that we would read. It would be similar to the existing tests for random values or stats. The file could of course be created using dfp or any other reference high precision package (having several different reference sources would be better IMHO). We would remove the random aspect of the tests, which may or may not be a problem. Sounds like a reasonable approach. Can you explain a little more what the tests do and what you have in mind in terms of data coverage? In particular, what are the random aspects of the tests? I know the answer here is really RTFP (p = patch ;) but hey, I am a little lazy this evening. Phil Luc - 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
Re: svn commit: r989543 - /commons/proper/math/trunk/src/main/java/org/apache/commons/math/FunctionEvaluationException.java
Rahul Akolkar wrote: On Fri, Aug 27, 2010 at 6:06 AM, Luc Maisonobe luc.maison...@free.fr wrote: Le 27/08/2010 00:37, Gilles Sadowski a écrit : MATH-410 Wrong variable (argument instead of arguments). Modified: commons/proper/math/trunk/src/main/java/org/apache/commons/math/FunctionEvaluationException.java Could this be also put in the new MATH_2_X branch ? Certainly, but I don't know how to do it. :-} Either you can check out the MATH_2_X branch and do the change here again or if you are already sure the file should be exactly the same in both versions you can copy it directly in the repository with a command like: svn cp -m the commit message you want https://svn.apache.org/repos/asf/commons/proper/math/trunk/src/main/java/org/apache/commons/math/FunctionEvaluationException.java https://svn.apache.org/repos/asf/commons/proper/math/branches/MATH_2_X/src/main/java/org/apache/commons/math/FunctionEvaluationException.java snip/ The files may be identical, but their svn histories no longer are -- which means no server side copies please. Yes, my strong recommendation is to just check out the 2_X branch and port changes to the checkout, then commit. The merge command using local paths can be helpful, but diffs should be observed and tests run on the local 2_X (or trunk) checkout before committing. Phil -Rahul You can also use svn.eu.apache.org if you happen to use the european mirror of the subversion repository. Luc - 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
Re: [math] unit tests for FastMath
Le 29/08/2010 00:25, Phil Steitz a écrit : Luc Maisonobe wrote: Hi all, I have started integrating the FastMath class from MATH-375. I have not committed anything for now as I am first fixing numerous checkstyle errors (more than 300) and wanted to have one clean commit to simplify patching both trunk for 3.0 and branch 2.X. One less obvious problem is unit tests. The current tests (which I converted to Junit 4) depend on a few external classes that themselve depend on a LGPL library, and this library doesn seem to be available in maven repositories. This imply that we cannot include the library in the release, and we cannot either use it as an optional dependency for tests. Bill is willing to offer the dependency library under the same terms as FastMath as he explained in the Jira comments for MATH-375. That could be another way to solve the problem (and would be another fine addition to [math]). I would suggest to completely remove this library and create tests simply by storing reference values in files that we would read. It would be similar to the existing tests for random values or stats. The file could of course be created using dfp or any other reference high precision package (having several different reference sources would be better IMHO). We would remove the random aspect of the tests, which may or may not be a problem. Sounds like a reasonable approach. Can you explain a little more what the tests do and what you have in mind in terms of data coverage? In particular, what are the random aspects of the tests? I know the answer here is really RTFP (p = patch ;) but hey, I am a little lazy this evening. We could start by a random set of values just like the current tests do. The current test structure is basically one big accuracy test for each function, consisting in 1 calls to random values obtained thanks to Math.random and normalized to the appropriate domain of the function (-inf; +inf) or (-1; +1) or (0; +inf) ... Then the FastMath implementation is compared with a reference computed with extended precision by the dfp library, and some features of the library are also used to compute precisely the error in terms of ulps. We could also add specific non random values for some corner cases (NaN, infinities, zero, one, big integers closes to multiples of pi for the argument reduction of angles ...). Of course, we would also add values corresponding to issues raised by users after they are solved. Luc Phil Luc - 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 - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [math] unit tests for FastMath
Some of these tests might benefit from choosing values from a highly skewed distribution. Gamma(0.01, 0.01), for instance will exercise small and large values much better than an exponential distribution. On Sat, Aug 28, 2010 at 4:49 PM, Luc Maisonobe luc.maison...@free.frwrote: We could start by a random set of values just like the current tests do. The current test structure is basically one big accuracy test for each function, consisting in 1 calls to random values obtained thanks to Math.random and normalized to the appropriate domain of the function (-inf; +inf) or (-1; +1) or (0; +inf) ...
Re: [math] unit tests for FastMath
Luc Maisonobe wrote: Le 29/08/2010 00:25, Phil Steitz a écrit : Luc Maisonobe wrote: Hi all, I have started integrating the FastMath class from MATH-375. I have not committed anything for now as I am first fixing numerous checkstyle errors (more than 300) and wanted to have one clean commit to simplify patching both trunk for 3.0 and branch 2.X. One less obvious problem is unit tests. The current tests (which I converted to Junit 4) depend on a few external classes that themselve depend on a LGPL library, and this library doesn seem to be available in maven repositories. This imply that we cannot include the library in the release, and we cannot either use it as an optional dependency for tests. Bill is willing to offer the dependency library under the same terms as FastMath as he explained in the Jira comments for MATH-375. That could be another way to solve the problem (and would be another fine addition to [math]). Excellent. Agreed this looks like another good addition. Thanks, Bill! Phil I would suggest to completely remove this library and create tests simply by storing reference values in files that we would read. It would be similar to the existing tests for random values or stats. The file could of course be created using dfp or any other reference high precision package (having several different reference sources would be better IMHO). We would remove the random aspect of the tests, which may or may not be a problem. Sounds like a reasonable approach. Can you explain a little more what the tests do and what you have in mind in terms of data coverage? In particular, what are the random aspects of the tests? I know the answer here is really RTFP (p = patch ;) but hey, I am a little lazy this evening. We could start by a random set of values just like the current tests do. The current test structure is basically one big accuracy test for each function, consisting in 1 calls to random values obtained thanks to Math.random and normalized to the appropriate domain of the function (-inf; +inf) or (-1; +1) or (0; +inf) ... Then the FastMath implementation is compared with a reference computed with extended precision by the dfp library, and some features of the library are also used to compute precisely the error in terms of ulps. We could also add specific non random values for some corner cases (NaN, infinities, zero, one, big integers closes to multiples of pi for the argument reduction of angles ...). Of course, we would also add values corresponding to issues raised by users after they are solved. Luc Phil Luc - 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 - 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
[GUMP@vmgump]: Project commons-io-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 gene...@gump.apache.org. Project commons-io-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 3 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-io-test : Apache Commons Full details are available at: http://vmgump.apache.org/gump/public/apache-commons/commons-io-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/io/gump_mvn_settings.xml] -DEBUG- (Gump generated) Maven2 Settings in: /srv/gump/public/workspace/apache-commons/io/gump_mvn_settings.xml -INFO- Failed with reason build failed -DEBUG- Maven POM in: /srv/gump/public/workspace/apache-commons/io/pom.xml -INFO- Project Reports in: /srv/gump/public/workspace/apache-commons/io/target/surefire-reports The following work was performed: http://vmgump.apache.org/gump/public/apache-commons/commons-io-test/gump_work/build_apache-commons_commons-io-test.html Work Name: build_apache-commons_commons-io-test (Type: Build) Work ended in a state of : Failed Elapsed: 2 mins 8 secs Command Line: mvn --batch-mode --settings /srv/gump/public/workspace/apache-commons/io/gump_mvn_settings.xml test [Working Directory: /srv/gump/public/workspace/apache-commons/io] - Running org.apache.commons.io.output.StringBuilderWriterTest Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.06 sec Running org.apache.commons.io.comparator.ExtensionFileComparatorTest Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.069 sec Running org.apache.commons.io.FileUtilsFileNewerTestCase Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.071 sec Running org.apache.commons.io.input.CountingInputStreamTest Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.088 sec Running org.apache.commons.io.input.ProxyReaderTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.057 sec Running org.apache.commons.io.output.NullWriterTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.055 sec Running org.apache.commons.io.output.TeeOutputStreamTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.054 sec Running org.apache.commons.io.comparator.SizeFileComparatorTest Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.085 sec Running org.apache.commons.io.FileUtilsListFilesTestCase Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.079 sec Running org.apache.commons.io.comparator.DirectoryFileComparatorTest Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.067 sec Running org.apache.commons.io.filefilter.AndFileFilterTestCase Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.062 sec Running org.apache.commons.io.TaggedIOExceptionTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.059 sec Running org.apache.commons.io.input.TaggedInputStreamTest Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.07 sec Running org.apache.commons.io.HexDumpTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.091 sec Running org.apache.commons.io.input.CloseShieldInputStreamTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.067 sec Results : Tests in error: Tests run: 644, Failures: 0, Errors: 3, Skipped: 0 [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. Please refer to /srv/gump/public/workspace/apache-commons/io/target/surefire-reports for the individual test results. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 2 minutes 7 seconds [INFO] Finished at: Sun Aug 29 02:17:57 UTC 2010 [INFO] Final Memory: 38M/92M [INFO] - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/apache-commons/commons-io-test/rss.xml - Atom: http://vmgump.apache.org/gump/public/apache-commons/commons-io-test/atom.xml == Gump Tracking Only === Produced by Gump version 2.3. Gump Run 0829082010, vmgump.apache.org:vmgump:0829082010 Gump E-mail
[g...@vmgump]: Project commons-scxml-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 gene...@gump.apache.org. Project commons-scxml-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 21 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-scxml-test : Apache Commons Full details are available at: http://vmgump.apache.org/gump/public/apache-commons/commons-scxml-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/scxml/gump_mvn_settings.xml] -DEBUG- (Gump generated) Maven2 Settings in: /srv/gump/public/workspace/apache-commons/scxml/gump_mvn_settings.xml -INFO- Failed with reason build failed -DEBUG- Maven POM in: /srv/gump/public/workspace/apache-commons/scxml/pom.xml -INFO- Project Reports in: /srv/gump/public/workspace/apache-commons/scxml/target/surefire-reports The following work was performed: http://vmgump.apache.org/gump/public/apache-commons/commons-scxml-test/gump_work/build_apache-commons_commons-scxml-test.html Work Name: build_apache-commons_commons-scxml-test (Type: Build) Work ended in a state of : Failed Elapsed: 18 secs Command Line: mvn --batch-mode --settings /srv/gump/public/workspace/apache-commons/scxml/gump_mvn_settings.xml test [Working Directory: /srv/gump/public/workspace/apache-commons/scxml] - --- T E S T S --- Running org.apache.commons.scxml.invoke.InvokeTestSuite Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.336 sec Running org.apache.commons.scxml.test.TestingTestSuite Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.008 sec Running org.apache.commons.scxml.env.EnvTestSuite Tests run: 21, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.169 sec Running org.apache.commons.scxml.SCXMLTestSuite Tests run: 71, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.829 sec FAILURE! Running org.apache.commons.scxml.issues.IssuesTestSuite Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.255 sec Running org.apache.commons.scxml.model.ModelTestSuite Tests run: 78, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.149 sec FAILURE! Running org.apache.commons.scxml.env.faces.EnvFacesTestSuite Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 sec Running org.apache.commons.scxml.semantics.SemanticsTestSuite Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec Running org.apache.commons.scxml.env.jsp.EnvJspTestSuite Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.035 sec Running org.apache.commons.scxml.env.jexl.EnvJexlTestSuite Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.021 sec Running org.apache.commons.scxml.env.servlet.EnvServletTestSuite Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec Running org.apache.commons.scxml.io.IOTestSuite Tests run: 30, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.507 sec Results : Failed tests: testNamespacePrefixedXPathsEL(org.apache.commons.scxml.NamespacePrefixedXPathsTest) testDatamodelSimultaneousJsp(org.apache.commons.scxml.model.DatamodelTest) Tests run: 228, Failures: 2, Errors: 0, Skipped: 0 [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. Please refer to /srv/gump/public/workspace/apache-commons/scxml/target/surefire-reports for the individual test results. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 17 seconds [INFO] Finished at: Sun Aug 29 04:26:20 UTC 2010 [INFO] Final Memory: 40M/97M [INFO] - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/apache-commons/commons-scxml-test/rss.xml - Atom: http://vmgump.apache.org/gump/public/apache-commons/commons-scxml-test/atom.xml == Gump Tracking Only === Produced by Gump version 2.3. Gump Run 0829082010, vmgump.apache.org:vmgump:0829082010 Gump E-mail Identifier (unique within run) #18. -- Apache Gump http://gump.apache.org/ [Instance:
[GUMP@vmgump]: Project commons-jelly-tags-validate (in module commons-jelly) 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 gene...@gump.apache.org. Project commons-jelly-tags-validate has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 21 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-validate : Commons Jelly Full details are available at: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-validate/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole jar output [commons-jelly-tags-validate-29082010.jar] identifier set to project name -DEBUG- Dependency on iso-relax exists, no need to add for property maven.jar.isorelax. -DEBUG- Dependency on relaxng exists, no need to add for property maven.jar.relaxngDatatype. -DEBUG- Dependency on xml-xerces exists, no need to add for property maven.jar.xerces. -DEBUG- Dependency on commons-jexl-1.x exists, no need to add for property maven.jar.commons-jexl. -DEBUG- Dependency on msv-core exists, no need to add for property maven.jar.msv. -DEBUG- (Gump generated) Maven Properties in: /srv/gump/public/workspace/commons-jelly/jelly-tags/validate/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /srv/gump/public/workspace/commons-jelly/jelly-tags/validate/project.xml -DEBUG- Maven project properties in: /srv/gump/public/workspace/commons-jelly/jelly-tags/validate/project.properties -INFO- Project Reports in: /srv/gump/public/workspace/commons-jelly/jelly-tags/validate/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-validate/gump_work/build_commons-jelly_commons-jelly-tags-validate.html Work Name: build_commons-jelly_commons-jelly-tags-validate (Type: Build) Work ended in a state of : Failed Elapsed: 8 secs Command Line: maven --offline jar [Working Directory: /srv/gump/public/workspace/commons-jelly/jelly-tags/validate] - [junit] [junit] [junit] Testcase: invalidateDTD(org.apache.commons.jelly.tags.junit.CaseTag$1): Caused an ERROR [junit] file:/srv/gump/public/workspace/commons-jelly/jelly-tags/validate/target/test-classes/org/apache/commons/jelly/tags/validate/suite.jelly:97:52: v:verifier com/sun/msv/datatype/xsd/ngimpl/DataTypeLibraryImpl [junit] org.apache.commons.jelly.JellyTagException: file:/srv/gump/public/workspace/commons-jelly/jelly-tags/validate/target/test-classes/org/apache/commons/jelly/tags/validate/suite.jelly:97:52: v:verifier com/sun/msv/datatype/xsd/ngimpl/DataTypeLibraryImpl [junit] at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:732) [junit] at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:287) [junit] at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:96) [junit] at org.apache.commons.jelly.tags.junit.CaseTag$1.runTest(CaseTag.java:60) [junit] Caused by: java.lang.NoClassDefFoundError: com/sun/msv/datatype/xsd/ngimpl/DataTypeLibraryImpl [junit] at com.sun.msv.reader.dtd.DTDReader.init(DTDReader.java:96) [junit] at com.sun.msv.reader.dtd.DTDReader.parse(DTDReader.java:74) [junit] at com.sun.msv.reader.dtd.DTDReader.parse(DTDReader.java:66) [junit] at com.sun.msv.reader.util.GrammarLoader._loadSchema(GrammarLoader.java:393) [junit] at com.sun.msv.reader.util.GrammarLoader.parse(GrammarLoader.java:325) [junit] at com.sun.msv.reader.util.GrammarLoader.loadSchema(GrammarLoader.java:189) [junit] at com.sun.msv.verifier.jarv.TheFactoryImpl.parse(TheFactoryImpl.java:42) [junit] at com.sun.msv.verifier.jarv.FactoryImpl.compileSchema(FactoryImpl.java:98) [junit] at org.iso_relax.verifier.VerifierFactory.compileSchema(Unknown Source) [junit] at org.apache.commons.jelly.tags.validate.VerifierTag.doTag(VerifierTag.java:92) [junit] at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:267) [junit] ... 11 more [junit] Root cause [junit] java.lang.NoClassDefFoundError: com/sun/msv/datatype/xsd/ngimpl/DataTypeLibraryImpl [junit] at com.sun.msv.reader.dtd.DTDReader.init(DTDReader.java:96) [junit] at com.sun.msv.reader.dtd.DTDReader.parse(DTDReader.java:74) [junit] at com.sun.msv.reader.dtd.DTDReader.parse(DTDReader.java:66) [junit] at com.sun.msv.reader.util.GrammarLoader._loadSchema(GrammarLoader.java:393) [junit] at
[g...@vmgump]: Project commons-proxy-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 gene...@gump.apache.org. Project commons-proxy-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 21 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-proxy-test : Apache Commons Full details are available at: http://vmgump.apache.org/gump/public/apache-commons/commons-proxy-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/proxy/gump_mvn_settings.xml] -DEBUG- (Gump generated) Maven2 Settings in: /srv/gump/public/workspace/apache-commons/proxy/gump_mvn_settings.xml -INFO- Failed with reason build failed -DEBUG- Maven POM in: /srv/gump/public/workspace/apache-commons/proxy/pom.xml -INFO- Project Reports in: /srv/gump/public/workspace/apache-commons/proxy/target/surefire-reports The following work was performed: http://vmgump.apache.org/gump/public/apache-commons/commons-proxy-test/gump_work/build_apache-commons_commons-proxy-test.html Work Name: build_apache-commons_commons-proxy-test (Type: Build) Work ended in a state of : Failed Elapsed: 11 secs Command Line: mvn --batch-mode --settings /srv/gump/public/workspace/apache-commons/proxy/gump_mvn_settings.xml test [Working Directory: /srv/gump/public/workspace/apache-commons/proxy] - Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec Running org.apache.commons.proxy.factory.util.TestMethodSignature Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec Running org.apache.commons.proxy.provider.TestConstantProvider Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.006 sec Running org.apache.commons.proxy.interceptor.TestFilteredInterceptor Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.029 sec Running org.apache.commons.proxy.interceptor.filter.TestPatternFilter Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec Running org.apache.commons.proxy.interceptor.TestSerializingInterceptor Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.014 sec Running org.apache.commons.proxy.interceptor.TestInterceptorChain Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.006 sec Running org.apache.commons.proxy.invoker.TestNullInvoker Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.025 sec Running org.apache.commons.proxy.provider.remoting.TestBurlapProvider Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.017 sec Running org.apache.commons.proxy.exception.TestDelegateProviderException Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec Running org.apache.commons.proxy.invoker.TestChainInvoker Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 sec Running org.apache.commons.proxy.factory.javassist.TestJavassistProxyFactory Tests run: 37, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.15 sec Running org.apache.commons.proxy.exception.TestProxyFactoryException Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec Running org.apache.commons.proxy.interceptor.filter.TestReturnTypeFilter Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec Running org.apache.commons.proxy.provider.TestBeanProvider Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.012 sec Results : Tests in error: testInvalidHandlerName(org.apache.commons.proxy.invoker.TestXmlRpcInvoker) Tests run: 179, Failures: 0, Errors: 1, Skipped: 0 [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. Please refer to /srv/gump/public/workspace/apache-commons/proxy/target/surefire-reports for the individual test results. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 10 seconds [INFO] Finished at: Sun Aug 29 05:03:15 UTC 2010 [INFO] Final Memory: 39M/94M [INFO] - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/apache-commons/commons-proxy-test/rss.xml - Atom:
[g...@vmgump]: Project commons-javaflow (in module commons-sandbox) 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 gene...@gump.apache.org.
Project commons-javaflow has an issue affecting its community integration.
This issue affects 1 projects,
and has been outstanding for 37 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-javaflow : Commons Javaflow
Full details are available at:
http://vmgump.apache.org/gump/public/commons-sandbox/commons-javaflow/index.html
That said, some information snippets are provided here.
The following annotations (debug/informational/warning/error messages) were
provided:
-DEBUG- Sole jar output [commons-javaflow-*[0-9T].jar] identifier set to
project name
-DEBUG- (Gump generated) Maven2 Settings in:
/srv/gump/public/workspace/commons-sandbox/javaflow/gump_mvn_settings.xml
-INFO- Failed with reason build failed
-DEBUG- Maven POM in:
/srv/gump/public/workspace/commons-sandbox/javaflow/pom.xml
-INFO- Project Reports in:
/srv/gump/public/workspace/commons-sandbox/javaflow/target/surefire-reports
-WARNING- No directory
[/srv/gump/public/workspace/commons-sandbox/javaflow/target/surefire-reports]
-INFO- Failed to extract fallback artifacts from Gump Repository
The following work was performed:
http://vmgump.apache.org/gump/public/commons-sandbox/commons-javaflow/gump_work/build_commons-sandbox_commons-javaflow.html
Work Name: build_commons-sandbox_commons-javaflow (Type: Build)
Work ended in a state of : Failed
Elapsed: 17 secs
Command Line: mvn --batch-mode --settings
/srv/gump/public/workspace/commons-sandbox/javaflow/gump_mvn_settings.xml
package
[Working Directory: /srv/gump/public/workspace/commons-sandbox/javaflow]
-
Downloading:
http://localhost:8192/maven2/asm/asm-analysis/3.2/asm-analysis-3.2.jar
17K downloaded (asm-analysis-3.2.jar)
Downloading: http://localhost:8192/maven2/asm/asm-util/3.2/asm-util-3.2.jar
34K downloaded (asm-util-3.2.jar)
[INFO] [antrun:run {execution: javadoc.resources}]
[INFO] Executing tasks
[copy] Copying 2 files to
/srv/gump/public/workspace/commons-sandbox/javaflow/target/apidocs/META-INF
[INFO] Executed tasks
[INFO] Setting property: classpath.resource.loader.class =
'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: velocimacro.messages.on = 'false'.
[INFO] Setting property: resource.loader = 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound = 'false'.
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'iso-8859-1' encoding to copy filtered resources.
[INFO] Copying 2 resources to META-INF
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Compiling 35 source files to
/srv/gump/public/workspace/commons-sandbox/javaflow/target/classes
[INFO] [bundle:manifest {execution: bundle-manifest}]
[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'iso-8859-1' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/srv/gump/public/workspace/commons-sandbox/javaflow/src/test/resources
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] Compiling 23 source files to
/srv/gump/public/workspace/commons-sandbox/javaflow/target/test-classes
[INFO] -
[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR]
/srv/gump/public/workspace/commons-sandbox/javaflow/src/test/java/org/apache/commons/javaflow/AsmTestSuite.java:[73,13]
addTestSuite(java.lang.Class? extends junit.framework.TestCase) in
junit.framework.TestSuite cannot be applied to (java.lang.Classcapture#831 of
?)
[ERROR]
/srv/gump/public/workspace/commons-sandbox/javaflow/src/test/java/org/apache/commons/javaflow/AsmTestSuite.java:[74,13]
addTestSuite(java.lang.Class? extends junit.framework.TestCase) in
junit.framework.TestSuite cannot be applied to (java.lang.Classcapture#283 of
?)
[INFO] 2 errors
[INFO] -
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
/srv/gump/public/workspace/commons-sandbox/javaflow/src/test/java/org/apache/commons/javaflow/AsmTestSuite.java:[73,13]
addTestSuite(java.lang.Class? extends junit.framework.TestCase) in
junit.framework.TestSuite cannot be applied to (java.lang.Classcapture#831 of
?)
/srv/gump/public/workspace/commons-sandbox/javaflow/src/test/java/org/apache/commons/javaflow/AsmTestSuite.java:[74,13]
addTestSuite(java.lang.Class? extends
[g...@vmgump]: Project commons-jelly-tags-xml-test (in module commons-jelly) 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 gene...@gump.apache.org. Project commons-jelly-tags-xml-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 21 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. -DEBUG- Dependency on commons-jexl-1.x exists, no need to add for property maven.jar.commons-jexl. -DEBUG- Dependency on xalan exists, no need to add for property maven.jar.xalan. -WARNING- Overriding Maven properties: [/srv/gump/public/workspace/commons-jelly/jelly-tags/xml/build.properties] -DEBUG- (Gump generated) Maven Properties in: /srv/gump/public/workspace/commons-jelly/jelly-tags/xml/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /srv/gump/public/workspace/commons-jelly/jelly-tags/xml/project.xml -DEBUG- Maven project properties in: /srv/gump/public/workspace/commons-jelly/jelly-tags/xml/project.properties -INFO- Project Reports in: /srv/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: 11 secs Command Line: maven --offline jar [Working Directory: /srv/gump/public/workspace/commons-jelly/jelly-tags/xml] - [junit] Should produce the correct output expected:...:test=http://apache/testNS; xmlns=http://java/ns; test:abc=testValuetest-subnode xmlns= attr=testtest-anotherSubNode/test-anotherSubNodetest-anotherSubNodeAgain xmlns:other=http://java/ns; xmlns... but was:...=http://java/ns; xmlns:test=http://apache/testNS; test:abc=testValuetest-subnode xmlns= attr=testtest-anotherSubNode/test-anotherSubNodetest-anotherSubNodeAgain xmlns=http://java/ns; xmlns:other... [junit] junit.framework.ComparisonFailure: Should produce the correct output expected:...:test=http://apache/testNS; xmlns=http://java/ns; test:abc=testValuetest-subnode xmlns= attr=testtest-anotherSubNode/test-anotherSubNodetest-anotherSubNodeAgain xmlns:other=http://java/ns; xmlns... but was:...=http://java/ns; xmlns:test=http://apache/testNS; test:abc=testValuetest-subnode xmlns= attr=testtest-anotherSubNode/test-anotherSubNodetest-anotherSubNodeAgain xmlns=http://java/ns; xmlns:other... [junit] at org.apache.commons.jelly.tags.xml.TestXMLTags.testNamespaceReplace(TestXMLTags.java:148) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [junit] [junit] [junit] Testcase: testAttributeNameSpace(org.apache.commons.jelly.tags.xml.TestXMLTags):FAILED [junit] Should produce the correct output expected:...:test=http://apache/testNS; xmlns=http://apache/true... but was:...=http://apache/trueNS; xmlns:test=http://apache/test... [junit] junit.framework.ComparisonFailure: Should produce the correct output expected:...:test=http://apache/testNS; xmlns=http://apache/true... but was:...=http://apache/trueNS; xmlns:test=http://apache/test... [junit] at org.apache.commons.jelly.tags.xml.TestXMLTags.testAttributeNameSpace(TestXMLTags.java:166) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [junit] [junit] [junit] Testcase: testAttributeNameSpaceDefaultNS(org.apache.commons.jelly.tags.xml.TestXMLTags): FAILED [junit] Should produce the correct output expected:...:test=http://apache/testNS; xmlns=http://apache/true... but was:...=http://apache/trueNS; xmlns:test=http://apache/test... [junit] junit.framework.ComparisonFailure: Should produce the correct output expected:...:test=http://apache/testNS; xmlns=http://apache/true... but was:...=http://apache/trueNS; xmlns:test=http://apache/test...
[g...@vmgump]: Project commons-jelly-tags-jaxme (in module commons-jelly) 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 gene...@gump.apache.org. Project commons-jelly-tags-jaxme has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 21 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-jaxme : Commons Jelly Full details are available at: http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-jaxme/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Sole jar output [commons-jelly-tags-jaxme-29082010.jar] identifier set to project name -DEBUG- Dependency on packaged-jaxme exists, no need to add for property maven.jar.jaxme. -DEBUG- Dependency on packaged-jaxme exists, no need to add for property maven.jar.jaxme-js. -DEBUG- Dependency on packaged-jaxme exists, no need to add for property maven.jar.jaxme-xs. -DEBUG- Dependency on packaged-jaxme exists, no need to add for property maven.jar.jaxme-api. -DEBUG- Dependency on xml-xerces exists, no need to add for property maven.jar.xerces. -DEBUG- Dependency on commons-jexl-1.x exists, no need to add for property maven.jar.commons-jexl. -DEBUG- (Gump generated) Maven Properties in: /srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/build.properties -INFO- Failed with reason build failed -DEBUG- Maven POM in: /srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/project.xml -DEBUG- Maven project properties in: /srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/project.properties -INFO- Project Reports in: /srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/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-jaxme/gump_work/build_commons-jelly_commons-jelly-tags-jaxme.html Work Name: build_commons-jelly_commons-jelly-tags-jaxme (Type: Build) Work ended in a state of : Failed Elapsed: 7 secs Command Line: maven --offline jar [Working Directory: /srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme] - [javac] symbol : method getResult() [javac] location: class org.apache.ws.jaxme.examples.misc.address.impl.AddressTypeHandler [javac] org.apache.ws.jaxme.examples.misc.address.AddressType _1 = (org.apache.ws.jaxme.examples.misc.address.AddressType) getResult(); [javac] ^ [javac] /srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/src/test/org/apache/ws/jaxme/examples/misc/address/impl/AddressTypeHandler.java:298: cannot find symbol [javac] symbol : variable super [javac] location: class org.apache.ws.jaxme.examples.misc.address.impl.AddressTypeHandler [javac] super.characters(pChars, pOffset, pLen); [javac] ^ [javac] /srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/src/test/org/apache/ws/jaxme/examples/misc/address/impl/AddressTypeHandler.java:305: cannot find symbol [javac] symbol : variable super [javac] location: class org.apache.ws.jaxme.examples.misc.address.impl.AddressTypeHandler [javac] super.init(pData); [javac] ^ [javac] /srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/src/test/org/apache/ws/jaxme/examples/misc/address/impl/AddressTypeHandler.java:315: cannot find symbol [javac] symbol : method getData() [javac] location: class org.apache.ws.jaxme.examples.misc.address.impl.AddressTypeHandler [javac] __handler_Name.init(getData()); [javac] ^ [javac] /srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/src/test/org/apache/ws/jaxme/examples/misc/address/impl/AddressHandler.java:22: cannot find symbol [javac] symbol : method getData() [javac] location: class org.apache.ws.jaxme.examples.misc.address.impl.AddressHandler [javac] return (org.apache.ws.jaxme.examples.misc.address.AddressType) getData().getFactory().getElement(org.apache.ws.jaxme.examples.misc.address.Address.class); [javac] ^ [javac] /srv/gump/public/workspace/commons-jelly/jelly-tags/jaxme/src/test/org/apache/ws/jaxme/examples/misc/address/impl/AddressTypeSerializer.java:62: cannot find symbol [javac] symbol : variable super [javac] location: class org.apache.ws.jaxme.examples.misc.address.impl.AddressTypeSerializer [javac] org.xml.sax.helpers.AttributesImpl _1 =
