Hi Niels, > The reason why you cannot see the dependency is probably that you looked > at the binary package eclipse. The package actually depending on > liblucene2-java is eclipse-platform, which is (also) built from a source > package called eclipse. :) > > The reason why we need to modify eclipse is because we got some > non-trivial with plugins not being loaded in eclipse if some > dependencies where upgraded. This lead to #587657, which started out > with a problem sat4j, but we later learned lucene2 produced a similar > effect (e.g. see message #125). > The issue is particularly annoying as it is non-trivial to debug why > this happens, because eclipse silently degrades itself in most cases and > the rest it says something like "Cannot open editor > org.eclipse.cdt.editor.CEdtior, class not found". Neither helps the > user to realise they have to manually fix a file that is out of date.
thanks for the detailed explanation. I fear that backporting a complex package as eclipse-platform is out of scope for me at the moment, sorry. Thanks for maintaining lucene in Debian! Ciao, Ferdinando -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
