+1 (non-binding) @Willem: Thanks for merging my PR.
I was able to build 2.13.1 with the following setup: Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17 11:22:22-0400) Maven home: C:\dev\maven-3.1.1 Java version: 1.7.0_55, vendor: Oracle Corporation Java home: c:\dev\jdk-1.7\jre Default locale: en_US, platform encoding: Cp1252 OS name: "windows 8.1", version: "6.3", arch: "amd64", family: "windows" Please note that I had to disable test "setJobName" in class PrinterPrintTest as it does not seem to work on Windows with JDK 1.7. I will need to further investigate, but definitely not a problem that was recently introduced with 2.13.1. On Mon, May 12, 2014 at 4:06 AM, Willem Jiang <willem.ji...@gmail.com>wrote: > Thanks for that. > I just merged the pull request. > > -- > Willem Jiang > > Red Hat, Inc. > Web: http://www.redhat.com > Blog: http://willemjiang.blogspot.com (English) > http://jnn.iteye.com (Chinese) > Twitter: willemjiang > Weibo: 姜宁willem > > > > On May 12, 2014 at 1:08:48 PM, Gregor Zurowski (gre...@zurowski.org) > wrote: > > It does not compile on my Windows box due to a recently added unit test > in > > class DefaultTraceEventMessageTest: > > > > ======================================================== > > Results : > > > > Failed tests: > > > > > DefaultTraceEventMessageTest>TestSupport.runBare:58->testDefaultTraceEventMessageBody:79 > > Get a wrong body string expected:<...s file based: target[/]test]> but > > was:<...s file based: target[\]test]> > > > > Tests run: 4902, Failures: 1, Errors: 0, Skipped: 3 > > > > [INFO] > > ------------------------------------------------------------------------ > > [INFO] Reactor Summary: > > [INFO] > > [INFO] Camel ............................................. SUCCESS > [1.165s] > > [...] > > [INFO] Camel :: Core ..................................... FAILURE > > [22:46.800s] > > ======================================================== > > > > An assertion in the test assumes Unix path separators which obviously > does > > not work with Windows. I have submitted the following PR that fixes this > > issue: > > > > https://github.com/apache/camel/pull/149 > > > > Note that functionality is not affected, only the unit test is broken on > > Windows. > > > > Thanks, > > Gregor > > > > > > On Sun, May 11, 2014 at 8:29 PM, Willem Jiang wrote: > > > > > Hi Peter, > > > > > > Can you revert your -1? > > > > > > I ran the tests before I cut the Camel 2.13.1, and Christian verified > the > > > source with “mvn clean install”, he didn’t find any issue. > > > > > > -- > > > Willem Jiang > > > > > > Red Hat, Inc. > > > Web: http://www.redhat.com > > > Blog: http://willemjiang.blogspot.com (English) > > > http://jnn.iteye.com (Chinese) > > > Twitter: willemjiang > > > Weibo: 姜宁willem > > > > > > > > > > > > On May 11, 2014 at 9:46:27 PM, Peter Keller (kellerb...@gmail.com) > wrote: > > > > -1 > > > > > > > > I use MacOS with java version "1.7.0_40". > > > > > > > > I downloaded > > > > > > > > http://repository.apache.org/content/repositories/orgapachecamel-1008/org/apache/camel/apache-camel/2.13.1/apache-camel-2.13.1-src.zip > > > , > > > > executed "mvn install" and got following error: > > > > > > > > Running org.apache.camel.view.XmlGraphTest > > > > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.092 > > > sec - > > > > in org.apache.camel.view.XmlGraphTest > > > > > > > > Results : > > > > > > > > Failed tests: > > > > > > > > > > > > FileProducerRenameUsingCopyTest>TestSupport.runBare:58->testMove:41->ContextTestSupport.assertMockEndpointsSatisfied:343 > > > > mock://result Content of file: target/file/done/hello.txt. Expected: > > > > > Camel> but was: <> > > > > > > > > Tests run: 4902, Failures: 1, Errors: 0, Skipped: 3 > > > > > > > > I re-exucuted "mvn install" and got several errors of following type: > > > > > > > > Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.077 > > > sec - > > > > in org.apache.camel.management.JmxInstrumentationUsingPropertiesTest > > > > Running > org.apache.camel.management.JmxInstrumentationWithConnectorTest > > > > Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: > 942.325 > > > sec > > > > <<< FAILURE! - in > > > > org.apache.camel.management.JmxInstrumentationWithConnectorTest > > > > > > > > testCounters(org.apache.camel.management.JmxInstrumentationWithConnectorTest) > > > > Time elapsed: 7.609 sec <<< ERROR! > > > > java.io.IOException: Failed to retrieve RMIServer stub: > > > > javax.naming.NameNotFoundException: jmxrmi/camel > > > > at > > > > > > > > com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:116) > > > > at > > > > > > > > com.sun.jndi.toolkit.url.GenericURLContext.lookup(GenericURLContext.java:203) > > > > at javax.naming.InitialContext.lookup(InitialContext.java:411) > > > > at > > > > > > > > javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnector.java:1925) > > > > at > > > > > > > > javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.java:1892) > > > > at > > > javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:275) > > > > at > > > > > > > > javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:268) > > > > at > > > > > > > > org.apache.camel.management.JmxInstrumentationWithConnectorTest.getMBeanConnection(JmxInstrumentationWithConnectorTest.java:100) > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > View this message in context: > > > > http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-13-1-tp5750981p5750990.html > > > > Sent from the Camel Development mailing list archive at Nabble.com. > > > > > > > > > > > > > >
