Date: Thu, 25 Jul 2013 09:59:00 +0200 From: Thomas Gellekum <Thomas.Gellekum@gmx.de> To: kron <kron24@gmail.com> Cc: freebsd-eclipse@freebsd.org Subject: Re: Upgrading java/eclipse and java/eclipse-devel Message-ID: <51F0DAC4.3010905@gmx.de> In-Reply-To: <51F0B78F.2030908@gmail.com> References: <0F5A2320-D5E0-4008-A065-E27959D54AA7@neville-neil.com> <51F0B78F.2030908@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 07/25/13 07:28, kron wrote: > On 2013/07/24 23:03, George Neville-Neil wrote: >> Howdy, >> >> Eclipse 4.2, which we have in java/eclipse-devel has been out for >> over a year and Eclipse 4.3 is "nearly done" as far as anyone can >> tell. It's been out for a few weeks now. >> I'd like to propose that we copy the devel port to the normal >> port, and then do two things. First I'd like to get Eclipse 4.2 >> working with openjdk7. RIght now the build fails but that was just a >> naive attempt to build the port with the new jdk. AFAIR, the problem lies with some of the 3rd party libraries (in ECLIPSE_*_BUNDLES) that were pre-built with a 1.4 or 1.5 JDK and miss necessary type info for some of the APIs that use generics. We could probably add ports for all those libraries and add appropriate OSGi headers to their manifests. This would also allow us to get rid of some of the patches to the manifest files which are a PITA to maintain. This could happen one library at a time, so it wouldn't have to be a disruptive process. IIRC, the problematic libraries are the sat4j bundles, so we'd start with those. Handling the versions requires some care, though, as different versions of Eclipse depend on different versions of those bundles. There might be an alternative: Kepler is supposed to be built with JDK7, so check for updates in those bundles. This sounds cheaper in the short term, but maintaing those patches is a major cost in the longer run. >> Secondly we can >> mark eclipse-devel broken until we can start getting 4.3 running in >> that port. Kepler (4.3) looks like it is going to be a major effort. I've only briefly checked the linuxtools.eclipse-build repo, but it seems they've abandoned the Ant based build and switched completely to Tycho, which is a Maven plugin. In theory, this should make things easier for us, too, but we don't have Tycho yet. Last time I looked at that, you needed a P2 repository from an Eclipse installation to build it, so bootstrapping is going to be an issue. I stopped digging further when I realized how much work it would be to provide a clean environment for building. Maven likes to load oodles of stuff from outside. Keeping that under control is not going to be much fun. tg
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51F0DAC4.3010905>