[jira] [Commented] (NETBEANS-2667) L - Netbeans Dialog API

2019-06-16 Thread Yann Dameron (JIRA)


[ 
https://issues.apache.org/jira/browse/NETBEANS-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16865305#comment-16865305
 ] 

Yann Dameron commented on NETBEANS-2667:


I fixed it. Waiting legal approval before creating the PR.

> L - Netbeans Dialog API
> -
>
> Key: NETBEANS-2667
> URL: https://issues.apache.org/jira/browse/NETBEANS-2667
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - DialogsWizards
>Affects Versions: 11.0
>Reporter: Yann Dameron
>Priority: Minor
> Attachments: example-java-api.png, example-netbeans-api.png
>
>
> This log described an issue observed with the Dialog APIs when you change few 
> look & feel properties. 
> As an example, I defined a border to apply on the OptionPaneUI. 
> When I'm opening an information message with the Java APIs, the rendering 
> looks OK (i.e. the border is in front of the message area and the button 
> area).
> When I'm opening an information message with the Netbeans APIs, the rendering 
> is bad.
> Border is well displayed in front of the original message area and original 
> button area but due to the addition of a new button panel done in 
> org.netbeans.core.windows.services.NbPresenter we have a weird rendering.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

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



[jira] [Created] (NETBEANS-2709) NullPointerException on trying to open Java Platforms

2019-06-16 Thread Levin Messing (JIRA)
Levin Messing created NETBEANS-2709:
---

 Summary: NullPointerException on trying to open Java Platforms
 Key: NETBEANS-2709
 URL: https://issues.apache.org/jira/browse/NETBEANS-2709
 Project: NetBeans
  Issue Type: Bug
  Components: java - Platform
Affects Versions: 11.0
 Environment: Product Version: Apache NetBeans IDE 11.0 (Build 
incubator-netbeans-release-404-on-20190319)
Java: 12.0.1; Java HotSpot(TM) 64-Bit Server VM 12.0.1+12
Runtime: Java(TM) SE Runtime Environment 12.0.1+12
System: Windows 10 version 10.0 running on amd64; Cp1252; de_DE (nb)
Reporter: Levin Messing


 I tried to set "[https://docs.oracle.com/en/java/javase/12/docs/api/]; in Java 
Platforms in Javadoc. (I do not know if it was this exact link)

I closed Java Platforms and then tried to open it again, but it did not open 
and the NullPointerException occurred.

Deleting my config folder under AppData\Roaming\NetBeans fixed this issue.

I was not able to reproduce this error. But the exception may help to find this 
Bug.

 

 

 

 

 

 

{{ }}{{java.lang.NullPointerException}}
{{ at 
org.openide.filesystems.JarArchiveRootProvider.isArchiveFile(JarArchiveRootProvider.java:51)}}
{{ at org.openide.filesystems.FileUtil.getArchiveRoot(FileUtil.java:1850)}}
{{ at 
org.netbeans.modules.java.j2seplatform.platformdefinition.J2SEPlatformCustomizer$PathRenderer.getDisplayName(J2SEPlatformCustomizer.java:800)}}
{{ at 
org.netbeans.modules.java.j2seplatform.platformdefinition.J2SEPlatformCustomizer$PathRenderer.getListCellRendererComponent(J2SEPlatformCustomizer.java:769)}}
{{ at 
java.desktop/javax.swing.plaf.basic.BasicListUI.updateLayoutState(BasicListUI.java:1439)}}
{{ at 
java.desktop/javax.swing.plaf.basic.BasicListUI.maybeUpdateLayoutState(BasicListUI.java:1389)}}
{{ at 
java.desktop/javax.swing.plaf.basic.BasicListUI.getPreferredSize(BasicListUI.java:648)}}
{{ at 
java.desktop/javax.swing.JComponent.getPreferredSize(JComponent.java:1680)}}
{{ at 
java.desktop/javax.swing.ScrollPaneLayout.layoutContainer(ScrollPaneLayout.java:795)}}
{{ at java.desktop/java.awt.Container.layout(Container.java:1537)}}
{{ at java.desktop/java.awt.Container.doLayout(Container.java:1526)}}
{{ at java.desktop/java.awt.Container.validateTree(Container.java:1722)}}
{{ at java.desktop/java.awt.Container.validateTree(Container.java:1731)}}
{{ at java.desktop/java.awt.Container.validateTree(Container.java:1731)}}
{{ at java.desktop/java.awt.Container.validateTree(Container.java:1731)}}
{{ at java.desktop/java.awt.Container.validateTree(Container.java:1731)}}
{{ at java.desktop/java.awt.Container.validateTree(Container.java:1731)}}
{{ at java.desktop/java.awt.Container.validateTree(Container.java:1731)}}
{{ at java.desktop/java.awt.Container.validateTree(Container.java:1731)}}
{{ at java.desktop/java.awt.Container.validateTree(Container.java:1731)}}
{{ at java.desktop/java.awt.Container.validateTree(Container.java:1731)}}
{{ at java.desktop/java.awt.Container.validateTree(Container.java:1731)}}
{{ at java.desktop/java.awt.Container.validate(Container.java:1657)}}
{{ at java.desktop/java.awt.Window.dispatchEventImpl(Window.java:2760)}}
{{ at java.desktop/java.awt.Component.dispatchEvent(Component.java:4840)}}
{{ at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:772)}}
{{ at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721)}}
{{ at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715)}}
{{ at 
java.base/java.security.AccessController.doPrivileged(AccessController.java:389)}}
{{ at 
java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)}}
{{ at 
java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:95)}}
{{ at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:745)}}
{{ at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:743)}}
{{ at 
java.base/java.security.AccessController.doPrivileged(AccessController.java:389)}}
{{ at 
java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)}}
{{ at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:742)}}
{{ at 
org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:136)}}
{{[catch] at 
java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)}}
{{ at 
java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)}}
{{ at 
java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)}}
{{ at 
java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109)}}
{{ at 
java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)}}
{{ at 
java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90)}}



--

[jira] [Commented] (NETBEANS-2708) New feature: Argument hints for method (function) calls

2019-06-16 Thread Vladimir Jelovac (JIRA)


[ 
https://issues.apache.org/jira/browse/NETBEANS-2708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16865055#comment-16865055
 ] 

Vladimir Jelovac commented on NETBEANS-2708:


Great, that's exactly what I was looking for.

Ty.

> New feature: Argument hints for method (function) calls
> ---
>
> Key: NETBEANS-2708
> URL: https://issues.apache.org/jira/browse/NETBEANS-2708
> Project: NetBeans
>  Issue Type: Wish
>  Components: editor - Hints  Annotations
>Reporter: Vladimir Jelovac
>Priority: Minor
> Attachments: idea_parameter_hints.png
>
>
> Often when inspecting a method call which consists of multiple arguments we 
> need to go to the definition of that method and find out what that argument 
> is about when dealing with badly named variables or direct scalar assignments.
> IntelJ IDEA added few years ago a nice feature called parameter hints which 
> solves the above issue: 
> [https://www.jetbrains.com/help/idea/viewing-reference-information.html#parameter-hints]
> Basically how it works is that it adds in front of the argument the original 
> name of that argument which has been defined in the methods definition. By 
> default the hints are shown only for arguments which have direct assignments 
> however this is configurable and can be set to show for all arguments. Also 
> there is an option to enable disable this using a shortcut key combination.
> Example:
> !idea_parameter_hints.png!
> It would be nice to see such feature implemented in NetBeans as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

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



[jira] [Commented] (NETBEANS-2708) New feature: Argument hints for method (function) calls

2019-06-16 Thread Geertjan Wielenga (JIRA)


[ 
https://issues.apache.org/jira/browse/NETBEANS-2708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16865052#comment-16865052
 ] 

Geertjan Wielenga commented on NETBEANS-2708:
-

See https://github.com/apache/netbeans/pull/1247.

> New feature: Argument hints for method (function) calls
> ---
>
> Key: NETBEANS-2708
> URL: https://issues.apache.org/jira/browse/NETBEANS-2708
> Project: NetBeans
>  Issue Type: Wish
>  Components: editor - Hints  Annotations
>Reporter: Vladimir Jelovac
>Priority: Minor
> Attachments: idea_parameter_hints.png
>
>
> Often when inspecting a method call which consists of multiple arguments we 
> need to go to the definition of that method and find out what that argument 
> is about when dealing with badly named variables or direct scalar assignments.
> IntelJ IDEA added few years ago a nice feature called parameter hints which 
> solves the above issue: 
> [https://www.jetbrains.com/help/idea/viewing-reference-information.html#parameter-hints]
> Basically how it works is that it adds in front of the argument the original 
> name of that argument which has been defined in the methods definition. By 
> default the hints are shown only for arguments which have direct assignments 
> however this is configurable and can be set to show for all arguments. Also 
> there is an option to enable disable this using a shortcut key combination.
> Example:
> !idea_parameter_hints.png!
> It would be nice to see such feature implemented in NetBeans as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

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



[jira] [Created] (NETBEANS-2708) New feature: Argument hints for method (function) calls

2019-06-16 Thread Vladimir Jelovac (JIRA)
Vladimir Jelovac created NETBEANS-2708:
--

 Summary: New feature: Argument hints for method (function) calls
 Key: NETBEANS-2708
 URL: https://issues.apache.org/jira/browse/NETBEANS-2708
 Project: NetBeans
  Issue Type: Wish
  Components: editor - Hints  Annotations
Reporter: Vladimir Jelovac
 Attachments: idea_parameter_hints.png

Often when inspecting a method call which consists of multiple arguments we 
need to go to the definition of that method and find out what that argument is 
about when dealing with badly named variables or direct scalar assignments.

IntelJ IDEA added few years ago a nice feature called parameter hints which 
solves the above issue: 
[https://www.jetbrains.com/help/idea/viewing-reference-information.html#parameter-hints]

Basically how it works is that it adds in front of the argument the original 
name of that argument which has been defined in the methods definition. By 
default the hints are shown only for arguments which have direct assignments 
however this is configurable and can be set to show for all arguments. Also 
there is an option to enable disable this using a shortcut key combination.

Example:

!idea_parameter_hints.png!

It would be nice to see such feature implemented in NetBeans as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

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



[netbeans] branch travis-openjdk deleted (was e65178b)

2019-06-16 Thread lkishalmi
This is an automated email from the ASF dual-hosted git repository.

lkishalmi pushed a change to branch travis-openjdk
in repository https://gitbox.apache.org/repos/asf/netbeans.git.


 was e65178b  Update .travis.yml

The revisions that were on this branch are still contained in
other references; therefore, this change does not discard any commits
from the repository.


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

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



[jira] [Created] (NETBEANS-2707) source path for java.logging not accepted

2019-06-16 Thread Manfred Steiner (JIRA)
Manfred Steiner created NETBEANS-2707:
-

 Summary: source path for java.logging not accepted
 Key: NETBEANS-2707
 URL: https://issues.apache.org/jira/browse/NETBEANS-2707
 Project: NetBeans
  Issue Type: Bug
Affects Versions: 11.0
 Environment: Ubuntu 18.04 amd64
Reporter: Manfred Steiner


Java sources (src.zip) extracted to _folder_. Then _folder/java.logging_ added 
to Java Platform/Sources list. But Navigate->Go to source does not work.
 (Same procedure for java.desktop works after reordering Platform/Sources list).

Netbeans generates following message in shell (java.logging is missing although 
in list of Java Platforms->Java).
{quote}{{INFO [org.netbeans.modules.java.classfile.CodeGenerator]: Cannot find 
resource: java/util/logging/LogRecord.class on classpath
 
:nbjrt:[file:/usr/lib/jvm/java-11-openjdk-amd64/!/modules/java.base/|file:///usr/lib/jvm/java-11-openjdk-amd64/!/modules/java.base/]
 
:nbjrt:[file:/usr/lib/jvm/java-11-openjdk-amd64/!/modules/java.compiler/|file:///usr/lib/jvm/java-11-openjdk-amd64/!/modules/java.compiler/]
 
:nbjrt:[file:/usr/lib/jvm/java-11-openjdk-amd64/!/modules/java.datatransfer/|file:///usr/lib/jvm/java-11-openjdk-amd64/!/modules/java.datatransfer/]
 
:nbjrt:[file:/usr/lib/jvm/java-11-openjdk-amd64/!/modules/java.desktop/|file:///usr/lib/jvm/java-11-openjdk-amd64/!/modules/java.desktop/]
 
:nbjrt:[file:/usr/lib/jvm/java-11-openjdk-amd64/!/modules/java.management/|file:///usr/lib/jvm/java-11-openjdk-amd64/!/modules/java.management/]
 
:nbjrt:[file:/usr/lib/jvm/java-11-openjdk-amd64/!/modules/java.naming/|file:///usr/lib/jvm/java-11-openjdk-amd64/!/modules/java.naming/]
 
:nbjrt:[file:/usr/lib/jvm/java-11-openjdk-amd64/!/modules/java.prefs/|file:///usr/lib/jvm/java-11-openjdk-amd64/!/modules/java.prefs/]
 
:nbjrt:[file:/usr/lib/jvm/java-11-openjdk-amd64/!/modules/java.scripting/|file:///usr/lib/jvm/java-11-openjdk-amd64/!/modules/java.scripting/]
 
:nbjrt:[file:/usr/lib/jvm/java-11-openjdk-amd64/!/modules/java.security.jgss/|file:///usr/lib/jvm/java-11-openjdk-amd64/!/modules/java.security.jgss/]
 
:nbjrt:[file:/usr/lib/jvm/java-11-openjdk-amd64/!/modules/java.xml/|file:///usr/lib/jvm/java-11-openjdk-amd64/!/modules/java.xml/]
 
:nbjrt:[file:/usr/lib/jvm/java-11-openjdk-amd64/!/modules/jdk.accessibility/|file:///usr/lib/jvm/java-11-openjdk-amd64/!/modules/jdk.accessibility/]
 
:nbjrt:[file:/usr/lib/jvm/java-11-openjdk-amd64/!/modules/jdk.attach/|file:///usr/lib/jvm/java-11-openjdk-amd64/!/modules/jdk.attach/]
 
:nbjrt:[file:/usr/lib/jvm/java-11-openjdk-amd64/!/modules/jdk.compiler/|file:///usr/lib/jvm/java-11-openjdk-amd64/!/modules/jdk.compiler/]
 
:nbjrt:[file:/usr/lib/jvm/java-11-openjdk-amd64/!/modules/jdk.dynalink/|file:///usr/lib/jvm/java-11-openjdk-amd64/!/modules/jdk.dynalink/]
 
:nbjrt:[file:/usr/lib/jvm/java-11-openjdk-amd64/!/modules/jdk.httpserver/|file:///usr/lib/jvm/java-11-openjdk-amd64/!/modules/jdk.httpserver/]
 
:nbjrt:[file:/usr/lib/jvm/java-11-openjdk-amd64/!/modules/jdk.jartool/|file:///usr/lib/jvm/java-11-openjdk-amd64/!/modules/jdk.jartool/]
 
:nbjrt:[file:/usr/lib/jvm/java-11-openjdk-amd64/!/modules/jdk.javadoc/|file:///usr/lib/jvm/java-11-openjdk-amd64/!/modules/jdk.javadoc/]
 
:nbjrt:[file:/usr/lib/jvm/java-11-openjdk-amd64/!/modules/jdk.jconsole/|file:///usr/lib/jvm/java-11-openjdk-amd64/!/modules/jdk.jconsole/]
 
:nbjrt:[file:/usr/lib/jvm/java-11-openjdk-amd64/!/modules/jdk.jdi/|file:///usr/lib/jvm/java-11-openjdk-amd64/!/modules/jdk.jdi/]
 
:nbjrt:[file:/usr/lib/jvm/java-11-openjdk-amd64/!/modules/jdk.jfr/|file:///usr/lib/jvm/java-11-openjdk-amd64/!/modules/jdk.jfr/]
 
:nbjrt:[file:/usr/lib/jvm/java-11-openjdk-amd64/!/modules/jdk.jshell/|file:///usr/lib/jvm/java-11-openjdk-amd64/!/modules/jdk.jshell/]
 
:nbjrt:[file:/usr/lib/jvm/java-11-openjdk-amd64/!/modules/jdk.jsobject/|file:///usr/lib/jvm/java-11-openjdk-amd64/!/modules/jdk.jsobject/]
 
:nbjrt:[file:/usr/lib/jvm/java-11-openjdk-amd64/!/modules/jdk.management/|file:///usr/lib/jvm/java-11-openjdk-amd64/!/modules/jdk.management/]
 
:nbjrt:[file:/usr/lib/jvm/java-11-openjdk-amd64/!/modules/jdk.management.jfr/|file:///usr/lib/jvm/java-11-openjdk-amd64/!/modules/jdk.management.jfr/]
 
:nbjrt:[file:/usr/lib/jvm/java-11-openjdk-amd64/!/modules/jdk.net/|file:///usr/lib/jvm/java-11-openjdk-amd64/!/modules/jdk.net/]
 
:nbjrt:[file:/usr/lib/jvm/java-11-openjdk-amd64/!/modules/jdk.scripting.nashorn/|file:///usr/lib/jvm/java-11-openjdk-amd64/!/modules/jdk.scripting.nashorn/]
 
:nbjrt:[file:/usr/lib/jvm/java-11-openjdk-amd64/!/modules/jdk.sctp/|file:///usr/lib/jvm/java-11-openjdk-amd64/!/modules/jdk.sctp/]
 
:nbjrt:[file:/usr/lib/jvm/java-11-openjdk-amd64/!/modules/jdk.security.auth/|file:///usr/lib/jvm/java-11-openjdk-amd64/!/modules/jdk.security.auth/]
 

[jira] [Created] (NETBEANS-2706) variable information is not available, source compiled without -g option

2019-06-16 Thread Yougeshwar Khatri (JIRA)
Yougeshwar Khatri created NETBEANS-2706:
---

 Summary: variable information is not available, source compiled 
without -g option
 Key: NETBEANS-2706
 URL: https://issues.apache.org/jira/browse/NETBEANS-2706
 Project: NetBeans
  Issue Type: Bug
  Components: apisupport - Maven, cnd - Debugger
Affects Versions: 8.2
Reporter: Yougeshwar Khatri


Hi,

During debugging local variables not showing and gives this information 
"variable information is not available, source compiled without -g option"

 

Please help in this

 

Thanks



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

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



[jira] [Closed] (NETBEANS-1204) Make Wicket generated Web-Apps work

2019-06-16 Thread Pete Whelpton (JIRA)


 [ 
https://issues.apache.org/jira/browse/NETBEANS-1204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pete Whelpton closed NETBEANS-1204.
---
Resolution: Not A Bug

I submitted a fix to the Apache Wicket project.  This will be fixed in Wicket 
8.6.0, so I'm closing this ticket as Not A Bug.

> Make Wicket generated Web-Apps work
> ---
>
> Key: NETBEANS-1204
> URL: https://issues.apache.org/jira/browse/NETBEANS-1204
> Project: NetBeans
>  Issue Type: Improvement
>  Components: serverplugins - GlassFish
>Affects Versions: 8.2
>Reporter: Peter Nabbefeld
>Priority: Major
>
> Could not yet test with NB 9.0, so added only version 8.2.
> Added Glassfish 5 as a Glassfish server type, but when I try to run my 
> project, I get the following error:
> java.io.IOException: org.xml.sax.SAXParseExceptionpublicId: 
> [file:/opt/glassfish5/glassfish/lib/schemas/web-app_3_1.xsd|file:///opt/glassfish5/glassfish/lib/schemas/web-app_3_1.xsd];
>  lineNumber: 8; columnNumber: 27; Deployment descriptor file WEB-INF/web.xml 
> in archive [PrivateCookingReceipes-1.0-SNAPSHOT].  TargetNamespace.1: 
> Namespace 'http://java.sun.com/xml/ns/javaee' wird erwartet, aber der 
> Ziel-Namespace des Schemadokuments ist '[http://xmlns.jcp.org/xml/ns/javaee'.]
> Sorry for the German message. It says the target namespace of the web.xml 
> schema does not fit, obviously this is checked by the glassfish plugin 
> (expected 'http://java.sun.com/xml/ns/javaee' but found 
> '[http://xmlns.jcp.org/xml/ns/javaee'|http://xmlns.jcp.org/xml/ns/javaee'.]).
> Probably it'd be sufficient to just test for both namespaces depending on 
> glassfish version.
> 
> While I first thought it's a problem with the Glassfish version, it turns out 
> to be a problem with the web.xml generated by Wicket Quickstart. I replaced 
> the schema declaration with another one copied from a web.xml generated by 
> NetBeans, after this change I can start my web app.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

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



[jira] [Updated] (NETBEANS-2705) allowExperimentalOptions support in org.netbeans.api.scripting.Scripting API

2019-06-16 Thread Gaurav Gupta (JIRA)


 [ 
https://issues.apache.org/jira/browse/NETBEANS-2705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gaurav Gupta updated NETBEANS-2705:
---
Description: 
If using Nashorn compatibility mode via setting the system property 
'*polyglot.js.nashorn-compat*', then on creation of script manager with 
'*Scripting.createManager()..getEngineByName("GraalVM:js")*' following 
exception is thrown :
{code:java}
js.nashorn-compat is experimental and must be enabled with 
allowExperimentalOptions()
{code}
See the Nashorn Migration Guide for more info: 
[https://github.com/graalvm/graaljs/blob/master/docs/user/NashornMigrationGuide.md
 ]

  was:
If using Nashorn compatibility mode via setting the system property 
'*polyglot.js.nashorn-compat*', then on creation of script manager with 
'*Scripting.createManager()..getEngineByName("GraalVM:js")*' folowing exception 
is thrown :
{code:java}
js.nashorn-compat is experimental and must be enabled with 
allowExperimentalOptions()
{code}
See the Nashorn Migration Guide for more info: 
[https://github.com/graalvm/graaljs/blob/master/docs/user/NashornMigrationGuide.md
]


> allowExperimentalOptions support in org.netbeans.api.scripting.Scripting API
> 
>
> Key: NETBEANS-2705
> URL: https://issues.apache.org/jira/browse/NETBEANS-2705
> Project: NetBeans
>  Issue Type: Improvement
>Affects Versions: 11.0
>Reporter: Gaurav Gupta
>Priority: Major
>  Labels: API, Scripting, js
>
> If using Nashorn compatibility mode via setting the system property 
> '*polyglot.js.nashorn-compat*', then on creation of script manager with 
> '*Scripting.createManager()..getEngineByName("GraalVM:js")*' following 
> exception is thrown :
> {code:java}
> js.nashorn-compat is experimental and must be enabled with 
> allowExperimentalOptions()
> {code}
> See the Nashorn Migration Guide for more info: 
> [https://github.com/graalvm/graaljs/blob/master/docs/user/NashornMigrationGuide.md
>  ]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

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



[jira] [Created] (NETBEANS-2705) allowExperimentalOptions support in org.netbeans.api.scripting.Scripting API

2019-06-16 Thread Gaurav Gupta (JIRA)
Gaurav Gupta created NETBEANS-2705:
--

 Summary: allowExperimentalOptions support in 
org.netbeans.api.scripting.Scripting API
 Key: NETBEANS-2705
 URL: https://issues.apache.org/jira/browse/NETBEANS-2705
 Project: NetBeans
  Issue Type: Improvement
Affects Versions: 11.0
Reporter: Gaurav Gupta


If using Nashorn compatibility mode via setting the system property 
'*polyglot.js.nashorn-compat*', then on creation of script manager with 
'*Scripting.createManager()..getEngineByName("GraalVM:js")*' folowing exception 
is thrown :
{code:java}
js.nashorn-compat is experimental and must be enabled with 
allowExperimentalOptions()
{code}
See the Nashorn Migration Guide for more info: 
[https://github.com/graalvm/graaljs/blob/master/docs/user/NashornMigrationGuide.md
]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

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