On Wed, Nov 15, 2017 at 12:08:10AM +0100, Markus Koschany wrote: >... > We should definitely try to avoid this sort of dependency mess in the > future by packaging important libraries like eclipse-rcp in a separate > source package. That would be similar to what we are doing whith > Netbeans and libnb-platform18-java at the moment. It simply ensures that > we can resolve such issues more easily by dropping the hard to maintain > IDE but keeping other important dependencies which don't require that > much effort in theory.
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. > Regards, > > Markus cu Adrian [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880470#10 -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
