Am 09.06.12 14:13 schrieb "Babak Vahdat" unter
:
>Yeah that makes sense, however what they say on their sites is
>contradictory
>to what they do provide (the parent POM of javax.mail:mail):
>
>http://search.maven.org/#artifactdetails%7Ccom.sun.mail%7Call%7C1.4.5%7Cpo
>m
>
>which brings:
>
>
Yeah that makes sense, however what they say on their sites is contradictory
to what they do provide (the parent POM of javax.mail:mail):
http://search.maven.org/#artifactdetails%7Ccom.sun.mail%7Call%7C1.4.5%7Cpom
which brings:
javax.activation
activation
On Sat, Jun 9, 2012 at 12:50 PM, Babak Vahdat
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/CAM
The other option could be also to modify the tests like:
if (jdk7) {
assertEquals("application/octet-stream ...", handler.getContentType());
} else {
assertEquals("image/jpeg ...", handler.getContentType());
}
Babak Vahdat wrote
>
> Hi
>
> The latest JDK 7 build went ALMOST well:
>
> ht
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 di
