Path: csiph.com!aioe.org!.POSTED.O5hsyUvK01te0L/SZurVSQ.user.gioia.aioe.org!not-for-mail From: =?UTF-8?Q?Arne_Vajh=c3=b8j?= Newsgroups: comp.lang.java.programmer Subject: Re: more porting issues to Java 11 Date: Thu, 4 Apr 2019 20:08:55 -0400 Organization: Aioe.org NNTP Server Lines: 23 Message-ID: References: NNTP-Posting-Host: O5hsyUvK01te0L/SZurVSQ.user.gioia.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 X-Notice: Filtered by postfilter v. 0.9.2 Content-Language: en-US Xref: csiph.com comp.lang.java.programmer:38869 On 4/4/2019 10:11 AM, Andreas Leitgeb wrote: > Andreas Leitgeb 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. :-) I will consider to be "as expected" that one can get JAXB working in Java 11 as JAXB is a current technology. Arne