Re: Plugin module development with daily build on JDK9

Hello Geertjan,

thank You for clarifying this. BTW, Java 8 will reach EOL at some time 
in the future, so it needs to be done.

OTOH I understand, there will be issues especially with "friend" 
dependencies, which will need clarification. And some packages reside in 
multiple modules. So probably many lines of code will have to be 
reorganized and/or rewritten.

How can I participate in NB development, when it has moved to Apache, 
i.e. what do I need to do? Do I have to subscribe an agreement similar 
to that for NB at Sun (now NB at Oracle)?

I've already subscribed to [email protected].

Kind regards
Peter


Am 15.03.2017 um 09:46 schrieb geertjan wielenga:
>
> JDK9 support for NetBeans modules is currently not planned. That would
> be a massive task.
>
> It's something we as a community could look at when we're in Apache. The
> question is also what the benefit would be, etc. Indeed, something to
> investigate though not on the immediate roadmap.
>
> Gj
>
>
> On 15-3-2017 8:30, Peter Nabbefeld wrote:
>> Hello Martin,
>>
>> sorry, seems there's a problem with communication via Gmane.
>>
>> After re-thinking about the problem, it seems Java 9 is used for
>> syntax and dependency checking when running the dev build on JDK 9 (so
>> it becomes the default VM) - could You please check this?
>>
>> For NB modules: For which release is JDK 9 support planned for NB
>> modules? I'd guess You need a tool then to replace the XML based
>> dependency mechanism by modules-info.java (and fill this file with the
>> correct dependencies).
>>
>> Kind regards
>> Peter
>>
>>
>> Am 14.03.2017 um 16:06 schrieb Martin Balin:
>>> Peter,
>>> When you say "modules" do you mean NetBeans modules or JDK9 modules?
>>> NetBeans modules have to be developed for JDK8 platform, NB 9 will be
>>> built by JDK8.
>>> Martin
>>>
>>> On 13.3.2017 16:36, Peter Nabbefeld wrote:
>>>> No problem with JDK 8.
>>>>
>>>> Regards
>>>> P.
>>>>
>>>> Am 13.03.2017 um 15:55 schrieb Peter Nabbefeld:
>>>>> Hello Martin,
>>>>>
>>>>> (comments inlined)
>>>>>
>>>>> Am 13.03.2017 um 09:48 schrieb Martin Balin:
>>>>>> Hello Peter,
>>>>>> I've tried to open, compile and debug several module projects -
>>>>>> Java SE
>>>>>> with only 1 module inside dependencies among them defined. I've used
>>>>>> these projects several times in NB 9 dev builds. It works.
>>>>>> Can you file a bug for it? Exception,...
>>>>>>
>>>>>
>>>>> So, if it works for You, we should probably first find out about the
>>>>> differences. Did You use the same build? Probably it has to do with
>>>>> the
>>>>> default JDK, did You run NB on JDK9?
>>>>>
>>>>> BTW, I'm using Arch Linux.
>>>>>
>>>>>
>>>>>> And this is a development build, still far from release and
>>>>>> undergoing
>>>>>> major update for JDK9 so it might not work and it is not
>>>>>> guaranteed it
>>>>>> will work.
>>>>>>
>>>>>
>>>>> That's why I didn't file a bug yet.
>>>>>
>>>>> Kind regards
>>>>> P.
>>>>>
>>>>>> Regards,
>>>>>> Martin
>>>>>>
>>>>>> On 13.3.2017 08:21, Peter Nabbefeld wrote:
>>>>>>>
>>>>>>> Hello,
>>>>>>>
>>>>>>> as the JDK9 branch has been merged into default:
>>>>>>> How can I use it for module development?
>>>>>>>
>>>>>>> I'm running netbeans-dev-201703120002 on Java9, with the following
>>>>>>> results:
>>>>>>> 1. I cannot set the source level of modules to Java 9.
>>>>>>> 2. I cannot open existing modules (which worked until merge)
>>>>>>> 3. New modules can be created. However, dependencies don't work
>>>>>>> (which
>>>>>>> is essentially the same issue as [2])
>>>>>>>
>>>>>>> [2] IMHO is most important, currently - sth. is broken in
>>>>>>> dependencies
>>>>>>> management.
>>>>>>>
>>>>>>> Kind regards
>>>>>>> Peter
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>
>