How important is OSGi support?

[Peter Nabbefeld]

Hello,

OSGi support is obviously broken since NB 9, see 
https://github.com/mojohaus/nbm-maven-plugin/issues/52 for details. I've 
created NETBEANS-1638 as a critical bug.


The question here is, how important is OSGi for functionality of 
NetBeans itself (e.g. JEE support), i.e. does it probably need to be a 
blocker?


Kind regards

Peter

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: How important is OSGi support?

[Peter Nabbefeld]

That's been my question about: I do not know if some module needs OSGi, 
JEE was just an idea for what could *probably* need OSGi. Probably my 
question wasn't exact.


Kind regards
Peter


Am 09.11.18 um 18:47 schrieb Emilian Bold:

PS: I what way is the broken OSGi break our JEE support? I would like
to see an issue explaining this.

--emi

On Fri, Nov 9, 2018 at 2:23 PM Peter Nabbefeld  wrote:


Hello,

OSGi support is obviously broken since NB 9, see
https://github.com/mojohaus/nbm-maven-plugin/issues/52 for details. I've
created NETBEANS-1638 as a critical bug.

The question here is, how important is OSGi for functionality of
NetBeans itself (e.g. JEE support), i.e. does it probably need to be a
blocker?

Kind regards

Peter

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists






-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: VC3 - JDK11 - gradle plugin

[Peter Nabbefeld]

Hello Mike,

the stack trace looks really strange - like some endless loop in the 
compiler. Could You probably just try to use any other JDK 9+, probably 
even JDK 12 EA?


Kind regards

Peter



Am 13.11.18 um 13:54 schrieb Mike Billman:

Laszlo/Geertjan -

After working with the plugin developer, we suspect it might be a nb issue.  I 
submitted a JIRA ticket.  As I have not done this before, I would welcome 
feedback on anything I could do to assist in this process.

https://issues.apache.org/jira/browse/NETBEANS-1668

Mike

-Original Message-
From: Mike Billman 
Sent: Wednesday, November 7, 2018 8:15 AM
To: dev@netbeans.incubator.apache.org
Subject: RE: VC3 - JDK11 - gradle plugin

Submitted issue with plugin...getting out of memory error.  Thanks for the 
help.  Running under JDK8, not having any issues.

Mike

-Original Message-
From: Laszlo Kishalmi 
Sent: Tuesday, November 6, 2018 6:17 PM
To: dev@netbeans.incubator.apache.org
Subject: Re: VC3 - JDK11 - gradle plugin

Well, JDK 11 has some issues with Gradle. You need to have at least Gradle 4.10 
to get the project loaded.

If you prefer to use the wrapper it is going to fail.

On 11/6/18 1:38 PM, Mike Billman wrote:

Of course...i just wasn't sure how to tell if it was the plugin or the ide.

Mike

-Original Message-
From: Geertjan Wielenga 
Sent: Tuesday, November 6, 2018 3:52 PM
To: dev@netbeans.incubator.apache.org
Subject: Re: VC3 - JDK11 - gradle plugin

Can you report issues with the Gradle plugin on the Gradle plugin site, please?

Gj

On Tuesday, November 6, 2018, Mike Billman

wrote:


Hi – it would appear I am having some issue related to either
environment, netbeans itself, or the gradle plugin.  I have tried
multiple times to load a large project running netbeans pointed to
11.0.1.  However, each time it stops at “background scanning of
projects” and I can’t do anything more meaningful.  Jumping to points
in the code doesn’t work etc.  I would like to try to provide more information, 
but I am not at all sure how.



VC3 seems to work fine if I run against JDK8u191.  At this point, all
of our code runs against jdk8 anyways, so this isn’t necessarily a
big issue, but I would like to try to understand where the problem is
so I can report it properly.  Can anybody give some suggestions or is
anybody else having issues with the gradle plugin?



Thanks!



Mike Billman

Senior Software Engineer

CPTE



[image: qclogo]



11800 Conrey Rd


Suite 150


Cincinnati, OH 45249




T +1 513 469 1424

E mikebill...@qcsoftware.com

F +1 513 469 1425




-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail:
dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists



-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists





-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: VC3 - JDK11 - gradle plugin

[Peter Nabbefeld]

I don't use gradle, and I don't want to install it, so I can only ask:
Is there, by any chance, an existing or generated "module-info.java" file?

The stack trace seems to originate from a recursive call:

1. From Modules.completeModule to Modules.retrieveRequiresTransitive:
(NOTE: During initialization (inInitModules == true) completer is set to 
lambda expression calling Modules.completeModule as Completer instance)


 for (RequiresDirective d : msym.requires) {
    d.module.complete();
    readable.add(d.module);
    Set s = retrieveRequiresTransitive(d.module);

2. Modules.retrieveRequiresTransitive calls ModuleSymbol.complete (see 
for-loop).
Because of the initialization (see NOTE on [1]), ModuleSymbol.complete 
calls Modules.completeModule again.


What I've not yet investigated is: what are the conditions to not 
enforce the recursive behavior? It seems, in "usual" cases the recursion 
stops at some point, while in Your case it doesn't.


IMHO, this seems to be a JDK problem (if there're cyclic dependencies, 
an error should be logged and compilation should just stop), but I'm not 
a JDK expert. OTOH, there seems to be a problem with Your dependencies, 
so You'd check Your dependencies graph. As method 
"retrieveRequiresTransitive" is involved, please check also if all 
dependencies are available at runtime.


Kind regards

Peter



Am 13.11.18 um 17:39 schrieb Mike Billman:

Tried really quick...same results.  Even deleted cache.

Mike

-Original Message-
From: Mike Billman 
Sent: Tuesday, November 13, 2018 11:02 AM
To: dev@netbeans.incubator.apache.org
Subject: RE: VC3 - JDK11 - gradle plugin

I'll give that a try tomorrow.  Thanks for the idea.

Mike

-Original Message-
From: Peter Nabbefeld 
Sent: Tuesday, November 13, 2018 10:59 AM
To: dev@netbeans.incubator.apache.org
Subject: Re: VC3 - JDK11 - gradle plugin


Hello Mike,

the stack trace looks really strange - like some endless loop in the compiler. 
Could You probably just try to use any other JDK 9+, probably even JDK 12 EA?

Kind regards

Peter



Am 13.11.18 um 13:54 schrieb Mike Billman:

Laszlo/Geertjan -

After working with the plugin developer, we suspect it might be a nb issue.  I 
submitted a JIRA ticket.  As I have not done this before, I would welcome 
feedback on anything I could do to assist in this process.

https://issues.apache.org/jira/browse/NETBEANS-1668

Mike

-Original Message-
From: Mike Billman 
Sent: Wednesday, November 7, 2018 8:15 AM
To: dev@netbeans.incubator.apache.org
Subject: RE: VC3 - JDK11 - gradle plugin

Submitted issue with plugin...getting out of memory error.  Thanks for the 
help.  Running under JDK8, not having any issues.

Mike

-Original Message-
From: Laszlo Kishalmi 
Sent: Tuesday, November 6, 2018 6:17 PM
To: dev@netbeans.incubator.apache.org
Subject: Re: VC3 - JDK11 - gradle plugin

Well, JDK 11 has some issues with Gradle. You need to have at least Gradle 4.10 
to get the project loaded.

If you prefer to use the wrapper it is going to fail.

On 11/6/18 1:38 PM, Mike Billman wrote:

Of course...i just wasn't sure how to tell if it was the plugin or the ide.

Mike

-Original Message-
From: Geertjan Wielenga 
Sent: Tuesday, November 6, 2018 3:52 PM
To: dev@netbeans.incubator.apache.org
Subject: Re: VC3 - JDK11 - gradle plugin

Can you report issues with the Gradle plugin on the Gradle plugin site, please?

Gj

On Tuesday, November 6, 2018, Mike Billman

wrote:


Hi – it would appear I am having some issue related to either
environment, netbeans itself, or the gradle plugin.  I have tried
multiple times to load a large project running netbeans pointed to
11.0.1.  However, each time it stops at “background scanning of
projects” and I can’t do anything more meaningful.  Jumping to
points in the code doesn’t work etc.  I would like to try to provide more 
information, but I am not at all sure how.



VC3 seems to work fine if I run against JDK8u191.  At this point,
all of our code runs against jdk8 anyways, so this isn’t necessarily
a big issue, but I would like to try to understand where the problem
is so I can report it properly.  Can anybody give some suggestions
or is anybody else having issues with the gradle plugin?



Thanks!



Mike Billman

Senior Software Engineer

CPTE



[image: qclogo]



11800 Conrey Rd
<https://maps.google.com/?q=11800+Conrey+Rd+%0D%0A+Suite+150+%0D%0A+
C i ncinnati,+OH+45249&entry=gmail&source=g>

Suite 150
<https://maps.google.com/?q=11800+Conrey+Rd+%0D%0A+Suite+150+%0D%0A+
C i ncinnati,+OH+45249&entry=gmail&source=g>

Cincinnati, OH 45249
<https://maps.google.com/?q=11800+Conrey+Rd+%0D%0A+Suite+150+%0D%0A+
C i ncinnati,+OH+45249&entry=gmail&source=g>



T +1 513 469 1424

E mikebill...@qcsoftware.com

F +1 513 469 1425




-

OSGi support for maven-based plugins

[Peter Nabbefeld]

Hello,

is there any progress in OSGi support?

I'm still trying to do some plugin development which uses a dependency 
which is an OSGi module (JAXB). I've been told, Felix 4.2.1 (as bundled 
with NB up to version 10-vc4) won't work with JDK 9.0+. I'm not able to 
fix that myself, as I've not yet used OSGi modules in plugin 
development, so even if I apply the proposed patch, I'll not be able to 
do any testing on it (I'd never know if the result is correct).


So I'd be glad if anybody could help me on this issue (see also 
NETBEANS-1638) or tell me how to work around it.


Kind regards

Peter

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: OSGi support for maven-based plugins

[Peter Nabbefeld]

Hm, this part of the discussion wasn't clear to me: as both are 
integrated, how do I decide which one will be used for modules? And do 
You probably know an open-source project using OSGi modules as 
dependencies succesfully, which I could use as a reference?


Kind regards

Peter


Am 15.12.18 um 16:42 schrieb Emilian Bold:

 From the discussion back then there was no real problem because by default
we use Equinox (via the Netbinox fork).

It's only the non-default Felix that's broken and I believe there was a
patch for this which basically upgraded to a newer Felix version.

--emi

On Sat, 15 Dec 2018 at 16:08, Peter Nabbefeld 
wrote:


Hello,

is there any progress in OSGi support?

I'm still trying to do some plugin development which uses a dependency
which is an OSGi module (JAXB). I've been told, Felix 4.2.1 (as bundled
with NB up to version 10-vc4) won't work with JDK 9.0+. I'm not able to
fix that myself, as I've not yet used OSGi modules in plugin
development, so even if I apply the proposed patch, I'll not be able to
do any testing on it (I'd never know if the result is correct).

So I'd be glad if anybody could help me on this issue (see also
NETBEANS-1638) or tell me how to work around it.

Kind regards

Peter

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists



--

--emi

http://coolbeans.xyz/ - CoolBeans: An IDE for Java, JavaEE, PHP and more!




-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: OSGi support for maven-based plugins

[Peter Nabbefeld]

Thank You, that's exactly what I've been looking for. :))

This will help me to locate my problem, as I should be able to see now, 
if it's my project's problem or if just OSGi modules don't work with 
JDK9+, currently, despite of the patch.


Kind regards

Peter


Am 15.12.18 um 23:41 schrieb Matthias Bläsing:

Hi again,

Am Samstag, den 15.12.2018, 23:24 +0200 schrieb Emilian Bold:

I believe Peter was asking for an open-source project related to
NetBeans (Platform) that uses successfully OSGi dependencies.

ok, maybe this is nearer to the question:

https://github.com/redminenb/redminenb

that is the redmine integration into the netbeans issue tracking
support. There are four OSGI dependencies:

- Eclipse Mylyn WikiText
- Eclipse Mylyn WikiText Textile
- Apache Commons Logging
- Apache Commons Lang

As visible there: There is no direct support for osgi dependencies, but
na ack was needed.

Greetings


Matthias


-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists






-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: OSGi support for maven-based plugins

[Peter Nabbefeld]

Thank You again, Matthias. I've still some questions.

But first, I should show my exception:

java.io.IOException: Cannot enable 
StandardModule:org.netbeans.modules.pm.DocsTree jarFile: 
/home/peter/NetBeansProjects/ProjectManagement/DocsTree/target/nbm/netbeans/extra/modules/org-netbeans-modules-pm-DocsTree.jar; 
problems: [module com.sun.xml.bind.jaxb_impl > 2.3.0.1, module 
com.sun.xml.bind.jaxb_core > 2.3.0.1, module jaxb_api > 2.3.0]
    at 
org.netbeans.core.startup.ModuleSystem.deployTestModule(ModuleSystem.java:423)
    at 
org.netbeans.core.startup.TestModuleDeployer.deployTestModule(TestModuleDeployer.java:46)
[catch] at 
org.netbeans.modules.maven.apisupport.ExecutionChecker.executionResult(ExecutionChecker.java:69)
    at 
org.netbeans.modules.maven.execute.MavenCommandLineExecutor.run(MavenCommandLineExecutor.java:303)
    at 
org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:128)


The interesting part is the line "at 
org.netbeans.modules.maven.execute.MavenCommandLineExecutor.run(MavenCommandLineExecutor.java:303)": 
Probably some parameters are missing, maybe the class path.


I've noticed, the RedmineNB POM generates entries for "X-Class-Path" and 
"Maven-Class-Path" in target/classes/META-INF/MANIFEST.MF, while only 
"X-Class-Path" seems to be used as "Class-Path" in the NBM file created. 
I couldn't find out how to create this entry, yet, but probably that's 
the missing part?


Kind regards

Peter



Am 15.12.18 um 23:41 schrieb Matthias Bläsing:

Hi again,

Am Samstag, den 15.12.2018, 23:24 +0200 schrieb Emilian Bold:

I believe Peter was asking for an open-source project related to
NetBeans (Platform) that uses successfully OSGi dependencies.

ok, maybe this is nearer to the question:

https://github.com/redminenb/redminenb

that is the redmine integration into the netbeans issue tracking
support. There are four OSGI dependencies:

- Eclipse Mylyn WikiText
- Eclipse Mylyn WikiText Textile
- Apache Commons Logging
- Apache Commons Lang

As visible there: There is no direct support for osgi dependencies, but
na ack was needed.

Greetings


Matthias


-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists






-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Netbinox install area?

[Peter Nabbefeld]

Hi,

when running a module project, I get the following messages in the IDE log:

[INFO] WARNING [org.netbeans.modules.netbinox]: Cannot compute install 
area. No common prefix between /usr/share/netbeans-incubator-10.0-vc5/ 
and 
/home/peter/NetBeansProjects/ProjectManagement/DocsTree/target/netbeans_clusters/docstree
[INFO] INFO [org.netbeans.modules.netbinox]: Install area set to 
file:/usr/share/netbeans-incubator-10.0-vc5/


I do understand the cause (NetBeans platform is set to 
"/usr/share/netbeans-incubator-10.0-vc5/" while it uses 
"/home/peter/NetBeansProjects/ProjectManagement/DocsTree/target/netbeans_clusters/docstree" 
as execution context is in 
"/home/peter/NetBeansProjects/ProjectManagement/DocsTree/target/netbeans_clusters/docstree"), 
but I'd like to know if I could change the installation folder for Netbinox?


Kind regards

Peter

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Netbinox install area?

[Peter Nabbefeld]

Why? Behaviour is like I'd expect it, the question is, if it can be 
changed, and how it can be changed, i.e. if there exists any parameter 
to configure NetBeans which installation folder to use (I'd even just 
use it to get rid of the warning).


Kind regards

Peter


Am 23.12.18 um 13:18 schrieb Geertjan Wielenga:

when running a module project


A lot more is needed than that in order to reproduce this.

Gj

On Sun, Dec 23, 2018 at 12:49 PM Peter Nabbefeld 
wrote:


Hi,

when running a module project, I get the following messages in the IDE log:

[INFO] WARNING [org.netbeans.modules.netbinox]: Cannot compute install
area. No common prefix between /usr/share/netbeans-incubator-10.0-vc5/
and

/home/peter/NetBeansProjects/ProjectManagement/DocsTree/target/netbeans_clusters/docstree
[INFO] INFO [org.netbeans.modules.netbinox]: Install area set to
file:/usr/share/netbeans-incubator-10.0-vc5/

I do understand the cause (NetBeans platform is set to
"/usr/share/netbeans-incubator-10.0-vc5/" while it uses
"/home/peter/NetBeansProjects/ProjectManagement/DocsTree/target/netbeans_clusters/docstree"

as execution context is in
"/home/peter/NetBeansProjects/ProjectManagement/DocsTree/target/netbeans_clusters/docstree"),

but I'd like to know if I could change the installation folder for
Netbinox?

Kind regards

Peter

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists







-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Netbinox install area?

[Peter Nabbefeld]

Em, sorry, running NB 10 VC5, I'm using latest NB 10 currently, so 
forgot to mention ...


However, this should be the case with every version.

Regards

Peter



Am 23.12.18 um 14:47 schrieb Peter Nabbefeld:
Why? Behaviour is like I'd expect it, the question is, if it can be 
changed, and how it can be changed, i.e. if there exists any parameter 
to configure NetBeans which installation folder to use (I'd even just 
use it to get rid of the warning).


Kind regards

Peter


Am 23.12.18 um 13:18 schrieb Geertjan Wielenga:

when running a module project


A lot more is needed than that in order to reproduce this.

Gj

On Sun, Dec 23, 2018 at 12:49 PM Peter Nabbefeld 


wrote:


Hi,

when running a module project, I get the following messages in the 
IDE log:


[INFO] WARNING [org.netbeans.modules.netbinox]: Cannot compute install
area. No common prefix between /usr/share/netbeans-incubator-10.0-vc5/
and

/home/peter/NetBeansProjects/ProjectManagement/DocsTree/target/netbeans_clusters/docstree 


[INFO] INFO [org.netbeans.modules.netbinox]: Install area set to
file:/usr/share/netbeans-incubator-10.0-vc5/

I do understand the cause (NetBeans platform is set to
"/usr/share/netbeans-incubator-10.0-vc5/" while it uses
"/home/peter/NetBeansProjects/ProjectManagement/DocsTree/target/netbeans_clusters/docstree" 



as execution context is in
"/home/peter/NetBeansProjects/ProjectManagement/DocsTree/target/netbeans_clusters/docstree"), 



but I'd like to know if I could change the installation folder for
Netbinox?

Kind regards

Peter

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists







-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists






-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

java.lang.UnsupportedOperationException: command: clean, JavaRunner ...

[Peter Nabbefeld]

Hello,

I'm getting the following exception when running and (re-)deploying a 
module in NB 10:


java.lang.UnsupportedOperationException: command: clean, JavaRunner 
impls: [org.netbeans.modules.java.source.ant.ProjectRunnerImpl@3a5bd107]
    at 
org.netbeans.api.java.project.runner.JavaRunner.execute(JavaRunner.java:303)
    at 
org.netbeans.modules.maven.cos.CosChecker.cleanGeneratedClassfiles(CosChecker.java:295)
    at 
org.netbeans.modules.maven.cos.CosChecker.touchProject(CosChecker.java:482)
    at 
org.netbeans.modules.maven.cos.CosChecker$CosPOH$1.propertyChange(CosChecker.java:643)
    at 
java.desktop/java.beans.PropertyChangeSupport.fire(PropertyChangeSupport.java:341)
    at 
java.desktop/java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:333)
    at 
java.desktop/java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:266)
    at 
org.netbeans.modules.maven.api.NbMavenProject.doFireReload(NbMavenProject.java:550)
    at 
org.netbeans.modules.maven.api.NbMavenProject.access$200(NbMavenProject.java:72)
    at 
org.netbeans.modules.maven.api.NbMavenProject$AccessorImpl.doFireReload(NbMavenProject.java:118)
    at 
org.netbeans.modules.maven.NbMavenProjectImpl$1.run(NbMavenProjectImpl.java:130)

Caused: org.openide.util.RequestProcessor$SlowItem: task failed due to
    at 
org.openide.util.RequestProcessor$Task.schedule(RequestProcessor.java:1459)
    at 
org.netbeans.modules.maven.NbMavenProjectImpl.fireProjectReload(NbMavenProjectImpl.java:463)
    at 
org.netbeans.modules.maven.api.NbMavenProject.fireProjectReload(NbMavenProject.java:544)
    at 
org.netbeans.modules.maven.api.NbMavenProject.fireMavenProjectReload(NbMavenProject.java:564)
    at 
org.netbeans.modules.maven.NbMavenProjectImpl$Updater.fileChanged(NbMavenProjectImpl.java:934)
    at 
org.openide.filesystems.FileChangeImpl.fileChanged(FileChangeImpl.java:111)
    at 
org.openide.filesystems.FCLSupport$DispatchEventWrapper.dispatchEventImpl(FCLSupport.java:153)
    at 
org.openide.filesystems.FCLSupport$DispatchEventWrapperSingle.dispatchAllEventsSync(FCLSupport.java:199)
    at 
org.openide.filesystems.FCLSupport$DispatchEventWrapper.dispatchEvent(FCLSupport.java:112)

    at org.openide.filesystems.FCLSupport.dispatchEvent(FCLSupport.java:80)
    at org.openide.filesystems.FileObject$ED.dispatch(FileObject.java:1373)
    at 
org.openide.filesystems.EventControl.invokeDispatchers(EventControl.java:188)
    at 
org.openide.filesystems.EventControl.exitAtomicAction(EventControl.java:163)
    at 
org.openide.filesystems.EventControl.runAtomicAction(EventControl.java:104)
    at 
org.openide.filesystems.FileSystem.runAtomicAction(FileSystem.java:494)
    at 
org.netbeans.modules.maven.M2AuxilaryConfigImpl$2.run(M2AuxilaryConfigImpl.java:126)
    at 
org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1418)
    at 
org.netbeans.modules.openide.util.GlobalLookup.execute(GlobalLookup.java:45)

    at org.openide.util.lookup.Lookups.executeWith(Lookups.java:278)
[catch] at 
org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2033)


At the moment, I'd just like to know, if this is a bug in Maven support 
or if it's just a problem restarting the "slave" IDE.


Steps to reproduce are in my case:
1. Start NB
2. Run the module project (which starts the "slave" IDE)
3. Try to re-deploy the module in the slave

As You can see, the stack trace shows an UnsupportedOperationException 
for the "clean" command, but it's caused by a problem at 
org.netbeans.modules.maven.NbMavenProjectImpl.fireProjectReload


Kind regards

Peter

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Netbinox install area?

[Peter Nabbefeld]

It's not just a duplicate, but rather sth. I noticed while investigating 
the problems. However, since I'm sure it doesn't have any effect on the 
issue, I'm just interested in the possibility to change some parameter.


Just opened my platform module and started it by pressing the "Run" 
button, which starts the module in a "new" IDE (which is effectively a 
copy of the one I'm using to build the module).


Well, AFAIK, it's not a physical copy of the full IDE, but it uses the 
original IDE (if configured as the Development IDE) with a copy of the 
original user dir, which may cause problems if there're some core 
modules replaced (if installed globally on linux in /usr/share, there're 
restricted permissions ...).


So, it would be interesting, if a module like Netbinox (or probably even 
other modules, too) could be loaded from a given folder.


OTOH, this doesn't have anything to do with my problems, as I've 
installed the Felix replacement (using the provided patch) using sudo 
into my global installation, it's only a question about the 
possibilities for parametrization.


Kind regards

Peter



Am 23.12.18 um 17:46 schrieb Emilian Bold:

Peter is continuing his quest of running OSGi modules inside the
Platform (on top of Equinox / Netbinox). I know this since we talked
about this in another thread but I understand how Geertjan might be
confused. For me it's rather clear what the problem is but I don't
really have the time to duplicate the issue on my system. My 2c.

--emi

http://coolbeans.xyz/ - CoolBeans: An IDE for Java, JavaEE, PHP and more!

On Sun, Dec 23, 2018 at 4:58 PM Geertjan Wielenga
 wrote:

I’m sorry, I am not able to help. For me “when running a module project” is
not enough info. Tell me exactly what to do, what the expected outcome is,
what the actual outcome is, I am not going to guess. Complete environment
needs to he described too. Ignoring this thread until these details are
provided.

Gj

On Sunday, December 23, 2018, Peter Nabbefeld 
wrote:


Em, sorry, running NB 10 VC5, I'm using latest NB 10 currently, so forgot
to mention ...

However, this should be the case with every version.

Regards

Peter



Am 23.12.18 um 14:47 schrieb Peter Nabbefeld:


Why? Behaviour is like I'd expect it, the question is, if it can be
changed, and how it can be changed, i.e. if there exists any parameter to
configure NetBeans which installation folder to use (I'd even just use it
to get rid of the warning).

Kind regards

Peter


Am 23.12.18 um 13:18 schrieb Geertjan Wielenga:


when running a module project

A lot more is needed than that in order to reproduce this.

Gj

On Sun, Dec 23, 2018 at 12:49 PM Peter Nabbefeld 
when running a module project, I get the following messages in the IDE
log:

[INFO] WARNING [org.netbeans.modules.netbinox]: Cannot compute install
area. No common prefix between /usr/share/netbeans-incubator-10.0-vc5/
and

/home/peter/NetBeansProjects/ProjectManagement/DocsTree/target/netbeans_clusters/docstree

[INFO] INFO [org.netbeans.modules.netbinox]: Install area set to
file:/usr/share/netbeans-incubator-10.0-vc5/

I do understand the cause (NetBeans platform is set to
"/usr/share/netbeans-incubator-10.0-vc5/" while it uses
"/home/peter/NetBeansProjects/ProjectManagement/DocsTree/tar
get/netbeans_clusters/docstree"

as execution context is in
"/home/peter/NetBeansProjects/ProjectManagement/DocsTree/tar
get/netbeans_clusters/docstree"),

but I'd like to know if I could change the installation folder for
Netbinox?

Kind regards

Peter

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists






-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists





-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists





-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.o

[OT] Does anybody know what happened to NBPython?

[Peter Nabbefeld]

Hello,

I've got a question about Python support: AFAIK, it was maintained via 
nbpython.org, but it seems inactive. So, there're plenty of sources in 
the "old" contrib repository, which should probably also be moved to 
apache, but without any responsible maintainer the required license 
changes will not be possible.


Anybody here knowing more?

Kind regards

Peter

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [OT] Does anybody know what happened to NBPython?

[Peter Nabbefeld]

Thank You, happy to read about that!

P.



Am 29.12.18 um 11:11 schrieb Geertjan Wielenga:

https://cwiki.apache.org/confluence/display/NETBEANS/Apache+Transition

You'll see it's scheduled for the 5th donation.

Gj


On Sat, Dec 29, 2018 at 11:04 AM Peter Nabbefeld 
wrote:


Hello,

I've got a question about Python support: AFAIK, it was maintained via
nbpython.org, but it seems inactive. So, there're plenty of sources in
the "old" contrib repository, which should probably also be moved to
apache, but without any responsible maintainer the required license
changes will not be possible.

Anybody here knowing more?

Kind regards

Peter

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists







-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

How to migrate German wiki entry to Apache?

[Peter Nabbefeld]

Hello,

I've found a German wiki entry, which does not seem to have an English 
counterpart:

http://wiki.netbeans.org/DevFaqCodeCompletionJavaAware_DE

How is it possible to migrate it into new Apache infrastructure?

Another issue is about blog links in those "old" articles, as they often 
still refer to blogs.sun.com - the new Oracle structure has different 
paths. Would it be possible, to add those blogs to Apache, too, probably 
even using the original headline paths? This would make it easier to 
find those referenced blog entries.


Kind regards

Peter

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Cannot build NetBeans from source

[Peter Nabbefeld]

Hello,

cannot build NetBeans from source:
- using git sources/master branch from 
https://github.com/apache/incubator-netbeans.git

- using NB10 with java-11-openjdk on Arch Linux
- ~/incubator-netbeans/nbbuild/user.build.properties contains 
nbjdk.home=/usr/lib64/jvm/java-8-openjdk



The problem cause is probably direct use of  in the applemenu 
module's build script, as I get the following error messages:


/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:22: 
error: package java.awt.desktop does not exist

import java.awt.desktop.AboutEvent;
/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:23: 
error: package java.awt.desktop does not exist

import java.awt.desktop.AboutHandler;
/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:24: 
error: package java.awt.desktop does not exist

import java.awt.desktop.OpenFilesEvent;
/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:25: 
error: package java.awt.desktop does not exist

import java.awt.desktop.OpenFilesHandler;
/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:26: 
error: package java.awt.desktop does not exist

import java.awt.desktop.PreferencesEvent;
/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:27: 
error: package java.awt.desktop does not exist

import java.awt.desktop.PreferencesHandler;
/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:28: 
error: package java.awt.desktop does not exist

import java.awt.desktop.QuitEvent;
/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:29: 
error: package java.awt.desktop does not exist

import java.awt.desktop.QuitHandler;
/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:30: 
error: package java.awt.desktop does not exist

import java.awt.desktop.QuitResponse;
/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:40: 
error: cannot find symbol
public class NbApplicationAdapterJDK9 extends NbApplicationAdapter 
implements AboutHandler, OpenFilesHandler, PreferencesHandler, QuitHandler {

  symbol: class AboutHandler

It seems, the desktop classes are missing because the module does not 
respect nbjdk.home setting, so JDK 11 is used instead.


Kind regards

Peter


-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Cannot build NetBeans from source

[Peter Nabbefeld]

Conditions are all met, simply the build file for applemenu module does 
not respect the settings for nbjdk.home. My best bet will be just to 
remove the module from cluster.properties file. However, the build file 
should be fixed, probably ...


P.


Am 29.12.18 um 15:14 schrieb Geertjan Wielenga:

https://github.com/apache/incubator-netbeans/blob/master/README.md

Gj

On Sat, Dec 29, 2018 at 1:29 PM Peter Nabbefeld 
wrote:


Hello,

cannot build NetBeans from source:
- using git sources/master branch from
https://github.com/apache/incubator-netbeans.git
- using NB10 with java-11-openjdk on Arch Linux
- ~/incubator-netbeans/nbbuild/user.build.properties contains
nbjdk.home=/usr/lib64/jvm/java-8-openjdk


The problem cause is probably direct use of  in the applemenu
module's build script, as I get the following error messages:

/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:22:

error: package java.awt.desktop does not exist
import java.awt.desktop.AboutEvent;
/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:23:

error: package java.awt.desktop does not exist
import java.awt.desktop.AboutHandler;
/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:24:

error: package java.awt.desktop does not exist
import java.awt.desktop.OpenFilesEvent;
/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:25:

error: package java.awt.desktop does not exist
import java.awt.desktop.OpenFilesHandler;
/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:26:

error: package java.awt.desktop does not exist
import java.awt.desktop.PreferencesEvent;
/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:27:

error: package java.awt.desktop does not exist
import java.awt.desktop.PreferencesHandler;
/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:28:

error: package java.awt.desktop does not exist
import java.awt.desktop.QuitEvent;
/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:29:

error: package java.awt.desktop does not exist
import java.awt.desktop.QuitHandler;
/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:30:

error: package java.awt.desktop does not exist
import java.awt.desktop.QuitResponse;
/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:40:

error: cannot find symbol
public class NbApplicationAdapterJDK9 extends NbApplicationAdapter
implements AboutHandler, OpenFilesHandler, PreferencesHandler, QuitHandler
{
symbol: class AboutHandler

It seems, the desktop classes are missing because the module does not
respect nbjdk.home setting, so JDK 11 is used instead.

Kind regards

Peter


-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists







-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Cannot build NetBeans from source

[Peter Nabbefeld]

The README describes how to build NB from the console - I don't want 
that. If I cannot use an IDE for building, I could just use a text 
editor. BTW, memory is not a problem on my system - 4GB should be 
sufficient for NB, otherwise I could increase -Xmx.


P.


Am 29.12.18 um 18:44 schrieb Geertjan Wielenga:

There is nothing in the README about nbjdk.home. Please follow the
instructions in the README:

https://github.com/apache/incubator-netbeans/blob/master/README.md

Gj


On Sat, Dec 29, 2018 at 6:41 PM Peter Nabbefeld 
wrote:


Conditions are all met, simply the build file for applemenu module does
not respect the settings for nbjdk.home. My best bet will be just to
remove the module from cluster.properties file. However, the build file
should be fixed, probably ...

P.


Am 29.12.18 um 15:14 schrieb Geertjan Wielenga:

https://github.com/apache/incubator-netbeans/blob/master/README.md

Gj

On Sat, Dec 29, 2018 at 1:29 PM Peter Nabbefeld 
wrote:


Hello,

cannot build NetBeans from source:
- using git sources/master branch from
https://github.com/apache/incubator-netbeans.git
- using NB10 with java-11-openjdk on Arch Linux
- ~/incubator-netbeans/nbbuild/user.build.properties contains
nbjdk.home=/usr/lib64/jvm/java-8-openjdk


The problem cause is probably direct use of  in the applemenu
module's build script, as I get the following error messages:



/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:22:

error: package java.awt.desktop does not exist
import java.awt.desktop.AboutEvent;


/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:23:

error: package java.awt.desktop does not exist
import java.awt.desktop.AboutHandler;


/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:24:

error: package java.awt.desktop does not exist
import java.awt.desktop.OpenFilesEvent;


/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:25:

error: package java.awt.desktop does not exist
import java.awt.desktop.OpenFilesHandler;


/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:26:

error: package java.awt.desktop does not exist
import java.awt.desktop.PreferencesEvent;


/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:27:

error: package java.awt.desktop does not exist
import java.awt.desktop.PreferencesHandler;


/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:28:

error: package java.awt.desktop does not exist
import java.awt.desktop.QuitEvent;


/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:29:

error: package java.awt.desktop does not exist
import java.awt.desktop.QuitHandler;


/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:30:

error: package java.awt.desktop does not exist
import java.awt.desktop.QuitResponse;


/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:40:

error: cannot find symbol
public class NbApplicationAdapterJDK9 extends NbApplicationAdapter
implements AboutHandler, OpenFilesHandler, PreferencesHandler,

QuitHandler

{
 symbol: class AboutHandler

It seems, the desktop classes are missing because the module does not
respect nbjdk.home setting, so JDK 11 is used instead.

Kind regards

Peter


-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists






-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists







-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Cannot build NetBeans from source

[Peter Nabbefeld]

The point is: I've configured nbbuild to use OpenJDK 8, but it doesn't 
respect the properties in every module - so IMHO this is a bug in the 
build scripts. I thought this would only be a problem with applemenu, 
but currently I get problems with other modules, too, so it's probably 
also sth. up the hierarchy (i.e. in projectized.xml).


Kind regards

Peter



Am 29.12.18 um 19:21 schrieb Geertjan Wielenga:

Please read this again:

https://github.com/apache/incubator-netbeans/blob/master/README.md

You cannot build NetBeans with a JDK greater than JDK 8.

Gj


On Sat, Dec 29, 2018 at 7:20 PM Gary Bello  wrote:


re building netbeans source;
i can always successfully build netbeans with nb82 - since it is running
jdk8 in my case;
when running nb9+ netbeans with jdk newer than jdk8 builds usually fail.

this seems to be documented - to build suppose to use jdk8;

i also would like to know how to build netbeans with newer jdk than jdk8,
-Gary



On Sat, Dec 29, 2018 at 9:44 AM Geertjan Wielenga
 wrote:


There is nothing in the README about nbjdk.home. Please follow the
instructions in the README:

https://github.com/apache/incubator-netbeans/blob/master/README.md

Gj


On Sat, Dec 29, 2018 at 6:41 PM Peter Nabbefeld 
wrote:


Conditions are all met, simply the build file for applemenu module does
not respect the settings for nbjdk.home. My best bet will be just to
remove the module from cluster.properties file. However, the build file
should be fixed, probably ...

P.


Am 29.12.18 um 15:14 schrieb Geertjan Wielenga:

https://github.com/apache/incubator-netbeans/blob/master/README.md

Gj

On Sat, Dec 29, 2018 at 1:29 PM Peter Nabbefeld <

peter.nabbef...@gmx.de>

wrote:


Hello,

cannot build NetBeans from source:
- using git sources/master branch from
https://github.com/apache/incubator-netbeans.git
- using NB10 with java-11-openjdk on Arch Linux
- ~/incubator-netbeans/nbbuild/user.build.properties contains
nbjdk.home=/usr/lib64/jvm/java-8-openjdk


The problem cause is probably direct use of  in the

applemenu

module's build script, as I get the following error messages:



/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:22:

error: package java.awt.desktop does not exist
import java.awt.desktop.AboutEvent;


/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:23:

error: package java.awt.desktop does not exist
import java.awt.desktop.AboutHandler;


/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:24:

error: package java.awt.desktop does not exist
import java.awt.desktop.OpenFilesEvent;


/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:25:

error: package java.awt.desktop does not exist
import java.awt.desktop.OpenFilesHandler;


/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:26:

error: package java.awt.desktop does not exist
import java.awt.desktop.PreferencesEvent;


/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:27:

error: package java.awt.desktop does not exist
import java.awt.desktop.PreferencesHandler;


/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:28:

error: package java.awt.desktop does not exist
import java.awt.desktop.QuitEvent;


/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:29:

error: package java.awt.desktop does not exist
import java.awt.desktop.QuitHandler;


/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:30:

error: package java.awt.desktop does not exist
import java.awt.desktop.QuitResponse;


/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:40:

error: cannot find symbol
public class NbApplicationAdapterJDK9 extends NbApplicationAdapter
implements AboutHandler, OpenFilesHandler, PreferencesHandler,

QuitHandler

{
 symbol: class AboutHandler

It seems, the desktop classes are missing because the module does

not

respect nbjdk.home setting, so JDK 11 is used instead.

Kind regards

Peter




-

To unsubscribe, e-mail:

dev-unsubscr...@netbeans.incubator.apache.org

For additional commands, e-mail:

dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists






-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additio

Re: Cannot build NetBeans from source

[Peter Nabbefeld]

That's the answer I'd liked to get the first time.

But now I have to be contradictory, as I get errors in a platform 
module, too:
/home/peter/incubator-netbeans/platform/core.network/src/org/netbeans/core/network/proxy/pac/impl/ClassFilterPacHelpers.java:21: 
error: package jdk.nashorn.api.scripting does not exist

import jdk.nashorn.api.scripting.ClassFilter;

That's why I guessed it has sth. to do with projectized.xml in my other 
post (Nashorn should be available at least up to JDK 10).


However, in this case the dependency should be removed completely, as 
Nashorn is scheduled for removal in JDK 11 (didn't check JDK 12, yet).


Kind regards

Peter



Am 29.12.18 um 19:25 schrieb Geertjan Wielenga:

The platform cluster can already be built by JDKs later than 8, more work
needs to be done in the other clusters to enable this there too.

Gj

On Sat, Dec 29, 2018 at 7:21 PM Geertjan Wielenga <
geertjan.wiele...@googlemail.com> wrote:


Please read this again:

https://github.com/apache/incubator-netbeans/blob/master/README.md

You cannot build NetBeans with a JDK greater than JDK 8.

Gj


On Sat, Dec 29, 2018 at 7:20 PM Gary Bello  wrote:


re building netbeans source;
i can always successfully build netbeans with nb82 - since it is running
jdk8 in my case;
when running nb9+ netbeans with jdk newer than jdk8 builds usually fail.

this seems to be documented - to build suppose to use jdk8;

i also would like to know how to build netbeans with newer jdk than jdk8,
-Gary



On Sat, Dec 29, 2018 at 9:44 AM Geertjan Wielenga
 wrote:


There is nothing in the README about nbjdk.home. Please follow the
instructions in the README:

https://github.com/apache/incubator-netbeans/blob/master/README.md

Gj


On Sat, Dec 29, 2018 at 6:41 PM Peter Nabbefeld 
Conditions are all met, simply the build file for applemenu module

does

not respect the settings for nbjdk.home. My best bet will be just to
remove the module from cluster.properties file. However, the build

file

should be fixed, probably ...

P.


Am 29.12.18 um 15:14 schrieb Geertjan Wielenga:

https://github.com/apache/incubator-netbeans/blob/master/README.md

Gj

On Sat, Dec 29, 2018 at 1:29 PM Peter Nabbefeld <

peter.nabbef...@gmx.de>

wrote:


Hello,

cannot build NetBeans from source:
- using git sources/master branch from
https://github.com/apache/incubator-netbeans.git
- using NB10 with java-11-openjdk on Arch Linux
- ~/incubator-netbeans/nbbuild/user.build.properties contains
nbjdk.home=/usr/lib64/jvm/java-8-openjdk


The problem cause is probably direct use of  in the

applemenu

module's build script, as I get the following error messages:



/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:22:

error: package java.awt.desktop does not exist
import java.awt.desktop.AboutEvent;


/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:23:

error: package java.awt.desktop does not exist
import java.awt.desktop.AboutHandler;


/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:24:

error: package java.awt.desktop does not exist
import java.awt.desktop.OpenFilesEvent;


/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:25:

error: package java.awt.desktop does not exist
import java.awt.desktop.OpenFilesHandler;


/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:26:

error: package java.awt.desktop does not exist
import java.awt.desktop.PreferencesEvent;


/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:27:

error: package java.awt.desktop does not exist
import java.awt.desktop.PreferencesHandler;


/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:28:

error: package java.awt.desktop does not exist
import java.awt.desktop.QuitEvent;


/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:29:

error: package java.awt.desktop does not exist
import java.awt.desktop.QuitHandler;


/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:30:

error: package java.awt.desktop does not exist
import java.awt.desktop.QuitResponse;


/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:40:

error: cannot find symbol
public class NbApplicationAdapterJDK9 extends NbApplicationAdapter
implements AboutHandler, OpenFilesHandler, PreferencesHandler,

QuitHandler

{
 symbol: class AboutHandler

It seems, the desktop classes are missing because the module does

not

respect nbjdk.home setting, so JDK 11 

Re: Cannot build NetBeans from source

[Peter Nabbefeld]

Thank You for Your answers! My problem is slightly more complex: NB has 
been able to compile its own sources most of the time, and IMHO it 
should be able to do that. The necessity of working around a buggy build 
system is not compatible to a high-quality IDE like NB has always been.


From this point of view, I don't just want to get it built somehow, but 
at least I want to know what's going wrong. I've noticed some strange 
points, and I want to share these and get some answers, as I'm 
interested in further improvements of NB, while I've currently not 
enough time to investigate the problems in the deep.  :-/


Kind regards

Peter



Am 29.12.18 um 19:19 schrieb Gary Bello:

re building netbeans source;
i can always successfully build netbeans with nb82 - since it is running
jdk8 in my case;
when running nb9+ netbeans with jdk newer than jdk8 builds usually fail.

this seems to be documented - to build suppose to use jdk8;

i also would like to know how to build netbeans with newer jdk than jdk8,
-Gary



On Sat, Dec 29, 2018 at 9:44 AM Geertjan Wielenga
 wrote:


There is nothing in the README about nbjdk.home. Please follow the
instructions in the README:

https://github.com/apache/incubator-netbeans/blob/master/README.md

Gj


On Sat, Dec 29, 2018 at 6:41 PM Peter Nabbefeld 
wrote:


Conditions are all met, simply the build file for applemenu module does
not respect the settings for nbjdk.home. My best bet will be just to
remove the module from cluster.properties file. However, the build file
should be fixed, probably ...

P.


Am 29.12.18 um 15:14 schrieb Geertjan Wielenga:

https://github.com/apache/incubator-netbeans/blob/master/README.md

Gj

On Sat, Dec 29, 2018 at 1:29 PM Peter Nabbefeld <

peter.nabbef...@gmx.de>

wrote:


Hello,

cannot build NetBeans from source:
- using git sources/master branch from
https://github.com/apache/incubator-netbeans.git
- using NB10 with java-11-openjdk on Arch Linux
- ~/incubator-netbeans/nbbuild/user.build.properties contains
nbjdk.home=/usr/lib64/jvm/java-8-openjdk


The problem cause is probably direct use of  in the

applemenu

module's build script, as I get the following error messages:



/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:22:

error: package java.awt.desktop does not exist
import java.awt.desktop.AboutEvent;


/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:23:

error: package java.awt.desktop does not exist
import java.awt.desktop.AboutHandler;


/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:24:

error: package java.awt.desktop does not exist
import java.awt.desktop.OpenFilesEvent;


/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:25:

error: package java.awt.desktop does not exist
import java.awt.desktop.OpenFilesHandler;


/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:26:

error: package java.awt.desktop does not exist
import java.awt.desktop.PreferencesEvent;


/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:27:

error: package java.awt.desktop does not exist
import java.awt.desktop.PreferencesHandler;


/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:28:

error: package java.awt.desktop does not exist
import java.awt.desktop.QuitEvent;


/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:29:

error: package java.awt.desktop does not exist
import java.awt.desktop.QuitHandler;


/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:30:

error: package java.awt.desktop does not exist
import java.awt.desktop.QuitResponse;


/home/peter/incubator-netbeans/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK9.java:40:

error: cannot find symbol
public class NbApplicationAdapterJDK9 extends NbApplicationAdapter
implements AboutHandler, OpenFilesHandler, PreferencesHandler,

QuitHandler

{
 symbol: class AboutHandler

It seems, the desktop classes are missing because the module does not
respect nbjdk.home setting, so JDK 11 is used instead.

Kind regards

Peter


-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail:

dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists






-

Re: Cannot build NetBeans from source

[Peter Nabbefeld]

Hi Matthias,


Am 29.12.18 um 20:27 schrieb Matthias Bläsing:

Hi Peter,

Am Samstag, den 29.12.2018, 20:20 +0100 schrieb Peter Nabbefeld:

Thank You for Your answers! My problem is slightly more complex: NB
has
been able to compile its own sources most of the time, and IMHO it
should be able to do that. The necessity of working around a buggy
build
system is not compatible to a high-quality IDE like NB has always
been.

I think we all agree on this and any work into that direction is
appretiated.

If I remember correctly though, netbeans was traditionally compiled
with JDK current - 1 and some time after release was fixed to be
compilable with the current JDK. Witht the faster release cadence of
the JDK and given the wide split: JDK 8 (non-modular) to JDK 11
(modular, deprecated modules removed), it was to be expected that
breakage occurs.


Ack. However, one of the problems seems to be rather old, but it pops up 
now because of Jigsaw: instead of only extending the features of Java, 
NB now must also handle removed features and probably their substitutes. 
That makes it very hard to support more than one JDK at the same time. 
As a result of this, I think there's no way to also support multiple 
JDKs for building NB, and of course it will be a challenge to support 
some recent JDK.


As a result of this, IMHO it's essential to implement a consistent build 
infrastructure, with every build script using the same JDK. This seems 
not to be the case, currently. In the past, as every JDK mostly extended 
existing features, that's not been a problem, but IMHO this is important 
now to be fixed.


Just for clarification: I don't have a problem with the fact, that I 
need JDK 8 for the build process. My problem just is, that I should be 
able to configure the build to use JDK 8, and then every build script 
should use that JDK. As a developer, it's essential for me to have 
several JDKs installed, but I'd need also build scripts using one JDK 
consistently.


Kind regards

Peter



Greetings

Matthias


-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists






-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Shall we make the "open project" dialog half of the screen size

[Peter Nabbefeld]

IMHO, the width is nearly sufficient (the "right part" showing the 
sub-projects could be a bit bigger, however), but the height should be 
increased - half the screen size would be nice, or even a bit more.


Kind regards

Peter


Am 30.12.18 um 12:25 schrieb Peter Cheung:

Hi
Shall we make the "open project" dialog half of the screen size? , i think 
it would be more user friendly. now is too small

In Line 445, 
ide/projectui/src/org/netbeans/modules/project/ui/ProjectChooserAccessory.java

  Dimension screenSize = Toolkit.getDefaultToolkit().getScreenSize();
  double width = screenSize.getWidth();
  double height = screenSize.getHeight();
  chooser.setPreferredSize(new Dimension((int)width/2, (int)height/2));

this will help


Thanks
 From Peter




-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Shall we make the "open project" dialog half of the screen size

[Peter Nabbefeld]

I'd see this as a matter of convenience, too, but as screen resolution 
increases, fixed-size boxes become smaller, so IMHO it's not a bad idea 
to depend on screen size.


P.



Am 30.12.18 um 13:26 schrieb Geertjan Wielenga:

Of course, these dialogs can simply be resized at any time by the user.

Gj

On Sun, Dec 30, 2018 at 1:23 PM Peter Nabbefeld 
wrote:


IMHO, the width is nearly sufficient (the "right part" showing the
sub-projects could be a bit bigger, however), but the height should be
increased - half the screen size would be nice, or even a bit more.

Kind regards

Peter


Am 30.12.18 um 12:25 schrieb Peter Cheung:

Hi
 Shall we make the "open project" dialog half of the screen size? , i

think it would be more user friendly. now is too small

In Line 445,

ide/projectui/src/org/netbeans/modules/project/ui/ProjectChooserAccessory.java

   Dimension screenSize = Toolkit.getDefaultToolkit().getScreenSize();
   double width = screenSize.getWidth();
   double height = screenSize.getHeight();
   chooser.setPreferredSize(new Dimension((int)width/2, (int)height/2));

this will help


Thanks
  From Peter



-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists







-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

[nbm-maven-plugin] How to add native libraries using maven?

[Peter Nabbefeld]

Hello,

I've got a problem adding a native library (libjep.so) to my plugin 
project. I've used the sample code from 
http://www.mojohaus.org/nbm-maven-plugin/nbm-mojo.html, so my plugin 
configuration is:


    
    org.codehaus.mojo
nbm-maven-plugin
    true
    
false
    
src/main/libs
modules/lib
    
    *.dll
    *.so
    
    
    
...
    
    
    
    ...
    
    
    
    

I've created a folder ${basedir}/src/main/libs and copied the native 
library into it, but the resulting nbm file does not contain the library 
after building.


What am I doing wrong?

Kind regards

Peter

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Porting 8.2 plugin to 10 problem

[Peter Nabbefeld]

Hi Peter,

the Generated annotation has moved somewhere, IIRC, so the annotation 
processor creates Java code with non-working imports. For the bundles, 
it will probably be better to use property files. Or better wait, until 
JDK > 8 is supported for module development, as modules targeted to NB 
8.x should still work in most cases.


Kind regards

Peter



Am 01.01.19 um 15:54 schrieb Peter Cheung:

Hi
I am porting my plugins to Netbeans 10, but all of them have this error. It 
auto generated a java file called Bundle.java and it is unable to compile since 
it can't find @javax.annotation.Generated

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile (default-compile) 
on project netbeans-antlr: Compilation failure: Compilation failure:
[ERROR] 
/Users/peter/workspace/netbeans-antlr/target/generated-sources/annotations/com/github/mcheung63/netbeans/antlr/syntax/antlr3/realtimecompile/Bundle.java:[3,17]
 error: cannot find symbol
[ERROR]   symbol:   class Generated
[ERROR]   location: package javax.annotation
[ERROR] 
/Users/peter/workspace/netbeans-antlr/target/generated-sources/annotations/com/github/mcheung63/netbeans/antlr/Bundle.java:[3,17]
 error: cannot find symbol
[ERROR]   symbol:   class Generated
[ERROR]   location: package javax.annotation
[ERROR] 
/Users/peter/workspace/netbeans-antlr/target/generated-sources/annotations/com/github/mcheung63/netbeans/antlr/syntax/antlr4/realtimecompile/Bundle.java:[3,17]
 error: cannot find symbol
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException


Thanks
 From Peter




-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

[OT] What's happening to nbpython.org?

[Peter Nabbefeld]

Hello,

as the Python source

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

[OT] What's happening to nbpython.org?

[Peter Nabbefeld]

Hello, and a Happy New Year!

As the Python source code will be donated to Apache NetBeans as part of 
main/contrib, what will happen to nbpython.org?


I Tried to sign in, but I've to wait for an administrator - does anybody 
know, if the there's still any activity? Somebody here who's involved in 
development of Python plugins?


Kind regards

Peter


-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [OT] What's happening to nbpython.org?

[Peter Nabbefeld]

Yes, I think You're right. But it seems, the code for the Python modules 
have been contributed by nbpython.org, and probably somebody of them is 
also involved here. So, if I cannot get in contact with the developers 
using their platform, asking here might probably help ...


Kind regards

Peter


Am 02.01.19 um 08:15 schrieb Emilian Bold:

nbpython.org does not belong to Apache afaik.

--emi

http://coolbeans.xyz/ - CoolBeans: An IDE for Java, JavaEE, PHP and more!

On Wed, Jan 2, 2019 at 9:01 AM Peter Nabbefeld  wrote:


Hello, and a Happy New Year!

As the Python source code will be donated to Apache NetBeans as part of
main/contrib, what will happen to nbpython.org?

I Tried to sign in, but I've to wait for an administrator - does anybody
know, if the there's still any activity? Somebody here who's involved in
development of Python plugins?

Kind regards

Peter


-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists






-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [OT] What's happening to nbpython.org?

[Peter Nabbefeld]

Hello Geertjan, Happy New Year!

It's nice the code will be donated - but the question is, who will 
maintain it?


Kind regards

Peter



Am 02.01.19 um 08:50 schrieb Geertjan Wielenga:

The code for Python support in NetBeans is in main/contrib which will be
part of the 5th donation:

https://cwiki.apache.org/confluence/display/NETBEANS/Apache+Transition

Gj


On Wed, Jan 2, 2019 at 8:49 AM Peter Nabbefeld 
wrote:


Yes, I think You're right. But it seems, the code for the Python modules
have been contributed by nbpython.org, and probably somebody of them is
also involved here. So, if I cannot get in contact with the developers
using their platform, asking here might probably help ...

Kind regards

Peter


Am 02.01.19 um 08:15 schrieb Emilian Bold:

nbpython.org does not belong to Apache afaik.

--emi

http://coolbeans.xyz/ - CoolBeans: An IDE for Java, JavaEE, PHP and

more!

On Wed, Jan 2, 2019 at 9:01 AM Peter Nabbefeld 

wrote:

Hello, and a Happy New Year!

As the Python source code will be donated to Apache NetBeans as part of
main/contrib, what will happen to nbpython.org?

I Tried to sign in, but I've to wait for an administrator - does anybody
know, if the there's still any activity? Somebody here who's involved in
development of Python plugins?

Kind regards

Peter


-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists





-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists







-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [nbm-maven-plugin] How to add native libraries using maven?

[Peter Nabbefeld]

Hi

Am 05.01.19 um 08:53 schrieb venkatram.akkin...@gmail.com:

Hi It has been a while since I've done this. So I may not be able to tell you 
right away by looking at your code without spending some time on it. So I've 
attached my module source code and the my plugin configuration below. See if it 
is any help.

 
 org.codehaus.mojo
 nbm-maven-plugin
 true
 
 
 
 
src/main/libs/11.0.0/native/linux/x86_64
 
modules/lib/11.0.0/native/linux/x86_64
 
 *.so
 
 
 
 
src/main/libs/11.0.0/native/linux/x86
 
modules/lib/11.0.0/native/linux/x86
 
 *.so
 
 
 
 
src/main/libs/11.0.0/native/win32/x86_64
 
modules/lib/11.0.0/native/win32/x86_64
 
 *.dll
 
 
 
 
src/main/libs/11.0.0/native/win32/x86
 
modules/lib/11.0.0/native/win32/x86
 
 *.dll
 
 
 
 
 
org.netbeans.modules.libswrapper
 
 com.microsoft.tfs.core
 
com.microsoft.tfs.core.clients.versioncontrol.workspacecache.internal
 
com.microsoft.tfs.core.clients.versioncontrol.soapextensions
 
com.microsoft.tfs.core.clients.versioncontrol
 
 
com.microsoft.tfs.core.clients.framework.configuration.entities
 
com.microsoft.tfs.core.exceptions
 
com.microsoft.tfs.core.httpclient
 com.microsoft.tfs.util
 
com.microsoft.tfs.core.util
 javax.xml.stream.events
 javax.xml.stream
 javax.xml.namespace
 javax.xml.stream.util
 
 Microsoft Visual Studio License
 
../MicrosoftVisualStudioLicense.txt
 
 

https://sourceforge.net/p/tfsonnb/code/ci/master/tree/LibsWrapper/





-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists






-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [nbm-maven-plugin] How to add native libraries using maven?

[Peter Nabbefeld]

Hi Venkatram,

thank You for sharing Your code!

Kind regards

Peter




Am 05.01.19 um 08:53 schrieb venkatram.akkin...@gmail.com:

Hi It has been a while since I've done this. So I may not be able to tell you 
right away by looking at your code without spending some time on it. So I've 
attached my module source code and the my plugin configuration below. See if it 
is any help.

 
 org.codehaus.mojo
 nbm-maven-plugin
 true
 
 
 
 
src/main/libs/11.0.0/native/linux/x86_64
 
modules/lib/11.0.0/native/linux/x86_64
 
 *.so
 
 
 
 
src/main/libs/11.0.0/native/linux/x86
 
modules/lib/11.0.0/native/linux/x86
 
 *.so
 
 
 
 
src/main/libs/11.0.0/native/win32/x86_64
 
modules/lib/11.0.0/native/win32/x86_64
 
 *.dll
 
 
 
 
src/main/libs/11.0.0/native/win32/x86
 
modules/lib/11.0.0/native/win32/x86
 
 *.dll
 
 
 
 
 
org.netbeans.modules.libswrapper
 
 com.microsoft.tfs.core
 
com.microsoft.tfs.core.clients.versioncontrol.workspacecache.internal
 
com.microsoft.tfs.core.clients.versioncontrol.soapextensions
 
com.microsoft.tfs.core.clients.versioncontrol
 
 
com.microsoft.tfs.core.clients.framework.configuration.entities
 
com.microsoft.tfs.core.exceptions
 
com.microsoft.tfs.core.httpclient
 com.microsoft.tfs.util
 
com.microsoft.tfs.core.util
 javax.xml.stream.events
 javax.xml.stream
 javax.xml.namespace
 javax.xml.stream.util
 
 Microsoft Visual Studio License
 
../MicrosoftVisualStudioLicense.txt
 
 

https://sourceforge.net/p/tfsonnb/code/ci/master/tree/LibsWrapper/





-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists






-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

GLF questions

[Peter Nabbefeld]

Hello,

I've got some questions about Generic Languages Framework (GLF):

1. I found two base packages in module "languages": 
"org.netbeans.api.languages" and "org.netbeans.modules.languages". While 
this is not unusual to NetBeans modules, the second one seems to include 
the "Schliemann" implementation (e.g. "NBSLanguage.java"). Shouldn't 
that be implemented in a separate module? IMHO, this would probably make 
bug-fixing easier.


2. Could somebody tell me, which classes are "general" (i.e. common 
implementation classes unrelated to "Schliemann") and which belong to 
the NBS implementation?


3. In the META-INF/netbeans folder, the file "translate.names" contains 
an entry "org.netbeans.modules.languages.dataobject.LanguagesOptions=", 
i.e. a key without a value - what is it used for?


Kind regards

Peter

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: GLF questions

[Peter Nabbefeld]

Another question:

4. What is the special "STAR" character in the Pattern class - is "STAR" 
an abbreviation for sth.?


The Directed Graph (DG) implementation is undocumented (as the rest of 
the language module, too), so very hard to read.  :-(


Kind regards

Peter



Am 07.01.19 um 16:15 schrieb Peter Nabbefeld:


Hello,

I've got some questions about Generic Languages Framework (GLF):

1. I found two base packages in module "languages": 
"org.netbeans.api.languages" and "org.netbeans.modules.languages". 
While this is not unusual to NetBeans modules, the second one seems to 
include the "Schliemann" implementation (e.g. "NBSLanguage.java"). 
Shouldn't that be implemented in a separate module? IMHO, this would 
probably make bug-fixing easier.


2. Could somebody tell me, which classes are "general" (i.e. common 
implementation classes unrelated to "Schliemann") and which belong to 
the NBS implementation?


3. In the META-INF/netbeans folder, the file "translate.names" 
contains an entry 
"org.netbeans.modules.languages.dataobject.LanguagesOptions=", i.e. a 
key without a value - what is it used for?


Kind regards

Peter

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists






-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Possible new splashscreen for NetBeans 9.0

[Peter Nabbefeld]

Hello all,

I'm working with NetBeans since several years, and I do like the 3D 
logo. The flat design maybe modern, but it's not the NetBeans logo, and 
I don't like it.


Just my opinion..

Kind Regards
Peter


Am 12.07.2017 um 13:13 schrieb Christian Lenz:

It was only to let you know that VS has the same logo for sure but in different 
shapes. I’m fine with the cube, but not with the 3D it has to look like a real 
cube thingy. We can use for example one of the cubes, from the Background from 
Dmitry for example. Everyone said yeah the logo was/is known, sure the VS logo 
too but it Looks different from time to time. Depents of what you said. So why 
not give the cube a new look and feel? All of the logos where proposals and as 
you can see there is still the cube, the black one. Not my style and maybe 
Needs a bit of a fix but yeah. I see often logos which Looks similar to others 
like the Company you said and WebPack and? What is the Problem, it depends on 
what you do via Marketing and so on. Webpack gave a fuck to the Company too. It 
is a complete other category.

The Problem with the old logo is that it doesn’t fit in the new style of the 
page for example and this is my opinion in the new style of your splash Screen 
too. So we can fully ignore the logo or we can rebrand the logo too but we 
should avoid to redesign the page or the splash Screen that it should fit 
because of the logo. Sure we can use e.g. NB with inside a cube or no cube, 
only a rectangle with NB inside or whatever. If anyone of you have ideas and 
are willing to Change smth, do it. I will create a ticket later and we can 
catch any splash Screens and logos and can vote.


Regards

Chris

Gesendet von Mail für Windows 10

Von: Siddhesh Rane
Gesendet: Mittwoch, 12. Juli 2017 12:44
An: dev@netbeans.incubator.apache.org
Betreff: RE: AW: AW: Possible new splashscreen for NetBeans 9.0

Here is a link to the history of Visual Studio logos along with timeline.
http://logos.wikia.com/wiki/Microsoft_Visual_Studio

If you'll observe there are just 3 logos as such and these follow the design 
language of whatever Windows version Microsoft had at the time. The first ones 
are clearly matching Windows XP, the infinity one suits Vista/7 and the current 
flat logo they have was introduced in 2012 to match windows 8. Microsoft 
changed logos to be consistent with their product range, not for the sake of 
change alone.

I saw the old logos of Intellij IDEA, PyCharm and RubyMine as well as 
Jetbrains. And I saw their current logos. What their current logos have is 
consistency of design language. So I can show you a logo of their least popular 
products and you'll still be able to identify that as an offering from 
Jetbrains. Here again their motive was consistency across their entire product 
range.

I did a quick Google Image search for Intellij IDEA splash screens and it seems 
Jetbrains is a bigger fan of vibrant images than us. Netbeans splash screens 
have been flat in comparison.
Even with their current text in a black box logos they haven't ditched 
vibrancy, with the gradient beams.
I guess their designers use 72" 4K LCD TVs as monitors.

Common to Microsoft and Jetbrains is that their logos are not too generic to 
have accidental correlation to any other brand's logo. And we have identified 
already 2 companies that have similar logos. We also don't have to abide by any 
operating systems ui choices because we are platform independent.
If at all we have to put out a message then it has to be about the Apache 
branding, as something good because Oracle's move raised a lot of questions 
about the future of Netbeans.

People in this thread have rightly pointed out to consistency, design 
philosophy and uniqueness to stand out. That's what they are asking for in the 
redesign.

Regards
Siddhesh Rane

 Christian Lenz wrote 


Please have a Look to the history of visual Studio. Everyone already Knows it 
after redesigned it from.time.to.time. the Logo and the ui. See the jetbrains 
Logos, and still known. It is more a marketing Thing to present a redesign and 
why. New organistation, why not having a new look/brand?



Von: Michael Müller
Gesendet: Dienstag, 11. Juli 2017 22:54
An: dev@netbeans.incubator.apache.org
Betreff: Re: AW: Possible new splashscreen for NetBeans 9.0

BTW: I'm talking about the solid silver cube, not about the old red line
drawing which is a sibling of a Visual Studio drawing.

And I like that proposal for a new splashscreen with that old logo too.
Personally, I prefer the word "NetBeans" a little bolder.


Herzliche Grüße - Best Regards,

Michael Müller
Brühl, Germany
blog.mueller-bruehl.de 
it-rezension.de 
@muellermi


Read my books
   "Web Development with Java and JSF": https://leanpub.com/jsf
   "Java Lambdas and Parallel Streams":
http://www.apress.com/de/book/9781484224861
   "Visitors" a photographic image book: https://leanpub.com/visitors


O

[NB Git] NetBeans does not compile with OpenJDK 8

[Peter Nabbefeld]

Hi,

I'm getting 
"/home/peter/incubator-netbeans/core.network/src/org/netbeans/core/network/proxy/pac/impl/ClassFilterPacHelpers.java:21: 
error: package jdk.nashorn.api.scripting does not exist", when trying to 
build NetBeans from incubator repository.


Value of "nbjdk.bootclasspath" is:
/usr/lib64/jvm/java-8-openjdk/jre/lib/charsets.jar:/usr/lib64/jvm/java-8-openjdk/jre/lib/jce.jar:/usr/lib64/jvm/java-8-openjdk/jre/lib/jfxswt.jar:/usr/lib64/jvm/java-8-openjdk/jre/lib/jsse.jar:/usr/lib64/jvm/java-8-openjdk/jre/lib/management-agent.jar:/usr/lib64/jvm/java-8-openjdk/jre/lib/resources.jar:/usr/lib64/jvm/java-8-openjdk/jre/lib/rt.jar

I tried to edit project.xml, adding the missing jar files, but got 
another problem:

...
Created dir: /home/peter/incubator-netbeans/libs.jsr223/build/classes
Compiling 1 source file to 
/home/peter/incubator-netbeans/libs.jsr223/build/classes

error: Source option 1.4 is no longer supported. Use 1.6 or later.
error: Target option 1.4 is no longer supported. Use 1.6 or later.
...

As libs.jsr223 is dummy only, it just should be removed, if possible.

And more of this:
Compiling 8 source files to 
/home/peter/incubator-netbeans/openide.util.enumerations/build/classes

error: Source option 1.4 is no longer supported. Use 1.6 or later.
error: Target option 1.4 is no longer supported. Use

Why are those outdated targets set?

And, because it seems others don't have the same problems: Is the 
repository url "https://github.com/apache/incubator-netbeans.git"; correct?


Kind regards
Peter


-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [NB Git] NetBeans does not compile with OpenJDK 8

[Peter Nabbefeld]

Hello Jan,

I created a file "nbjdk.home=/usr/lib64/jvm/java-8-openjdk" in the 
nbbuild folder as advised when I tried to just build NetBeans, but the 
build file itself seems not to always recognize this. I've not fully 
investigated this, however, so I might be wrong.


As far as I can see from the README file, it even seems nobody ever 
tried to build using NetBeans (ant seems to be used from the command 
line), so probably it's a problem with the execution environment. This 
seems also to be true for my Maven/OSGi problem, as the antrun plugin 
gets different runtime paths dependend of if the target directory 
already exists (runtime dependencies on other projects are resolved to 
jar files only if the target directory is deleted before running the 
project, otherwise resolved to the classes folder, which causes Felix to 
fail).


Kind regards
Peter


Am 05.01.2018 um 17:19 schrieb Jan Lahoda:

Hi Peter,

On Fri, Jan 5, 2018 at 3:44 PM, Peter Nabbefeld 
wrote:


Hi,

I'm getting "/home/peter/incubator-netbeans/core.network/src/org/netbean
s/core/network/proxy/pac/impl/ClassFilterPacHelpers.java:21: error:
package jdk.nashorn.api.scripting does not exist", when trying to build
NetBeans from incubator repository.

Value of "nbjdk.bootclasspath" is:
/usr/lib64/jvm/java-8-openjdk/jre/lib/charsets.jar:/usr/lib6
4/jvm/java-8-openjdk/jre/lib/jce.jar:/usr/lib64/jvm/java-8-
openjdk/jre/lib/jfxswt.jar:/usr/lib64/jvm/java-8-openjdk/
jre/lib/jsse.jar:/usr/lib64/jvm/java-8-openjdk/jre/lib/
management-agent.jar:/usr/lib64/jvm/java-8-openjdk/jre/lib/
resources.jar:/usr/lib64/jvm/java-8-openjdk/jre/lib/rt.jar

I tried to edit project.xml, adding the missing jar files, but got another
problem:
...
Created dir: /home/peter/incubator-netbeans/libs.jsr223/build/classes
Compiling 1 source file to /home/peter/incubator-netbeans
/libs.jsr223/build/classes
error: Source option 1.4 is no longer supported. Use 1.6 or later.
error: Target option 1.4 is no longer supported. Use 1.6 or later.
...

As libs.jsr223 is dummy only, it just should be removed, if possible.

And more of this:
Compiling 8 source files to /home/peter/incubator-netbeans
/openide.util.enumerations/build/classes
error: Source option 1.4 is no longer supported. Use 1.6 or later.
error: Target option 1.4 is no longer supported. Use


The build was using JDK 9, right? (JDK 8 supports -source 1.4/-target 1.4,
while this support was removed in JDK 9, see JEP 182:
http://openjdk.java.net/jeps/182
)

Sorry, but building on JDK 9 is not currently supported.



Why are those outdated targets set?


In some cases, these were set long time ago, and not changed, as it wasn't
needed. In some other cases, like the openide.util.enumerations, the
sources are actually using a 1.4 features ("enum" as an identifier, not a
keyword) for backwards compatibility reasons (and in case of
openide.util.enumerations, it might be OK to stop building it). In yet
other cases, like java.j2seplatform/probesrc, there is a good reason to use
an old -target setting. In the probesrc case, this defines the oldest
JDK/Java platform that the IDE will ever be able to recognize as a Java
platform. In this case, I am not sure if we can drop support for developing
projects for any Java platform older than JDK 6, I would not take such a
decision lightly. OTOH, for the probesrc, it is only a single class, which
we could generate using other means.

Jan



And, because it seems others don't have the same problems: Is the
repository url "https://github.com/apache/incubator-netbeans.git"; correct?

Kind regards
Peter


-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists







-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [NB Git] NetBeans does not compile with OpenJDK 8

[Peter Nabbefeld]

Hello,

I'm trying to build NB inside NB. When using standard build process 
("Clean and Build project" from Toolbar), the result shown in Output 
window is:
ant -f /home/peter/incubator-netbeans/nbbuild/nbproject/nbjdk.xml 
localclean bootstrap

localclean:
Duplicated project name in import. Project jdk defined first in 
/home/peter/incubator-netbeans/nbbuild/nbproject/jdk.xml and again in 
/home/peter/incubator-netbeans/nbbuild/jdk.xml

nbbuild.clean-cluster-flags:
nbbuild.localclean:
Deleting directory /home/peter/incubator-netbeans/nbbuild/netbeans
bootstrap:
Duplicated project name in import. Project jdk defined first in 
/home/peter/incubator-netbeans/nbbuild/nbproject/jdk.xml and again in 
/home/peter/incubator-netbeans/nbbuild/jdk.xml

nbbuild.bootstrap:
Created dir: /home/peter/incubator-netbeans/nbbuild/build/antclasses
Compiling 4 source files to 
/home/peter/incubator-netbeans/nbbuild/build/antclasses

Bootstrapping NetBeans-specific Ant extensions...
Compiling 85 source files to 
/home/peter/incubator-netbeans/nbbuild/build/antclasses

Building jar: /home/peter/incubator-netbeans/nbbuild/build/nbantext.jar
BUILD SUCCESSFUL (total time: 6 seconds)


It just seems like there hasn't been anything compiled other than some 
classes needed for ant.


When I try to use the "all" target from build xml, I keep getting errors 
(those described in previous posts).


Also, the "tryme" target fails:
ant -f /home/peter/incubator-netbeans/nbbuild tryme
tryme-setup-debug-args:
tryme:
sh: /home/peter/incubator-netbeans/nbbuild/netbeans/platform/lib/nbexec: 
Datei oder Verzeichnis nicht gefunden

/home/peter/incubator-netbeans/nbbuild/build.xml:1053: exec returned: 127
BUILD FAILED (total time: 0 seconds)


However, "ant all" works from the command line, so it's problem with the 
environment provided within the IDE. I've noticed, NetBeans insists in 
having a folder "java-8-openjdk/jre/classes", which is not available. 
After creating it as an empty directory, it seems the extension 
libraries are found now, but I still get compilation errors, probably 
forked compilation processes don't work correctly (using default 
platform Java 9 instead of Java 8).


So, currently I've got two bugs:
[1] Java platform initialized incorrectly: Only existing folders should 
be added (the non-existing classes folder seems to block import of 
folders following this entry).
[2] Some forks use default java compiler, which is ususally now Java 9 
in NetBeans IDE.


Further, the following should be added to the README file:
It's possible to add a "user.build.properties" file with the following 
possible entries:

(1) nbjdk.home=/path/to/jdk8
(2) run.validation=false  # only needed in case of uncommitted local changes

Further, the build script still contains references to Mercurial, like 
"-hg-clean". These should be removed; it would be great, if these could 
be documented like a tutorial (what problems do they solve etc.) and 
contributed to the Apache Ant project.



Kind regards
Peter



Am 06.01.2018 um 00:54 schrieb Antonio:

Hi,

I have been successfully compiling with OpenJDK 8 for several months 
now (I don't have Oracle JDK8 installed in my preferred box, nor JavaFX).


Make sure that:

a) JAVA_HOME is either _NOT_ set or set to a proper OpenJDK8 place.
(run "unset JAVA_HOME" if unsure, "echo $JAVA_HOME" to check)

b) Add a OpenJDK8 java binary to your PATH
In my case:
$ java -version
openjdk version "1.8.0_151"
OpenJDK Runtime Environment (build 1.8.0_151-8u151-b12-1~deb9u1-b12)
OpenJDK 64-Bit Server VM (build 25.151-b12, mixed mode)

Cheers,
Antonio

P.S.: I don't set any "nbjdk.bootclasspath" nor any other weird things.
I also have Java 9 installed, when I want to run with Java 9 I use:
./nbbuild/netbeans/bin/netbeans --jdkhome /THE/PATH/TO/jdk-9.0.1/


On 05/01/18 15:44, Peter Nabbefeld wrote:


Hi,

I'm getting 
"/home/peter/incubator-netbeans/core.network/src/org/netbeans/core/network/proxy/pac/impl/ClassFilterPacHelpers.java:21: 
error: package jdk.nashorn.api.scripting does not exist", when trying 
to build NetBeans from incubator repository.


Value of "nbjdk.bootclasspath" is:
/usr/lib64/jvm/java-8-openjdk/jre/lib/charsets.jar:/usr/lib64/jvm/java-8-openjdk/jre/lib/jce.jar:/usr/lib64/jvm/java-8-openjdk/jre/lib/jfxswt.jar:/usr/lib64/jvm/java-8-openjdk/jre/lib/jsse.jar:/usr/lib64/jvm/java-8-openjdk/jre/lib/management-agent.jar:/usr/lib64/jvm/java-8-openjdk/jre/lib/resources.jar:/usr/lib64/jvm/java-8-openjdk/jre/lib/rt.jar 



I tried to edit project.xml, adding the missing jar files, but got 
another problem:

...
Created dir: /home/peter/incubator-netbeans/libs.jsr223/build/classes
Compiling 1 source file to 
/home/peter/incubator-netbeans/libs.jsr223/build/classes

error: Source option 1.4 is no longer supported. Use 1.6 or later.

Re: [NB Git] NetBeans does not compile with OpenJDK 8

[Peter Nabbefeld]

Hm, sorry, stopping validation of commits isn't obviously this easy. :-/

Am 07.01.2018 um 08:50 schrieb Peter Nabbefeld:

[...]

(2) run.validation=false  # only needed in case of uncommitted local 
changes





-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [NB Git] NetBeans does not compile with OpenJDK 8

[Peter Nabbefeld]

"ant all" works at the command line, when validation is disabled 
("nb.run.validation=false").


Validation fails in "org.netbeans.core.validation".

Building does not work inside NetBeans, as in some cases obviously the 
default Java platform (JDK 9) is used.


Regards
P.



Am 07.01.2018 um 08:54 schrieb Geertjan Wielenga:

Just start by building it on the command line, following the standard
instructions. If/when that works, do your special thing -- i.e., build
NetBeans inside NetBeans.

Thanks,

Gj

On Sun, Jan 7, 2018 at 8:50 AM, Peter Nabbefeld  wrote:

Hello,

I'm trying to build NB inside NB. When using standard build process ("Clean
and Build project" from Toolbar), the result shown in Output window is:
ant -f /home/peter/incubator-netbeans/nbbuild/nbproject/nbjdk.xml localclean
bootstrap
localclean:
Duplicated project name in import. Project jdk defined first in
/home/peter/incubator-netbeans/nbbuild/nbproject/jdk.xml and again in
/home/peter/incubator-netbeans/nbbuild/jdk.xml
nbbuild.clean-cluster-flags:
nbbuild.localclean:
Deleting directory /home/peter/incubator-netbeans/nbbuild/netbeans
bootstrap:
Duplicated project name in import. Project jdk defined first in
/home/peter/incubator-netbeans/nbbuild/nbproject/jdk.xml and again in
/home/peter/incubator-netbeans/nbbuild/jdk.xml
nbbuild.bootstrap:
Created dir: /home/peter/incubator-netbeans/nbbuild/build/antclasses
Compiling 4 source files to
/home/peter/incubator-netbeans/nbbuild/build/antclasses
Bootstrapping NetBeans-specific Ant extensions...
Compiling 85 source files to
/home/peter/incubator-netbeans/nbbuild/build/antclasses
Building jar: /home/peter/incubator-netbeans/nbbuild/build/nbantext.jar
BUILD SUCCESSFUL (total time: 6 seconds)


It just seems like there hasn't been anything compiled other than some
classes needed for ant.

When I try to use the "all" target from build xml, I keep getting errors
(those described in previous posts).

Also, the "tryme" target fails:
ant -f /home/peter/incubator-netbeans/nbbuild tryme
tryme-setup-debug-args:
tryme:
sh: /home/peter/incubator-netbeans/nbbuild/netbeans/platform/lib/nbexec:
Datei oder Verzeichnis nicht gefunden
/home/peter/incubator-netbeans/nbbuild/build.xml:1053: exec returned: 127
BUILD FAILED (total time: 0 seconds)


However, "ant all" works from the command line, so it's problem with the
environment provided within the IDE. I've noticed, NetBeans insists in
having a folder "java-8-openjdk/jre/classes", which is not available. After
creating it as an empty directory, it seems the extension libraries are
found now, but I still get compilation errors, probably forked compilation
processes don't work correctly (using default platform Java 9 instead of
Java 8).

So, currently I've got two bugs:
[1] Java platform initialized incorrectly: Only existing folders should be
added (the non-existing classes folder seems to block import of folders
following this entry).
[2] Some forks use default java compiler, which is ususally now Java 9 in
NetBeans IDE.

Further, the following should be added to the README file:
It's possible to add a "user.build.properties" file with the following
possible entries:
(1) nbjdk.home=/path/to/jdk8
(2) run.validation=false  # only needed in case of uncommitted local changes

Further, the build script still contains references to Mercurial, like
"-hg-clean". These should be removed; it would be great, if these could be
documented like a tutorial (what problems do they solve etc.) and
contributed to the Apache Ant project.


Kind regards
Peter




Am 06.01.2018 um 00:54 schrieb Antonio:

Hi,

I have been successfully compiling with OpenJDK 8 for several months now
(I don't have Oracle JDK8 installed in my preferred box, nor JavaFX).

Make sure that:

a) JAVA_HOME is either _NOT_ set or set to a proper OpenJDK8 place.
(run "unset JAVA_HOME" if unsure, "echo $JAVA_HOME" to check)

b) Add a OpenJDK8 java binary to your PATH
In my case:
$ java -version
openjdk version "1.8.0_151"
OpenJDK Runtime Environment (build 1.8.0_151-8u151-b12-1~deb9u1-b12)
OpenJDK 64-Bit Server VM (build 25.151-b12, mixed mode)

Cheers,
Antonio

P.S.: I don't set any "nbjdk.bootclasspath" nor any other weird things.
I also have Java 9 installed, when I want to run with Java 9 I use:
./nbbuild/netbeans/bin/netbeans --jdkhome /THE/PATH/TO/jdk-9.0.1/


On 05/01/18 15:44, Peter Nabbefeld wrote:


Hi,

I'm getting
"/home/peter/incubator-netbeans/core.network/src/org/netbeans/core/network/proxy/pac/impl/ClassFilterPacHelpers.java:21:
error: package jdk.nashorn.api.scripting does not exist", when trying to
build NetBeans from incubator repository.

Value of "nbjdk.bootclasspath" is:

/usr/lib64/jvm/java-8-openjdk/jre/lib/charsets.jar:/usr/lib64/jvm/java-8-openjdk/jre/lib/jce.jar:/usr/lib64/jvm/jav

[NB Git] Why are there two JDK definitions?

[Peter Nabbefeld]

Hello,

when I try to debug the build of incubator-netbeans, I get the following 
output:


ant -f /home/peter/incubator-netbeans/nbbuild/nbproject/nbjdk.xml 
tryme-debug

tryme-debug:
Duplicated project name in import. Project jdk defined first in 
/home/peter/incubator-netbeans/nbbuild/nbproject/jdk.xml and again in 
/home/peter/incubator-netbeans/nbbuild/jdk.xml

nbbuild.tryme-debug:
Searching for JARs in /home/peter/incubator-netbeans/nbbuild/netbeans, 
this may take a moment...
/home/peter/incubator-netbeans/nbbuild/nbproject/nbjdk.xml:46: The 
following error occurred while executing this line:
/home/peter/incubator-netbeans/nbbuild/build.xml:977: Only one 
bootclasspath subelement is supported

BUILD FAILED (total time: 0 seconds)


Both files exist, and they're different.

Kind regards
Peter

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [NB Git] NetBeans does not compile with OpenJDK 8

[Peter Nabbefeld]

Hm, "ant all" creates some zip files and initiates the validation step. 
While this is probably an unnecessary step, when I use "ant all" and 
disable validation, it says that validation is a needed before 
committing any changes, so IMHO it should work.


Kind regards
Peter



Am 07.01.2018 um 11:37 schrieb Geertjan Wielenga:

I’ve never used ‘ant all’. Probably best to take another look at the README
and just use ‘ant’, as stated there. Not sure if that’s the same as ‘ant
all’ but based on your result it probably isn’t.

Gj

On Sunday, January 7, 2018, Peter Nabbefeld  wrote:


"ant all" works at the command line, when validation is disabled
("nb.run.validation=false").

Validation fails in "org.netbeans.core.validation".

Building does not work inside NetBeans, as in some cases obviously the
default Java platform (JDK 9) is used.

Regards
P.



Am 07.01.2018 um 08:54 schrieb Geertjan Wielenga:


Just start by building it on the command line, following the standard
instructions. If/when that works, do your special thing -- i.e., build
NetBeans inside NetBeans.

Thanks,

Gj

On Sun, Jan 7, 2018 at 8:50 AM, Peter Nabbefeld 
wrote:


Hello,

I'm trying to build NB inside NB. When using standard build process
("Clean
and Build project" from Toolbar), the result shown in Output window is:
ant -f /home/peter/incubator-netbeans/nbbuild/nbproject/nbjdk.xml
localclean
bootstrap
localclean:
Duplicated project name in import. Project jdk defined first in
/home/peter/incubator-netbeans/nbbuild/nbproject/jdk.xml and again in
/home/peter/incubator-netbeans/nbbuild/jdk.xml
nbbuild.clean-cluster-flags:
nbbuild.localclean:
Deleting directory /home/peter/incubator-netbeans/nbbuild/netbeans
bootstrap:
Duplicated project name in import. Project jdk defined first in
/home/peter/incubator-netbeans/nbbuild/nbproject/jdk.xml and again in
/home/peter/incubator-netbeans/nbbuild/jdk.xml
nbbuild.bootstrap:
Created dir: /home/peter/incubator-netbeans/nbbuild/build/antclasses
Compiling 4 source files to
/home/peter/incubator-netbeans/nbbuild/build/antclasses
Bootstrapping NetBeans-specific Ant extensions...
Compiling 85 source files to
/home/peter/incubator-netbeans/nbbuild/build/antclasses
Building jar: /home/peter/incubator-netbeans/nbbuild/build/nbantext.jar
BUILD SUCCESSFUL (total time: 6 seconds)


It just seems like there hasn't been anything compiled other than some
classes needed for ant.

When I try to use the "all" target from build xml, I keep getting errors
(those described in previous posts).

Also, the "tryme" target fails:
ant -f /home/peter/incubator-netbeans/nbbuild tryme
tryme-setup-debug-args:
tryme:
sh: /home/peter/incubator-netbeans/nbbuild/netbeans/platform/lib/nbexec:
Datei oder Verzeichnis nicht gefunden
/home/peter/incubator-netbeans/nbbuild/build.xml:1053: exec returned:
127
BUILD FAILED (total time: 0 seconds)


However, "ant all" works from the command line, so it's problem with the
environment provided within the IDE. I've noticed, NetBeans insists in
having a folder "java-8-openjdk/jre/classes", which is not available.
After
creating it as an empty directory, it seems the extension libraries are
found now, but I still get compilation errors, probably forked
compilation
processes don't work correctly (using default platform Java 9 instead of
Java 8).

So, currently I've got two bugs:
[1] Java platform initialized incorrectly: Only existing folders should
be
added (the non-existing classes folder seems to block import of folders
following this entry).
[2] Some forks use default java compiler, which is ususally now Java 9 in
NetBeans IDE.

Further, the following should be added to the README file:
It's possible to add a "user.build.properties" file with the following
possible entries:
(1) nbjdk.home=/path/to/jdk8
(2) run.validation=false  # only needed in case of uncommitted local
changes

Further, the build script still contains references to Mercurial, like
"-hg-clean". These should be removed; it would be great, if these could
be
documented like a tutorial (what problems do they solve etc.) and
contributed to the Apache Ant project.


Kind regards
Peter




Am 06.01.2018 um 00:54 schrieb Antonio:


Hi,

I have been successfully compiling with OpenJDK 8 for several months now
(I don't have Oracle JDK8 installed in my preferred box, nor JavaFX).

Make sure that:

a) JAVA_HOME is either _NOT_ set or set to a proper OpenJDK8 place.
(run "unset JAVA_HOME" if unsure, "echo $JAVA_HOME" to check)

b) Add a OpenJDK8 java binary to your PATH
In my case:
$ java -version
openjdk version "1.8.0_151"
OpenJDK Runtime Environment (build 1.8.0_151-8u151-b12-1~deb9u1-b12)
OpenJDK 64-Bit Server VM (build 25.151-b12, mixed mode)

Cheers,
Antonio

P.S.: I don't set any "nbjdk.bootclasspath" nor any other weird things.
I al

Re: [VOTE] Apache NetBeans Version Number: 2019.03

[Peter Nabbefeld]

-1

Am 26.01.19 um 04:51 schrieb Laszlo Kishalmi:

Dear all,

Well, it is time to finalize out version scheme for a while. There 
will be three voting threads created on this topic with subjects:


 * [VOTE] Apache NetBeans Version Number: 11
 * [VOTE] Apache NetBeans Version Number: 11.0
 * [VOTE] Apache NetBeans Version Number: 2019.03

Everyone from the community can cast his/her own vote  on each thread as:

+1  I like it, let's do this way
0    I'm Ok with it, does not particularly like it, but won't mind it
-1   I do not like it at all.

Each thread is going to be open for 72+ hours and going to be closed 
at the same time. Regardless from the number of votes, that version 
number would win which has the greatest sum of the vote values.


Voting is a community event! Be  a proud community member and cast 
your vote!


Thank you!

Laszlo Kishalmi

Volunteer Release Manager of Apache NetBeans 2019.03

P.S.: Please keep this thread for voting only!





-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [VOTE] Apache NetBeans Version Number: 11

[Peter Nabbefeld]

-1

Am 26.01.19 um 04:50 schrieb Laszlo Kishalmi:

Dear all,

Well, it is time to finalize out version scheme for a while. There 
will be three voting threads created on this topic with subjects:


 * [VOTE] Apache NetBeans Version Number: 11
 * [VOTE] Apache NetBeans Version Number: 11.0
 * [VOTE] Apache NetBeans Version Number: 2019.03

Everyone from the community can cast his/her own vote  on each thread as:

+1  I like it, let's do this way
0    I'm Ok with it, does not particularly like it, but won't mind it
-1   I do not like it at all.

Each thread is going to be open for 72+ hours and going to be closed 
at the same time. Regardless from the number of votes, that version 
number would win which has the greatest sum of the vote values.


Voting is a community event! Be a proud community member and cast your 
vote!


Thank you!

Laszlo Kishalmi

Volunteer Release Manager of Apache NetBeans 11

P.S.: Please keep this thread for voting only!





-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [VOTE] Apache NetBeans Version Number: 11.0

[Peter Nabbefeld]

+1

Am 26.01.19 um 04:51 schrieb Laszlo Kishalmi:

Dear all,

Well, it is time to finalize out version scheme for a while. There 
will be three voting threads created on this topic with subjects:


 * [VOTE] Apache NetBeans Version Number: 11
 * [VOTE] Apache NetBeans Version Number: 11.0
 * [VOTE] Apache NetBeans Version Number: 2019.03

Everyone from the community can cast his/her own vote  on each thread as:

+1  I like it, let's do this way
0    I'm Ok with it, does not particularly like it, but won't mind it
-1   I do not like it at all.

Each thread is going to be open for 72+ hours and going to be closed 
at the same time. Regardless from the number of votes, that version 
number would win which has the greatest sum of the vote values.


Voting is a community event! Be a proud community member and cast your 
vote!


Thank you!

Laszlo Kishalmi

Volunteer Release Manager of Apache NetBeans 11.0

P.S.: Please keep this thread for voting only!





-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

How to disable the default httpd.conf editor?

[Peter Nabbefeld]

Hello,

is it somehow possible to disable the default editor for httpd.conf?

Kind regards

Peter

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

nbm-maven-plugin

[Peter Nabbefeld]

Hello,

I've noticed 
http://bits.netbeans.org/mavenutilities/nbm-maven-plugin/index.html 
which seems to bundle the migration efforts for nbm-maven-plugin.


There's some more information about it at mojohaus, which I missed on 
the above site:


http://www.mojohaus.org/nbm-maven-plugin/

http://www.mojohaus.org/nbm-maven-plugin/descriptor.html

http://www.mojohaus.org/nbm-maven-plugin/plugin-info.html

http://www.mojohaus.org/nbm-maven-plugin/nbm-mojo.html


Though these pages all have the same parent, I couldn't always find the 
links from one page to the other on the first glance, so I prefer to 
list these all.


Kind regards

Peter

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: nbm-maven-plugin

[Peter Nabbefeld]

Thank You, Eric. Just haven't found them in their new home and wanted to 
make sure that these don't get lost.


Kind regards
Peter


Am 28.01.19 um 10:47 schrieb Eric Barboni:

Hi Peter,

The page you mention are in the new site with some evolution of the content due 
to maven jar plugin changes. The style may not be good as it tries to mimic the 
main Apache Netbeans site.
http://bits.netbeans.org/mavenutilities/nbm-maven-plugin/descriptor.html
http://bits.netbeans.org/mavenutilities/nbm-maven-plugin/plugin-info.html
http://bits.netbeans.org/mavenutilities/nbm-maven-plugin/nbm-mojo.html

Regards
Eric
-Message d'origine-----
De : Peter Nabbefeld 
Envoyé : dimanche 27 janvier 2019 19:03
À : dev 
Objet : nbm-maven-plugin


Hello,

I've noticed
http://bits.netbeans.org/mavenutilities/nbm-maven-plugin/index.html
which seems to bundle the migration efforts for nbm-maven-plugin.

There's some more information about it at mojohaus, which I missed on the above 
site:

http://www.mojohaus.org/nbm-maven-plugin/

http://www.mojohaus.org/nbm-maven-plugin/descriptor.html

http://www.mojohaus.org/nbm-maven-plugin/plugin-info.html

http://www.mojohaus.org/nbm-maven-plugin/nbm-mojo.html


Though these pages all have the same parent, I couldn't always find the links 
from one page to the other on the first glance, so I prefer to list these all.

Kind regards

Peter

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists





-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists






-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Cannot find the generated layer file

[Peter Nabbefeld]

Hello,

there may be a bug related to annotation processors:
Created a NB module project (Maven, using JDK 8, release build 382 on Linux)

1. Usually there was a file "generated-layer.xml" when using NB 
annotations - cannot find it now.
2. I'm getting problems related to bundle.properties, especially in one 
folder where I've got a properties file (from a JPanel window) and a 
Java file (from NbBundle.Message in a DataLoader).


AFAIK, both use annotation processors, so there might be a general 
problem with those, or just different problems in different APs.


Kind regards

Peter

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Cannot find the generated layer file

[Peter Nabbefeld]

I've verified the generated layer should have been created as 
META-INF/generated-layer.xml, but it's not there. I do have a layer.xml, 
already, but this had never been a problem before. Probably some needed 
modules are not active? So it's most probably not related to problems 
with bundle annotations.


Regards
P.



Am 28.01.19 um 12:57 schrieb Peter Nabbefeld:


Hello,

there may be a bug related to annotation processors:
Created a NB module project (Maven, using JDK 8, release build 382 on 
Linux)


1. Usually there was a file "generated-layer.xml" when using NB 
annotations - cannot find it now.
2. I'm getting problems related to bundle.properties, especially in 
one folder where I've got a properties file (from a JPanel window) and 
a Java file (from NbBundle.Message in a DataLoader).


AFAIK, both use annotation processors, so there might be a general 
problem with those, or just different problems in different APs.


Kind regards

Peter

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists






-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Cannot find the generated layer file

[Peter Nabbefeld]

Hm, I'd file a ticket if I'd be able to find out more details - 
otherwise I can only file my complete project (including binaries) so 
somebody could find out what's wrong with it. Seems, there's sth. 
strange with my project, so I'll see if I have some time for debugging 
at the week-end. BTW, did You try using Maven? I guess, problems are 
caused by nbm-maven-plugin here, I'm using 4.x (tried 4.0.1 and 4.1).


Kind regards

Peter



Am 28.01.19 um 14:32 schrieb Eric Barboni:

Hi,
  Would you have the time fill a jira ticket with a small example ? I was not 
able to reproduce on my computer.

Regards
Eric


-----Message d'origine-
De : Peter Nabbefeld 
Envoyé : lundi 28 janvier 2019 13:49
À : dev@netbeans.incubator.apache.org
Objet : Re: Cannot find the generated layer file


I've verified the generated layer should have been created as 
META-INF/generated-layer.xml, but it's not there. I do have a layer.xml, 
already, but this had never been a problem before. Probably some needed modules 
are not active? So it's most probably not related to problems with bundle 
annotations.

Regards
P.



Am 28.01.19 um 12:57 schrieb Peter Nabbefeld:

Hello,

there may be a bug related to annotation processors:
Created a NB module project (Maven, using JDK 8, release build 382 on
Linux)

1. Usually there was a file "generated-layer.xml" when using NB
annotations - cannot find it now.
2. I'm getting problems related to bundle.properties, especially in
one folder where I've got a properties file (from a JPanel window) and
a Java file (from NbBundle.Message in a DataLoader).

AFAIK, both use annotation processors, so there might be a general
problem with those, or just different problems in different APs.

Kind regards

Peter

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail:
dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists





-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists





-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists






-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Cannot find the generated layer file

[Peter Nabbefeld]

Same here.

Then my problems may have to do with the "bundles clash" (using 
Bundle.properties and Bundle.java in the same package). First time 
building I'm getting some error messages (Bundle not found), second time 
works (for the bundle files). Only at the second run, the manifest file 
is copied (seems the toolchain has been interrupted on the first build).


Otherwise I really don't know, currently.

Kind regards
Peter




Am 28.01.19 um 15:19 schrieb Eric Barboni:

I'm using 4.1 with release82 artefacts (and also custom release100).
I also updated the maven-jar-plugin configuration because I use version 3.0.2 
here:

 
 
${project.build.outputDirectory}/META-INF/MANIFEST.MF
 
 

But in all case I have, generated layer is created.
Eric

-Message d'origine-
De : Peter Nabbefeld 
Envoyé : lundi 28 janvier 2019 15:08
À : dev@netbeans.incubator.apache.org
Objet : Re: Cannot find the generated layer file


Hm, I'd file a ticket if I'd be able to find out more details - otherwise I can 
only file my complete project (including binaries) so somebody could find out 
what's wrong with it. Seems, there's sth.
strange with my project, so I'll see if I have some time for debugging at the 
week-end. BTW, did You try using Maven? I guess, problems are caused by 
nbm-maven-plugin here, I'm using 4.x (tried 4.0.1 and 4.1).

Kind regards

Peter



Am 28.01.19 um 14:32 schrieb Eric Barboni:

Hi,
   Would you have the time fill a jira ticket with a small example ? I was not 
able to reproduce on my computer.

Regards
Eric


-Message d'origine-
De : Peter Nabbefeld  Envoyé : lundi 28
janvier 2019 13:49 À : dev@netbeans.incubator.apache.org Objet : Re:
Cannot find the generated layer file


I've verified the generated layer should have been created as 
META-INF/generated-layer.xml, but it's not there. I do have a layer.xml, 
already, but this had never been a problem before. Probably some needed modules 
are not active? So it's most probably not related to problems with bundle 
annotations.

Regards
P.



Am 28.01.19 um 12:57 schrieb Peter Nabbefeld:

Hello,

there may be a bug related to annotation processors:
Created a NB module project (Maven, using JDK 8, release build 382 on
Linux)

1. Usually there was a file "generated-layer.xml" when using NB
annotations - cannot find it now.
2. I'm getting problems related to bundle.properties, especially in
one folder where I've got a properties file (from a JPanel window)
and a Java file (from NbBundle.Message in a DataLoader).

AFAIK, both use annotation processors, so there might be a general
problem with those, or just different problems in different APs.

Kind regards

Peter

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail:
dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail:
dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists





-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail:
dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists





-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists





-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists






-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Cannot find the generated layer file

[Peter Nabbefeld]

Hi Geertjan,

we just want to find out what's going on, otherwise I cannot tell You 
how to reproduce the problems. Seems I have to do some debugging next 
week-end - otherwise the only option will be to put everything into a 
zip-file, so somebody will eventually be able to retrace what happens.  :-/


I'd like to be able to give some more details, currently I don't know 
much more than "it doesn't work for me, but it does for Eric ...". The 
real difference is still unknown.


Kind regards
Peter


Am 28.01.19 um 16:12 schrieb Geertjan Wielenga:

Steps to reproduce, environment, etc, so someone can take a look and try to
reproduce.

Gj

On Mon, Jan 28, 2019 at 4:10 PM Peter Nabbefeld 
wrote:


Same here.

Then my problems may have to do with the "bundles clash" (using
Bundle.properties and Bundle.java in the same package). First time
building I'm getting some error messages (Bundle not found), second time
works (for the bundle files). Only at the second run, the manifest file
is copied (seems the toolchain has been interrupted on the first build).

Otherwise I really don't know, currently.

Kind regards
Peter




Am 28.01.19 um 15:19 schrieb Eric Barboni:

I'm using 4.1 with release82 artefacts (and also custom release100).
I also updated the maven-jar-plugin configuration because I use version

3.0.2 here:


  


${project.build.outputDirectory}/META-INF/MANIFEST.MF

  
  

But in all case I have, generated layer is created.
Eric

-Message d'origine-
De : Peter Nabbefeld 
Envoyé : lundi 28 janvier 2019 15:08
À : dev@netbeans.incubator.apache.org
Objet : Re: Cannot find the generated layer file


Hm, I'd file a ticket if I'd be able to find out more details -

otherwise I can only file my complete project (including binaries) so
somebody could find out what's wrong with it. Seems, there's sth.

strange with my project, so I'll see if I have some time for debugging

at the week-end. BTW, did You try using Maven? I guess, problems are caused
by nbm-maven-plugin here, I'm using 4.x (tried 4.0.1 and 4.1).

Kind regards

Peter



Am 28.01.19 um 14:32 schrieb Eric Barboni:

Hi,
Would you have the time fill a jira ticket with a small example ? I

was not able to reproduce on my computer.

Regards
Eric


-Message d'origine-
De : Peter Nabbefeld  Envoyé : lundi 28
janvier 2019 13:49 À : dev@netbeans.incubator.apache.org Objet : Re:
Cannot find the generated layer file


I've verified the generated layer should have been created as

META-INF/generated-layer.xml, but it's not there. I do have a layer.xml,
already, but this had never been a problem before. Probably some needed
modules are not active? So it's most probably not related to problems with
bundle annotations.

Regards
P.



Am 28.01.19 um 12:57 schrieb Peter Nabbefeld:

Hello,

there may be a bug related to annotation processors:
Created a NB module project (Maven, using JDK 8, release build 382 on
Linux)

1. Usually there was a file "generated-layer.xml" when using NB
annotations - cannot find it now.
2. I'm getting problems related to bundle.properties, especially in
one folder where I've got a properties file (from a JPanel window)
and a Java file (from NbBundle.Message in a DataLoader).

AFAIK, both use annotation processors, so there might be a general
problem with those, or just different problems in different APs.

Kind regards

Peter

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail:
dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail:
dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists





-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail:
dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Cannot find the generated layer file

[Peter Nabbefeld]

If I cannot isolate the issue, it might be necessary to provide some 
environment (such as test userdir) - then it may be better to use a 
pastebin and a zip file. But still I hope to be able to get some more 
details next week-end.


P.


Am 28.01.19 um 16:33 schrieb Geertjan Wielenga:

Rather than putting anything into a ZIP file, please put it on GitHub and
then provide a link to it here.

Gj

On Mon, Jan 28, 2019 at 4:24 PM Peter Nabbefeld 
wrote:


Hi Geertjan,

we just want to find out what's going on, otherwise I cannot tell You
how to reproduce the problems. Seems I have to do some debugging next
week-end - otherwise the only option will be to put everything into a
zip-file, so somebody will eventually be able to retrace what happens.  :-/

I'd like to be able to give some more details, currently I don't know
much more than "it doesn't work for me, but it does for Eric ...". The
real difference is still unknown.

Kind regards
Peter


Am 28.01.19 um 16:12 schrieb Geertjan Wielenga:

Steps to reproduce, environment, etc, so someone can take a look and try

to

reproduce.

Gj

On Mon, Jan 28, 2019 at 4:10 PM Peter Nabbefeld 
wrote:


Same here.

Then my problems may have to do with the "bundles clash" (using
Bundle.properties and Bundle.java in the same package). First time
building I'm getting some error messages (Bundle not found), second time
works (for the bundle files). Only at the second run, the manifest file
is copied (seems the toolchain has been interrupted on the first build).

Otherwise I really don't know, currently.

Kind regards
Peter




Am 28.01.19 um 15:19 schrieb Eric Barboni:

I'm using 4.1 with release82 artefacts (and also custom release100).
I also updated the maven-jar-plugin configuration because I use version

3.0.2 here:


   


${project.build.outputDirectory}/META-INF/MANIFEST.MF

   
   

But in all case I have, generated layer is created.
Eric

-Message d'origine-
De : Peter Nabbefeld 
Envoyé : lundi 28 janvier 2019 15:08
À : dev@netbeans.incubator.apache.org
Objet : Re: Cannot find the generated layer file


Hm, I'd file a ticket if I'd be able to find out more details -

otherwise I can only file my complete project (including binaries) so
somebody could find out what's wrong with it. Seems, there's sth.

strange with my project, so I'll see if I have some time for debugging

at the week-end. BTW, did You try using Maven? I guess, problems are

caused

by nbm-maven-plugin here, I'm using 4.x (tried 4.0.1 and 4.1).

Kind regards

Peter



Am 28.01.19 um 14:32 schrieb Eric Barboni:

Hi,
 Would you have the time fill a jira ticket with a small example ?

I

was not able to reproduce on my computer.

Regards
Eric


-Message d'origine-
De : Peter Nabbefeld  Envoyé : lundi 28
janvier 2019 13:49 À : dev@netbeans.incubator.apache.org Objet : Re:
Cannot find the generated layer file


I've verified the generated layer should have been created as

META-INF/generated-layer.xml, but it's not there. I do have a layer.xml,
already, but this had never been a problem before. Probably some needed
modules are not active? So it's most probably not related to problems

with

bundle annotations.

Regards
P.



Am 28.01.19 um 12:57 schrieb Peter Nabbefeld:

Hello,

there may be a bug related to annotation processors:
Created a NB module project (Maven, using JDK 8, release build 382 on
Linux)

1. Usually there was a file "generated-layer.xml" when using NB
annotations - cannot find it now.
2. I'm getting problems related to bundle.properties, especially in
one folder where I've got a properties file (from a JPanel window)
and a Java file (from NbBundle.Message in a DataLoader).

AFAIK, both use annotation processors, so there might be a general
problem with those, or just different problems in different APs.

Kind regards

Peter

-
To unsubscribe, e-mail:

dev-unsubscr...@netbeans.incubator.apache.org

For additional commands, e-mail:
dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail:
dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists





-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail:
dev-h...@netbeans.incubator.apache.org

F

How to debug Maven compile?

[Peter Nabbefeld]

Hello,

I get a strange error compiling a NetBeans module using Maven (see debug 
output at the bottom; the file "Bundle.properties" exists, of course). 
This exception only is thrown when compiling first time, second time 
compilation works (but other errors exist, so it's no option to just 
ignore the exception).


The problem for me is, the stack trace shows only classes in external 
modules, so my question is: where can I set a breakpoint to see what 
happens? Are there any documents describing how Maven is used to start 
the lifecycle steps? E.g. I'd like to know how and when NB annotations 
are processed in Maven context - obviously this is related to my problems.


Kind regards

Peter




org.apache.maven.lifecycle.LifecycleExecutionException: Failed to 
execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile 
(default-compile) on project ApacheHttpdConfigurator: Compilation failure
de/epdv/tools/configurator/httpd/CfgEdTopComponent.java:[33,14] Cannot 
find resource de/epdv/tools/configurator/httpd/Bundle.properties


    at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
    at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
    at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
    at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
    at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
    at 
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
    at 
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)

    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
    at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
    at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

    at java.lang.reflect.Method.invoke(Method.java:498)
    at 
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
    at 
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
    at 
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
    at 
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.compiler.CompilationFailureException: 
Compilation failure
de/epdv/tools/configurator/httpd/CfgEdTopComponent.java:[33,14] Cannot 
find resource de/epdv/tools/configurator/httpd/Bundle.properties


    at 
org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:1215)
    at 
org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:188)
    at 
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
    at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)

    ... 20 more


For more information about the errors and possible solutions, please 
read the following articles:
[Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException



-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Cannot find the generated layer file

[Peter Nabbefeld]

The problems have been caused by the following annotation:

@TopComponent.OpenActionRegistration(
    displayName = "#CTL_CfgEdAction",
    preferredID = "CfgEdTopComponent"
)

As it seemed to cause problems having two components in the same package 
using @NbBundle.Messages, I removed the annotation and moved the 
corresponding message into Bundle.properties. While it does not cause 
problems in the editor, for some unknown reason it causes problems with 
Maven build structure. Even worse, annotation processing stops after an 
exception is thrown (Bundle.properties not found), so also no 
generated-layer.xml file is processed.


I've tried to work around the problem using this snippet in my POM, but 
it failed to work for me:


    
org.apache.maven.plugins
maven-resources-plugin
    3.1.0
    
    
    pre-merge-properties
    initialize
    
    copy-resources
    
    
target/classes
    
    
src/main/resources
    
*.properties
    
    
    
    
    
    
    

Does somebody have a better idea? Or did I just miss sth.?

Kind regards

Peter



Am 28.01.19 um 16:33 schrieb Geertjan Wielenga:

Rather than putting anything into a ZIP file, please put it on GitHub and
then provide a link to it here.

Gj

On Mon, Jan 28, 2019 at 4:24 PM Peter Nabbefeld 
wrote:


Hi Geertjan,

we just want to find out what's going on, otherwise I cannot tell You
how to reproduce the problems. Seems I have to do some debugging next
week-end - otherwise the only option will be to put everything into a
zip-file, so somebody will eventually be able to retrace what happens.  :-/

I'd like to be able to give some more details, currently I don't know
much more than "it doesn't work for me, but it does for Eric ...". The
real difference is still unknown.

Kind regards
Peter


Am 28.01.19 um 16:12 schrieb Geertjan Wielenga:

Steps to reproduce, environment, etc, so someone can take a look and try

to

reproduce.

Gj

On Mon, Jan 28, 2019 at 4:10 PM Peter Nabbefeld 
wrote:


Same here.

Then my problems may have to do with the "bundles clash" (using
Bundle.properties and Bundle.java in the same package). First time
building I'm getting some error messages (Bundle not found), second time
works (for the bundle files). Only at the second run, the manifest file
is copied (seems the toolchain has been interrupted on the first build).

Otherwise I really don't know, currently.

Kind regards
Peter




Am 28.01.19 um 15:19 schrieb Eric Barboni:

I'm using 4.1 with release82 artefacts (and also custom release100).
I also updated the maven-jar-plugin configuration because I use version

3.0.2 here:


   


${project.build.outputDirectory}/META-INF/MANIFEST.MF

   
   

But in all case I have, generated layer is created.
Eric

-Message d'origine-
De : Peter Nabbefeld 
Envoyé : lundi 28 janvier 2019 15:08
À : dev@netbeans.incubator.apache.org
Objet : Re: Cannot find the generated layer file


Hm, I'd file a ticket if I'd be able to find out more details -

otherwise I can only file my complete project (including binaries) so
somebody could find out what's wrong with it. Seems, there's sth.

strange with my project, so I'll see if I have some time for debugging

at the week-end. BTW, did You try using Maven? I guess, problems are

caused

by nbm-maven-plugin here, I'm using 4.x (tried 4.0.1 and 4.1).

Kind regards

Peter



Am 28.01.19 um 14:32 schrieb Eric Barboni:

Hi,
 Would you have the time fill a jira ticket with a small example ?

I

was not able to reproduce on my computer.

Regards
Eric


-Message d'origine-
De : Peter Nabbefeld  Envoyé : lundi 28
janvier 2019 13:49 À : dev@netbeans.incubator.apache.org Objet : Re:
Cannot find the generated layer file


I've verified the generated layer should have been created as

META-INF/generated-layer.xml, but it's not there. I do have a layer.xml,
already, but this had never been a problem before. Probably some needed
modules are not active? So it's most probably not related to problems

with

bundle annotations.

Regards
P.



Am 28.01.19 um 12:57 schrieb Peter Nabbefeld:

Hello,

there may be a bug related to annotation processors:
Created a NB module project (Maven, using JDK 8, release build 382 on
Linux)

1. Usually there was a file "generated-layer.xml" when using NB
annotations - cannot find it now.
2. I'm getting problems related to bundle.properties, especially in
o