[
https://issues.apache.org/activemq/browse/CAMEL-542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=42959#action_42959
]
Gert Vanthienen commented on CAMEL-542:
---------------------------------------
On my machine, Camel now builds with Java 1.6 after this change
(http://svn.apache.org/viewvc/activemq/camel/trunk/components/camel-jxpath/src/test/java/org/apache/camel/language/jxpath/SpringJXPathFilterTest.java?r1=659263&r2=659262&pathrev=659263)
Multiple test classes that use the same Spring XML file when extending
AbstractJUnit38SpringContextTests are *not* independent of each other. In this
case, the mock endpoint still 'remembers' the messages from this test when it
arrives at the SpringJXPathFilterNonMatchingTest -- causing the latter one to
fail. This problem doesn't occur in Java 1.5 because the tests are being
executed in a different order (the non-matching test precedes the matching
test).
> Camel should be able to be build with Java 1.6
> ----------------------------------------------
>
> Key: CAMEL-542
> URL: https://issues.apache.org/activemq/browse/CAMEL-542
> Project: Apache Camel
> Issue Type: Task
> Components: camel-core
> Affects Versions: 1.3.0, 1.4.0
> Reporter: Claus Ibsen
> Priority: Minor
>
> Currently build from the source requires Java 1.5 only.
> Sometime in the future we should be able to build using 1.6 - eg. when 1.6 is
> mainstream on the mac's ;)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
