Re: [ANNOUNCE] Apache NetBeans (incubating) 9.0 Beta released

[Brett Ryan]

Well done. This is a huge undertaking and mass effort to make this happen.

> On 17 Feb 2018, at 01:35, Geertjan Wielenga 
>  wrote:
> 
> The Apache NetBeans team is proud to announce the release of Apache
> NetBeans (incubating) 9.0 Beta.
> 
> Apache NetBeans (incubating) 9.0 Beta constitutes all the modules in
> the Apache NetBeans Git repo, which together provide the NetBeans
> Platform (i.e., the underlying application framework), which was
> released as Apache NetBeans (incubating) 9.0 Alpha, as well as all the
> modules that provide the Java SE-related features of Apache NetBeans.
> In short, Apache NetBeans (incubating) 9.0 Beta is a full IDE for Java
> SE development.
> 
> See the below for the donation status of features that have not been
> donated to Apache yet, i.e., are not part of Apache NetBeans
> (incubating) 9.0 Beta, e.g., features for working with Java EE,
> JavaScript, PHP, C/C++, and more:
> 
> https://cwiki.apache.org/confluence/display/NETBEANS/Apache+Transition
> 
> Note: Apache NetBeans (incubating) 9.0 Beta is primarily focused on IP
> clearance. Its functionality has not been tested — the NetCAT
> (NetBeans Community Acceptance Testing) process will begin now that
> Apache NetBeans (incubating) 9.0 Beta has been released. Watch this
> space for upcoming announcements about NetCAT. When NetCAT completes,
> we will vote on the final release of Apache NetBeans (incubating) 9.0.
> 
> Details on Apache NetBeans (incubating) 9.0 Beta:
> 
> https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+9.0+Beta
> 
> Download and try out Apache NetBeans (incubating) 9.0 Beta:
> 
> https://www.apache.org/dyn/closer.cgi/incubator/netbeans/incubating-netbeans-java/incubating-9.0-beta/
> 
> Work is being done on bringing netbeans.org to Apache. In the
> meantime, refer to the below for all details related to Apache
> NetBeans:
> 
> https://cwiki.apache.org/confluence/display/NETBEANS
> 
> Geertjan
> on behalf of Apache NetBeans PPMC
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: users-h...@netbeans.apache.org
> 
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> 

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

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

Re: Compile on Save for a Kotlin/Maven project

[Emilian Bold]

Such a positive reply email!

I don't have much experience in the Compile on Save / Maven area but I'll try 
in the coming weeks, when I get some spare time, to look into it.

Thanks for reporting the issue.

--emi
​
 Original Message 
 On 15 February 2018 10:30 PM, Mátyás Bene  wrote:

>Here's the JIRA ticket: https://issues.apache.org/jira/browse/NETBEANS-399 as 
>suggested.
>
>From: Mátyás Bene 
>Sent: Thursday, February 15, 2018 20:56
>To: Emilian Bold
>Cc: us...@netbeans.incubator.apache.org
>Subject: Re: Compile on Save for a Kotlin/Maven project
>
>Hi Emilian,
>
>Thank you for your response. I had thought that my email got completely 
>unnoticed, or worse, simply ignored, for the reason you touched below: it's 
>not something that you (officially) support. Just one more reason to be more 
>than happy for any response I get.
>
>To get to the topic: I have already posted this in the plugin's site on Github 
>(https://github.com/JetBrains/kotlin-netbeans/issues/126) but that plugin is 
>not maintained any more (cited reason: lack of users, but obviously there's 
>more to this than meets the
> eye). So i thought I may try my chances getting some guidance in the netbeans 
> group and perhaps, really just perhaps I could get it work - as long as it 
> would not involve changing netbeans internals, just adding some callbacks to 
> the plugin - or what not.
>
>Anyway, I'll try as you suggested on JIRA. The Compile on Save feature is one 
>of the best features of netbeans which makes my productivity with Java EE an 
>order of magnitude higher. Now if I could combine this with the sparseness and 
>advanced capabilities of
> Kotlin, that would be a killer combination. This would be something that 
> would not be possible (AFAIK) with any other IDE today.
>
>M.
>
>From: Emilian Bold 
>Sent: Thursday, February 15, 2018 13:28
>To: Mátyás Bene
>Cc: us...@netbeans.incubator.apache.org
>Subject: Re: Compile on Save for a Kotlin/Maven project
>
>We don't officially support Kotlin out of the box, so it's might be worth also 
>bothering the Kotlin plugin authors so they see they also have NetBeans users 
>and have to support other IDEs too.
>
>I don't believe Compile on Save for Maven projects really executes Maven as it 
>would be too slow I guess. It might do something more low level which explains 
>why it probably doesn't work for Kotlin projects. This might be a workaround 
>we could do on NetBeans
> side. Please report it on JIRA and reference in it the Kotlin-NetBeans plugin 
> issue you also posted.
>
>--emi
>
> Original Message 
>On 13 February 2018 1:15 AM, Mátyás Bene  wrote:
>
>>
>>Dear Netbeans pros,
>>
>>Assuming I have a maven based KOTLIN project by following the guide here: 
>>https://kotlinlang.org/docs/reference/using-maven.html and using the Kotlin 
>>plugin for NB.
>>
>>I am wondering how to enable to Compile On Save in Netbeans 8.2 so that 
>>changes in .kt files are picked up and recompiled automatically?
>>
>>While the FAQ http://wiki.netbeans.org/FaqCompileOnSave states that for maven 
>>projects it actually executes the corresponding maven goals (phases?),  it 
>>does not really seem like the kotlin-maven-plugin was called.
>>
>>Any ideas? Or is Netbeans filtering files that actually trigger the CoS 
>>feature to those with the '.java' extension?
>>
>>M.
>>
>


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

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

Re: TR: java.lang.LinkageError: loader constraint violation: loader

[Emilian Bold]

Try to create a small reproducible suite with this problem.

In theory what you did is correct and you don't have a duplicate of 
commons-configuration but it's hard to debug this over email with partial info.

Also try looking at the actual build output JARs that you have, I'm not 
entirely certain nbm-maven-plugin doesn't bundle things differently. I assume 
you've read stuff like 
http://www.mojohaus.org/nbm-maven-plugin/#Maven_Dependency_vs._NetBeans_runtime_dependency

--emi
​

 Original Message 
 On 16 February 2018 11:40 AM, GRYSPEERDT Bastien [CLEMESSY] 
 wrote:

>
> Hi,
>
> Yes that is what I think too.
>
> I changed my architecture since I posted my issue.
>
> I still have the issue but I think the best is to explain the module 
> hierarchy :
> - I have module A (netbeans module)
>
> - the module A has a maven dependency to module B
>
> - the module B has a dependency to a library 1 (maven java project which is 
> not a Netbeans module).
>
> - the library 1 has dependencies to maven libraries, including 
> commons-configuration.
>
> => The library 1 includes some classes and module A has a class which 
> inherits from one of this classes.
>=> In the super class (in library 1), there is an attribute named 
>"configuration" (which is a "org.apache.commons.configuration.Configuration").
>=> The issue appends when I call a method of the inherited attribute 
>"configuration" in the class of module A.
>
> => in module B, the package "org.apache.commons.configuration" has been 
> declared as "publicPackage" in the "nbm-maven-plugin" in the POM.
>I would have hope that it would be sufficient to avoid that kind of problem, 
>but it is not.
>
> The problem must be that module A and module B both add the classes of the 
> apache "commons-configuration" project to their class loader.
>
> Bastien
>
>
> -Message d'origine-
> De : Emilian Bold [mailto:emilian.b...@protonmail.ch]
> Envoyé : jeudi 15 février 2018 13:13
> À : GRYSPEERDT Bastien [CLEMESSY]
> Cc : us...@netbeans.incubator.apache.org
> Objet : Re: java.lang.LinkageError: loader constraint violation: loader
>
> My guess is that you are bunding twice 
> org/apache/commons/configuration/Configuration (ie. commons-configuration).
>
> Maybe you have two modules that have a library wrapper? Or some other 
> external JAR that also bundles it in a fat jar?
>
> ​--emi
>
>
>  Original Message 
> On 13 February 2018 4:21 PM, GRYSPEERDT Bastien [CLEMESSY] 
> bastien.gryspee...@eiffage.com wrote:
>
>>Hi,
>>I have an application build on the Netbeans Platform that uses some netbeans 
>>modules.
>>These netbeans modules import some subprojects (that are not Netbeans
>> modules). In one of the subproject, I need to call the 
>> org.apache.configuration.Configuration (from “commons-configuration” Apache 
>> project) class to  check that a parameter is true (if it is, I display some 
>> field on a HMI).
>>To set the Configuration install, I do it like this : 
>>VariableSelectorGuiManager.setConfiguration(myInstance) è this is passed as 
>>static.
>>Then, The VariableSelectorGui class gets the configuration instance an 
>>display the fields depending on the parameters of the configuration instance.
>>The problem is the following :
>>-We have a standard Java HMI (not integrated in Netbeans) in which everything 
>>works fine.
>>-With the Netbeans platform, the
>> “VariableSelectorGuiManager.setConfiguration(myInstance)” is done in the 
>> register method of our “ModuleInstall” class. When we try to display the 
>> VariableSelectorGui, this error  is thrown :
>>java.lang.LinkageError: loader constraint violation: loader (instance of 
>>org/netbeans/StandardModule$OneModuleClassLoader) previously initiated 
>>loading for a different type with name 
>>"org/apache/commons/configuration/Configuration"
>>   at java.lang.ClassLoader.defineClass1(Native Method)
>>
>>
>>   at
>>
>>java.lang.ClassLoader.defineClass(ClassLoader.java:760)
>>   at
>>
>>org.netbeans.JarClassLoader.doLoadClass(JarClassLoader.java:311)
>>   at
>>
>>org.netbeans.ProxyClassLoader.selfLoadClass(ProxyClassLoader.java:259)
>>   at
>>
>>org.netbeans.ProxyClassLoader.loadClass(ProxyClassLoader.java:217)
>>   at
>>
>>java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>>   at
>>
>>fr.variable.selector.component.VariableSelectorGui.getCenterPane(Variab
>> leSelectorGui.java:562)
>>   at
>>
>>fr.variable.selector.component.VariableSelectorGui.createComponent(Vari
>> ableSelectorGui.java:821)
>>   at
>>
>>fr.variable.selector.component.VariableSelectorGui.lambda$getComponent$
>> 1(VariableSelectorGui.java:181)
>>   at
>>
>>fr.variable.selector.component.VariableSelectorGui$$Lambda$116/70093424
>> 6.run(Unknown Source)
>>   at
>>
>>com.sun.javafx.application.PlatformImpl.lambda$null$164(PlatformImpl.ja
>> va:292)
>>   at
>>

TR: java.lang.LinkageError: loader constraint violation: loader

[GRYSPEERDT Bastien [CLEMESSY]]

Hi,

Yes that is what I think too.

I changed my architecture since I posted my issue.

I still have the issue but I think the best is to explain the module hierarchy :
- I have module A (netbeans module)
- the module A has a maven dependency to module B
- the module B has a dependency to a library 1 (maven java project which is not 
a Netbeans module).
- the library 1 has dependencies to maven libraries, including 
commons-configuration.

=> The library 1 includes some classes and module A has a class which inherits 
from one of this classes.
=> In the super class (in library 1), there is an attribute named 
"configuration" (which is a "org.apache.commons.configuration.Configuration").
=> The issue appends when I call a method of the inherited attribute 
"configuration" in the class of module A.

=> in module B, the package "org.apache.commons.configuration" has been 
declared as "publicPackage" in the "nbm-maven-plugin" in the POM.
I would have hope that it would be sufficient to avoid that kind of problem, 
but it is not.

The problem must be that module A and module B both add the classes of the 
apache "commons-configuration" project to their class loader.

Bastien


-Message d'origine-
De : Emilian Bold [mailto:emilian.b...@protonmail.ch]
Envoyé : jeudi 15 février 2018 13:13
À : GRYSPEERDT Bastien [CLEMESSY]
Cc : us...@netbeans.incubator.apache.org
Objet : Re: java.lang.LinkageError: loader constraint violation: loader

My guess is that you are bunding twice 
org/apache/commons/configuration/Configuration (ie. commons-configuration).

Maybe you have two modules that have a library wrapper? Or some other external 
JAR that also bundles it in a fat jar?

​--emi


 Original Message 
 On 13 February 2018 4:21 PM, GRYSPEERDT Bastien [CLEMESSY] 
 wrote:

>
>Hi,
>
>
>
>
>
>I have an application build on the Netbeans Platform that uses some netbeans 
>modules.
>
>
>These netbeans modules import some subprojects (that are not Netbeans
>modules). In one of the subproject, I need to call the 
>org.apache.configuration.Configuration (from “commons-configuration” Apache 
>project) class to  check that a parameter is true (if it is, I display some 
>field on a HMI).
>
>
>To set the Configuration install, I do it like this : 
>VariableSelectorGuiManager.setConfiguration(myInstance) è this is passed as 
>static.
>
>
>Then, The VariableSelectorGui class gets the configuration instance an display 
>the fields depending on the parameters of the configuration instance.
>
>
>
>
>
>The problem is the following :
>
>
>-We have a standard Java HMI (not integrated in Netbeans) in which everything 
>works fine.
>
>
>-With the Netbeans platform, the
>“VariableSelectorGuiManager.setConfiguration(myInstance)” is done in the 
>register method of our “ModuleInstall” class. When we try to display the 
>VariableSelectorGui, this error  is thrown :
>
>
>
>
>
>java.lang.LinkageError: loader constraint violation: loader (instance of 
>org/netbeans/StandardModule$OneModuleClassLoader) previously initiated loading 
>for a different type with name "org/apache/commons/configuration/Configuration"
>
>
>at java.lang.ClassLoader.defineClass1(Native Method)
>
>
>at
>java.lang.ClassLoader.defineClass(ClassLoader.java:760)
>
>
>at
>org.netbeans.JarClassLoader.doLoadClass(JarClassLoader.java:311)
>
>
>at
>org.netbeans.ProxyClassLoader.selfLoadClass(ProxyClassLoader.java:259)
>
>
>at
>org.netbeans.ProxyClassLoader.loadClass(ProxyClassLoader.java:217)
>
>
>at
>java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>
>
>at
>fr.variable.selector.component.VariableSelectorGui.getCenterPane(Variab
>leSelectorGui.java:562)
>
>
>at
>fr.variable.selector.component.VariableSelectorGui.createComponent(Vari
>ableSelectorGui.java:821)
>
>
>at
>fr.variable.selector.component.VariableSelectorGui.lambda$getComponent$
>1(VariableSelectorGui.java:181)
>
>
>at
>fr.variable.selector.component.VariableSelectorGui$$Lambda$116/70093424
>6.run(Unknown Source)
>
>
>at
>com.sun.javafx.application.PlatformImpl.lambda$null$164(PlatformImpl.ja
>va:292)
>
>
>at
>com.sun.javafx.application.PlatformImpl$$Lambda$64/1862576770.run(Unkno
>wn Source)
>
>
>at java.security.AccessController.doPrivileged(Native
>Method)
>
>
>at
>com.sun.javafx.application.PlatformImpl.lambda$runLater$165(PlatformImp
>l.java:291)
>
>
>at
>com.sun.javafx.application.PlatformImpl$$Lambda$63/2029243975.run(Unkno
>wn Source)
>
>
>[catch] at
>com.sun.glass.ui.InvokeLaterDispatcher$Future.run(InvokeLaterDispatcher
>.java:95)
>
>
>at com.sun.glass.ui.win.WinApplication._runLoop(Native
>Method)
>
>
>at
>com.sun.glass.ui.win.WinApplication.lambda$null$141(WinApplication.java
>:102)
>
>
>