Re: Plugin module development with daily build on JDK9

Peter Nabbefeld <[email protected]> Wed, 15 Mar 2017 07:59:00 +0100
Newsgroups gmane.comp.java.netbeans.devel
Message-ID <[email protected]>
Hello Martin,

while I'd prefer to be able to develop NB 9 modules using Java 9, I can 
only create module projects targeting Java 8. However, dependencies on 
other NB modules seem to be only handled correctly only with NB 9 
running on JDK 8.

When I start NB 9 on Java 9 (so it becomes the default platform), 
dependencies aren't resolved. Probably they're expected to be Java 9 for 
some unknown reason.

As NB 9 is about Java 9 development, IMHO it should be possible to 
develop NB modules using Java 9, too, or there should be a roadmap at least.

I understand, using the Java 9 module system will interfere with NB 
module system, as Java 9 is about partitioning, while NB is about 
dependencies, so it should be forbidden to use Java 9 modules, but this 
has to be defined somewhere. E.g. module-info.java should be flagged as 
an error with an appropriate message in a module project. OTOH, Java 9 
modules may be useful for platform projects and/or module suites to 
exclude unused modules. This also needs NB to be cut in pieces.

So, Java 9 support for NB development IMO should look like this:
1. Support Java 9 source code
2. Flag module-info.java in default package as an error
3. Support Java 9 module includes for suites

I'd propose to handle the first two issues in NB 9.0 and defer the third 
to NB 9.1.

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
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>
>