javamail 1.3.2 ist available and should be in the portage tree. 'dev-java/sun-javamail-bin' has fetch restriction turned on and if you want to download the needed zip file it's hard to do so for version 1.3.1. a version bump should be enough Reproducible: Always Steps to Reproduce:
it's enough to change 'At="javamail-${PV//./_}-upd.zip"' to 'At="javamail-${PV//./_}.zip"'
i added a direct link to 1.3.1 so its 'easy' to get ;) not bumping to 1.3.2 yet since it requires jdk 1.5
*** Bug 81009 has been marked as a duplicate of this bug. ***
*** Bug 84176 has been marked as a duplicate of this bug. ***
Just putting another vote in for this version bump. Works fine here. ~x86
JDK 1.5.0 is only required for SASL IMAP support. A simple warning after the emerge should suffice. The fixes and changes in 1.3.2 are _plenty_ to warrant an upgrade despite this version issue.
Moreover, a new version of javamail has been recently released. The current version is 1.3.3, and contains over 20 bug fixes and enhancements, as described on: http://java.sun.com/products/javamail/downloads/index.html And the jdk-1.5.0 requirement is no longer valid, according to the docs: http://java.sun.com/products/javamail/README.txt [quote] ------------------------------ README JavaMail(TM) API 1.3.3 release JDK Version notes The JavaMail API supports JDK 1.1.x or higher, including the Java 2 platform, Standard Edition (J2SE) 1.2.x, 1.3.x, 1.4.x, and 1.5.x. Note that we have currently tested this implementation only with JDK 1.1.8 and J2SE 1.3, 1.4, and 1.5. ------------------------------ [/quote] Please consider creating a new ebuild and putting it in the Portage tree. Usual steps can be taken, like keywording it ~arch, but the upgraded ebuild should go into the tree. Thanks!
Consider checking gnu-javamail. We are heading towards preferring the OSS implementations over the sun ones. It would be nice to get feedback from people coding against/using javamail.
Added to CVS.
