Both. That is the netbeans_jdkhome in netbeans.conf points to m2/../images/jdk and the platform of the created Maven project is the default platform (ie the same path). What's having immediate issues though is the later, as changing to a platform pointing to a jdk9/jdk9 build clears those issues. The platform manager shows no jars for jigsaw/m2 so if Netbeans does its look up on those jars then it is 'normal' that it does not find any classes. I didn't mention but the Netbeans installer would not recognise the image as valid.
On Sun, Oct 12, 2014 at 10:11 PM, Alan Bateman <[email protected]> wrote: > On 12/10/2014 19:55, Ludovic HOCHET wrote: >> >> Hello Alan, >> Copying the DLL to the bin directory fixes the issue for jconsole yes. >> After jconsole, my sanity checks continue with Netbeans which launch >> fine (provided I disable JavaFX) but has then issues when editing code >> (my take it doesn't find everything it expects in a JDK, ie jars as it >> complains of missing java.lang, not unexpected). >> Maven on the same hello world is fine though. >> > Does your test launch NetBeans with --jdkhome to point to your build of > jigsaw/m? Or maybe you mean that you added your build of jigsaw/m2 as a > platform and created a project that uses it? In any case, NetBeans and other > IDEs that read scan the JDK image for JAR files is an area that will need > attention. One long standing suggestion is a "finder API" to be used in > conjunction with javax.lang.model to avoid needing to poke around in the JDK > image. > > -Alan. -- Ludovic ----------------------------------------- "Les formes qui differencient les etres importent peu si leur pensees s'unissent pour batir un univers..." Yoko Tsuno (in 'Les titans' by Roger Leloup) [The shapes that differenciate beings are not important if their thoughts unite to build a universe]
