[jira] [Commented] (NETBEANS-373) Netbeans sometimes freezes when showing any refactor dialog when running with jdk 1.8.0_152-b16 or later

2018-04-06 Thread Gili (JIRA)

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

Gili commented on NETBEANS-373:
---

[~Sir Intellegence] Good question, I'm not sure. [~jlahoda] probably knows the 
answer.

> Netbeans sometimes freezes when showing any refactor dialog when running with 
> jdk 1.8.0_152-b16 or later
> 
>
> Key: NETBEANS-373
> URL: https://issues.apache.org/jira/browse/NETBEANS-373
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Refactoring
>Affects Versions: 8.2, 9.0
> Environment: Mac
>Reporter: Austin Stephens
>Priority: Blocker
> Attachments: Screen Shot 2018-04-02 at 11.22.11 AM.png, Screen Shot 
> 2018-04-02 at 11.23.15 AM.png, nbpresenter.diff
>
>
> Sometimes (or almost always), when you try to do some refactor action, 
> NetBeans freezes. It appears that a lock is obtained on a panel when the 
> dialog is shown, and the AppKit Thread tries to get the lock while trying to 
> add an accessible listener to it.
> AppKit Thread:
> {code:java}
> Container.addContainerListener:2142    
> Container$AccessibleAWTContainer.addPropertyChangeListener:3885    
> JComponent$AccessibleJComponent.addPropertyChangeListener:3765    
> Hidden Source Calls    
> CAccessible.addNotificationListeners:102    
> CAccessible.:84    
> CAccessible.getCAccessible:60
> {code}
> EDT Thread:
> {code:java}
> Hidden Source Calls    
> Unsafe.park    
> LockSupport.park:194    
> AbstractQueuedSynchronizer$ConditionObject.await:2062    
> EventQueue.getNextEvent:557    
> EventDispatchThread.pumpOneEventForFilters:173    
> EventDispatchThread.pumpEventsForFilter:124    
> EventDispatchThread.pumpEventsForFilter:117    
> WaitDispatchSupport$2.run:190    
> WaitDispatchSupport$4.run:235    
> WaitDispatchSupport$4.run:233    
> AccessController.doPrivileged    
> WaitDispatchSupport.enter:233    
> Dialog.show:1070    
> NbPresenter.superShow:1060    
> NbPresenter.doShow:1110    
> NbPresenter.run:1082    
> NbPresenter.run:105    
> NbMutexEventProvider$Event.doEventAccess:115    
> NbMutexEventProvider$Event.readAccess:75    
> LazyMutexImplementation.readAccess:71    
> Mutex.readAccess:193    
> NbPresenter.show:1067    
> Component.show:1669    
> Component.setVisible:1616    
> Window.setVisible:1017    
> Dialog.setVisible:1005    
> ParametersPanel.showDialog:674    
> RefactoringPanel.refresh:660    
> RefactoringPanel.:144    
> UI.openRefactoringUI:61    
> ContextAnalyzer$4.show:648    
> ContextAnalyzer$TextComponentTask.run:369    
> RefactoringActionsProvider.doFindUsages:232    
> ActionsImplementationFactory.doFindUsages:91    
> WhereUsedAction.performAction:52    
> RefactoringGlobalAction$ContextAction.actionPerformed:172    
> TopComponent.processKeyBinding:1151    
> JComponent.processKeyBindings:2963    
> JComponent.processKeyEvent:2863    
> Component.processEvent:6355    
> Container.processEvent:2259    
> Component.dispatchEventImpl:4961    
> Container.dispatchEventImpl:2317    
> Component.dispatchEvent:4793    
> KeyboardFocusManager.redispatchEvent:1955    
> DefaultKeyboardFocusManager.dispatchKeyEvent:827    
> DefaultKeyboardFocusManager.preDispatchKeyEvent:1096    
> DefaultKeyboardFocusManager.typeAheadAssertions:966    
> DefaultKeyboardFocusManager.dispatchEvent:792    
> Component.dispatchEventImpl:4842    
> Container.dispatchEventImpl:2317    
> Window.dispatchEventImpl:2758    
> Component.dispatchEvent:4793    
> EventQueue.dispatchEventImpl:766    
> EventQueue.access$500:97    
> EventQueue$3.run:717    
> EventQueue$3.run:711    
> AccessController.doPrivileged    
> ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege:89    
> ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege:99    
> EventQueue$4.run:739    
> EventQueue$4.run:737    
> AccessController.doPrivileged    
> ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege:89    
> EventQueue.dispatchEvent:736    
> TimableEventQueue.dispatchEvent:136    
> EventDispatchThread.pumpOneEventForFilters:199    
> EventDispatchThread.pumpEventsForFilter:124    
> EventDispatchThread.pumpEventsForHierarchy:113    
> EventDispatchThread.pumpEvents:109    
> EventDispatchThread.pumpEvents:101    
> EventDispatchThread.run:90   
> {code}
>  



--
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-373) Netbeans sometimes freezes when showing any refactor dialog when running with jdk 1.8.0_152-b16 or later

2018-04-06 Thread Austin Stephens (JIRA)

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

Austin Stephens commented on NETBEANS-373:
--

[~cowwoc] I was checking that one. I meant the one before that. The sources 
page 
([https://web.archive.org/web/20171022112341/https://netbeans.org/community/sources/])
 (using a wayback machine link since it will likely change) mentions "the old 
CVS repository". I was thinking the refactor sources would have come from there 
possibly since I don't know where else the code could have come from. Here is a 
link to the revision I tracked the things down to: 
http://hg.netbeans.org/releases/rev/bb5436a892c1

> Netbeans sometimes freezes when showing any refactor dialog when running with 
> jdk 1.8.0_152-b16 or later
> 
>
> Key: NETBEANS-373
> URL: https://issues.apache.org/jira/browse/NETBEANS-373
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Refactoring
>Affects Versions: 8.2, 9.0
> Environment: Mac
>Reporter: Austin Stephens
>Priority: Blocker
> Attachments: Screen Shot 2018-04-02 at 11.22.11 AM.png, Screen Shot 
> 2018-04-02 at 11.23.15 AM.png, nbpresenter.diff
>
>
> Sometimes (or almost always), when you try to do some refactor action, 
> NetBeans freezes. It appears that a lock is obtained on a panel when the 
> dialog is shown, and the AppKit Thread tries to get the lock while trying to 
> add an accessible listener to it.
> AppKit Thread:
> {code:java}
> Container.addContainerListener:2142    
> Container$AccessibleAWTContainer.addPropertyChangeListener:3885    
> JComponent$AccessibleJComponent.addPropertyChangeListener:3765    
> Hidden Source Calls    
> CAccessible.addNotificationListeners:102    
> CAccessible.:84    
> CAccessible.getCAccessible:60
> {code}
> EDT Thread:
> {code:java}
> Hidden Source Calls    
> Unsafe.park    
> LockSupport.park:194    
> AbstractQueuedSynchronizer$ConditionObject.await:2062    
> EventQueue.getNextEvent:557    
> EventDispatchThread.pumpOneEventForFilters:173    
> EventDispatchThread.pumpEventsForFilter:124    
> EventDispatchThread.pumpEventsForFilter:117    
> WaitDispatchSupport$2.run:190    
> WaitDispatchSupport$4.run:235    
> WaitDispatchSupport$4.run:233    
> AccessController.doPrivileged    
> WaitDispatchSupport.enter:233    
> Dialog.show:1070    
> NbPresenter.superShow:1060    
> NbPresenter.doShow:1110    
> NbPresenter.run:1082    
> NbPresenter.run:105    
> NbMutexEventProvider$Event.doEventAccess:115    
> NbMutexEventProvider$Event.readAccess:75    
> LazyMutexImplementation.readAccess:71    
> Mutex.readAccess:193    
> NbPresenter.show:1067    
> Component.show:1669    
> Component.setVisible:1616    
> Window.setVisible:1017    
> Dialog.setVisible:1005    
> ParametersPanel.showDialog:674    
> RefactoringPanel.refresh:660    
> RefactoringPanel.:144    
> UI.openRefactoringUI:61    
> ContextAnalyzer$4.show:648    
> ContextAnalyzer$TextComponentTask.run:369    
> RefactoringActionsProvider.doFindUsages:232    
> ActionsImplementationFactory.doFindUsages:91    
> WhereUsedAction.performAction:52    
> RefactoringGlobalAction$ContextAction.actionPerformed:172    
> TopComponent.processKeyBinding:1151    
> JComponent.processKeyBindings:2963    
> JComponent.processKeyEvent:2863    
> Component.processEvent:6355    
> Container.processEvent:2259    
> Component.dispatchEventImpl:4961    
> Container.dispatchEventImpl:2317    
> Component.dispatchEvent:4793    
> KeyboardFocusManager.redispatchEvent:1955    
> DefaultKeyboardFocusManager.dispatchKeyEvent:827    
> DefaultKeyboardFocusManager.preDispatchKeyEvent:1096    
> DefaultKeyboardFocusManager.typeAheadAssertions:966    
> DefaultKeyboardFocusManager.dispatchEvent:792    
> Component.dispatchEventImpl:4842    
> Container.dispatchEventImpl:2317    
> Window.dispatchEventImpl:2758    
> Component.dispatchEvent:4793    
> EventQueue.dispatchEventImpl:766    
> EventQueue.access$500:97    
> EventQueue$3.run:717    
> EventQueue$3.run:711    
> AccessController.doPrivileged    
> ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege:89    
> ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege:99    
> EventQueue$4.run:739    
> EventQueue$4.run:737    
> AccessController.doPrivileged    
> ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege:89    
> EventQueue.dispatchEvent:736    
> TimableEventQueue.dispatchEvent:136    
> EventDispatchThread.pumpOneEventForFilters:199    
> EventDispatchThread.pumpEventsForFilter:124    
> EventDispatchThread.pumpEventsForHierarchy:113    
> EventDispatchThread.pumpEvents:109    
> EventDispatchThread.pumpEvents:101    
> EventDispatchThread.run:90   

[jira] [Commented] (NETBEANS-373) Netbeans sometimes freezes when showing any refactor dialog when running with jdk 1.8.0_152-b16 or later

2018-04-06 Thread Gili (JIRA)

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

Gili commented on NETBEANS-373:
---

[~Sir Intellegence] I think you're looking for this: 
https://github.com/apache/incubator-netbeans#full-history

> Netbeans sometimes freezes when showing any refactor dialog when running with 
> jdk 1.8.0_152-b16 or later
> 
>
> Key: NETBEANS-373
> URL: https://issues.apache.org/jira/browse/NETBEANS-373
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Refactoring
>Affects Versions: 8.2, 9.0
> Environment: Mac
>Reporter: Austin Stephens
>Priority: Blocker
> Attachments: Screen Shot 2018-04-02 at 11.22.11 AM.png, Screen Shot 
> 2018-04-02 at 11.23.15 AM.png, nbpresenter.diff
>
>
> Sometimes (or almost always), when you try to do some refactor action, 
> NetBeans freezes. It appears that a lock is obtained on a panel when the 
> dialog is shown, and the AppKit Thread tries to get the lock while trying to 
> add an accessible listener to it.
> AppKit Thread:
> {code:java}
> Container.addContainerListener:2142    
> Container$AccessibleAWTContainer.addPropertyChangeListener:3885    
> JComponent$AccessibleJComponent.addPropertyChangeListener:3765    
> Hidden Source Calls    
> CAccessible.addNotificationListeners:102    
> CAccessible.:84    
> CAccessible.getCAccessible:60
> {code}
> EDT Thread:
> {code:java}
> Hidden Source Calls    
> Unsafe.park    
> LockSupport.park:194    
> AbstractQueuedSynchronizer$ConditionObject.await:2062    
> EventQueue.getNextEvent:557    
> EventDispatchThread.pumpOneEventForFilters:173    
> EventDispatchThread.pumpEventsForFilter:124    
> EventDispatchThread.pumpEventsForFilter:117    
> WaitDispatchSupport$2.run:190    
> WaitDispatchSupport$4.run:235    
> WaitDispatchSupport$4.run:233    
> AccessController.doPrivileged    
> WaitDispatchSupport.enter:233    
> Dialog.show:1070    
> NbPresenter.superShow:1060    
> NbPresenter.doShow:1110    
> NbPresenter.run:1082    
> NbPresenter.run:105    
> NbMutexEventProvider$Event.doEventAccess:115    
> NbMutexEventProvider$Event.readAccess:75    
> LazyMutexImplementation.readAccess:71    
> Mutex.readAccess:193    
> NbPresenter.show:1067    
> Component.show:1669    
> Component.setVisible:1616    
> Window.setVisible:1017    
> Dialog.setVisible:1005    
> ParametersPanel.showDialog:674    
> RefactoringPanel.refresh:660    
> RefactoringPanel.:144    
> UI.openRefactoringUI:61    
> ContextAnalyzer$4.show:648    
> ContextAnalyzer$TextComponentTask.run:369    
> RefactoringActionsProvider.doFindUsages:232    
> ActionsImplementationFactory.doFindUsages:91    
> WhereUsedAction.performAction:52    
> RefactoringGlobalAction$ContextAction.actionPerformed:172    
> TopComponent.processKeyBinding:1151    
> JComponent.processKeyBindings:2963    
> JComponent.processKeyEvent:2863    
> Component.processEvent:6355    
> Container.processEvent:2259    
> Component.dispatchEventImpl:4961    
> Container.dispatchEventImpl:2317    
> Component.dispatchEvent:4793    
> KeyboardFocusManager.redispatchEvent:1955    
> DefaultKeyboardFocusManager.dispatchKeyEvent:827    
> DefaultKeyboardFocusManager.preDispatchKeyEvent:1096    
> DefaultKeyboardFocusManager.typeAheadAssertions:966    
> DefaultKeyboardFocusManager.dispatchEvent:792    
> Component.dispatchEventImpl:4842    
> Container.dispatchEventImpl:2317    
> Window.dispatchEventImpl:2758    
> Component.dispatchEvent:4793    
> EventQueue.dispatchEventImpl:766    
> EventQueue.access$500:97    
> EventQueue$3.run:717    
> EventQueue$3.run:711    
> AccessController.doPrivileged    
> ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege:89    
> ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege:99    
> EventQueue$4.run:739    
> EventQueue$4.run:737    
> AccessController.doPrivileged    
> ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege:89    
> EventQueue.dispatchEvent:736    
> TimableEventQueue.dispatchEvent:136    
> EventDispatchThread.pumpOneEventForFilters:199    
> EventDispatchThread.pumpEventsForFilter:124    
> EventDispatchThread.pumpEventsForHierarchy:113    
> EventDispatchThread.pumpEvents:109    
> EventDispatchThread.pumpEvents:101    
> EventDispatchThread.run:90   
> {code}
>  



--
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-618) JDK 10 Profiler: When profiling "Selected Classes", intermittant java.lang.ClassNotFoundException is thrown

2018-04-06 Thread Josh Juneau (JIRA)
Josh Juneau created NETBEANS-618:


 Summary: JDK 10 Profiler:  When profiling "Selected Classes", 
intermittant java.lang.ClassNotFoundException is thrown
 Key: NETBEANS-618
 URL: https://issues.apache.org/jira/browse/NETBEANS-618
 Project: NetBeans
  Issue Type: Bug
  Components: cnd - Profile
Affects Versions: 9.0
 Environment: OS X 10.12.6
Reporter: Josh Juneau
 Fix For: 9.0


When profiling under JDK 10 and using "Selected Classes" option, the following 
error is thrown after clicking "Apply" and the profiled application starts up.  
This occurred during one of the Profiler tests with the AnagramGame.

 

java.lang.ClassNotFoundException: java/lang/reflect/WeakPairMap$Pair
at java.base/java.lang.Class.forName0(Native Method)
at java.base/java.lang.Class.forName(Class.java:291)
at 
org.netbeans.lib.profiler.server.ProfilerInterface$InitiateProfilingThread.initiateInstrumentation(ProfilerInterface.java:165)
at 
org.netbeans.lib.profiler.server.ProfilerInterface$InitiateProfilingThread.run(ProfilerInterface.java:117)

   



--
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-430) "Invalid or deleted file", "Absent Code attribute" exceptions during Java editing and app/test running

2018-04-06 Thread Eirik Bakke (JIRA)

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

Eirik Bakke commented on NETBEANS-430:
--

A similar error is reported at 
https://issues.apache.org/jira/browse/NETBEANS-564 , with confirmed steps to 
reproduce. In the latter case the file is in an Ant project as opposed to a 
Maven project.

> "Invalid or deleted file", "Absent Code attribute" exceptions during Java 
> editing and app/test running
> --
>
> Key: NETBEANS-430
> URL: https://issues.apache.org/jira/browse/NETBEANS-430
> Project: NetBeans
>  Issue Type: Bug
>  Components: guibuilder - Code, java - Classfile, java - Source, 
> projects - Maven
>Affects Versions: 9.0
> Environment: Apache NetBeans IDE Dev (Build 
> incubator-netbeans-release-205-on-20180202), OpenJDK 64-Bit Server VM 
> 9.0.4.1+11, Mac OS X version 10.9.5
>Reporter: Eirik Bakke
>Priority: Major
> Attachments: Class Files causing Trouble.zip, parseerror.txt
>
>
> While editing Java sources in a maven-based multi-module NetBeans Platform 
> application on NetBeans 9.0 beta, the following IDE exception happens at 
> irregular intervals, while editing unrelated files in a different module:
> {noformat}
> ALL [null]: An error occurred during parsing of 
> '/var/folders/38/g_r_gdts0wx49_kbz5sjfj30gn/T/vcs-1518825448194/vcs-1519673427266/FilterPanel.java'.
>  Please report a bug against java/source and attach dump file 
> '/Users/ebakke/Library/Application 
> Support/NetBeans/dev/var/log/FilterPanel_8.dump'.
> {noformat}
> See the attached text file for the complete log dump and stack trace (can't 
> attach the ".dump" file as it contains source code). The source file in 
> question, FilterPanel.java, is generated in part by the Matisse GUI builder 
> (so there's also a FilterPanel.form file). I've also got maven 
> Compile-on-Save enabled.
> At other times, occasionally when running the same NetBeans Platform-based 
> application, the application itself throws the following exception, 
> mentioning the same file:
> {noformat}
> java.lang.ClassFormatError: Absent Code attribute in method that is not 
> native or abstract in class file com/somepackage/project/filter/FilterPanel$2
> {noformat}
> See again the attached text file for the complete log dump and stack trace.
>  



--
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-617) Cyclic dependency dialog box appears while it shouldn't

2018-04-06 Thread John Kostaras (JIRA)
John Kostaras created NETBEANS-617:
--

 Summary: Cyclic dependency dialog box appears while it shouldn't
 Key: NETBEANS-617
 URL: https://issues.apache.org/jira/browse/NETBEANS-617
 Project: NetBeans
  Issue Type: Bug
  Components: apisupport - Project
Affects Versions: 9.0
 Environment: MacOSX
Reporter: John Kostaras
 Fix For: 9.0
 Attachments: Screen Shot 2018-04-06 at 17.08.53.png

Following [[API Support] Window 
Wizard|http://netbeans-vm.apache.org/synergy/client/app/#/specification/207] 
Test specification, Create Top Component Window Test Case, the created 
TopComponent contains errors.

Trying to resolve the errors by adding the missing modules, the attached error 
is displayed.

It is very weird how this error appears. I started with a clean NB 9 beta 
(incubator) (i.e. clean cache, plugins, settings etc.). After having run the 
Ant-based NB Suite test specification, step 5 "Creating a New Window" was 
executed without any issues.

After finishing the Ant-based NB Suite test specification and started the [[API 
Support] Window 
Wizard|http://netbeans-vm.apache.org/synergy/client/app/#/specification/207] 
Test specification, this issue appeared. 

It could be that it works OK only the first time that a TopComponent is 
created, and after that the cyclic dependency issue appears. It could be that 
the issue appears after a module suite is created. 

In any case, the error should not be displayed as there are no cyclic 
dependencies with the remaining modules (that need to be added) with the three 
modules that were added to the project (Lookup API, Base Utilities API and 
Utilities API).

 



--
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] [Comment Edited] (NETBEANS-373) Netbeans sometimes freezes when showing any refactor dialog when running with jdk 1.8.0_152-b16 or later

2018-04-06 Thread Austin Stephens (JIRA)

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

Austin Stephens edited comment on NETBEANS-373 at 4/6/18 9:11 PM:
--

Why is `ParametersPanel.showDialog` (in refactoring.api) `synchronized` anyway? 
I tried to get a blame on that line, and it goes back to 10/24/2006 with what 
appears to be the creation of the file in the repo from somewhere else... Does 
anyone happen to have a copy of the old CVS repo anywhere? The revision in 
question has the tag of "{color:#00}after_retouche_2006_merge_trunk{color}"


was (Author: sir intellegence):
Why is `ParametersPanel.showDialog` (in refactoring.api) `synchronized` anyway? 
I tried to get a blame on that line, and it goes back to 10/24/2006 with what 
appears to be the creation of the file in the repo from somewhere else... Does 
anyone happen to have a copy of the old CVS repo anywhere?

> Netbeans sometimes freezes when showing any refactor dialog when running with 
> jdk 1.8.0_152-b16 or later
> 
>
> Key: NETBEANS-373
> URL: https://issues.apache.org/jira/browse/NETBEANS-373
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Refactoring
>Affects Versions: 8.2, 9.0
> Environment: Mac
>Reporter: Austin Stephens
>Priority: Blocker
> Attachments: Screen Shot 2018-04-02 at 11.22.11 AM.png, Screen Shot 
> 2018-04-02 at 11.23.15 AM.png, nbpresenter.diff
>
>
> Sometimes (or almost always), when you try to do some refactor action, 
> NetBeans freezes. It appears that a lock is obtained on a panel when the 
> dialog is shown, and the AppKit Thread tries to get the lock while trying to 
> add an accessible listener to it.
> AppKit Thread:
> {code:java}
> Container.addContainerListener:2142    
> Container$AccessibleAWTContainer.addPropertyChangeListener:3885    
> JComponent$AccessibleJComponent.addPropertyChangeListener:3765    
> Hidden Source Calls    
> CAccessible.addNotificationListeners:102    
> CAccessible.:84    
> CAccessible.getCAccessible:60
> {code}
> EDT Thread:
> {code:java}
> Hidden Source Calls    
> Unsafe.park    
> LockSupport.park:194    
> AbstractQueuedSynchronizer$ConditionObject.await:2062    
> EventQueue.getNextEvent:557    
> EventDispatchThread.pumpOneEventForFilters:173    
> EventDispatchThread.pumpEventsForFilter:124    
> EventDispatchThread.pumpEventsForFilter:117    
> WaitDispatchSupport$2.run:190    
> WaitDispatchSupport$4.run:235    
> WaitDispatchSupport$4.run:233    
> AccessController.doPrivileged    
> WaitDispatchSupport.enter:233    
> Dialog.show:1070    
> NbPresenter.superShow:1060    
> NbPresenter.doShow:1110    
> NbPresenter.run:1082    
> NbPresenter.run:105    
> NbMutexEventProvider$Event.doEventAccess:115    
> NbMutexEventProvider$Event.readAccess:75    
> LazyMutexImplementation.readAccess:71    
> Mutex.readAccess:193    
> NbPresenter.show:1067    
> Component.show:1669    
> Component.setVisible:1616    
> Window.setVisible:1017    
> Dialog.setVisible:1005    
> ParametersPanel.showDialog:674    
> RefactoringPanel.refresh:660    
> RefactoringPanel.:144    
> UI.openRefactoringUI:61    
> ContextAnalyzer$4.show:648    
> ContextAnalyzer$TextComponentTask.run:369    
> RefactoringActionsProvider.doFindUsages:232    
> ActionsImplementationFactory.doFindUsages:91    
> WhereUsedAction.performAction:52    
> RefactoringGlobalAction$ContextAction.actionPerformed:172    
> TopComponent.processKeyBinding:1151    
> JComponent.processKeyBindings:2963    
> JComponent.processKeyEvent:2863    
> Component.processEvent:6355    
> Container.processEvent:2259    
> Component.dispatchEventImpl:4961    
> Container.dispatchEventImpl:2317    
> Component.dispatchEvent:4793    
> KeyboardFocusManager.redispatchEvent:1955    
> DefaultKeyboardFocusManager.dispatchKeyEvent:827    
> DefaultKeyboardFocusManager.preDispatchKeyEvent:1096    
> DefaultKeyboardFocusManager.typeAheadAssertions:966    
> DefaultKeyboardFocusManager.dispatchEvent:792    
> Component.dispatchEventImpl:4842    
> Container.dispatchEventImpl:2317    
> Window.dispatchEventImpl:2758    
> Component.dispatchEvent:4793    
> EventQueue.dispatchEventImpl:766    
> EventQueue.access$500:97    
> EventQueue$3.run:717    
> EventQueue$3.run:711    
> AccessController.doPrivileged    
> ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege:89    
> ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege:99    
> EventQueue$4.run:739    
> EventQueue$4.run:737    
> AccessController.doPrivileged    
> ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege:89    
> EventQueue.dispatchEvent:736    
> TimableEventQueue.dispatchEvent:136    
> 

[jira] [Commented] (NETBEANS-373) Netbeans sometimes freezes when showing any refactor dialog when running with jdk 1.8.0_152-b16 or later

2018-04-06 Thread Austin Stephens (JIRA)

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

Austin Stephens commented on NETBEANS-373:
--

Why is `ParametersPanel.showDialog` (in refactoring.api) `synchronized` anyway? 
I tried to get a blame on that line, and it goes back to 10/24/2006 with what 
appears to be the creation of the file in the repo from somewhere else... Does 
anyone happen to have a copy of the old CVS repo anywhere?

> Netbeans sometimes freezes when showing any refactor dialog when running with 
> jdk 1.8.0_152-b16 or later
> 
>
> Key: NETBEANS-373
> URL: https://issues.apache.org/jira/browse/NETBEANS-373
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Refactoring
>Affects Versions: 8.2, 9.0
> Environment: Mac
>Reporter: Austin Stephens
>Priority: Blocker
> Attachments: Screen Shot 2018-04-02 at 11.22.11 AM.png, Screen Shot 
> 2018-04-02 at 11.23.15 AM.png, nbpresenter.diff
>
>
> Sometimes (or almost always), when you try to do some refactor action, 
> NetBeans freezes. It appears that a lock is obtained on a panel when the 
> dialog is shown, and the AppKit Thread tries to get the lock while trying to 
> add an accessible listener to it.
> AppKit Thread:
> {code:java}
> Container.addContainerListener:2142    
> Container$AccessibleAWTContainer.addPropertyChangeListener:3885    
> JComponent$AccessibleJComponent.addPropertyChangeListener:3765    
> Hidden Source Calls    
> CAccessible.addNotificationListeners:102    
> CAccessible.:84    
> CAccessible.getCAccessible:60
> {code}
> EDT Thread:
> {code:java}
> Hidden Source Calls    
> Unsafe.park    
> LockSupport.park:194    
> AbstractQueuedSynchronizer$ConditionObject.await:2062    
> EventQueue.getNextEvent:557    
> EventDispatchThread.pumpOneEventForFilters:173    
> EventDispatchThread.pumpEventsForFilter:124    
> EventDispatchThread.pumpEventsForFilter:117    
> WaitDispatchSupport$2.run:190    
> WaitDispatchSupport$4.run:235    
> WaitDispatchSupport$4.run:233    
> AccessController.doPrivileged    
> WaitDispatchSupport.enter:233    
> Dialog.show:1070    
> NbPresenter.superShow:1060    
> NbPresenter.doShow:1110    
> NbPresenter.run:1082    
> NbPresenter.run:105    
> NbMutexEventProvider$Event.doEventAccess:115    
> NbMutexEventProvider$Event.readAccess:75    
> LazyMutexImplementation.readAccess:71    
> Mutex.readAccess:193    
> NbPresenter.show:1067    
> Component.show:1669    
> Component.setVisible:1616    
> Window.setVisible:1017    
> Dialog.setVisible:1005    
> ParametersPanel.showDialog:674    
> RefactoringPanel.refresh:660    
> RefactoringPanel.:144    
> UI.openRefactoringUI:61    
> ContextAnalyzer$4.show:648    
> ContextAnalyzer$TextComponentTask.run:369    
> RefactoringActionsProvider.doFindUsages:232    
> ActionsImplementationFactory.doFindUsages:91    
> WhereUsedAction.performAction:52    
> RefactoringGlobalAction$ContextAction.actionPerformed:172    
> TopComponent.processKeyBinding:1151    
> JComponent.processKeyBindings:2963    
> JComponent.processKeyEvent:2863    
> Component.processEvent:6355    
> Container.processEvent:2259    
> Component.dispatchEventImpl:4961    
> Container.dispatchEventImpl:2317    
> Component.dispatchEvent:4793    
> KeyboardFocusManager.redispatchEvent:1955    
> DefaultKeyboardFocusManager.dispatchKeyEvent:827    
> DefaultKeyboardFocusManager.preDispatchKeyEvent:1096    
> DefaultKeyboardFocusManager.typeAheadAssertions:966    
> DefaultKeyboardFocusManager.dispatchEvent:792    
> Component.dispatchEventImpl:4842    
> Container.dispatchEventImpl:2317    
> Window.dispatchEventImpl:2758    
> Component.dispatchEvent:4793    
> EventQueue.dispatchEventImpl:766    
> EventQueue.access$500:97    
> EventQueue$3.run:717    
> EventQueue$3.run:711    
> AccessController.doPrivileged    
> ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege:89    
> ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege:99    
> EventQueue$4.run:739    
> EventQueue$4.run:737    
> AccessController.doPrivileged    
> ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege:89    
> EventQueue.dispatchEvent:736    
> TimableEventQueue.dispatchEvent:136    
> EventDispatchThread.pumpOneEventForFilters:199    
> EventDispatchThread.pumpEventsForFilter:124    
> EventDispatchThread.pumpEventsForHierarchy:113    
> EventDispatchThread.pumpEvents:109    
> EventDispatchThread.pumpEvents:101    
> EventDispatchThread.run:90   
> {code}
>  



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

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

[jira] [Commented] (NETBEANS-346) Tabs, characters, and the right Margin don't line up

2018-04-06 Thread Austin Stephens (JIRA)

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

Austin Stephens commented on NETBEANS-346:
--

Interesting... Changing the font from the default monospace to Lucida Sans 
Typewriter fixes the issue for some reason. We should still fix the issue for 
the default monospace font though. Maybe you could ask some more Mac users to 
figure out why it happens.

> Tabs, characters, and the right Margin don't line up
> 
>
> Key: NETBEANS-346
> URL: https://issues.apache.org/jira/browse/NETBEANS-346
> Project: NetBeans
>  Issue Type: Bug
>  Components: editor - Other
>Affects Versions: 9.0
> Environment: Mac OS 10.10 (at least)
>Reporter: Austin Stephens
>Priority: Critical
> Fix For: 9.0
>
> Attachments: Screen Shot 2018-01-29 at 4.58.35 PM.png, Screen Shot 
> 2018-02-28 at 11.27.32 AM.png, linewidth.png
>
>
> When the Right Margin is set at 80 chars, it is drawn at 8*2* chars. This is 
> annoying because I have a 1440x900 screen that I split vertically in to two. 
> This results in two editing areas that are about 80 chars wide. I could see 
> the margin line in both editors when scrolled all the way to the left. Since 
> Netbeans (9.0 beta) is now drawing them at char 8*2*, it is not possible to 
> size those editors so I can see the line in both windows and it is driving me 
> crazy.
> This is a first world issue at the moment, but you might find code coming 
> from mac programmers coming in two or more chars too wide in the Netbeans 
> source code.



--
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-593) Test Failure: Execution default-branding of goal org.codehaus.mojo:nbm-maven-plugin:4.1:branding failed: An API incompatibility was encountered while executing org.co

2018-04-06 Thread Eric Barboni (JIRA)

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

Eric Barboni commented on NETBEANS-593:
---

I Agree but platform test is I will put a note on slack for memo. 
And with no population of Apache Netbeans artifacts we are also testing the 
artifacts that are generated from mercurial Oracle Netbeans
.  

> Test Failure: Execution default-branding of goal 
> org.codehaus.mojo:nbm-maven-plugin:4.1:branding failed: An API 
> incompatibility was encountered while executing 
> org.codehaus.mojo:nbm-maven-plugin:4.1:branding: 
> java.lang.ExceptionInInitializerError: null
> 
>
> Key: NETBEANS-593
> URL: https://issues.apache.org/jira/browse/NETBEANS-593
> Project: NetBeans
>  Issue Type: Bug
> Environment: Product Version: Apache NetBeans IDE Dev (Build 
> incubator-netbeans-linux-392-on-20180403)
> Java: 10; Java HotSpot(TM) 64-Bit Server VM 10+46
> Runtime: Java(TM) SE Runtime Environment 10+46
> System: Mac OS X version 10.13.4 running on x86_64; UTF-8; en_US (nb)
> User directory: /Users/javierortiz/Library/Application Support/NetBeans/dev
> Cache directory: /Users/javierortiz/Library/Caches/NetBeans/dev
>Reporter: Javier A. Ortiz
>Priority: Major
>  Labels: jdk10, maven
>
> Running test case Build installers for NB application step 2:
> {noformat}
> Failed to execute goal org.codehaus.mojo:nbm-maven-plugin:4.1:branding 
> (default-branding) on project Nbapp-branding: Execution default-branding of 
> goal org.codehaus.mojo:nbm-maven-plugin:4.1:branding failed: An API 
> incompatibility was encountered while executing 
> org.codehaus.mojo:nbm-maven-plugin:4.1:branding: 
> java.lang.ExceptionInInitializerError: null
> -
> realm = extension>org.codehaus.mojo:nbm-maven-plugin:4.1
> strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> urls[0] = 
> file:/Users/javierortiz/.m2/repository/org/codehaus/mojo/nbm-maven-plugin/4.1/nbm-maven-plugin-4.1.jar
> urls[1] = 
> file:/Users/javierortiz/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
> urls[2] = 
> file:/Users/javierortiz/.m2/repository/org/sonatype/sisu/sisu-inject-bean/2.3.0/sisu-inject-bean-2.3.0.jar
> urls[3] = 
> file:/Users/javierortiz/.m2/repository/org/sonatype/sisu/sisu-guice/3.1.0/sisu-guice-3.1.0-no_aop.jar
> urls[4] = 
> file:/Users/javierortiz/.m2/repository/org/sonatype/sisu/sisu-guava/0.9.9/sisu-guava-0.9.9.jar
> urls[5] = 
> file:/Users/javierortiz/.m2/repository/org/codehaus/plexus/plexus-component-annotations/1.5.5/plexus-component-annotations-1.5.5.jar
> urls[6] = 
> file:/Users/javierortiz/.m2/repository/org/apache/maven/plugin-tools/maven-plugin-annotations/3.4/maven-plugin-annotations-3.4.jar
> urls[7] = 
> file:/Users/javierortiz/.m2/repository/org/apache/ant/ant/1.9.6/ant-1.9.6.jar
> urls[8] = 
> file:/Users/javierortiz/.m2/repository/org/apache/ant/ant-launcher/1.9.6/ant-launcher-1.9.6.jar
> urls[9] = 
> file:/Users/javierortiz/.m2/repository/org/codehaus/plexus/plexus-utils/3.0.22/plexus-utils-3.0.22.jar
> urls[10] = 
> file:/Users/javierortiz/.m2/repository/org/codehaus/plexus/plexus-archiver/3.0.1/plexus-archiver-3.0.1.jar
> urls[11] = 
> file:/Users/javierortiz/.m2/repository/org/iq80/snappy/snappy/0.3/snappy-0.3.jar
> urls[12] = 
> file:/Users/javierortiz/.m2/repository/org/apache/maven/shared/maven-dependency-tree/2.2/maven-dependency-tree-2.2.jar
> urls[13] = 
> file:/Users/javierortiz/.m2/repository/org/eclipse/aether/aether-util/0.9.0.M2/aether-util-0.9.0.M2.jar
> urls[14] = 
> file:/Users/javierortiz/.m2/repository/org/apache/maven/shared/maven-dependency-analyzer/1.6/maven-dependency-analyzer-1.6.jar
> urls[15] = 
> file:/Users/javierortiz/.m2/repository/org/ow2/asm/asm/5.0.2/asm-5.0.2.jar
> urls[16] = 
> file:/Users/javierortiz/.m2/repository/org/apache/xbean/xbean-reflect/3.7/xbean-reflect-3.7.jar
> urls[17] = 
> file:/Users/javierortiz/.m2/repository/com/google/collections/google-collections/1.0/google-collections-1.0.jar
> urls[18] = 
> file:/Users/javierortiz/.m2/repository/org/apache/maven/shared/maven-filtering/1.3/maven-filtering-1.3.jar
> urls[19] = 
> file:/Users/javierortiz/.m2/repository/org/apache/maven/shared/maven-shared-utils/0.6/maven-shared-utils-0.6.jar
> urls[20] = 
> file:/Users/javierortiz/.m2/repository/com/google/code/findbugs/jsr305/2.0.1/jsr305-2.0.1.jar
> urls[21] = 
> file:/Users/javierortiz/.m2/repository/org/sonatype/plexus/plexus-build-api/0.0.4/plexus-build-api-0.0.4.jar
> urls[22] = 
> 

[jira] [Created] (NETBEANS-616) Hamcrest library is missing when trying to create a unit test for a topcomponent

2018-04-06 Thread John Kostaras (JIRA)
John Kostaras created NETBEANS-616:
--

 Summary: Hamcrest library is missing when trying to create a unit 
test for a topcomponent
 Key: NETBEANS-616
 URL: https://issues.apache.org/jira/browse/NETBEANS-616
 Project: NetBeans
  Issue Type: Bug
  Components: apisupport - Project
Affects Versions: 9.0
Reporter: John Kostaras
 Fix For: 9.0
 Attachments: Screen Shot 2018-04-06 at 17.08.53.png

Performing Create Unit Test Test Case of [[API Support] Ant-based NetBeans 
Suite and Module Projects 
Operations|http://netbeans-vm.apache.org/synergy/client/app/#/specification/19] 
Test specification, an error about missing hamcrest library is displayed (see 
attachment).



--
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-593) Test Failure: Execution default-branding of goal org.codehaus.mojo:nbm-maven-plugin:4.1:branding failed: An API incompatibility was encountered while executing org.co

2018-04-06 Thread Javier A. Ortiz (JIRA)

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

Javier A. Ortiz commented on NETBEANS-593:
--

This was part of NetCat testing, as such it'll need to be updated on the 
wizards, etc. that created the project.  

> Test Failure: Execution default-branding of goal 
> org.codehaus.mojo:nbm-maven-plugin:4.1:branding failed: An API 
> incompatibility was encountered while executing 
> org.codehaus.mojo:nbm-maven-plugin:4.1:branding: 
> java.lang.ExceptionInInitializerError: null
> 
>
> Key: NETBEANS-593
> URL: https://issues.apache.org/jira/browse/NETBEANS-593
> Project: NetBeans
>  Issue Type: Bug
> Environment: Product Version: Apache NetBeans IDE Dev (Build 
> incubator-netbeans-linux-392-on-20180403)
> Java: 10; Java HotSpot(TM) 64-Bit Server VM 10+46
> Runtime: Java(TM) SE Runtime Environment 10+46
> System: Mac OS X version 10.13.4 running on x86_64; UTF-8; en_US (nb)
> User directory: /Users/javierortiz/Library/Application Support/NetBeans/dev
> Cache directory: /Users/javierortiz/Library/Caches/NetBeans/dev
>Reporter: Javier A. Ortiz
>Priority: Major
>  Labels: jdk10, maven
>
> Running test case Build installers for NB application step 2:
> {noformat}
> Failed to execute goal org.codehaus.mojo:nbm-maven-plugin:4.1:branding 
> (default-branding) on project Nbapp-branding: Execution default-branding of 
> goal org.codehaus.mojo:nbm-maven-plugin:4.1:branding failed: An API 
> incompatibility was encountered while executing 
> org.codehaus.mojo:nbm-maven-plugin:4.1:branding: 
> java.lang.ExceptionInInitializerError: null
> -
> realm = extension>org.codehaus.mojo:nbm-maven-plugin:4.1
> strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> urls[0] = 
> file:/Users/javierortiz/.m2/repository/org/codehaus/mojo/nbm-maven-plugin/4.1/nbm-maven-plugin-4.1.jar
> urls[1] = 
> file:/Users/javierortiz/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
> urls[2] = 
> file:/Users/javierortiz/.m2/repository/org/sonatype/sisu/sisu-inject-bean/2.3.0/sisu-inject-bean-2.3.0.jar
> urls[3] = 
> file:/Users/javierortiz/.m2/repository/org/sonatype/sisu/sisu-guice/3.1.0/sisu-guice-3.1.0-no_aop.jar
> urls[4] = 
> file:/Users/javierortiz/.m2/repository/org/sonatype/sisu/sisu-guava/0.9.9/sisu-guava-0.9.9.jar
> urls[5] = 
> file:/Users/javierortiz/.m2/repository/org/codehaus/plexus/plexus-component-annotations/1.5.5/plexus-component-annotations-1.5.5.jar
> urls[6] = 
> file:/Users/javierortiz/.m2/repository/org/apache/maven/plugin-tools/maven-plugin-annotations/3.4/maven-plugin-annotations-3.4.jar
> urls[7] = 
> file:/Users/javierortiz/.m2/repository/org/apache/ant/ant/1.9.6/ant-1.9.6.jar
> urls[8] = 
> file:/Users/javierortiz/.m2/repository/org/apache/ant/ant-launcher/1.9.6/ant-launcher-1.9.6.jar
> urls[9] = 
> file:/Users/javierortiz/.m2/repository/org/codehaus/plexus/plexus-utils/3.0.22/plexus-utils-3.0.22.jar
> urls[10] = 
> file:/Users/javierortiz/.m2/repository/org/codehaus/plexus/plexus-archiver/3.0.1/plexus-archiver-3.0.1.jar
> urls[11] = 
> file:/Users/javierortiz/.m2/repository/org/iq80/snappy/snappy/0.3/snappy-0.3.jar
> urls[12] = 
> file:/Users/javierortiz/.m2/repository/org/apache/maven/shared/maven-dependency-tree/2.2/maven-dependency-tree-2.2.jar
> urls[13] = 
> file:/Users/javierortiz/.m2/repository/org/eclipse/aether/aether-util/0.9.0.M2/aether-util-0.9.0.M2.jar
> urls[14] = 
> file:/Users/javierortiz/.m2/repository/org/apache/maven/shared/maven-dependency-analyzer/1.6/maven-dependency-analyzer-1.6.jar
> urls[15] = 
> file:/Users/javierortiz/.m2/repository/org/ow2/asm/asm/5.0.2/asm-5.0.2.jar
> urls[16] = 
> file:/Users/javierortiz/.m2/repository/org/apache/xbean/xbean-reflect/3.7/xbean-reflect-3.7.jar
> urls[17] = 
> file:/Users/javierortiz/.m2/repository/com/google/collections/google-collections/1.0/google-collections-1.0.jar
> urls[18] = 
> file:/Users/javierortiz/.m2/repository/org/apache/maven/shared/maven-filtering/1.3/maven-filtering-1.3.jar
> urls[19] = 
> file:/Users/javierortiz/.m2/repository/org/apache/maven/shared/maven-shared-utils/0.6/maven-shared-utils-0.6.jar
> urls[20] = 
> file:/Users/javierortiz/.m2/repository/com/google/code/findbugs/jsr305/2.0.1/jsr305-2.0.1.jar
> urls[21] = 
> file:/Users/javierortiz/.m2/repository/org/sonatype/plexus/plexus-build-api/0.0.4/plexus-build-api-0.0.4.jar
> urls[22] = 
> file:/Users/javierortiz/.m2/repository/org/sonatype/aether/aether-util/1.13.1/aether-util-1.13.1.jar

[jira] [Commented] (NETBEANS-593) Test Failure: Execution default-branding of goal org.codehaus.mojo:nbm-maven-plugin:4.1:branding failed: An API incompatibility was encountered while executing org.co

2018-04-06 Thread Eric Barboni (JIRA)

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

Eric Barboni commented on NETBEANS-593:
---

Hi, 
 I proposed this fix https://github.com/mojohaus/nbm-maven-plugin/pull/35

 maybe you can clone https://github.com/ebarboni/nbm-maven-plugin/tree/jdk10

Note that jar config should be changed also in pom:
 {code}
 
org.apache.maven.plugins
maven-jar-plugin
3.0.2



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



{code}

Regards


> Test Failure: Execution default-branding of goal 
> org.codehaus.mojo:nbm-maven-plugin:4.1:branding failed: An API 
> incompatibility was encountered while executing 
> org.codehaus.mojo:nbm-maven-plugin:4.1:branding: 
> java.lang.ExceptionInInitializerError: null
> 
>
> Key: NETBEANS-593
> URL: https://issues.apache.org/jira/browse/NETBEANS-593
> Project: NetBeans
>  Issue Type: Bug
> Environment: Product Version: Apache NetBeans IDE Dev (Build 
> incubator-netbeans-linux-392-on-20180403)
> Java: 10; Java HotSpot(TM) 64-Bit Server VM 10+46
> Runtime: Java(TM) SE Runtime Environment 10+46
> System: Mac OS X version 10.13.4 running on x86_64; UTF-8; en_US (nb)
> User directory: /Users/javierortiz/Library/Application Support/NetBeans/dev
> Cache directory: /Users/javierortiz/Library/Caches/NetBeans/dev
>Reporter: Javier A. Ortiz
>Priority: Major
>  Labels: jdk10, maven
>
> Running test case Build installers for NB application step 2:
> {noformat}
> Failed to execute goal org.codehaus.mojo:nbm-maven-plugin:4.1:branding 
> (default-branding) on project Nbapp-branding: Execution default-branding of 
> goal org.codehaus.mojo:nbm-maven-plugin:4.1:branding failed: An API 
> incompatibility was encountered while executing 
> org.codehaus.mojo:nbm-maven-plugin:4.1:branding: 
> java.lang.ExceptionInInitializerError: null
> -
> realm = extension>org.codehaus.mojo:nbm-maven-plugin:4.1
> strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> urls[0] = 
> file:/Users/javierortiz/.m2/repository/org/codehaus/mojo/nbm-maven-plugin/4.1/nbm-maven-plugin-4.1.jar
> urls[1] = 
> file:/Users/javierortiz/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
> urls[2] = 
> file:/Users/javierortiz/.m2/repository/org/sonatype/sisu/sisu-inject-bean/2.3.0/sisu-inject-bean-2.3.0.jar
> urls[3] = 
> file:/Users/javierortiz/.m2/repository/org/sonatype/sisu/sisu-guice/3.1.0/sisu-guice-3.1.0-no_aop.jar
> urls[4] = 
> file:/Users/javierortiz/.m2/repository/org/sonatype/sisu/sisu-guava/0.9.9/sisu-guava-0.9.9.jar
> urls[5] = 
> file:/Users/javierortiz/.m2/repository/org/codehaus/plexus/plexus-component-annotations/1.5.5/plexus-component-annotations-1.5.5.jar
> urls[6] = 
> file:/Users/javierortiz/.m2/repository/org/apache/maven/plugin-tools/maven-plugin-annotations/3.4/maven-plugin-annotations-3.4.jar
> urls[7] = 
> file:/Users/javierortiz/.m2/repository/org/apache/ant/ant/1.9.6/ant-1.9.6.jar
> urls[8] = 
> file:/Users/javierortiz/.m2/repository/org/apache/ant/ant-launcher/1.9.6/ant-launcher-1.9.6.jar
> urls[9] = 
> file:/Users/javierortiz/.m2/repository/org/codehaus/plexus/plexus-utils/3.0.22/plexus-utils-3.0.22.jar
> urls[10] = 
> file:/Users/javierortiz/.m2/repository/org/codehaus/plexus/plexus-archiver/3.0.1/plexus-archiver-3.0.1.jar
> urls[11] = 
> file:/Users/javierortiz/.m2/repository/org/iq80/snappy/snappy/0.3/snappy-0.3.jar
> urls[12] = 
> file:/Users/javierortiz/.m2/repository/org/apache/maven/shared/maven-dependency-tree/2.2/maven-dependency-tree-2.2.jar
> urls[13] = 
> file:/Users/javierortiz/.m2/repository/org/eclipse/aether/aether-util/0.9.0.M2/aether-util-0.9.0.M2.jar
> urls[14] = 
> file:/Users/javierortiz/.m2/repository/org/apache/maven/shared/maven-dependency-analyzer/1.6/maven-dependency-analyzer-1.6.jar
> urls[15] = 
> file:/Users/javierortiz/.m2/repository/org/ow2/asm/asm/5.0.2/asm-5.0.2.jar
> urls[16] = 
> file:/Users/javierortiz/.m2/repository/org/apache/xbean/xbean-reflect/3.7/xbean-reflect-3.7.jar
> urls[17] = 
> file:/Users/javierortiz/.m2/repository/com/google/collections/google-collections/1.0/google-collections-1.0.jar
> urls[18] = 
> file:/Users/javierortiz/.m2/repository/org/apache/maven/shared/maven-filtering/1.3/maven-filtering-1.3.jar
> urls[19] = 
> 

[jira] [Issue Comment Deleted] (NETBEANS-491) Turn off exception reporter

2018-04-06 Thread Reema Taneja (JIRA)

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

Reema Taneja updated NETBEANS-491:
--
Comment: was deleted

(was: Tried the suggested approach, pointed defaultURI to a local copy of 
[http://netbeans.org/nonav/uigestures/error2.html] that has submit button 
removed. With this, on clicking Review and Report problem button , error2.html 
is shown in the JEditorPane, scrshot attached.  Is this behaviour ok? Should we 
update text and provide link to JIRA here? Redirect to external url like JIRA 
isn't supported in this flow, will require code changes.)

> Turn off exception reporter
> ---
>
> Key: NETBEANS-491
> URL: https://issues.apache.org/jira/browse/NETBEANS-491
> Project: NetBeans
>  Issue Type: Bug
>  Components: ide - Code
>Affects Versions: 9.0
>Reporter: Jiří Kovalský
>Assignee: Reema Taneja
>Priority: Critical
>  Labels: pull-request-available
>  Time Spent: 2h 20m
>  Remaining Estimate: 0h
>
> Apache NetBeans 9.0 tries to send exception reports even though the backend 
> infrastructure is no longer available. In case of an exception NetBeans IDE 
> should no longer display the *Review and Report Problem* button and report 
> URL in the error message should instead read: 
> [https://issues.apache.org/jira/secure/CreateIssue!default.jspa]
> *Steps to reproduce:*
>  # Launch development build #20180320 of Apache NetBeans 9.0.
>  # Type e.g. _properties_ into the *Search* field in the upper right corner 
> of the IDE.
>  # Press Enter.
> *Expected:*
> Due to another bug NetBeans opens an exception dialog which contains old link 
> to _issues.html_ page and *Review and Report Problem* button.
> *Actual:*
> NetBeans opens an exception dialog only instructing user to report the 
> exception to Apache Jira and no *Review and Report Problem* button is shown.



--
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] [Issue Comment Deleted] (NETBEANS-491) Turn off exception reporter

2018-04-06 Thread Reema Taneja (JIRA)

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

Reema Taneja updated NETBEANS-491:
--
Comment: was deleted

(was: Tried the suggested approach. Pointed defaultURI to a local copy of 
[http://netbeans.org/nonav/uigestures/error2.html] that has submit button 
removed. With this, on clicking Review and Report problem button , error2.html 
is shown in the JEditorPane, scrshot attached.  Is this behaviour ok? Should we 
update text and provide link to JIRA here? Redirect to external url like JIRA 
in browser doesn't seem to be supported in this flow, will require code change.)

> Turn off exception reporter
> ---
>
> Key: NETBEANS-491
> URL: https://issues.apache.org/jira/browse/NETBEANS-491
> Project: NetBeans
>  Issue Type: Bug
>  Components: ide - Code
>Affects Versions: 9.0
>Reporter: Jiří Kovalský
>Assignee: Reema Taneja
>Priority: Critical
>  Labels: pull-request-available
>  Time Spent: 2h 20m
>  Remaining Estimate: 0h
>
> Apache NetBeans 9.0 tries to send exception reports even though the backend 
> infrastructure is no longer available. In case of an exception NetBeans IDE 
> should no longer display the *Review and Report Problem* button and report 
> URL in the error message should instead read: 
> [https://issues.apache.org/jira/secure/CreateIssue!default.jspa]
> *Steps to reproduce:*
>  # Launch development build #20180320 of Apache NetBeans 9.0.
>  # Type e.g. _properties_ into the *Search* field in the upper right corner 
> of the IDE.
>  # Press Enter.
> *Expected:*
> Due to another bug NetBeans opens an exception dialog which contains old link 
> to _issues.html_ page and *Review and Report Problem* button.
> *Actual:*
> NetBeans opens an exception dialog only instructing user to report the 
> exception to Apache Jira and no *Review and Report Problem* button is shown.



--
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-491) Turn off exception reporter

2018-04-06 Thread Reema Taneja (JIRA)

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

Reema Taneja commented on NETBEANS-491:
---

Tried the suggested approach, pointed defaultURI to a local copy of 
[http://netbeans.org/nonav/uigestures/error2.html] that has submit button 
removed. With this, on clicking Review and Report problem button , error2.html 
is shown in the JEditorPane, scrshot attached.  Is this behaviour ok? Should we 
update text and provide link to JIRA here? Redirect to external url like JIRA 
in browser doesn't seem to be supported in this flow, will require code change .

> Turn off exception reporter
> ---
>
> Key: NETBEANS-491
> URL: https://issues.apache.org/jira/browse/NETBEANS-491
> Project: NetBeans
>  Issue Type: Bug
>  Components: ide - Code
>Affects Versions: 9.0
>Reporter: Jiří Kovalský
>Assignee: Reema Taneja
>Priority: Critical
>  Labels: pull-request-available
>  Time Spent: 2h 20m
>  Remaining Estimate: 0h
>
> Apache NetBeans 9.0 tries to send exception reports even though the backend 
> infrastructure is no longer available. In case of an exception NetBeans IDE 
> should no longer display the *Review and Report Problem* button and report 
> URL in the error message should instead read: 
> [https://issues.apache.org/jira/secure/CreateIssue!default.jspa]
> *Steps to reproduce:*
>  # Launch development build #20180320 of Apache NetBeans 9.0.
>  # Type e.g. _properties_ into the *Search* field in the upper right corner 
> of the IDE.
>  # Press Enter.
> *Expected:*
> Due to another bug NetBeans opens an exception dialog which contains old link 
> to _issues.html_ page and *Review and Report Problem* button.
> *Actual:*
> NetBeans opens an exception dialog only instructing user to report the 
> exception to Apache Jira and no *Review and Report Problem* button is shown.



--
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-491) Turn off exception reporter

2018-04-06 Thread Reema Taneja (JIRA)

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

Reema Taneja commented on NETBEANS-491:
---

Tried the suggested approach. Pointed defaultURI to a local copy of 
[http://netbeans.org/nonav/uigestures/error2.html] that has submit button 
removed. With this, on clicking Review and Report problem button , error2.html 
is shown in the JEditorPane, scrshot attached.  Is this behaviour ok? Should we 
update text and provide link to JIRA here? Redirect to external url like JIRA 
in browser doesn't seem to be supported in this flow, will require code change.

> Turn off exception reporter
> ---
>
> Key: NETBEANS-491
> URL: https://issues.apache.org/jira/browse/NETBEANS-491
> Project: NetBeans
>  Issue Type: Bug
>  Components: ide - Code
>Affects Versions: 9.0
>Reporter: Jiří Kovalský
>Assignee: Reema Taneja
>Priority: Critical
>  Labels: pull-request-available
>  Time Spent: 2h 20m
>  Remaining Estimate: 0h
>
> Apache NetBeans 9.0 tries to send exception reports even though the backend 
> infrastructure is no longer available. In case of an exception NetBeans IDE 
> should no longer display the *Review and Report Problem* button and report 
> URL in the error message should instead read: 
> [https://issues.apache.org/jira/secure/CreateIssue!default.jspa]
> *Steps to reproduce:*
>  # Launch development build #20180320 of Apache NetBeans 9.0.
>  # Type e.g. _properties_ into the *Search* field in the upper right corner 
> of the IDE.
>  # Press Enter.
> *Expected:*
> Due to another bug NetBeans opens an exception dialog which contains old link 
> to _issues.html_ page and *Review and Report Problem* button.
> *Actual:*
> NetBeans opens an exception dialog only instructing user to report the 
> exception to Apache Jira and no *Review and Report Problem* button is shown.



--
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-491) Turn off exception reporter

2018-04-06 Thread Reema Taneja (JIRA)

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

Reema Taneja commented on NETBEANS-491:
---

Tried the suggested approach, pointed defaultURI to a local copy of 
[http://netbeans.org/nonav/uigestures/error2.html] that has submit button 
removed. With this, on clicking Review and Report problem button , error2.html 
is shown in the JEditorPane, scrshot attached.  Is this behaviour ok? Should we 
update text and provide link to JIRA here? Redirect to external url like JIRA 
isn't supported in this flow, will require code changes.

> Turn off exception reporter
> ---
>
> Key: NETBEANS-491
> URL: https://issues.apache.org/jira/browse/NETBEANS-491
> Project: NetBeans
>  Issue Type: Bug
>  Components: ide - Code
>Affects Versions: 9.0
>Reporter: Jiří Kovalský
>Assignee: Reema Taneja
>Priority: Critical
>  Labels: pull-request-available
>  Time Spent: 2h 20m
>  Remaining Estimate: 0h
>
> Apache NetBeans 9.0 tries to send exception reports even though the backend 
> infrastructure is no longer available. In case of an exception NetBeans IDE 
> should no longer display the *Review and Report Problem* button and report 
> URL in the error message should instead read: 
> [https://issues.apache.org/jira/secure/CreateIssue!default.jspa]
> *Steps to reproduce:*
>  # Launch development build #20180320 of Apache NetBeans 9.0.
>  # Type e.g. _properties_ into the *Search* field in the upper right corner 
> of the IDE.
>  # Press Enter.
> *Expected:*
> Due to another bug NetBeans opens an exception dialog which contains old link 
> to _issues.html_ page and *Review and Report Problem* button.
> *Actual:*
> NetBeans opens an exception dialog only instructing user to report the 
> exception to Apache Jira and no *Review and Report Problem* button is shown.



--
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-480) Need to disable hint ConvertToDiamondBulkHint for var type statement.

2018-04-06 Thread ARUNAVA SINHA (JIRA)

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

ARUNAVA SINHA updated NETBEANS-480:
---
Description: 
Fix hint 'Use diamond inference' should be disabled for below kind of statement.

var list = new ArrayList();

> Need to disable hint ConvertToDiamondBulkHint for var type statement.
> -
>
> Key: NETBEANS-480
> URL: https://issues.apache.org/jira/browse/NETBEANS-480
> Project: NetBeans
>  Issue Type: Bug
>Reporter: ARUNAVA SINHA
>Assignee: ARUNAVA SINHA
>Priority: Trivial
>  Labels: JDK10-LVTI
>
> Fix hint 'Use diamond inference' should be disabled for below kind of 
> statement.
> var list = new ArrayList();



--
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-480) Need to disable hint ConvertToDiamondBulkHint for var type statement.

2018-04-06 Thread ARUNAVA SINHA (JIRA)

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

ARUNAVA SINHA updated NETBEANS-480:
---
Summary: Need to disable hint ConvertToDiamondBulkHint for var type 
statement.  (was: Need to disable hint FIX_ConvertToDiamond for var type 
statement.)

> Need to disable hint ConvertToDiamondBulkHint for var type statement.
> -
>
> Key: NETBEANS-480
> URL: https://issues.apache.org/jira/browse/NETBEANS-480
> Project: NetBeans
>  Issue Type: Bug
>Reporter: ARUNAVA SINHA
>Assignee: ARUNAVA SINHA
>Priority: Trivial
>  Labels: JDK10-LVTI
>




--
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-615) Cannot run java application from IDE

2018-04-06 Thread Filippo (JIRA)
Filippo created NETBEANS-615:


 Summary: Cannot run java application from IDE
 Key: NETBEANS-615
 URL: https://issues.apache.org/jira/browse/NETBEANS-615
 Project: NetBeans
  Issue Type: Bug
Affects Versions: 9.0
 Environment: Netbeans 9 beta x64

Windows 2008 R2 x64

Java 10 sdk 
Reporter: Filippo


I created the following class:
{code:java}
public static void main(String[] args) {
    
    System.out.println("java version: " + 
System.getProperty("java.version"));
    }
{code}
It compiles correctly and I can  execute it from coammand line with *java*.

If I try to run it from the ide a new .class file is generated which contains 
RuntimeException as the first line.

I double checked the configuration and found nothing wrong.



--
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-614) Pasting whole lines causes insertion at wrong position

2018-04-06 Thread Lukas Troyer (JIRA)
Lukas Troyer created NETBEANS-614:
-

 Summary: Pasting whole lines causes insertion at wrong position
 Key: NETBEANS-614
 URL: https://issues.apache.org/jira/browse/NETBEANS-614
 Project: NetBeans
  Issue Type: Improvement
Affects Versions: 8.2
Reporter: Lukas Troyer


 | represents the cursor 
{code:java}
// Example code
System.out.pri|ntln("Hello");
{code}
Pressing CTRL + C and CTRL + V causes this:
{code:java}
// Example code
System.out.priSystem.out.println("Hello");
|ntln("Hello");
{code}
But it should cause this: 
{code:java}
// Example code
System.out.println("Hello");
|System.out.println("Hello");
{code}



--
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-601) branding failed: An API incompatibility was encountered while executing org.codehaus.mojo:nbm-maven-plugin:4.1:branding

2018-04-06 Thread Rami Swailem (JIRA)

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

Rami Swailem updated NETBEANS-601:
--
Labels: jdk10 maven  (was: maven)

> branding failed: An API incompatibility was encountered while executing 
> org.codehaus.mojo:nbm-maven-plugin:4.1:branding
> ---
>
> Key: NETBEANS-601
> URL: https://issues.apache.org/jira/browse/NETBEANS-601
> Project: NetBeans
>  Issue Type: Bug
>  Components: apisupport - Maven
>Affects Versions: 9.0
> Environment: Product Version: Apache NetBeans IDE Dev (Build 
> incubator-netbeans-release-260-on-20180404)
> Java: 10; OpenJDK 64-Bit Server VM 10+46
> Runtime: OpenJDK Runtime Environment 10+46
> System: Mac OS X version 10.13.4 running on x86_64; UTF-8; en_DE (nb)
>Reporter: Rami Swailem
>Priority: Major
>  Labels: jdk10, maven
> Attachments: jdk10.zip, stacktrace.txt
>
>
>  
> with JDK 9 no problems.
> steps to reproduce:
> 1. create maven project (Maven -> Netbeans Application)
> 2. build branding module
> The following error occurred while executing:
> --- nbm-maven-plugin:4.1:branding (default-branding) @ jdk10-branding ---
> Configuring mojo org.codehaus.mojo:nbm-maven-plugin:4.1:branding from plugin 
> realm ClassRealm[extension>org.codehaus.mojo:nbm-maven-plugin:4.1, parent: 
> jdk.internal.loader.ClassLoaders$AppClassLoader@1de0aca6]
> Configuring mojo 'org.codehaus.mojo:nbm-maven-plugin:4.1:branding' with basic 
> configurator -->
> (f) brandingSources = 
> /Users/rami/NetBeansProjects/jdk10/branding/src/main/nbm-branding
> (f) brandingToken = jdk10
> (f) cluster = jdk10
> (f) nbmBuildDir = /Users/rami/NetBeansProjects/jdk10/branding/target/nbm
> (f) outputDirectory = /Users/rami/NetBeansProjects/jdk10/branding/target
> (f) project = MavenProject: org.swailem:jdk10-branding:0.0.1 @ 
> /Users/rami/NetBeansProjects/jdk10/branding/pom.xml
> -- end configuration --
> 
> BUILD FAILURE
> 
> Total time: 5.499 s
> Finished at: 2018-04-05T13:27:55+02:00
> 
> Failed to execute goal org.codehaus.mojo:nbm-maven-plugin:4.1:branding 
> (default-branding) on project jdk10-branding: Execution default-branding of 
> goal org.codehaus.mojo:nbm-maven-plugin:4.1:branding failed: An API 
> incompatibility was encountered while executing 
> org.codehaus.mojo:nbm-maven-plugin:4.1:branding: 
> java.lang.ExceptionInInitializerError: null
> -
> realm = extension>org.codehaus.mojo:nbm-maven-plugin:4.1
> strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> ...



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