Please stablise =dev-util/eclipse-sdk-3.5.1-r1 I realise that -r1 hasn't been in the tree a month but the changes where minor and -r0 has been in for well over a month. This ebuild will have the give stable users the highest quality eclipse gentoo package ever. It is light years better than 3.4
Please include dev-java/swt-3.5.2 in this instead of swt-3.5.1 because it resolves UI problems with gtk+-2.18 (which is already stable as I can see) such as buttons not responding to mouse clicks. I just noticed I forgot to commit 3.5.2 month ago, so I did it just now. But the rc1 which was already in tree for months is the same internal version, there were no changes between so it should be fine without waiting.
dev-java/swt-3.5.2 dev-java/icu4j-4.0.1.1 dev-java/sat4j-core-2.1 dev-java/sat4j-pseudo-2.1 dev-util/eclipse-sdk-3.5.1-r1 amd64 stable
dev-java/swt-3.5.2 dev-java/icu4j-4.0.1.1 dev-java/sat4j-core-2.1 dev-java/sat4j-pseudo-2.1 dev-util/eclipse-sdk-3.5.1-r1 on x86 Help -> Software Updates -> Find and Install cannot connect to any update site. The following error is produced: Network connection problems encountered during search. Unable to access "http://download.eclipse.org/eclipse/updates/3.5". Unable to access site: "http://download.eclipse.org/eclipse/updates/3.5" [Server returned HTTP response code: "403 Forbidden" for URL: http://download.eclipse.org/eclipse/updates/3.5.] Server returned HTTP response code: "403 Forbidden" for URL: http://download.eclipse.org/eclipse/updates/3.5. Unable to access site: "http://download.eclipse.org/eclipse/updates/3.5" [Server returned HTTP response code: "403 Forbidden" for URL: http://download.eclipse.org/eclipse/updates/3.5.] Server returned HTTP response code: "403 Forbidden" for URL: http://download.eclipse.org/eclipse/updates/3.5. The Help -> Install New Software works fine, but you need to manually add the Galileo site.
Sadly that sounds similar to a known upstream issue. Which is "unfixable" :|
Well in that case, it works fine x86 ;) On a side not there are some issues with the slotting and workspaces. For example if you open ~/workspace with 3.4 the with 3.5 and then again with 3.4 very strange things start happening in both versions.
(In reply to comment #5) > On a side not there are some issues with the slotting and workspaces. For > example if you open ~/workspace with 3.4 the with 3.5 and then again with 3.4 > very strange things start happening in both versions. That's not surprising. However workspaces are completely under user control and people that keep multiple slots use them in different workspaces. Most could be done is ewarn.
I have test failures in TestBigDecimals for dev-java/icu4j-4.0.1.1...anyone can reproduce?
(In reply to comment #7) > I have test failures in TestBigDecimals for dev-java/icu4j-4.0.1.1...anyone can > reproduce? > If by test failures you mean FEATURES=test for icu4j-4.0.1.1 then no, all my tests appear to pass.
(In reply to comment #8) > (In reply to comment #7) > > I have test failures in TestBigDecimals for dev-java/icu4j-4.0.1.1...anyone can > > reproduce? > > > > If by test failures you mean FEATURES=test for icu4j-4.0.1.1 then no, all my > tests appear to pass. Can anyone from x86 team please reproduce?
I get exactly the same testsuite-failure like Christian.
As said in bug 299082, tests fail only with icedtea. Looking at the test code it seems to assume too much about conversions between doubles and strings, will probably have to kill this test...
Go on!
(In reply to comment #11) > As said in bug 299082, tests fail only with icedtea. Ok, i had to uninstall icedtea! java-config -S wasn't enough! :-) I haven't tested the rest so far...
(In reply to comment #13) > (In reply to comment #11) > > As said in bug 299082, tests fail only with icedtea. > > Ok, i had to uninstall icedtea! java-config -S wasn't enough! :-) > I haven't tested the rest so far... Erm I've fixed the bug, you should've resync/update. Also system vm != build vm http://www.gentoo.org/doc/en/java.xml
eclipse-sdk fails with ecj-3.5 as compiler, javac is fine (on icedtea-bin): init: @dot: [mkdir] Created dir: /var/tmp/portage/dev-util/eclipse-sdk-3.5.1-r1/work/eclipse-build-R0_4_0/build/eclipse-R3_5_1-fetched-src/plugins/org.eclipse.equinox.common/@dot [javac] Compiling 52 source files to /var/tmp/portage/dev-util/eclipse-sdk-3.5.1-r1/work/eclipse-build-R0_4_0/build/eclipse-R3_5_1-fetched-src/plugins/org.eclipse.equinox.common/@dot [javac] expansion argument file @/var/tmp/portage/dev-util/eclipse-sdk-3.5.1-r1/work/eclipse-build-R0_4_0/build/eclipse-R3_5_1-fetched-src/plugins/org.eclipse.equinox.common/javaCompiler...args does not exist or cannot be read
(In reply to comment #15) > eclipse-sdk fails with ecj-3.5 as compiler, javac is fine (on icedtea-bin): Yeah the ebuild already forces javac: 09 Apr 2010; Vlastimil Babka <caster@gentoo.org> eclipse-sdk-3.5.1-r1.ebuild: Force javac, as building with ecj fails, probably due to classpath polution. If you're testing this with JAVA_PKG_FORCE_COMPILER, IIRC you override this :)
Sorry, the forcing really didn't work. Fixed.
stable x86, thanks Andreas, closing
(In reply to comment #1) > Please include dev-java/swt-3.5.2 in this instead of swt-3.5.1 because it > resolves UI problems with gtk+-2.18 (which is already stable as I can see) such > as buttons not responding to mouse clicks. x86 please do the swt as well
dev-java/swt-3.5.2 also passed all tests on my side.
Sorry, x86 no definitely stable.
Argh, "now"
