On Wed, 15 Nov 2017 18:01:07 +0200 Adrian Bunk <b...@debian.org> wrote:
[...]
> I tried to sort out what I could find as required for getting the
> ancient eclipse out of testing in [1]:
> 
> 1. src:bnd
> You fixed that already.
> 
> 2. batik -> maven -> guice -> libspring-java -> aspectj -> eclipse-platform
> Is there some good way to break this dependency chain?
> 
> 3. split libequinox-osgi-java out of src:eclise
> Or as a short-term hack, build only libequinox-osgi-java from src:eclipse.

I have spent some time this weekend on Eclipse again. I have created a
standalone src:libequinox-osgi-java package and successfully rebuilt all
reverse-dependencies. We only have to make a small adjustment in
src:netbeans and src:libnb-platform18-java and update the osgi patch.

If there are no objections I could go ahead and upload
libequinox-osgi-java to NEW.

eclipse-rcp:

* svnkit:

There are two Eclipse specific classes that fail to build. As a
workaround we could remove one of them and patch SVNWCUtil.

* android-sdktools and android-platform-tools-swt

According to [1] both packages should be removed anyway.

After that there would be only three packages left (not counting the
eclipse plugins) that build-depend on either eclipse-platform (aspectj)
or eclipse-jdt (lombok, biogenesis)

Next I'm going to try if a separate eclipse-jdt package from [2] could
be a drop-in-replacement for our current package. The latest stable
release appears to be S4_8_0_M5.

Regards,

Markus

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879175#10
[2] https://github.com/eclipse/eclipse.jdt.core

__
This is the maintainer address of Debian's Java team
<http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers>. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Reply via email to