Path: csiph.com!eternal-september.org!feeder.eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: Andreas Leitgeb <avl@logic.at>
Newsgroups: comp.lang.java.programmer
Subject: Re: more porting issues to Java 11
Date: Thu, 4 Apr 2019 14:11:38 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 18
Message-ID: <slrnqac44q.cfl.avl@logic.at>
References: <slrnqa9qsg.cfl.avl@logic.at> <q82u07$1rii$1@gioia.aioe.org> <q82u80$1t7b$1@gioia.aioe.org> <slrnqabvgs.cfl.avl@logic.at>
Reply-To: avl@logic.at
Injection-Date: Thu, 4 Apr 2019 14:11:38 -0000 (UTC)
Injection-Info: reader02.eternal-september.org; posting-host="e62b29e720dbf7aab24875ead4725a5d"; logging-data="9688"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/F1wOg8ga85Ks3qKkoEZAG"
User-Agent: slrn/1.0.3 (Linux)
Cancel-Lock: sha1:rRYQBuJ1LDAhcDlsgyXnva5PIO4=
Xref: csiph.com comp.lang.java.programmer:38864

Andreas Leitgeb <avl@logic.at> wrote:
> Now, the new question driving me crazy is: why doesn't eclipse find
> org.w3c.dom.Document, when it perfectly well can find
> javax.xml.namespace.NamespaceContext almost right next to the other,
> and why doesn't it find javax.xml.namespace.NamespaceContext anymore
> once I add a jar file with org.w3c.dom.Document ?.

Well, after a pause to cool down from fury, I now got to not just look
at the red wavy lines, but actually trying to understand their message...

It turned out, that some of the jar files in the classpath were really
too much, because the message really said, that the particular packages
were found both in unnamed and some of Java's modules.

Kicking those jars out of the classpath was the way to go.

Remains the quest for some JDK11-compatible Corba...