On Sat, Jun 9, 2012 at 12:50 PM, Babak Vahdat <babak.vah...@swissonline.ch>wrote:
> Hi > > The latest JDK 7 build went ALMOST well: > > > https://builds.apache.org/job/Camel.trunk.fulltest.java7/131/#showFailuresLink > > The cause of the failed 5 tests in camel-mail is because of: > > https://issues.apache.org/jira/browse/CAMEL-5339 > > As the built-in activation API inside JDK 7 itself behaves differently than > the one coming through the maven transitive dependency: > > javax.activation:activation:jar:1.1 > > As we intend to support both the JDK 6 & JDK 7 I think we should revert the > change here (doing so on my own workspace resolves while building on JDK 7 > / > OS X). > > Any thoughts? > > No the unit tests should be adjusted so they support both java 6 and 7. When people use camel-mail on Java 7, in eg Tomcat / JEE server etc. then activation JAR is already part of the JDK. This is also what Oracle/SUN says on their website, that you only need activation JAR if you use Java5 or older. > Babak > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Getting-closer-with-Java7-tp5692627p5714252.html > Sent from the Camel Development mailing list archive at Nabble.com. > -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
