NetBeans Forums

 FAQFAQ   SearchSearch   MemberlistMemberlist   RegisterRegister   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
  

Plugin module development with daily build on JDK9

 
Post new topic   Reply to topic    NetBeans Forums -> NetBeans Developers
View previous topic :: View next topic  
Author Message
Peter Nabbefeld
Posted via mailing list.





PostPosted: Mon Mar 13, 2017 7:23 am    Post subject: Plugin module development with daily build on JDK9 Reply with quote

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
Back to top
Martin Balin
Posted via mailing list.





PostPosted: Mon Mar 13, 2017 8:49 am    Post subject: Plugin module development with daily build on JDK9 Reply with quote

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

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.

Regards,
Martin

On 13.3.2017 08:21, Peter Nabbefeld wrote:
Quote:

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

Back to top
Peter Nabbefeld
Posted via mailing list.





PostPosted: Mon Mar 13, 2017 2:57 pm    Post subject: Plugin module development with daily build on JDK9 Reply with quote

Hello Martin,

(comments inlined)

Am 13.03.2017 um 09:48 schrieb Martin Balin:
Quote:
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.


Quote:
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.

Quote:
Regards,
Martin

On 13.3.2017 08:21, Peter Nabbefeld wrote:
Quote:

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



Back to top
Peter Nabbefeld
Posted via mailing list.





PostPosted: Mon Mar 13, 2017 3:38 pm    Post subject: Plugin module development with daily build on JDK9 Reply with quote

No problem with JDK 8.

Regards
P.

Am 13.03.2017 um 15:55 schrieb Peter Nabbefeld:
Quote:
Hello Martin,

(comments inlined)

Am 13.03.2017 um 09:48 schrieb Martin Balin:
Quote:
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.


Quote:
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.

Quote:
Regards,
Martin

On 13.3.2017 08:21, Peter Nabbefeld wrote:
Quote:

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






Back to top
Martin Balin
Posted via mailing list.





PostPosted: Tue Mar 14, 2017 3:07 pm    Post subject: Plugin module development with daily build on JDK9 Reply with quote

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:
Quote:
No problem with JDK 8.

Regards
P.

Am 13.03.2017 um 15:55 schrieb Peter Nabbefeld:
Quote:
Hello Martin,

(comments inlined)

Am 13.03.2017 um 09:48 schrieb Martin Balin:
Quote:
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.


Quote:
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.

Quote:
Regards,
Martin

On 13.3.2017 08:21, Peter Nabbefeld wrote:
Quote:

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








Back to top
Peter Nabbefeld
Posted via mailing list.





PostPosted: Wed Mar 15, 2017 8:21 am    Post subject: Plugin module development with daily build on JDK9 Reply with quote

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:
Quote:
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:
Quote:
No problem with JDK 8.

Regards
P.

Am 13.03.2017 um 15:55 schrieb Peter Nabbefeld:
Quote:
Hello Martin,

(comments inlined)

Am 13.03.2017 um 09:48 schrieb Martin Balin:
Quote:
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.


Quote:
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.

Quote:
Regards,
Martin

On 13.3.2017 08:21, Peter Nabbefeld wrote:
Quote:

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










Back to top
Peter Nabbefeld
Posted via mailing list.





PostPosted: Wed Mar 15, 2017 8:21 am    Post subject: Plugin module development with daily build on JDK9 Reply with quote

Hello Martin,

sorry, what I've written bore isn't correct, but cannot correct it
because it's not yet shown on Gmane - will have to re-write that later ...

Regards
P.

Am 14.03.2017 um 16:06 schrieb Martin Balin:
Quote:
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:
Quote:
No problem with JDK 8.

Regards
P.

Am 13.03.2017 um 15:55 schrieb Peter Nabbefeld:
Quote:
Hello Martin,

(comments inlined)

Am 13.03.2017 um 09:48 schrieb Martin Balin:
Quote:
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.


Quote:
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.

Quote:
Regards,
Martin

On 13.3.2017 08:21, Peter Nabbefeld wrote:
Quote:

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










Back to top
Peter Nabbefeld
Posted via mailing list.





PostPosted: Wed Mar 15, 2017 8:21 am    Post subject: Plugin module development with daily build on JDK9 Reply with quote

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:
Quote:
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:
Quote:
No problem with JDK 8.

Regards
P.

Am 13.03.2017 um 15:55 schrieb Peter Nabbefeld:
Quote:
Hello Martin,

(comments inlined)

Am 13.03.2017 um 09:48 schrieb Martin Balin:
Quote:
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.


Quote:
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.

Quote:
Regards,
Martin

On 13.3.2017 08:21, Peter Nabbefeld wrote:
Quote:

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










Back to top
geertjan



Joined: 22 Jan 2014
Posts: 978

PostPosted: Wed Mar 15, 2017 8:47 am    Post subject: Plugin module development with daily build on JDK9 Reply with quote

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:
Quote:
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:
Quote:
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:
Quote:
No problem with JDK 8.

Regards
P.

Am 13.03.2017 um 15:55 schrieb Peter Nabbefeld:
Quote:
Hello Martin,

(comments inlined)

Am 13.03.2017 um 09:48 schrieb Martin Balin:
Quote:
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.


Quote:
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.

Quote:
Regards,
Martin

On 13.3.2017 08:21, Peter Nabbefeld wrote:
Quote:

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











Back to top
Peter Nabbefeld
Posted via mailing list.





PostPosted: Wed Mar 15, 2017 9:01 am    Post subject: Plugin module development with daily build on JDK9 Reply with quote

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 address-removed.

Kind regards
Peter


Am 15.03.2017 um 09:46 schrieb geertjan wielenga:
Quote:

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:
Quote:
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:
Quote:
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:
Quote:
No problem with JDK 8.

Regards
P.

Am 13.03.2017 um 15:55 schrieb Peter Nabbefeld:
Quote:
Hello Martin,

(comments inlined)

Am 13.03.2017 um 09:48 schrieb Martin Balin:
Quote:
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.


Quote:
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.

Quote:
Regards,
Martin

On 13.3.2017 08:21, Peter Nabbefeld wrote:
Quote:

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













Back to top
geertjan



Joined: 22 Jan 2014
Posts: 978

PostPosted: Wed Mar 15, 2017 9:03 am    Post subject: Plugin module development with daily build on JDK9 Reply with quote

https://cwiki.apache.org/confluence/display/NETBEANS/How+to+Participate

Gj


On 15-3-2017 10:00, Peter Nabbefeld wrote:
Quote:
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 address-removed.

Kind regards
Peter


Am 15.03.2017 um 09:46 schrieb geertjan wielenga:
Quote:

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:
Quote:
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:
Quote:
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:
Quote:
No problem with JDK 8.

Regards
P.

Am 13.03.2017 um 15:55 schrieb Peter Nabbefeld:
Quote:
Hello Martin,

(comments inlined)

Am 13.03.2017 um 09:48 schrieb Martin Balin:
Quote:
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.


Quote:
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.

Quote:
Regards,
Martin

On 13.3.2017 08:21, Peter Nabbefeld wrote:
Quote:

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















Back to top
Svata Dedic
Posted via mailing list.





PostPosted: Wed Mar 15, 2017 12:11 pm    Post subject: Plugin module development with daily build on JDK9 Reply with quote

Hi,

The first thing to understand is that NB 9 release will be still
compiled against JDK8.

[*] So while NB 9 primarily aims support development for JDK9,
developing *NB-based applications* will be most probably well tested
only for JDK8 target.
Specifically the NetBeans own buildsystem is not (as a whole) prepared
to handle JDK9. Checks for various supplemental JARs fail as JDK has
changed layout etc. Many Ant tasks are totally unaware of different ways
how to read classes in JDK9 (nor jars, bud jmods), so they fail as well.
The harness used to run/debug applications may lack --add-opens,
--add-module switches, so the application may crash on reflective access
etc. You are welcome to provide patches - don't forget about Apache Ant
project as well.

Second. Given the definition of JDK9 modular system as specified *at
this point*, Jigsaw does not support *directly* many many features of NB
module system. Just to name few - OpenIDE-Module-Needs, Recommends,
Hide-Classpath-Packages ... entire versioning scheme is also out of
scope of (current) Jigsaw, I think.

So there is a lot of decisions to make, what features to keep, which
ones can be approximated using Jigsaw, which need to be dropped and what
will be the effect on NetBeans platform -- all those are nontrivial to
decide, and even harder to implement. "A tool that replaces XML based
definition" is a great underestimation of the problem, I am afraid.

Back to the real and immediate problems.

1/ allowing source level 9 for NetBeans module development is easy to
code, but because of [*], it may help but many corner cases handled by
harness will simply fail. I would prefer consistency ("NB modules must
be developed for JDK8 platform") over bleeding edge here.
Again - contributions are welcome, as always.

2/ I need more information on that. I was able to _open_ any modules
(Nb, samples) when running on JDK9 - but immediately run into issues in
editor - these are being fixed right now.
If you were not able to _open_ a module project - please elaborate /
send logs / file issues.

3/ What does mean "dependencies do not work" ? If the editor marks
identifier from the dependency as error/unknown - I've found that
yesterday, and it is being fixed. The key point is that the module can
be compiled, just the editor turned mad.
If your observations are different - please elaborate.

Thanks for the testing !
-Svata

Dne 15.3.2017 v 08:30 Peter Nabbefeld napsal(a):
Quote:
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:
Quote:
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:
Quote:
No problem with JDK 8.

Regards
P.

Am 13.03.2017 um 15:55 schrieb Peter Nabbefeld:
Quote:
Hello Martin,

(comments inlined)

Am 13.03.2017 um 09:48 schrieb Martin Balin:
Quote:
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.


Quote:
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.

Quote:
Regards,
Martin

On 13.3.2017 08:21, Peter Nabbefeld wrote:
Quote:

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











Back to top
Display posts from previous:   
Post new topic   Reply to topic    NetBeans Forums -> NetBeans Developers All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB
By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo