[jira] [Created] (NETBEANS-891) Performing undo on a document causes all cloned editors to scroll to that point

2018-05-30 Thread Austin Stephens (JIRA)
Austin Stephens created NETBEANS-891:


 Summary: Performing undo on a document causes all cloned editors 
to scroll to that point
 Key: NETBEANS-891
 URL: https://issues.apache.org/jira/browse/NETBEANS-891
 Project: NetBeans
  Issue Type: Bug
  Components: editor - Navigation
Affects Versions: 8.2, 9.0
Reporter: Austin Stephens


It is rather annoying when working in multiple places in a large file. I loose 
my places in the other files.
It moves the caret too.



--
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-891) Performing undo on a document causes all cloned editors to scroll to that point

2018-05-30 Thread Austin Stephens (JIRA)


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

Austin Stephens updated NETBEANS-891:
-
Priority: Major  (was: Critical)

> Performing undo on a document causes all cloned editors to scroll to that 
> point
> ---
>
> Key: NETBEANS-891
> URL: https://issues.apache.org/jira/browse/NETBEANS-891
> Project: NetBeans
>  Issue Type: Bug
>  Components: editor - Navigation
>Affects Versions: 8.2, 9.0
>Reporter: Austin Stephens
>Priority: Major
>
> It is rather annoying when working in multiple places in a large file. I 
> loose my places in the other files.
> It moves the caret too.



--
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-892) Refactor -> Move Class into other class breaks multicatches and lambas in destination class

2018-05-30 Thread Austin Stephens (JIRA)
Austin Stephens created NETBEANS-892:


 Summary: Refactor -> Move Class into other class breaks 
multicatches and lambas in destination class
 Key: NETBEANS-892
 URL: https://issues.apache.org/jira/browse/NETBEANS-892
 Project: NetBeans
  Issue Type: Bug
  Components: java - Refactoring
Affects Versions: 9.0
Reporter: Austin Stephens
 Attachments: SampleProject.7z

Move the class "MoveMe" into the class "Killer". Things break



--
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-892) Refactor -> Move Class into other class breaks multicatches and lambas in destination class

2018-05-30 Thread Austin Stephens (JIRA)


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

Austin Stephens updated NETBEANS-892:
-
Priority: Major  (was: Critical)

> Refactor -> Move Class into other class breaks multicatches and lambas in 
> destination class
> ---
>
> Key: NETBEANS-892
> URL: https://issues.apache.org/jira/browse/NETBEANS-892
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Refactoring
>Affects Versions: 9.0
>Reporter: Austin Stephens
>Priority: Major
> Attachments: SampleProject.7z
>
>
> Move the class "MoveMe" into the class "Killer". Things break



--
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-892) Refactor -> Move Class into other class breaks multicatches and lambas in destination class

2018-05-30 Thread Austin Stephens (JIRA)


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

Austin Stephens commented on NETBEANS-892:
--

It appears, likewise, that moving a class OUT of the current class causes the 
same issue.

> Refactor -> Move Class into other class breaks multicatches and lambas in 
> destination class
> ---
>
> Key: NETBEANS-892
> URL: https://issues.apache.org/jira/browse/NETBEANS-892
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Refactoring
>Affects Versions: 9.0
>Reporter: Austin Stephens
>Priority: Major
> Attachments: SampleProject.7z
>
>
> Move the class "MoveMe" into the class "Killer". Things break



--
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-892) Refactor -> Move Class into other class breaks multicatches and lambas in destination class

2018-05-31 Thread Austin Stephens (JIRA)


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

Austin Stephens updated NETBEANS-892:
-
Priority: Blocker  (was: Major)

> Refactor -> Move Class into other class breaks multicatches and lambas in 
> destination class
> ---
>
> Key: NETBEANS-892
> URL: https://issues.apache.org/jira/browse/NETBEANS-892
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Refactoring
>Affects Versions: 9.0
>Reporter: Austin Stephens
>Priority: Blocker
> Attachments: SampleProject.7z
>
>
> Move the class "MoveMe" into the class "Killer". Things break



--
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-892) Refactor -> Move Class into other class breaks multicatches and lambas in destination class

2018-05-31 Thread Austin Stephens (JIRA)


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

Austin Stephens commented on NETBEANS-892:
--

Apparently, the refactoring engine wasn't satisfied with just messing up the 
large code file I was working on, it also decided to mess up (almost) every 
file in the project those files were in. It was also messing with imports as 
well. It even did this in blocks of READ-ONLY CODE! Please fix this.

> Refactor -> Move Class into other class breaks multicatches and lambas in 
> destination class
> ---
>
> Key: NETBEANS-892
> URL: https://issues.apache.org/jira/browse/NETBEANS-892
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Refactoring
>Affects Versions: 9.0
>Reporter: Austin Stephens
>Priority: Blocker
> Attachments: SampleProject.7z
>
>
> Move the class "MoveMe" into the class "Killer". Things break



--
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-892) Refactor -> Move Class into other class breaks multicatches and lambas in destination class

2018-05-31 Thread Austin Stephens (JIRA)


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

Austin Stephens updated NETBEANS-892:
-
Attachment: EvilRefactorBug.zip

> Refactor -> Move Class into other class breaks multicatches and lambas in 
> destination class
> ---
>
> Key: NETBEANS-892
> URL: https://issues.apache.org/jira/browse/NETBEANS-892
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Refactoring
>Affects Versions: 9.0
>Reporter: Austin Stephens
>Priority: Blocker
> Attachments: EvilRefactorBug.zip, SampleProject.7z
>
>
> Move the class "MoveMe" into the class "Killer". Things break



--
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-892) Refactor -> Move Class into other class breaks multicatches and lambas in destination class

2018-05-31 Thread Austin Stephens (JIRA)


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

Austin Stephens updated NETBEANS-892:
-
Description: Move the class "MoveMe" into the class "Killer". Things break. 
Many, many thing break.  (was: Move the class "MoveMe" into the class "Killer". 
Things break)

> Refactor -> Move Class into other class breaks multicatches and lambas in 
> destination class
> ---
>
> Key: NETBEANS-892
> URL: https://issues.apache.org/jira/browse/NETBEANS-892
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Refactoring
>Affects Versions: 9.0
>Reporter: Austin Stephens
>Priority: Blocker
> Attachments: EvilRefactorBug.zip, SampleProject.7z
>
>
> Move the class "MoveMe" into the class "Killer". Things break. Many, many 
> thing break.



--
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-892) Refactor -> Move Class into other class breaks multicatches and lambas in destination class

2018-05-31 Thread Austin Stephens (JIRA)


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

Austin Stephens commented on NETBEANS-892:
--

Ok, it appears it only happens when moving a class into another class, but it 
modifies every file in the project, even if they are unrelated. The 
* It modifies generated code in read-only blocks. This will be a pain with 
versioning since the user would appear to have modified code for no reason 
whatsoever.
* It breaks the files it touches. Have fun going through your large project and 
trying to figure out what changes were yours and what changes were done by the 
refactoring engine being stupid.

> Refactor -> Move Class into other class breaks multicatches and lambas in 
> destination class
> ---
>
> Key: NETBEANS-892
> URL: https://issues.apache.org/jira/browse/NETBEANS-892
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Refactoring
>Affects Versions: 9.0
>Reporter: Austin Stephens
>Priority: Blocker
> Attachments: EvilRefactorBug.zip, SampleProject.7z
>
>
> Move the class "MoveMe" into the class "Killer". Things break. Many, many 
> thing break.



--
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-892) Refactor -> Move Class into other class breaks multicatches and lambas in destination class

2018-05-31 Thread Austin Stephens (JIRA)


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

Austin Stephens updated NETBEANS-892:
-
Description: Move the class "MoveMeIn" into the class "MoveTo". Things 
break. Many, many thing break.  (was: Move the class "MoveMe" into the class 
"Killer". Things break. Many, many thing break.)

> Refactor -> Move Class into other class breaks multicatches and lambas in 
> destination class
> ---
>
> Key: NETBEANS-892
> URL: https://issues.apache.org/jira/browse/NETBEANS-892
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Refactoring
>Affects Versions: 9.0
>Reporter: Austin Stephens
>Priority: Blocker
> Attachments: EvilRefactorBug.zip
>
>
> Move the class "MoveMeIn" into the class "MoveTo". Things break. Many, many 
> thing break.



--
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-892) Refactor -> Move Class into other class breaks multicatches and lambas in destination class

2018-05-31 Thread Austin Stephens (JIRA)


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

Austin Stephens edited comment on NETBEANS-892 at 5/31/18 3:45 PM:
---

Ok, it appears it only happens when moving a class into another class, but it 
modifies every file in the project, even if they are unrelated. The example 
project has versioning on it so you can see what it changed.
* It modifies generated code in read-only blocks. This will be a pain with 
versioning since the user would appear to have modified code for no reason 
whatsoever.
* It breaks the files it touches. Have fun going through your large project and 
trying to figure out what changes were yours and what changes were done by the 
refactoring engine being stupid.


was (Author: sir intellegence):
Ok, it appears it only happens when moving a class into another class, but it 
modifies every file in the project, even if they are unrelated. The 
* It modifies generated code in read-only blocks. This will be a pain with 
versioning since the user would appear to have modified code for no reason 
whatsoever.
* It breaks the files it touches. Have fun going through your large project and 
trying to figure out what changes were yours and what changes were done by the 
refactoring engine being stupid.

> Refactor -> Move Class into other class breaks multicatches and lambas in 
> destination class
> ---
>
> Key: NETBEANS-892
> URL: https://issues.apache.org/jira/browse/NETBEANS-892
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Refactoring
>Affects Versions: 9.0
>Reporter: Austin Stephens
>Priority: Blocker
> Attachments: EvilRefactorBug.zip
>
>
> Move the class "MoveMe" into the class "Killer". Things break. Many, many 
> thing break.



--
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-892) Refactor -> Move Class into other class breaks multicatches and lambas in destination class

2018-05-31 Thread Austin Stephens (JIRA)


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

Austin Stephens updated NETBEANS-892:
-
Attachment: (was: SampleProject.7z)

> Refactor -> Move Class into other class breaks multicatches and lambas in 
> destination class
> ---
>
> Key: NETBEANS-892
> URL: https://issues.apache.org/jira/browse/NETBEANS-892
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Refactoring
>Affects Versions: 9.0
>Reporter: Austin Stephens
>Priority: Blocker
> Attachments: EvilRefactorBug.zip
>
>
> Move the class "MoveMe" into the class "Killer". Things break. Many, many 
> thing break.



--
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-892) Refactor -> Move Class into other class breaks multicatches and lambas in destination class

2018-06-01 Thread Austin Stephens (JIRA)


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

Austin Stephens updated NETBEANS-892:
-
Fix Version/s: 9.0

> Refactor -> Move Class into other class breaks multicatches and lambas in 
> destination class
> ---
>
> Key: NETBEANS-892
> URL: https://issues.apache.org/jira/browse/NETBEANS-892
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Refactoring
>Affects Versions: 9.0
>Reporter: Austin Stephens
>Priority: Blocker
> Fix For: 9.0
>
> Attachments: EvilRefactorBug.zip
>
>
> Move the class "MoveMeIn" into the class "MoveTo". Things break. Many, many 
> thing break.



--
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-438) Cannot Sign Platform app due to symlink

2018-06-01 Thread Austin Stephens (JIRA)


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

Austin Stephens commented on NETBEANS-438:
--

A NetBeans platform application.

> Cannot Sign Platform app due to symlink
> ---
>
> Key: NETBEANS-438
> URL: https://issues.apache.org/jira/browse/NETBEANS-438
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - Other
>Affects Versions: 9.0
> Environment: Mac OS X
>Reporter: Austin Stephens
>Assignee: Austin Stephens
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 4h 20m
>  Remaining Estimate: 0h
>
> When you run "Package as->Mac OS X Application", it creates a .app that has a 
> symlink as the main executable. Attempting to sign it with `codesign` results 
> in the following error:
> {noformat}
> the main executable or Info.plist must be a regular file (no symlinks, 
> etc.){noformat}
> This can be solved by calling the resulting script via bash (resulting in 
> another instance of bash...) or cd-ing to the script directory and sourcing 
> it.



--
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] [Resolved] (NETBEANS-438) Cannot Sign Platform app due to symlink

2018-06-07 Thread Austin Stephens (JIRA)


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

Austin Stephens resolved NETBEANS-438.
--
   Resolution: Fixed
Fix Version/s: 9.0

Was merged into the main repo

> Cannot Sign Platform app due to symlink
> ---
>
> Key: NETBEANS-438
> URL: https://issues.apache.org/jira/browse/NETBEANS-438
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - Other
>Affects Versions: 9.0
> Environment: Mac OS X
>Reporter: Austin Stephens
>Assignee: Austin Stephens
>Priority: Major
>  Labels: pull-request-available
> Fix For: 9.0
>
>  Time Spent: 7h
>  Remaining Estimate: 0h
>
> When you run "Package as->Mac OS X Application", it creates a .app that has a 
> symlink as the main executable. Attempting to sign it with `codesign` results 
> in the following error:
> {noformat}
> the main executable or Info.plist must be a regular file (no symlinks, 
> etc.){noformat}
> This can be solved by calling the resulting script via bash (resulting in 
> another instance of bash...) or cd-ing to the script directory and sourcing 
> it.



--
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-1019) False positive of "Null Pointer Dereference" when passing a lambda with a null possible result to a non-null argument

2018-07-02 Thread Austin Stephens (JIRA)
Austin Stephens created NETBEANS-1019:
-

 Summary: False positive of "Null Pointer Dereference" when passing 
a lambda with a null possible result to a non-null argument
 Key: NETBEANS-1019
 URL: https://issues.apache.org/jira/browse/NETBEANS-1019
 Project: NetBeans
  Issue Type: Bug
  Components: java - Hints
Affects Versions: 9.0, Next
Reporter: Austin Stephens


Sample code:


{code:java}
private void func(@NonNull Function func){

}
@CheckForNull
private Object foo(){
return null;
}
private void bar(){
func(item->foo());//false positive
}
{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-1026) Cannot test custom annotations

2018-07-05 Thread Austin Stephens (JIRA)
Austin Stephens created NETBEANS-1026:
-

 Summary: Cannot test custom annotations
 Key: NETBEANS-1026
 URL: https://issues.apache.org/jira/browse/NETBEANS-1026
 Project: NetBeans
  Issue Type: Bug
  Components: java - Hints
Affects Versions: 9.0
Reporter: Austin Stephens
 Attachments: BrokenHintBug.zip

I was working on an annotation and I discovered that the test crashes with the 
following error:
{noformat}
Testcase: testWarningProduced(org.apache.netbeans.bugkiller.TestHintTest):    
Caused an ERROR
superclass access check failed: class 
org.netbeans.lib.nbjavac.services.NBMessager (in unnamed module @0x4d14b6c2) 
cannot access class com.sun.tools.javadoc.main.Messager (in module jdk.javadoc) 
because module jdk.javadoc does not export com.sun.tools.javadoc.main to 
unnamed module @0x4d14b6c2
java.lang.IllegalAccessError: superclass access check failed: class 
org.netbeans.lib.nbjavac.services.NBMessager (in unnamed module @0x4d14b6c2) 
cannot access class com.sun.tools.javadoc.main.Messager (in module jdk.javadoc) 
because module jdk.javadoc does not export com.sun.tools.javadoc.main to 
unnamed module @0x4d14b6c2
    at 
org.netbeans.modules.java.source.parsing.JavacParser.createJavacTask(JavacParser.java:885)
    at 
org.netbeans.modules.java.source.parsing.JavacParser.createJavacTask(JavacParser.java:741)
    at 
org.netbeans.modules.java.source.parsing.CompilationInfoImpl.getJavacTask(CompilationInfoImpl.java:374)
    at 
org.netbeans.modules.java.source.parsing.JavacParser.moveToPhase(JavacParser.java:582)
    at 
org.netbeans.modules.java.source.parsing.CompilationInfoImpl.toPhase(CompilationInfoImpl.java:361)
    at 
org.netbeans.api.java.source.CompilationController.toPhase(CompilationController.java:84)
    at 
org.netbeans.modules.java.hints.test.api.HintTest$DeadlockTask.run(HintTest.java:727)
    at 
org.netbeans.modules.java.hints.test.api.HintTest$DeadlockTask.run(HintTest.java:715)
    at 
org.netbeans.api.java.source.JavaSource$MultiTask.run(JavaSource.java:501)
    at 
org.netbeans.modules.parsing.impl.TaskProcessor.callUserTask(TaskProcessor.java:586)
    at 
org.netbeans.modules.parsing.api.ParserManager$UserTaskAction.run(ParserManager.java:130)
    at 
org.netbeans.modules.parsing.api.ParserManager$UserTaskAction.run(ParserManager.java:114)
    at 
org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:181)
    at 
org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:178)
    at 
org.netbeans.modules.masterfs.filebasedfs.utils.FileChangedManager.priorityIO(FileChangedManager.java:153)
    at 
org.netbeans.modules.masterfs.providers.ProvidedExtensions.priorityIO(ProvidedExtensions.java:335)
    at 
org.netbeans.modules.parsing.nb.DataObjectEnvFactory.runPriorityIO(DataObjectEnvFactory.java:118)
    at 
org.netbeans.modules.parsing.impl.Utilities.runPriorityIO(Utilities.java:67)
    at 
org.netbeans.modules.parsing.impl.TaskProcessor.runUserTask(TaskProcessor.java:178)
    at 
org.netbeans.modules.parsing.api.ParserManager.parse(ParserManager.java:81)
    at 
org.netbeans.api.java.source.JavaSource.runUserActionTaskImpl(JavaSource.java:451)
    at 
org.netbeans.api.java.source.JavaSource.runUserActionTask(JavaSource.java:422)
    at 
org.netbeans.modules.java.hints.test.api.HintTest.parse(HintTest.java:558)
    at 
org.netbeans.modules.java.hints.test.api.HintTest.ensureCompilable(HintTest.java:370)
    at org.netbeans.modules.java.hints.test.api.HintTest.run(HintTest.java:444)
    at org.netbeans.modules.java.hints.test.api.HintTest.run(HintTest.java:429)
    at 
org.apache.netbeans.bugkiller.TestHintTest.testWarningProduced(TestHintTest.java:30){noformat}



--
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-1026) Cannot test custom annotations

2018-07-05 Thread Austin Stephens (JIRA)


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

Austin Stephens updated NETBEANS-1026:
--
Description: 
The test case in the attached project crashes with the following error:
{noformat}
Testcase: testWarningProduced(org.apache.netbeans.bugkiller.TestHintTest):    
Caused an ERROR
superclass access check failed: class 
org.netbeans.lib.nbjavac.services.NBMessager (in unnamed module @0x4d14b6c2) 
cannot access class com.sun.tools.javadoc.main.Messager (in module jdk.javadoc) 
because module jdk.javadoc does not export com.sun.tools.javadoc.main to 
unnamed module @0x4d14b6c2
java.lang.IllegalAccessError: superclass access check failed: class 
org.netbeans.lib.nbjavac.services.NBMessager (in unnamed module @0x4d14b6c2) 
cannot access class com.sun.tools.javadoc.main.Messager (in module jdk.javadoc) 
because module jdk.javadoc does not export com.sun.tools.javadoc.main to 
unnamed module @0x4d14b6c2
    at 
org.netbeans.modules.java.source.parsing.JavacParser.createJavacTask(JavacParser.java:885)
    at 
org.netbeans.modules.java.source.parsing.JavacParser.createJavacTask(JavacParser.java:741)
    at 
org.netbeans.modules.java.source.parsing.CompilationInfoImpl.getJavacTask(CompilationInfoImpl.java:374)
    at 
org.netbeans.modules.java.source.parsing.JavacParser.moveToPhase(JavacParser.java:582)
    at 
org.netbeans.modules.java.source.parsing.CompilationInfoImpl.toPhase(CompilationInfoImpl.java:361)
    at 
org.netbeans.api.java.source.CompilationController.toPhase(CompilationController.java:84)
    at 
org.netbeans.modules.java.hints.test.api.HintTest$DeadlockTask.run(HintTest.java:727)
    at 
org.netbeans.modules.java.hints.test.api.HintTest$DeadlockTask.run(HintTest.java:715)
    at 
org.netbeans.api.java.source.JavaSource$MultiTask.run(JavaSource.java:501)
    at 
org.netbeans.modules.parsing.impl.TaskProcessor.callUserTask(TaskProcessor.java:586)
    at 
org.netbeans.modules.parsing.api.ParserManager$UserTaskAction.run(ParserManager.java:130)
    at 
org.netbeans.modules.parsing.api.ParserManager$UserTaskAction.run(ParserManager.java:114)
    at 
org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:181)
    at 
org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:178)
    at 
org.netbeans.modules.masterfs.filebasedfs.utils.FileChangedManager.priorityIO(FileChangedManager.java:153)
    at 
org.netbeans.modules.masterfs.providers.ProvidedExtensions.priorityIO(ProvidedExtensions.java:335)
    at 
org.netbeans.modules.parsing.nb.DataObjectEnvFactory.runPriorityIO(DataObjectEnvFactory.java:118)
    at 
org.netbeans.modules.parsing.impl.Utilities.runPriorityIO(Utilities.java:67)
    at 
org.netbeans.modules.parsing.impl.TaskProcessor.runUserTask(TaskProcessor.java:178)
    at 
org.netbeans.modules.parsing.api.ParserManager.parse(ParserManager.java:81)
    at 
org.netbeans.api.java.source.JavaSource.runUserActionTaskImpl(JavaSource.java:451)
    at 
org.netbeans.api.java.source.JavaSource.runUserActionTask(JavaSource.java:422)
    at 
org.netbeans.modules.java.hints.test.api.HintTest.parse(HintTest.java:558)
    at 
org.netbeans.modules.java.hints.test.api.HintTest.ensureCompilable(HintTest.java:370)
    at org.netbeans.modules.java.hints.test.api.HintTest.run(HintTest.java:444)
    at org.netbeans.modules.java.hints.test.api.HintTest.run(HintTest.java:429)
    at 
org.apache.netbeans.bugkiller.TestHintTest.testWarningProduced(TestHintTest.java:30){noformat}

  was:
I was working on an annotation and I discovered that the test crashes with the 
following error:
{noformat}
Testcase: testWarningProduced(org.apache.netbeans.bugkiller.TestHintTest):    
Caused an ERROR
superclass access check failed: class 
org.netbeans.lib.nbjavac.services.NBMessager (in unnamed module @0x4d14b6c2) 
cannot access class com.sun.tools.javadoc.main.Messager (in module jdk.javadoc) 
because module jdk.javadoc does not export com.sun.tools.javadoc.main to 
unnamed module @0x4d14b6c2
java.lang.IllegalAccessError: superclass access check failed: class 
org.netbeans.lib.nbjavac.services.NBMessager (in unnamed module @0x4d14b6c2) 
cannot access class com.sun.tools.javadoc.main.Messager (in module jdk.javadoc) 
because module jdk.javadoc does not export com.sun.tools.javadoc.main to 
unnamed module @0x4d14b6c2
    at 
org.netbeans.modules.java.source.parsing.JavacParser.createJavacTask(JavacParser.java:885)
    at 
org.netbeans.modules.java.source.parsing.JavacParser.createJavacTask(JavacParser.java:741)
    at 
org.netbeans.modules.java.source.parsing.CompilationInfoImpl.getJavacTask(CompilationInfoImpl.java:374)
    at 
org.netbeans.modules.java.source.parsing.JavacParser.moveToPhase(JavacParser.java:582)
    at 
org.netbeans.modules.java.source.parsing.CompilationInfoImpl.toPhase(CompilationInfoImpl.java:361)
    at 
org.netbeans.api.java.source.CompilationController.toPh

[jira] [Created] (NETBEANS-1037) Netbeans sometimes freezes when showing the InspectAndRefactorPanel dialog when running with jdk 1.8.0_152-b16 or later

2018-07-10 Thread Austin Stephens (JIRA)
Austin Stephens created NETBEANS-1037:
-

 Summary: Netbeans sometimes freezes when showing the 
InspectAndRefactorPanel dialog when running with jdk 1.8.0_152-b16 or later
 Key: NETBEANS-1037
 URL: https://issues.apache.org/jira/browse/NETBEANS-1037
 Project: NetBeans
  Issue Type: Bug
  Components: java - Refactoring
Affects Versions: 9.0
Reporter: Austin Stephens


The culprit seems to be another "do we really need to synchronize this method" 
issue.

The method is InspectAndrefactorPanel.manageRefactorings(boolean single)



--
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-1037) Netbeans sometimes freezes when showing the InspectAndRefactorPanel dialog when running with jdk 1.8.0_152-b16 or later

2018-07-10 Thread Austin Stephens (JIRA)


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

Austin Stephens updated NETBEANS-1037:
--
Fix Version/s: 9.0

> Netbeans sometimes freezes when showing the InspectAndRefactorPanel dialog 
> when running with jdk 1.8.0_152-b16 or later
> ---
>
> Key: NETBEANS-1037
> URL: https://issues.apache.org/jira/browse/NETBEANS-1037
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Refactoring
>Affects Versions: 9.0
>Reporter: Austin Stephens
>Priority: Major
> Fix For: 9.0
>
>
> The culprit seems to be another "do we really need to synchronize this 
> method" issue.
> The method is InspectAndrefactorPanel.manageRefactorings(boolean single)



--
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-1042) IndexOutOfBoundsException in BreakpointAnnotationProvider can be avoided

2018-07-13 Thread Austin Stephens (JIRA)
Austin Stephens created NETBEANS-1042:
-

 Summary: IndexOutOfBoundsException in BreakpointAnnotationProvider 
can be avoided
 Key: NETBEANS-1042
 URL: https://issues.apache.org/jira/browse/NETBEANS-1042
 Project: NetBeans
  Issue Type: Bug
  Components: debugger - Java
Reporter: Austin Stephens
Assignee: Austin Stephens


It is rather annoying to have exceptions like that thrown when you have 
breakpoints on them to help you find bugs, so I fixed it. This bug report is 
mostly to get a branch name that won't cause issues...



--
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-1043) Refactor -> Move method does not update method::references

2018-07-13 Thread Austin Stephens (JIRA)
Austin Stephens created NETBEANS-1043:
-

 Summary: Refactor -> Move method does not update method::references
 Key: NETBEANS-1043
 URL: https://issues.apache.org/jira/browse/NETBEANS-1043
 Project: NetBeans
  Issue Type: Bug
  Components: java - Refactoring
Affects Versions: 9.0
Reporter: Austin Stephens


Given the following code (was done inside a class for simplicity):
{code:java}
    public static class Baz{
        public static void doStuff(BooleanSupplier source){
            boolean val = source.getAsBoolean();
        }
        public static void prepareStuff(){
            doStuff(Bar::moveThis);
        }
    }

    public static class Bar {
        public static boolean moveThis(){
            return true;
        }
    }
    public static class Foo{
    
    }
{code}
If you Refactor Move `moveThis` from `Bar` to `Foo`, the reference in 
Baz.prepareStuff() does not get updated.



--
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-1042) IndexOutOfBoundsException in BreakpointAnnotationProvider can be avoided

2018-07-16 Thread Austin Stephens (JIRA)


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

Austin Stephens commented on NETBEANS-1042:
---

It was -1. I will get you the stack trace. Would a heap dump be better?

> IndexOutOfBoundsException in BreakpointAnnotationProvider can be avoided
> 
>
> Key: NETBEANS-1042
> URL: https://issues.apache.org/jira/browse/NETBEANS-1042
> Project: NetBeans
>  Issue Type: Bug
>  Components: debugger - Java
>Reporter: Austin Stephens
>Assignee: Austin Stephens
>Priority: Trivial
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> It is rather annoying to have exceptions like that thrown when you have 
> breakpoints on them to help you find bugs, so I fixed it. This bug report is 
> mostly to get a branch name that won't cause issues...



--
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-1050) Slay all of the warnings! (Root task)

2018-07-16 Thread Austin Stephens (JIRA)
Austin Stephens created NETBEANS-1050:
-

 Summary: Slay all of the warnings! (Root task)
 Key: NETBEANS-1050
 URL: https://issues.apache.org/jira/browse/NETBEANS-1050
 Project: NetBeans
  Issue Type: Task
Reporter: Austin Stephens


(It is recommended you read this with good humor, like Think Geek)

While building Netbeans, a number of warnings show up. We should fix that.

For the sake of organization, we should probably open a new task for each 
module. This will be the root/umbrella task. *The main project heads should 
take a look at this task and update it with official stuff.*

We should probably slay warnings in this order:
 # Warnings that don't require changes to other modules (like API changes). 
Examples would be changing raw types to non-raw types or something that would 
cause another module to not build after the warning has be properly dealt with.
 # Warnings that Do require changes to other modules (see previous entry for 
examples)
 # Those evil warnings that don't leave any links behind. Here are some 
examples:
{noformat}
warning: [options] bootstrap class path not set in conjunction with -source 1.7
/Volumes/Data/Code//incubator-netbeans/nbbuild/build/public-package-jars/org-netbeans-api-annotations-common.jar(org/netbeans/api/annotations/common/NonNull.class):
 warning: Cannot find annotation method 'when()' in type 'Nonnull': class file 
for javax.annotation.Nonnull not found
warning: unknown enum constant When.ALWAYS
  reason: class file for javax.annotation.meta.When not found
/Volumes/Data/Code//incubator-netbeans/nbbuild/build/public-package-jars/org-netbeans-api-annotations-common.jar(org/netbeans/api/annotations/common/NullAllowed.class):
 warning: Cannot find annotation method 'when()' in type 'Nonnull'
warning: unknown enum constant When.MAYBE
/Volumes/Data/Code//incubator-netbeans/nbbuild/build/public-package-jars/org-netbeans-api-annotations-common.jar(org/netbeans/api/annotations/common/CheckForNull.class):
 warning: Cannot find annotation method 'when()' in type 'Nonnull'
warning: unknown enum constant When.MAYBE
warning: Supported source version 'RELEASE_6' from annotation processor 
'org.netbeans.modules.openide.util.NbBundleProcessor' less than -source '1.7'
warning: No processor claimed any of these annotations: 
org.netbeans.api.annotations.common.NullAllowed,org.netbeans.api.annotations.common.CheckForNull,org.netbeans.api.annotations.common.NonNull{noformat}

 The following guide-lines should be followed while slaying warnings:
 * You shall make every effort to resolve the warning without suppressing it. 
This may involve one or more of the following (non-inclusive):
 ** Adding a new variable so assignments are not done to method parameters
 ** Adding a variable followed with an "assert var != null" to let the IDE know 
that it can't be null
 ** In the second pass, breaking APIs so raw types and such are not used if 
possible
 * You shall suppress the warning on the *smallest scope possible*. Why? 
Warnings exist for a reason. They are there to tell you that you did something 
wrong, unless that was your intention and you know what you are doing. That is 
what @SuppressWarnings is for. If (heaven forbid) you suppress all warnings in 
a class file, you may be (figuratively) slain, so DON'T!
 * The following (in my opinion) is a good way to suppress a warning on a line:

{code:java}
@SuppressWarning("unchecked")
Object shush = bar = (Foo)foo;{code}

 * You may want to add dummy return values to some void methods to enable 
suppression via the above method.
 * If you do suppress a warning, and it is not obvious why it was suppressed, 
*document it*! Leave a comment that says why it was suppressed. The following 
is an example:

{code:java}
//the following is intentional
//the method is expected to return an constant array
@SuppressWarnings("OverridableMethodCallInConstructor")
List shush = ImmutableList.copyOf(getSupportedTypes());{code}

I think that is all for now...



--
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-1042) IndexOutOfBoundsException in BreakpointAnnotationProvider can be avoided

2018-07-16 Thread Austin Stephens (JIRA)


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

Austin Stephens commented on NETBEANS-1042:
---

Here is your stack trace:
{noformat}
LineRootElement.getElement:64    
NbDocument$DocumentRenderer.run:898    
BaseDocument.render:1402    
NbDocument$DocumentRenderer.renderToInt:873    
NbDocument.findLineOffset:176    
DocumentLine$Set.offset:1054    
DocumentLine$Set.access$400:921    
DocumentLine$Set$OffsetLineCreator.createLine:1095    
LineVector.findOrCreateLine:142    
Line$Set.findOrCreateLine:533    
DocumentLine$Set.access$301:921    
DocumentLine$Set$1DocumentRenderer.run:1077    
BaseDocument.render:1402    
DocumentLine$Set.safelyFindOrCreateLine:1083    
DocumentLine$Set.getCurrent:1049    
BreakpointAnnotationProvider.addAnnotationTo:416    
BreakpointAnnotationProvider.access$600:67    
BreakpointAnnotationProvider$2.run:360    
RequestProcessor$Task.run:1418    
GlobalLookup.execute:45    
Lookups.executeWith:278    
RequestProcessor$Processor.run:2033   {noformat}
The exception thrown is "Invalid line index=-2 < 0"

> IndexOutOfBoundsException in BreakpointAnnotationProvider can be avoided
> 
>
> Key: NETBEANS-1042
> URL: https://issues.apache.org/jira/browse/NETBEANS-1042
> Project: NetBeans
>  Issue Type: Bug
>  Components: debugger - Java
>Reporter: Austin Stephens
>Assignee: Austin Stephens
>Priority: Trivial
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> It is rather annoying to have exceptions like that thrown when you have 
> breakpoints on them to help you find bugs, so I fixed it. This bug report is 
> mostly to get a branch name that won't cause issues...



--
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-1042) IndexOutOfBoundsException in BreakpointAnnotationProvider can be avoided

2018-07-16 Thread Austin Stephens (JIRA)


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

Austin Stephens edited comment on NETBEANS-1042 at 7/16/18 5:57 PM:


Here is your stack trace:
{noformat}
LineRootElement.getElement:64    
NbDocument$DocumentRenderer.run:898    
BaseDocument.render:1402    
NbDocument$DocumentRenderer.renderToInt:873    
NbDocument.findLineOffset:176    
DocumentLine$Set.offset:1054    
DocumentLine$Set.access$400:921    
DocumentLine$Set$OffsetLineCreator.createLine:1095    
LineVector.findOrCreateLine:142    
Line$Set.findOrCreateLine:533    
DocumentLine$Set.access$301:921    
DocumentLine$Set$1DocumentRenderer.run:1077    
BaseDocument.render:1402    
DocumentLine$Set.safelyFindOrCreateLine:1083    
DocumentLine$Set.getCurrent:1049    
BreakpointAnnotationProvider.addAnnotationTo:416    
BreakpointAnnotationProvider.access$600:67    
BreakpointAnnotationProvider$2.run:360    
RequestProcessor$Task.run:1418    
GlobalLookup.execute:45    
Lookups.executeWith:278    
RequestProcessor$Processor.run:2033   {noformat}
The exception thrown is "Invalid line index=-2 < 0"

Edit: A -1 comes from an array produced by 
BreakpointAnnotationProvider.getAnnotationLines on line 126. It (the array of 
\{-1}) is then passed to addAnnotationTo where the -1 is pulled from the array, 
1 is subtracted from it, and then is used as an index into 
LineCookie.getLineSet().getCurrent(int) on line 416.


was (Author: sir intellegence):
Here is your stack trace:
{noformat}
LineRootElement.getElement:64    
NbDocument$DocumentRenderer.run:898    
BaseDocument.render:1402    
NbDocument$DocumentRenderer.renderToInt:873    
NbDocument.findLineOffset:176    
DocumentLine$Set.offset:1054    
DocumentLine$Set.access$400:921    
DocumentLine$Set$OffsetLineCreator.createLine:1095    
LineVector.findOrCreateLine:142    
Line$Set.findOrCreateLine:533    
DocumentLine$Set.access$301:921    
DocumentLine$Set$1DocumentRenderer.run:1077    
BaseDocument.render:1402    
DocumentLine$Set.safelyFindOrCreateLine:1083    
DocumentLine$Set.getCurrent:1049    
BreakpointAnnotationProvider.addAnnotationTo:416    
BreakpointAnnotationProvider.access$600:67    
BreakpointAnnotationProvider$2.run:360    
RequestProcessor$Task.run:1418    
GlobalLookup.execute:45    
Lookups.executeWith:278    
RequestProcessor$Processor.run:2033   {noformat}
The exception thrown is "Invalid line index=-2 < 0"

> IndexOutOfBoundsException in BreakpointAnnotationProvider can be avoided
> 
>
> Key: NETBEANS-1042
> URL: https://issues.apache.org/jira/browse/NETBEANS-1042
> Project: NetBeans
>  Issue Type: Bug
>  Components: debugger - Java
>Reporter: Austin Stephens
>Assignee: Austin Stephens
>Priority: Trivial
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> It is rather annoying to have exceptions like that thrown when you have 
> breakpoints on them to help you find bugs, so I fixed it. This bug report is 
> mostly to get a branch name that won't cause issues...



--
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-1059) AutoComplete list won't show

2018-07-18 Thread Austin Stephens (JIRA)
Austin Stephens created NETBEANS-1059:
-

 Summary: AutoComplete list won't show
 Key: NETBEANS-1059
 URL: https://issues.apache.org/jira/browse/NETBEANS-1059
 Project: NetBeans
  Issue Type: Bug
  Components: java - Editor
Affects Versions: 9.0
Reporter: Austin Stephens
 Attachments: Screen Shot 2018-07-18 at 3.04.07 PM.png, Screen Shot 
2018-07-18 at 3.04.16 PM.png, SlayBugs.java

Given the attached Java file, NetBeans will not give an auto-complete list if 
the cursor is on the second line before the semi-colon. I have attached 
screenshots to display the issue.



--
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-1043) Refactor -> Move method does not update method::references

2018-07-30 Thread Austin Stephens (JIRA)


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

Austin Stephens commented on NETBEANS-1043:
---

According to the branch names, I am using vc3

> Refactor -> Move method does not update method::references
> --
>
> Key: NETBEANS-1043
> URL: https://issues.apache.org/jira/browse/NETBEANS-1043
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Refactoring
>Affects Versions: 9.0
>Reporter: Austin Stephens
>Assignee: ARUNAVA SINHA
>Priority: Major
>
> Given the following code (was done inside a class for simplicity):
> {code:java}
>     public static class Baz{
>         public static void doStuff(BooleanSupplier source){
>             boolean val = source.getAsBoolean();
>         }
>         public static void prepareStuff(){
>             doStuff(Bar::moveThis);
>         }
>     }
>     public static class Bar {
>         public static boolean moveThis(){
>             return true;
>         }
>     }
>     public static class Foo{
>     
>     }
> {code}
> If you Refactor Move `moveThis` from `Bar` to `Foo`, the reference in 
> Baz.prepareStuff() does not get updated.



--
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-1128) Use the JSON format to read mercurial blame data

2018-08-10 Thread Austin Stephens (JIRA)
Austin Stephens created NETBEANS-1128:
-

 Summary: Use the JSON format to read mercurial blame data
 Key: NETBEANS-1128
 URL: https://issues.apache.org/jira/browse/NETBEANS-1128
 Project: NetBeans
  Issue Type: Bug
  Components: versioncontrol - Mercurial
Affects Versions: 9.0
Reporter: Austin Stephens
Assignee: Austin Stephens


To avoid nasty surprises in the future.



--
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-1128) Use the JSON format to read mercurial blame data

2018-08-10 Thread Austin Stephens (JIRA)


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

Austin Stephens updated NETBEANS-1128:
--
Description: 
To avoid nasty surprises in the future.

See [https://github.com/apache/incubator-netbeans/pull/508] for the discussion 
about why I suggest we use JSON.

  was:To avoid nasty surprises in the future.


> Use the JSON format to read mercurial blame data
> 
>
> Key: NETBEANS-1128
> URL: https://issues.apache.org/jira/browse/NETBEANS-1128
> Project: NetBeans
>  Issue Type: Bug
>  Components: versioncontrol - Mercurial
>Affects Versions: 9.0
>Reporter: Austin Stephens
>Assignee: Austin Stephens
>Priority: Major
>
> To avoid nasty surprises in the future.
> See [https://github.com/apache/incubator-netbeans/pull/508] for the 
> discussion about why I suggest we use JSON.



--
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-1129) Add worktree support

2018-08-10 Thread Austin Stephens (JIRA)
Austin Stephens created NETBEANS-1129:
-

 Summary: Add worktree support
 Key: NETBEANS-1129
 URL: https://issues.apache.org/jira/browse/NETBEANS-1129
 Project: NetBeans
  Issue Type: Bug
  Components: versioncontrol - Git
Affects Versions: 9.0
Reporter: Austin Stephens


Currently, Netbeans says that all files in a different work-tree are new, even 
if they are not.



--
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-1129) Add Git worktree support

2018-08-10 Thread Austin Stephens (JIRA)


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

Austin Stephens updated NETBEANS-1129:
--
Summary: Add Git worktree support  (was: Add worktree support)

> Add Git worktree support
> 
>
> Key: NETBEANS-1129
> URL: https://issues.apache.org/jira/browse/NETBEANS-1129
> Project: NetBeans
>  Issue Type: Bug
>  Components: versioncontrol - Git
>Affects Versions: 9.0
>Reporter: Austin Stephens
>Priority: Major
>
> Currently, Netbeans says that all files in a different work-tree are new, 
> even if they are not.



--
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-530) No Bind option on the popup to create Bindings

2018-08-10 Thread Austin Stephens (JIRA)


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

Austin Stephens commented on NETBEANS-530:
--

I have a revision that brings the form.bindings module back from the dead. How 
do I reference an external library to go with it? Note: I did not being back 
jdesktop

> No Bind option on the popup to create Bindings 
> ---
>
> Key: NETBEANS-530
> URL: https://issues.apache.org/jira/browse/NETBEANS-530
> Project: NetBeans
>  Issue Type: Bug
>  Components: ide - Code
>Affects Versions: 9.0
> Environment: Window 8.1, MacOs 10.11.6
>Reporter: efrem mccrimon
>Priority: Major
> Attachments: Screenshot from 2018-08-02 21-18-53.png, 
> no_bind_popup_item.JPG
>
>
> Trying to create bindings, created a textfield and Slider to demonstrate and 
> test basic bean binding.  From the Design view, I wanted to bind the slider 
> to the text field.
> Right-click the text field component and wanted to choose Bind.  There is not 
> Bind option on the popup menu.  It is not present in build #375, or #378.  It 
> is on NB 8.2 and NB 8.02.



--
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-530) No Bind option on the popup to create Bindings

2018-08-10 Thread Austin Stephens (JIRA)


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

Austin Stephens commented on NETBEANS-530:
--

[~patrick.angle], is [https://github.com/pangle/PACommons] the project that you 
are working on?

> No Bind option on the popup to create Bindings 
> ---
>
> Key: NETBEANS-530
> URL: https://issues.apache.org/jira/browse/NETBEANS-530
> Project: NetBeans
>  Issue Type: Bug
>  Components: ide - Code
>Affects Versions: 9.0
> Environment: Window 8.1, MacOs 10.11.6
>Reporter: efrem mccrimon
>Priority: Major
> Attachments: Screenshot from 2018-08-02 21-18-53.png, 
> no_bind_popup_item.JPG
>
>
> Trying to create bindings, created a textfield and Slider to demonstrate and 
> test basic bean binding.  From the Design view, I wanted to bind the slider 
> to the text field.
> Right-click the text field component and wanted to choose Bind.  There is not 
> Bind option on the popup menu.  It is not present in build #375, or #378.  It 
> is on NB 8.2 and NB 8.02.



--
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-663) Shortcuts using "alt/option" on the mac do not work.

2018-08-13 Thread Austin Stephens (JIRA)


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

Austin Stephens commented on NETBEANS-663:
--

So, it appears that Oracle, in their infinite wisdom, decided to emit the 
ALT_GR modifier with the ALT modifier in Java 9+. It happens to both ALTs on 
the Mac and the right one on windows. The added causes the shortcut lookup to 
fail since it was only expecting ALT. It seems to break other things like the 
shortcut option window (Alt + key don't register)

> Shortcuts using "alt/option" on the mac do not work.
> 
>
> Key: NETBEANS-663
> URL: https://issues.apache.org/jira/browse/NETBEANS-663
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - Action Items
>Affects Versions: 9.0
>Reporter: Austin Stephens
>Priority: Major
>
> The menu item flashes like it was activated, but nothing happens. This might 
> be because the key is interpreted like "alt altGraph pressed \{Key}" or 
> because it is never added to the binding map. I do note that "alt + F11" was 
> in the map, but that didn't work either (probably for the first reason). All 
> of the others are just not in the map. See NbKeymap.getAction.



--
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-663) Shortcuts using "alt/option" on the mac do not work.

2018-08-13 Thread Austin Stephens (JIRA)


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

Austin Stephens updated NETBEANS-663:
-
Priority: Critical  (was: Major)

> Shortcuts using "alt/option" on the mac do not work.
> 
>
> Key: NETBEANS-663
> URL: https://issues.apache.org/jira/browse/NETBEANS-663
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - Action Items
>Affects Versions: 9.0
>Reporter: Austin Stephens
>Priority: Critical
>
> The menu item flashes like it was activated, but nothing happens. This might 
> be because the key is interpreted like "alt altGraph pressed \{Key}" or 
> because it is never added to the binding map. I do note that "alt + F11" was 
> in the map, but that didn't work either (probably for the first reason). All 
> of the others are just not in the map. See NbKeymap.getAction.



--
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-663) Shortcuts using "alt/option" on the mac do not work.

2018-08-13 Thread Austin Stephens (JIRA)


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

Austin Stephens edited comment on NETBEANS-663 at 8/13/18 11:03 PM:


So, it appears that Oracle, in their infinite wisdom, decided to emit the 
ALT_GR modifier with the ALT modifier in Java 9+. It happens to both ALTs on 
the Mac and the right one on windows. The added causes the shortcut lookup to 
fail since it was only expecting ALT. It seems to break other things like the 
shortcut option window (Alt + key don't register)

Edit: This results in certain common shortcuts such as "copy up" and "move left 
one word" to not work.


was (Author: sir intellegence):
So, it appears that Oracle, in their infinite wisdom, decided to emit the 
ALT_GR modifier with the ALT modifier in Java 9+. It happens to both ALTs on 
the Mac and the right one on windows. The added causes the shortcut lookup to 
fail since it was only expecting ALT. It seems to break other things like the 
shortcut option window (Alt + key don't register)

> Shortcuts using "alt/option" on the mac do not work.
> 
>
> Key: NETBEANS-663
> URL: https://issues.apache.org/jira/browse/NETBEANS-663
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - Action Items
>Affects Versions: 9.0
>Reporter: Austin Stephens
>Priority: Critical
>
> The menu item flashes like it was activated, but nothing happens. This might 
> be because the key is interpreted like "alt altGraph pressed \{Key}" or 
> because it is never added to the binding map. I do note that "alt + F11" was 
> in the map, but that didn't work either (probably for the first reason). All 
> of the others are just not in the map. See NbKeymap.getAction.



--
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-530) No Bind option on the popup to create Bindings

2018-08-14 Thread Austin Stephens (JIRA)


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

Austin Stephens commented on NETBEANS-530:
--

I have brought back the form.binding module here: 
[https://github.com/SirIntellegence/incubator-netbeans/tree/NETBEANS-530]

Haven't done anything else so far though.

> No Bind option on the popup to create Bindings 
> ---
>
> Key: NETBEANS-530
> URL: https://issues.apache.org/jira/browse/NETBEANS-530
> Project: NetBeans
>  Issue Type: Bug
>  Components: ide - Code
>Affects Versions: 9.0
> Environment: Window 8.1, MacOs 10.11.6
>Reporter: efrem mccrimon
>Priority: Major
> Attachments: Screenshot from 2018-08-02 21-18-53.png, 
> no_bind_popup_item.JPG
>
>
> Trying to create bindings, created a textfield and Slider to demonstrate and 
> test basic bean binding.  From the Design view, I wanted to bind the slider 
> to the text field.
> Right-click the text field component and wanted to choose Bind.  There is not 
> Bind option on the popup menu.  It is not present in build #375, or #378.  It 
> is on NB 8.2 and NB 8.02.



--
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-1139) AssertionError in org.netbeans.modules.editor.java.JavaCodeTemplateProcessor.getProposedValue

2018-08-14 Thread Austin Stephens (JIRA)
Austin Stephens created NETBEANS-1139:
-

 Summary: AssertionError in 
org.netbeans.modules.editor.java.JavaCodeTemplateProcessor.getProposedValue
 Key: NETBEANS-1139
 URL: https://issues.apache.org/jira/browse/NETBEANS-1139
 Project: NetBeans
  Issue Type: Bug
  Components: java - Editor
Affects Versions: 9.0, Next
 Environment: Mac 10.10
Java 10.0.2+13
Reporter: Austin Stephens
 Attachments: AutoCompleteBug1.java

Attempting to Autocomplete the constructor after new in the attached file 
throws an AssertionError.

StackTrace:
{noformat}
java.lang.AssertionError
    at com.sun.tools.javac.util.Assert.error(Assert.java:155)
    at com.sun.tools.javac.util.Assert.check(Assert.java:46)
    at com.sun.tools.javac.code.Scope$ScopeImpl.dble(Scope.java:410)
    at com.sun.tools.javac.code.Scope$ScopeImpl.enter(Scope.java:433)
    at com.sun.tools.javac.comp.MemberEnter.visitVarDef(MemberEnter.java:476)
    at 
com.sun.tools.javadoc.main.JavadocMemberEnter.visitVarDef(JavadocMemberEnter.java:83)
    at 
org.netbeans.lib.nbjavac.services.NBJavadocMemberEnter.visitVarDef(NBJavadocMemberEnter.java:92)
    at com.sun.tools.javac.tree.JCTree$JCVariableDecl.accept(JCTree.java:962)
    at com.sun.tools.javac.comp.MemberEnter.memberEnter(MemberEnter.java:171)
    at com.sun.tools.javac.comp.Attr.visitVarDef(Attr.java:1171)
    at com.sun.tools.javac.tree.JCTree$JCVariableDecl.accept(JCTree.java:962)
    at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:660)
    at com.sun.tools.javac.comp.Attr.attribStat(Attr.java:736)
    at com.sun.tools.javac.comp.Attr.attribStats(Attr.java:760)
    at com.sun.tools.javac.comp.Attr.visitBlock(Attr.java:1337)
    at org.netbeans.lib.nbjavac.services.NBAttr.visitBlock(NBAttr.java:73)
    at com.sun.tools.javac.tree.JCTree$JCBlock.accept(JCTree.java:1026)
    at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:660)
    at com.sun.tools.javac.comp.Attr.attribStat(Attr.java:736)
    at 
org.netbeans.api.java.source.TreeUtilities.attributeTree(TreeUtilities.java:878)
    at 
org.netbeans.api.java.source.TreeUtilities.attributeTree(TreeUtilities.java:808)
    at 
org.netbeans.modules.editor.java.JavaCodeTemplateProcessor.type(JavaCodeTemplateProcessor.java:716)
    at 
org.netbeans.modules.editor.java.JavaCodeTemplateProcessor.getProposedValue(JavaCodeTemplateProcessor.java:431)
    at 
org.netbeans.modules.editor.java.JavaCodeTemplateProcessor.updateDefaultValues(JavaCodeTemplateProcessor.java:143)
    at 
org.netbeans.lib.editor.codetemplates.CodeTemplateInsertHandler.processTemplate(CodeTemplateInsertHandler.java:225)
    at 
org.netbeans.lib.editor.codetemplates.CodeTemplateManagerOperation.insert(CodeTemplateManagerOperation.java:273)
    at 
org.netbeans.lib.editor.codetemplates.api.CodeTemplate.insert(CodeTemplate.java:82)
    at 
org.netbeans.modules.editor.java.JavaCompletionItem.process(JavaCompletionItem.java:566)
    at 
org.netbeans.modules.editor.java.JavaCompletionItem.defaultAction(JavaCompletionItem.java:286)
    at 
org.netbeans.modules.editor.completion.CompletionImpl.dispatchKeyEvent(CompletionImpl.java:785)
    at 
org.netbeans.modules.editor.completion.CompletionImpl.keyPressed(CompletionImpl.java:386)
    at 
java.desktop/java.awt.AWTEventMulticaster.keyPressed(AWTEventMulticaster.java:258)
    at 
java.desktop/java.awt.AWTEventMulticaster.keyPressed(AWTEventMulticaster.java:257)
    at 
java.desktop/java.awt.AWTEventMulticaster.keyPressed(AWTEventMulticaster.java:257)
    at java.desktop/java.awt.Component.processKeyEvent(Component.java:6547)
    at java.desktop/javax.swing.JComponent.processKeyEvent(JComponent.java:2849)
    at java.desktop/java.awt.Component.processEvent(Component.java:6366)
    at java.desktop/java.awt.Container.processEvent(Container.java:2261)
    at java.desktop/java.awt.Component.dispatchEventImpl(Component.java:4966)
    at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2319)
    at java.desktop/java.awt.Component.dispatchEvent(Component.java:4798)
    at 
java.desktop/java.awt.KeyboardFocusManager.redispatchEvent(KeyboardFocusManager.java:1950)
    at 
java.desktop/java.awt.DefaultKeyboardFocusManager.dispatchKeyEvent(DefaultKeyboardFocusManager.java:871)
    at 
java.desktop/java.awt.DefaultKeyboardFocusManager.preDispatchKeyEvent(DefaultKeyboardFocusManager.java:1140)
    at 
java.desktop/java.awt.DefaultKeyboardFocusManager.typeAheadAssertions(DefaultKeyboardFocusManager.java:1010)
    at 
java.desktop/java.awt.DefaultKeyboardFocusManager.dispatchEvent(DefaultKeyboardFocusManager.java:836)
    at java.desktop/java.awt.Component.dispatchEventImpl(Component.java:4847)
    at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2319)
    at java.desktop/java.awt.Window.dispatchEventImpl(Window.java:2772)
    at java.desktop/java.awt.Component.dispatchEvent(Component

[jira] [Updated] (NETBEANS-1139) AssertionError in org.netbeans.modules.editor.java.JavaCodeTemplateProcessor.getProposedValue

2018-08-14 Thread Austin Stephens (JIRA)


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

Austin Stephens updated NETBEANS-1139:
--
Environment: (was: Mac 10.10
Java 10.0.2+13)

> AssertionError in 
> org.netbeans.modules.editor.java.JavaCodeTemplateProcessor.getProposedValue
> -
>
> Key: NETBEANS-1139
> URL: https://issues.apache.org/jira/browse/NETBEANS-1139
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Editor
>Affects Versions: 9.0, Next
>Reporter: Austin Stephens
>Priority: Major
> Attachments: AutoCompleteBug1.java
>
>
> Attempting to Autocomplete the constructor after new in the attached file 
> throws an AssertionError.
> StackTrace:
> {noformat}
> java.lang.AssertionError
>     at com.sun.tools.javac.util.Assert.error(Assert.java:155)
>     at com.sun.tools.javac.util.Assert.check(Assert.java:46)
>     at com.sun.tools.javac.code.Scope$ScopeImpl.dble(Scope.java:410)
>     at com.sun.tools.javac.code.Scope$ScopeImpl.enter(Scope.java:433)
>     at com.sun.tools.javac.comp.MemberEnter.visitVarDef(MemberEnter.java:476)
>     at 
> com.sun.tools.javadoc.main.JavadocMemberEnter.visitVarDef(JavadocMemberEnter.java:83)
>     at 
> org.netbeans.lib.nbjavac.services.NBJavadocMemberEnter.visitVarDef(NBJavadocMemberEnter.java:92)
>     at com.sun.tools.javac.tree.JCTree$JCVariableDecl.accept(JCTree.java:962)
>     at com.sun.tools.javac.comp.MemberEnter.memberEnter(MemberEnter.java:171)
>     at com.sun.tools.javac.comp.Attr.visitVarDef(Attr.java:1171)
>     at com.sun.tools.javac.tree.JCTree$JCVariableDecl.accept(JCTree.java:962)
>     at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:660)
>     at com.sun.tools.javac.comp.Attr.attribStat(Attr.java:736)
>     at com.sun.tools.javac.comp.Attr.attribStats(Attr.java:760)
>     at com.sun.tools.javac.comp.Attr.visitBlock(Attr.java:1337)
>     at org.netbeans.lib.nbjavac.services.NBAttr.visitBlock(NBAttr.java:73)
>     at com.sun.tools.javac.tree.JCTree$JCBlock.accept(JCTree.java:1026)
>     at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:660)
>     at com.sun.tools.javac.comp.Attr.attribStat(Attr.java:736)
>     at 
> org.netbeans.api.java.source.TreeUtilities.attributeTree(TreeUtilities.java:878)
>     at 
> org.netbeans.api.java.source.TreeUtilities.attributeTree(TreeUtilities.java:808)
>     at 
> org.netbeans.modules.editor.java.JavaCodeTemplateProcessor.type(JavaCodeTemplateProcessor.java:716)
>     at 
> org.netbeans.modules.editor.java.JavaCodeTemplateProcessor.getProposedValue(JavaCodeTemplateProcessor.java:431)
>     at 
> org.netbeans.modules.editor.java.JavaCodeTemplateProcessor.updateDefaultValues(JavaCodeTemplateProcessor.java:143)
>     at 
> org.netbeans.lib.editor.codetemplates.CodeTemplateInsertHandler.processTemplate(CodeTemplateInsertHandler.java:225)
>     at 
> org.netbeans.lib.editor.codetemplates.CodeTemplateManagerOperation.insert(CodeTemplateManagerOperation.java:273)
>     at 
> org.netbeans.lib.editor.codetemplates.api.CodeTemplate.insert(CodeTemplate.java:82)
>     at 
> org.netbeans.modules.editor.java.JavaCompletionItem.process(JavaCompletionItem.java:566)
>     at 
> org.netbeans.modules.editor.java.JavaCompletionItem.defaultAction(JavaCompletionItem.java:286)
>     at 
> org.netbeans.modules.editor.completion.CompletionImpl.dispatchKeyEvent(CompletionImpl.java:785)
>     at 
> org.netbeans.modules.editor.completion.CompletionImpl.keyPressed(CompletionImpl.java:386)
>     at 
> java.desktop/java.awt.AWTEventMulticaster.keyPressed(AWTEventMulticaster.java:258)
>     at 
> java.desktop/java.awt.AWTEventMulticaster.keyPressed(AWTEventMulticaster.java:257)
>     at 
> java.desktop/java.awt.AWTEventMulticaster.keyPressed(AWTEventMulticaster.java:257)
>     at java.desktop/java.awt.Component.processKeyEvent(Component.java:6547)
>     at 
> java.desktop/javax.swing.JComponent.processKeyEvent(JComponent.java:2849)
>     at java.desktop/java.awt.Component.processEvent(Component.java:6366)
>     at java.desktop/java.awt.Container.processEvent(Container.java:2261)
>     at java.desktop/java.awt.Component.dispatchEventImpl(Component.java:4966)
>     at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2319)
>     at java.desktop/java.awt.Component.dispatchEvent(Component.java:4798)
>     at 
> java.desktop/java.awt.KeyboardFocusManager.redispatchEvent(KeyboardFocusManager.java:1950)
>     at 
> java.desktop/java.awt.DefaultKeyboardFocusManager.dispatchKeyEvent(DefaultKeyboardFocusManager.java:871)
>     at 
> java.desktop/java.awt.DefaultKeyboardFocusManager.preDispatchKeyEvent(DefaultKeyboardFocusManager.java:1140)
>     at 
> java.desktop/java.awt.DefaultKeyboardFocusManager.typeAheadAssertions(DefaultKeyboardFocusManager.java:1010)
>

[jira] [Created] (NETBEANS-2094) AssertionError while typing before an annotation in anonymous inner class

2019-02-07 Thread Austin Stephens (JIRA)
Austin Stephens created NETBEANS-2094:
-

 Summary: AssertionError while typing before an annotation in 
anonymous inner class
 Key: NETBEANS-2094
 URL: https://issues.apache.org/jira/browse/NETBEANS-2094
 Project: NetBeans
  Issue Type: Bug
  Components: java - Source
Affects Versions: 10.0
Reporter: Austin Stephens


Paste the following into a code file:

 
{code:java}
    public static InputStream foo(InputStream from){
    return new InputStream() {
            MemoryStream ms = new MemoryStream();
            GZIPOutputStream compress = new 
GZIPOutputStream(ms.getOutputStream());
            
            @Override
            public int read() throws IOException {
                throw new UnsupportedOperationException("Not supported yet."); 
//To change body of generated methods, choose Tools | Templates.
            }
        }
    }
{code}
and try to type "byte[] buffer" above the Override Annotation. An assertion 
error will be thrown with the stack trace of:

 
{noformat}
Assert.error:155    
Assert.checkNonNull:62    
Annotate.fromAnnotations:167    
Annotate.lambda$annotateTypeSecondStage$5:1031    
861978341.run    
Annotate.flush:194    
Annotate.unblockAnnotations:144    
TypeEnter.complete:229    
Symbol.complete:645    
Symbol$ClassSymbol.complete:1352    
Attr.visitClassDef:982    
NBAttr.visitClassDef:61    
JCTree$JCClassDecl.accept:778    
Attr.attribTree:673    
Attr.attribStat:749    
Attr.visitAnonymousClassDefinition:2508    
Attr.visitNewClass:2391    
JCTree$JCNewClass.accept:1695    
Attr.attribTree:673    
Attr.visitReturn:1931    
JCTree$JCReturn.accept:1552    
Attr.attribTree:673    
Attr.attribStat:749    
Attr.attribStats:773    
Attr.visitBlock:1350    
NBAttr.visitBlock:73    
JCTree$JCBlock.accept:1026    
Attr.attribTree:673    
Attr.attribStat:749     
JavacParser.parseImpl:399    
JavacParser.parse:332    
TaskProcessor.callParse:598    
SourceCache.getResult:228    
ResultIterator.getParserResult:115    
ResultIterator.getParserResult:129   
TaskProcessor.callUserTask:586    
ParserManager$UserTaskAction.run:130    
ParserManager$UserTaskAction.run:114    
TaskProcessor$2.call:181    
TaskProcessor$2.call:178    
FileChangedManager.priorityIO:153    
ProvidedExtensions.priorityIO:335    
DataObjectEnvFactory.runPriorityIO:118    
Utilities.runPriorityIO:67    
TaskProcessor.runUserTask:178    
ParserManager.parse:81    
JPACodeCompletionProvider$JPACodeCompletionQuery.query:118    
AsyncCompletionTask.run:198    
RequestProcessor$Task.run:1418    
GlobalLookup.execute:45    
Lookups.executeWith:278    
RequestProcessor$Processor.run:2033   {noformat}
 



--
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-2094) AssertionError while typing before an annotation in anonymous inner class

2019-02-07 Thread Austin Stephens (JIRA)


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

Austin Stephens updated NETBEANS-2094:
--
Description: 
Paste the following into a code file:
{code:java}
    public static InputStream foo(InputStream from){
    return new InputStream() {
            MemoryStream ms = new MemoryStream();
            GZIPOutputStream compress = new 
GZIPOutputStream(ms.getOutputStream());
            
            @Override
            public int read() throws IOException {
                throw new UnsupportedOperationException("Not supported yet."); 
//To change body of generated methods, choose Tools | Templates.
            }
        }
    }
{code}
and try to type "byte[] buffer" above the Override Annotation. An assertion 
error will be thrown with the stack trace of:
{noformat}
Assert.error:155    
Assert.checkNonNull:62    
Annotate.fromAnnotations:167    
Annotate.lambda$annotateTypeSecondStage$5:1031    
861978341.run    
Annotate.flush:194    
Annotate.unblockAnnotations:144    
TypeEnter.complete:229    
Symbol.complete:645    
Symbol$ClassSymbol.complete:1352    
Attr.visitClassDef:982    
NBAttr.visitClassDef:61    
JCTree$JCClassDecl.accept:778    
Attr.attribTree:673    
Attr.attribStat:749    
Attr.visitAnonymousClassDefinition:2508    
Attr.visitNewClass:2391    
JCTree$JCNewClass.accept:1695    
Attr.attribTree:673    
Attr.visitReturn:1931    
JCTree$JCReturn.accept:1552    
Attr.attribTree:673    
Attr.attribStat:749    
Attr.attribStats:773    
Attr.visitBlock:1350    
NBAttr.visitBlock:73    
JCTree$JCBlock.accept:1026    
Attr.attribTree:673    
Attr.attribStat:749     
JavacParser.parseImpl:399    
JavacParser.parse:332    
TaskProcessor.callParse:598    
SourceCache.getResult:228    
ResultIterator.getParserResult:115    
ResultIterator.getParserResult:129   
TaskProcessor.callUserTask:586    
ParserManager$UserTaskAction.run:130    
ParserManager$UserTaskAction.run:114    
TaskProcessor$2.call:181    
TaskProcessor$2.call:178    
FileChangedManager.priorityIO:153    
ProvidedExtensions.priorityIO:335    
DataObjectEnvFactory.runPriorityIO:118    
Utilities.runPriorityIO:67    
TaskProcessor.runUserTask:178    
ParserManager.parse:81    
JPACodeCompletionProvider$JPACodeCompletionQuery.query:118    
AsyncCompletionTask.run:198    
RequestProcessor$Task.run:1418    
GlobalLookup.execute:45    
Lookups.executeWith:278    
RequestProcessor$Processor.run:2033   {noformat}
 It will also explode with a NullPointer if you try to add a variable before 
"MemoryStream"

  was:
Paste the following into a code file:

 
{code:java}
    public static InputStream foo(InputStream from){
    return new InputStream() {
            MemoryStream ms = new MemoryStream();
            GZIPOutputStream compress = new 
GZIPOutputStream(ms.getOutputStream());
            
            @Override
            public int read() throws IOException {
                throw new UnsupportedOperationException("Not supported yet."); 
//To change body of generated methods, choose Tools | Templates.
            }
        }
    }
{code}
and try to type "byte[] buffer" above the Override Annotation. An assertion 
error will be thrown with the stack trace of:

 
{noformat}
Assert.error:155    
Assert.checkNonNull:62    
Annotate.fromAnnotations:167    
Annotate.lambda$annotateTypeSecondStage$5:1031    
861978341.run    
Annotate.flush:194    
Annotate.unblockAnnotations:144    
TypeEnter.complete:229    
Symbol.complete:645    
Symbol$ClassSymbol.complete:1352    
Attr.visitClassDef:982    
NBAttr.visitClassDef:61    
JCTree$JCClassDecl.accept:778    
Attr.attribTree:673    
Attr.attribStat:749    
Attr.visitAnonymousClassDefinition:2508    
Attr.visitNewClass:2391    
JCTree$JCNewClass.accept:1695    
Attr.attribTree:673    
Attr.visitReturn:1931    
JCTree$JCReturn.accept:1552    
Attr.attribTree:673    
Attr.attribStat:749    
Attr.attribStats:773    
Attr.visitBlock:1350    
NBAttr.visitBlock:73    
JCTree$JCBlock.accept:1026    
Attr.attribTree:673    
Attr.attribStat:749     
JavacParser.parseImpl:399    
JavacParser.parse:332    
TaskProcessor.callParse:598    
SourceCache.getResult:228    
ResultIterator.getParserResult:115    
ResultIterator.getParserResult:129   
TaskProcessor.callUserTask:586    
ParserManager$UserTaskAction.run:130    
ParserManager$UserTaskAction.run:114    
TaskProcessor$2.call:181    
TaskProcessor$2.call:178    
FileChangedManager.priorityIO:153    
ProvidedExtensions.priorityIO:335    
DataObjectEnvFactory.runPriorityIO:118    
Utilities.runPriorityIO:67    
TaskProcessor.runUserTask:178    
ParserManager.parse:81    
JPACodeCompletionProvider$JPACodeCompletionQuery.query:118    
AsyncCompletionTask.run:198    
RequestProcessor$Task.run:1418    
GlobalLookup.execute:45    
Lookups.executeWith:278    
RequestProcessor$Processor.run:2033   {noformat}
 


> AssertionError whi

[jira] [Updated] (NETBEANS-2094) AssertionError while typing before an annotation in anonymous inner class

2019-02-07 Thread Austin Stephens (JIRA)


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

Austin Stephens updated NETBEANS-2094:
--
Description: 
Paste the following into a code file:
{code:java}
    public static InputStream foo(InputStream from){
    return new InputStream() {
            MemoryStream ms = new MemoryStream();
            GZIPOutputStream compress = new 
GZIPOutputStream(ms.getOutputStream());
            
            @Override
            public int read() throws IOException {
                throw new UnsupportedOperationException("Not supported yet."); 
//To change body of generated methods, choose Tools | Templates.
            }
        }
    }
{code}
and try to type "byte[] buffer" above the Override Annotation. An assertion 
error will be thrown with the stack trace of:
{noformat}
Assert.error:155    
Assert.checkNonNull:62    
Annotate.fromAnnotations:167    
Annotate.lambda$annotateTypeSecondStage$5:1031    
861978341.run    
Annotate.flush:194    
Annotate.unblockAnnotations:144    
TypeEnter.complete:229    
Symbol.complete:645    
Symbol$ClassSymbol.complete:1352    
Attr.visitClassDef:982    
NBAttr.visitClassDef:61    
JCTree$JCClassDecl.accept:778    
Attr.attribTree:673    
Attr.attribStat:749    
Attr.visitAnonymousClassDefinition:2508    
Attr.visitNewClass:2391    
JCTree$JCNewClass.accept:1695    
Attr.attribTree:673    
Attr.visitReturn:1931    
JCTree$JCReturn.accept:1552    
Attr.attribTree:673    
Attr.attribStat:749    
Attr.attribStats:773    
Attr.visitBlock:1350    
NBAttr.visitBlock:73    
JCTree$JCBlock.accept:1026    
Attr.attribTree:673    
Attr.attribStat:749     
JavacParser.parseImpl:399    
JavacParser.parse:332    
TaskProcessor.callParse:598    
SourceCache.getResult:228    
ResultIterator.getParserResult:115    
ResultIterator.getParserResult:129   
TaskProcessor.callUserTask:586    
ParserManager$UserTaskAction.run:130    
ParserManager$UserTaskAction.run:114    
TaskProcessor$2.call:181    
TaskProcessor$2.call:178    
FileChangedManager.priorityIO:153    
ProvidedExtensions.priorityIO:335    
DataObjectEnvFactory.runPriorityIO:118    
Utilities.runPriorityIO:67    
TaskProcessor.runUserTask:178    
ParserManager.parse:81    
JPACodeCompletionProvider$JPACodeCompletionQuery.query:118    
AsyncCompletionTask.run:198    
RequestProcessor$Task.run:1418    
GlobalLookup.execute:45    
Lookups.executeWith:278    
RequestProcessor$Processor.run:2033   {noformat}
 It will also explode with a NullPointer if you try to add a variable before 
"MemoryStream" (e.g. "byte[] buffer =")

  was:
Paste the following into a code file:
{code:java}
    public static InputStream foo(InputStream from){
    return new InputStream() {
            MemoryStream ms = new MemoryStream();
            GZIPOutputStream compress = new 
GZIPOutputStream(ms.getOutputStream());
            
            @Override
            public int read() throws IOException {
                throw new UnsupportedOperationException("Not supported yet."); 
//To change body of generated methods, choose Tools | Templates.
            }
        }
    }
{code}
and try to type "byte[] buffer" above the Override Annotation. An assertion 
error will be thrown with the stack trace of:
{noformat}
Assert.error:155    
Assert.checkNonNull:62    
Annotate.fromAnnotations:167    
Annotate.lambda$annotateTypeSecondStage$5:1031    
861978341.run    
Annotate.flush:194    
Annotate.unblockAnnotations:144    
TypeEnter.complete:229    
Symbol.complete:645    
Symbol$ClassSymbol.complete:1352    
Attr.visitClassDef:982    
NBAttr.visitClassDef:61    
JCTree$JCClassDecl.accept:778    
Attr.attribTree:673    
Attr.attribStat:749    
Attr.visitAnonymousClassDefinition:2508    
Attr.visitNewClass:2391    
JCTree$JCNewClass.accept:1695    
Attr.attribTree:673    
Attr.visitReturn:1931    
JCTree$JCReturn.accept:1552    
Attr.attribTree:673    
Attr.attribStat:749    
Attr.attribStats:773    
Attr.visitBlock:1350    
NBAttr.visitBlock:73    
JCTree$JCBlock.accept:1026    
Attr.attribTree:673    
Attr.attribStat:749     
JavacParser.parseImpl:399    
JavacParser.parse:332    
TaskProcessor.callParse:598    
SourceCache.getResult:228    
ResultIterator.getParserResult:115    
ResultIterator.getParserResult:129   
TaskProcessor.callUserTask:586    
ParserManager$UserTaskAction.run:130    
ParserManager$UserTaskAction.run:114    
TaskProcessor$2.call:181    
TaskProcessor$2.call:178    
FileChangedManager.priorityIO:153    
ProvidedExtensions.priorityIO:335    
DataObjectEnvFactory.runPriorityIO:118    
Utilities.runPriorityIO:67    
TaskProcessor.runUserTask:178    
ParserManager.parse:81    
JPACodeCompletionProvider$JPACodeCompletionQuery.query:118    
AsyncCompletionTask.run:198    
RequestProcessor$Task.run:1418    
GlobalLookup.execute:45    
Lookups.executeWith:278    
RequestProcessor$Processor.run:2033   {noformat}
 It w

[jira] [Commented] (NETBEANS-2094) AssertionError while typing before an annotation in anonymous inner class

2019-02-11 Thread Austin Stephens (JIRA)


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

Austin Stephens commented on NETBEANS-2094:
---

Promoting to critical since it makes writing anonymous inner classes a pain if 
it has an override (which, unless I am wrong, is almost always).

> AssertionError while typing before an annotation in anonymous inner class
> -
>
> Key: NETBEANS-2094
> URL: https://issues.apache.org/jira/browse/NETBEANS-2094
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Source
>Affects Versions: 10.0
>Reporter: Austin Stephens
>Priority: Major
>
> Paste the following into a code file:
> {code:java}
>     public static InputStream foo(InputStream from){
>     return new InputStream() {
>             MemoryStream ms = new MemoryStream();
>             GZIPOutputStream compress = new 
> GZIPOutputStream(ms.getOutputStream());
>             
>             @Override
>             public int read() throws IOException {
>                 throw new UnsupportedOperationException("Not supported 
> yet."); //To change body of generated methods, choose Tools | Templates.
>             }
>         }
>     }
> {code}
> and try to type "byte[] buffer" above the Override Annotation. An assertion 
> error will be thrown with the stack trace of:
> {noformat}
> Assert.error:155    
> Assert.checkNonNull:62    
> Annotate.fromAnnotations:167    
> Annotate.lambda$annotateTypeSecondStage$5:1031    
> 861978341.run    
> Annotate.flush:194    
> Annotate.unblockAnnotations:144    
> TypeEnter.complete:229    
> Symbol.complete:645    
> Symbol$ClassSymbol.complete:1352    
> Attr.visitClassDef:982    
> NBAttr.visitClassDef:61    
> JCTree$JCClassDecl.accept:778    
> Attr.attribTree:673    
> Attr.attribStat:749    
> Attr.visitAnonymousClassDefinition:2508    
> Attr.visitNewClass:2391    
> JCTree$JCNewClass.accept:1695    
> Attr.attribTree:673    
> Attr.visitReturn:1931    
> JCTree$JCReturn.accept:1552    
> Attr.attribTree:673    
> Attr.attribStat:749    
> Attr.attribStats:773    
> Attr.visitBlock:1350    
> NBAttr.visitBlock:73    
> JCTree$JCBlock.accept:1026    
> Attr.attribTree:673    
> Attr.attribStat:749     
> JavacParser.parseImpl:399    
> JavacParser.parse:332    
> TaskProcessor.callParse:598    
> SourceCache.getResult:228    
> ResultIterator.getParserResult:115    
> ResultIterator.getParserResult:129   
> TaskProcessor.callUserTask:586    
> ParserManager$UserTaskAction.run:130    
> ParserManager$UserTaskAction.run:114    
> TaskProcessor$2.call:181    
> TaskProcessor$2.call:178    
> FileChangedManager.priorityIO:153    
> ProvidedExtensions.priorityIO:335    
> DataObjectEnvFactory.runPriorityIO:118    
> Utilities.runPriorityIO:67    
> TaskProcessor.runUserTask:178    
> ParserManager.parse:81    
> JPACodeCompletionProvider$JPACodeCompletionQuery.query:118    
> AsyncCompletionTask.run:198    
> RequestProcessor$Task.run:1418    
> GlobalLookup.execute:45    
> Lookups.executeWith:278    
> RequestProcessor$Processor.run:2033   {noformat}
>  It will also explode with a NullPointer if you try to add a variable before 
> "MemoryStream" (e.g. "byte[] buffer =")



--
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-2094) AssertionError while typing before an annotation in anonymous inner class

2019-02-11 Thread Austin Stephens (JIRA)


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

Austin Stephens updated NETBEANS-2094:
--
Priority: Critical  (was: Major)

> AssertionError while typing before an annotation in anonymous inner class
> -
>
> Key: NETBEANS-2094
> URL: https://issues.apache.org/jira/browse/NETBEANS-2094
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Source
>Affects Versions: 10.0
>Reporter: Austin Stephens
>Priority: Critical
>
> Paste the following into a code file:
> {code:java}
>     public static InputStream foo(InputStream from){
>     return new InputStream() {
>             MemoryStream ms = new MemoryStream();
>             GZIPOutputStream compress = new 
> GZIPOutputStream(ms.getOutputStream());
>             
>             @Override
>             public int read() throws IOException {
>                 throw new UnsupportedOperationException("Not supported 
> yet."); //To change body of generated methods, choose Tools | Templates.
>             }
>         }
>     }
> {code}
> and try to type "byte[] buffer" above the Override Annotation. An assertion 
> error will be thrown with the stack trace of:
> {noformat}
> Assert.error:155    
> Assert.checkNonNull:62    
> Annotate.fromAnnotations:167    
> Annotate.lambda$annotateTypeSecondStage$5:1031    
> 861978341.run    
> Annotate.flush:194    
> Annotate.unblockAnnotations:144    
> TypeEnter.complete:229    
> Symbol.complete:645    
> Symbol$ClassSymbol.complete:1352    
> Attr.visitClassDef:982    
> NBAttr.visitClassDef:61    
> JCTree$JCClassDecl.accept:778    
> Attr.attribTree:673    
> Attr.attribStat:749    
> Attr.visitAnonymousClassDefinition:2508    
> Attr.visitNewClass:2391    
> JCTree$JCNewClass.accept:1695    
> Attr.attribTree:673    
> Attr.visitReturn:1931    
> JCTree$JCReturn.accept:1552    
> Attr.attribTree:673    
> Attr.attribStat:749    
> Attr.attribStats:773    
> Attr.visitBlock:1350    
> NBAttr.visitBlock:73    
> JCTree$JCBlock.accept:1026    
> Attr.attribTree:673    
> Attr.attribStat:749     
> JavacParser.parseImpl:399    
> JavacParser.parse:332    
> TaskProcessor.callParse:598    
> SourceCache.getResult:228    
> ResultIterator.getParserResult:115    
> ResultIterator.getParserResult:129   
> TaskProcessor.callUserTask:586    
> ParserManager$UserTaskAction.run:130    
> ParserManager$UserTaskAction.run:114    
> TaskProcessor$2.call:181    
> TaskProcessor$2.call:178    
> FileChangedManager.priorityIO:153    
> ProvidedExtensions.priorityIO:335    
> DataObjectEnvFactory.runPriorityIO:118    
> Utilities.runPriorityIO:67    
> TaskProcessor.runUserTask:178    
> ParserManager.parse:81    
> JPACodeCompletionProvider$JPACodeCompletionQuery.query:118    
> AsyncCompletionTask.run:198    
> RequestProcessor$Task.run:1418    
> GlobalLookup.execute:45    
> Lookups.executeWith:278    
> RequestProcessor$Processor.run:2033   {noformat}
>  It will also explode with a NullPointer if you try to add a variable before 
> "MemoryStream" (e.g. "byte[] buffer =")



--
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-320) Mac modal dialogs pop-under non-modal dialogs

2019-05-20 Thread Austin Stephens (JIRA)


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

Austin Stephens updated NETBEANS-320:
-
Affects Version/s: 11.0

> Mac modal dialogs pop-under non-modal dialogs
> -
>
> Key: NETBEANS-320
> URL: https://issues.apache.org/jira/browse/NETBEANS-320
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - Window System
>Affects Versions: 8.2, 9.0, 11.0
> Environment: Mac OS
>Reporter: Austin Stephens
>Assignee: Austin Stephens
>Priority: Major
>  Labels: mac-os-x, pull-request-available
> Attachments: Screen Shot 2018-01-23 at 1.28.20 PM.png, Screen Shot 
> 2018-01-26 at 11.37.55 AM.png
>
>  Time Spent: 5h
>  Remaining Estimate: 0h
>
> It is very annoying to users. One easy way to reproduce this is to find a 
> module with a wrapped jar and then go to (Right 
> click)>Properties>Libraries>Wrapped JARs and select a wrapped jar. Then click 
> "Edit...". If your Mac is more severely affected, the "Edit Jar Reference" 
> dialog will pop-under the Project Properties, if you Mac is less severly 
> affected, then clicking on the Project Properties window while the "Edit Jar 
> Reference" dialog is open will cause the Project Properties window to hide 
> the dialog.



--
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-530) No Bind option on the popup to create Bindings

2019-05-20 Thread Austin Stephens (JIRA)


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

Austin Stephens updated NETBEANS-530:
-
Affects Version/s: 11.0

> No Bind option on the popup to create Bindings 
> ---
>
> Key: NETBEANS-530
> URL: https://issues.apache.org/jira/browse/NETBEANS-530
> Project: NetBeans
>  Issue Type: Bug
>  Components: ide - Code
>Affects Versions: 9.0, 11.0
> Environment: Window 8.1, MacOs 10.11.6
>Reporter: efrem mccrimon
>Priority: Major
> Attachments: Screenshot from 2018-08-02 21-18-53.png, 
> no_bind_popup_item.JPG
>
>
> Trying to create bindings, created a textfield and Slider to demonstrate and 
> test basic bean binding.  From the Design view, I wanted to bind the slider 
> to the text field.
> Right-click the text field component and wanted to choose Bind.  There is not 
> Bind option on the popup menu.  It is not present in build #375, or #378.  It 
> is on NB 8.2 and NB 8.02.



--
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-1937) Import on code paste error

2019-01-15 Thread Austin Stephens (JIRA)
Austin Stephens created NETBEANS-1937:
-

 Summary: Import on code paste error
 Key: NETBEANS-1937
 URL: https://issues.apache.org/jira/browse/NETBEANS-1937
 Project: NetBeans
  Issue Type: Bug
  Components: java - Source
Affects Versions: 10.0
 Environment: Mac
JDK 10
Reporter: Austin Stephens


Create a class file named "IterableUtil.java" and paste the following into the 
class:

 
{code:java}
    @Deprecated
    public static  Iterable cast(final Iterable source){
    return () -> new Iterator() {
            final Iterator iterator = source.iterator();
            @Override
            public boolean hasNext() {
                return iterator.hasNext();
            }
            
            @Override
            @SuppressWarnings("unchecked")
            public T next() {
                return (T)iterator.next();
            }

            @Override
            public void remove() {
                iterator.remove();
            }
        };
    }

    public static  ListIterator cast(final ListIterator source,
    final Class clazz){
    return new ListIterator() {

    @Override
    public boolean hasNext() {
    return source.hasNext();
    }

    @Override
    @SuppressWarnings("unchecked")
    public T next() {
    return (T)source.next();
    }

    @Override
    public boolean hasPrevious() {
    return source.hasPrevious();
    }

    @Override
    @SuppressWarnings("unchecked")
    public T previous() {
    return (T)source.previous();
    }

    @Override
    public int nextIndex() {
    return source.nextIndex();
    }

    @Override
    public int previousIndex() {
    return source.nextIndex();
    }

    @Override
    public void remove() {
    source.remove();
    }

    @Override
    public void set(T e) {
    source.set(clazz.cast(e));
    }

    @Override
    public void add(T e) {
    source.add(clazz.cast(e));
    }
    };
    }
    
    /**
     *
     * @param 
     * @param collection
     * @return
     * @deprecated Does not truly do the conversion.
     */
    @Deprecated
    public static  Iterable enumerationToIterable(final Enumeration 
collection){
    return () -> enumerationToIterator(collection);
    }

    public static  Iterator enumerationToIterator(
            final Enumeration collection) {
        return new Iterator() {

            @Override
            public boolean hasNext() {
                return collection.hasMoreElements();
            }

            @Override
            public T next() {
                return collection.nextElement();
            }

            @Override
            public void remove() {
                throw new UnsupportedOperationException("Not supported."); //To 
change body of generated methods, choose Tools | Templates.
            }
        };
    }
{code}
The IDE will ask if you would like it to resolve imports. Click "ok". The 
resulting code will now have `return new IteratorIterator(){` and `return 
new ListIteratorListIterator() {`, which is 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] [Commented] (NETBEANS-1937) Import on code paste error

2019-01-15 Thread Austin Stephens (JIRA)


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

Austin Stephens commented on NETBEANS-1937:
---

For reference, it also appears that nb-javac is not installed. Netbeans seems 
to be unable to download it.

> Import on code paste error
> --
>
> Key: NETBEANS-1937
> URL: https://issues.apache.org/jira/browse/NETBEANS-1937
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Source
>Affects Versions: 10.0
> Environment: Mac
> JDK 10
>Reporter: Austin Stephens
>Priority: Major
>
> Create a class file named "IterableUtil.java" and paste the following into 
> the class:
>  
> {code:java}
>     @Deprecated
>     public static  Iterable cast(final Iterable source){
>     return () -> new Iterator() {
>             final Iterator iterator = source.iterator();
>             @Override
>             public boolean hasNext() {
>                 return iterator.hasNext();
>             }
>             
>             @Override
>             @SuppressWarnings("unchecked")
>             public T next() {
>                 return (T)iterator.next();
>             }
>             @Override
>             public void remove() {
>                 iterator.remove();
>             }
>         };
>     }
>     public static  ListIterator cast(final ListIterator source,
>     final Class clazz){
>     return new ListIterator() {
>     @Override
>     public boolean hasNext() {
>     return source.hasNext();
>     }
>     @Override
>     @SuppressWarnings("unchecked")
>     public T next() {
>     return (T)source.next();
>     }
>     @Override
>     public boolean hasPrevious() {
>     return source.hasPrevious();
>     }
>     @Override
>     @SuppressWarnings("unchecked")
>     public T previous() {
>     return (T)source.previous();
>     }
>     @Override
>     public int nextIndex() {
>     return source.nextIndex();
>     }
>     @Override
>     public int previousIndex() {
>     return source.nextIndex();
>     }
>     @Override
>     public void remove() {
>     source.remove();
>     }
>     @Override
>     public void set(T e) {
>     source.set(clazz.cast(e));
>     }
>     @Override
>     public void add(T e) {
>     source.add(clazz.cast(e));
>     }
>     };
>     }
>     
>     /**
>      *
>      * @param 
>      * @param collection
>      * @return
>      * @deprecated Does not truly do the conversion.
>      */
>     @Deprecated
>     public static  Iterable enumerationToIterable(final Enumeration 
> collection){
>     return () -> enumerationToIterator(collection);
>     }
>     public static  Iterator enumerationToIterator(
>             final Enumeration collection) {
>         return new Iterator() {
>             @Override
>             public boolean hasNext() {
>                 return collection.hasMoreElements();
>             }
>             @Override
>             public T next() {
>                 return collection.nextElement();
>             }
>             @Override
>             public void remove() {
>                 throw new UnsupportedOperationException("Not supported."); 
> //To change body of generated methods, choose Tools | Templates.
>             }
>         };
>     }
> {code}
> The IDE will ask if you would like it to resolve imports. Click "ok". The 
> resulting code will now have `return new IteratorIterator(){` and `return 
> new ListIteratorListIterator() {`, which is 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-1949) AssertionError in DeferredAttr$2$1.setOverloadKind (Java parsing)

2019-01-17 Thread Austin Stephens (JIRA)
Austin Stephens created NETBEANS-1949:
-

 Summary: AssertionError in DeferredAttr$2$1.setOverloadKind (Java 
parsing)
 Key: NETBEANS-1949
 URL: https://issues.apache.org/jira/browse/NETBEANS-1949
 Project: NetBeans
  Issue Type: Bug
  Components: java - Source
Affects Versions: 10.0
Reporter: Austin Stephens
 Attachments: SlayBugs.java

The parser explodes when trying to parse the attached code file. Here is the 
stack trace:
{noformat}
"Editor Parsing Loop (incubator-netbeans-release-380-on-20181217)"
    at com.sun.tools.javac.util.Assert.error(Assert.java:155)
    at com.sun.tools.javac.util.Assert.check(Assert.java:46)
    at 
com.sun.tools.javac.comp.DeferredAttr$2$1.setOverloadKind(DeferredAttr.java:177)
    at 
com.sun.tools.javac.comp.ArgumentAttr.visitReference(ArgumentAttr.java:283)
    at 
com.sun.tools.javac.tree.JCTree$JCMemberReference.accept(JCTree.java:2196)
    at com.sun.tools.javac.comp.ArgumentAttr.attribArg(ArgumentAttr.java:197)
    at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:671)
    at com.sun.tools.javac.comp.Attr.attribArgs(Attr.java:782)
    at com.sun.tools.javac.comp.Attr.visitApply(Attr.java:2062)
    at 
com.sun.tools.javac.tree.JCTree$JCMethodInvocation.accept(JCTree.java:1640)
    at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:673)
    at com.sun.tools.javac.comp.Attr.visitSelect(Attr.java:3826)
    at com.sun.tools.javac.tree.JCTree$JCFieldAccess.accept(JCTree.java:2116)
    at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:673)
    at com.sun.tools.javac.comp.Attr.visitApply(Attr.java:2079)
    at 
com.sun.tools.javac.tree.JCTree$JCMethodInvocation.accept(JCTree.java:1640)
    at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:673)
    at 
com.sun.tools.javac.comp.DeferredAttr.attribSpeculative(DeferredAttr.java:505)
    at 
com.sun.tools.javac.comp.DeferredAttr.attribSpeculative(DeferredAttr.java:486)
    at 
com.sun.tools.javac.comp.ArgumentAttr.lambda$processArg$0(ArgumentAttr.java:220)
    at com.sun.tools.javac.comp.ArgumentAttr$$Lambda$668.334963799.get
    at com.sun.tools.javac.comp.ArgumentAttr.processArg(ArgumentAttr.java:242)
    at com.sun.tools.javac.comp.ArgumentAttr.processArg(ArgumentAttr.java:219)
    at com.sun.tools.javac.comp.ArgumentAttr.visitApply(ArgumentAttr.java:307)
    at 
com.sun.tools.javac.tree.JCTree$JCMethodInvocation.accept(JCTree.java:1640)
    at com.sun.tools.javac.comp.ArgumentAttr.attribArg(ArgumentAttr.java:197)
    at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:671)
    at com.sun.tools.javac.comp.Attr.attribArgs(Attr.java:782)
    at com.sun.tools.javac.comp.Attr.visitApply(Attr.java:2062)
    at 
com.sun.tools.javac.tree.JCTree$JCMethodInvocation.accept(JCTree.java:1640)
    at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:673)
    at com.sun.tools.javac.comp.Attr.visitReturn(Attr.java:1931)
    at com.sun.tools.javac.tree.JCTree$JCReturn.accept(JCTree.java:1552)
    at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:673)
    at com.sun.tools.javac.comp.Attr.attribStat(Attr.java:749)
    at com.sun.tools.javac.comp.Attr.attribStats(Attr.java:773)
    at com.sun.tools.javac.comp.Attr.visitLambda(Attr.java:2751)
    at com.sun.tools.javac.tree.JCTree$JCLambda.accept(JCTree.java:1813)
    at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:673)
    at com.sun.tools.javac.comp.DeferredAttr$4.complete(DeferredAttr.java:379)
    at 
com.sun.tools.javac.comp.DeferredAttr$DeferredType.check(DeferredAttr.java:340)
    at 
com.sun.tools.javac.comp.DeferredAttr$DeferredType.check(DeferredAttr.java:326)
    at 
com.sun.tools.javac.comp.Resolve$MethodResultInfo.check(Resolve.java:1062)
    at com.sun.tools.javac.comp.Resolve$4.checkArg(Resolve.java:889)
    at 
com.sun.tools.javac.comp.Resolve$AbstractMethodCheck.argumentsAcceptable(Resolve.java:777)
    at com.sun.tools.javac.comp.Resolve$4.argumentsAcceptable(Resolve.java:898)
    at com.sun.tools.javac.comp.Resolve.rawInstantiate(Resolve.java:620)
    at com.sun.tools.javac.comp.Resolve.checkMethod(Resolve.java:646)
    at com.sun.tools.javac.comp.Attr.checkMethod(Attr.java:4378)
    at com.sun.tools.javac.comp.Attr.checkIdInternal(Attr.java:4166)
    at com.sun.tools.javac.comp.Attr.checkMethodIdInternal(Attr.java:4067)
    at com.sun.tools.javac.comp.Attr.checkId(Attr.java:4056)
    at com.sun.tools.javac.comp.Attr.visitSelect(Attr.java:3949)
    at com.sun.tools.javac.tree.JCTree$JCFieldAccess.accept(JCTree.java:2116)
    at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:673)
    at com.sun.tools.javac.comp.Attr.visitApply(Attr.java:2079)
    at 
com.sun.tools.javac.tree.JCTree$JCMethodInvocation.accept(JCTree.java:1640)
    at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:673)
    at com.sun.tools.javac.comp.Attr.visitTypeCast(Attr.java:3689)
    at com.sun.tools.javac.tree.JCTree$JCTypeCast.accept(JCTr

[jira] [Updated] (NETBEANS-1949) AssertionError in DeferredAttr$2$1.setOverloadKind (Java parsing)

2019-01-17 Thread Austin Stephens (JIRA)


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

Austin Stephens updated NETBEANS-1949:
--
Environment: jdk 10.0.2

> AssertionError in DeferredAttr$2$1.setOverloadKind (Java parsing)
> -
>
> Key: NETBEANS-1949
> URL: https://issues.apache.org/jira/browse/NETBEANS-1949
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Source
>Affects Versions: 10.0
> Environment: jdk 10.0.2
>Reporter: Austin Stephens
>Priority: Major
> Attachments: SlayBugs.java
>
>
> The parser explodes when trying to parse the attached code file. Here is the 
> stack trace:
> {noformat}
> "Editor Parsing Loop (incubator-netbeans-release-380-on-20181217)"
>     at com.sun.tools.javac.util.Assert.error(Assert.java:155)
>     at com.sun.tools.javac.util.Assert.check(Assert.java:46)
>     at 
> com.sun.tools.javac.comp.DeferredAttr$2$1.setOverloadKind(DeferredAttr.java:177)
>     at 
> com.sun.tools.javac.comp.ArgumentAttr.visitReference(ArgumentAttr.java:283)
>     at 
> com.sun.tools.javac.tree.JCTree$JCMemberReference.accept(JCTree.java:2196)
>     at com.sun.tools.javac.comp.ArgumentAttr.attribArg(ArgumentAttr.java:197)
>     at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:671)
>     at com.sun.tools.javac.comp.Attr.attribArgs(Attr.java:782)
>     at com.sun.tools.javac.comp.Attr.visitApply(Attr.java:2062)
>     at 
> com.sun.tools.javac.tree.JCTree$JCMethodInvocation.accept(JCTree.java:1640)
>     at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:673)
>     at com.sun.tools.javac.comp.Attr.visitSelect(Attr.java:3826)
>     at com.sun.tools.javac.tree.JCTree$JCFieldAccess.accept(JCTree.java:2116)
>     at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:673)
>     at com.sun.tools.javac.comp.Attr.visitApply(Attr.java:2079)
>     at 
> com.sun.tools.javac.tree.JCTree$JCMethodInvocation.accept(JCTree.java:1640)
>     at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:673)
>     at 
> com.sun.tools.javac.comp.DeferredAttr.attribSpeculative(DeferredAttr.java:505)
>     at 
> com.sun.tools.javac.comp.DeferredAttr.attribSpeculative(DeferredAttr.java:486)
>     at 
> com.sun.tools.javac.comp.ArgumentAttr.lambda$processArg$0(ArgumentAttr.java:220)
>     at com.sun.tools.javac.comp.ArgumentAttr$$Lambda$668.334963799.get
>     at com.sun.tools.javac.comp.ArgumentAttr.processArg(ArgumentAttr.java:242)
>     at com.sun.tools.javac.comp.ArgumentAttr.processArg(ArgumentAttr.java:219)
>     at com.sun.tools.javac.comp.ArgumentAttr.visitApply(ArgumentAttr.java:307)
>     at 
> com.sun.tools.javac.tree.JCTree$JCMethodInvocation.accept(JCTree.java:1640)
>     at com.sun.tools.javac.comp.ArgumentAttr.attribArg(ArgumentAttr.java:197)
>     at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:671)
>     at com.sun.tools.javac.comp.Attr.attribArgs(Attr.java:782)
>     at com.sun.tools.javac.comp.Attr.visitApply(Attr.java:2062)
>     at 
> com.sun.tools.javac.tree.JCTree$JCMethodInvocation.accept(JCTree.java:1640)
>     at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:673)
>     at com.sun.tools.javac.comp.Attr.visitReturn(Attr.java:1931)
>     at com.sun.tools.javac.tree.JCTree$JCReturn.accept(JCTree.java:1552)
>     at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:673)
>     at com.sun.tools.javac.comp.Attr.attribStat(Attr.java:749)
>     at com.sun.tools.javac.comp.Attr.attribStats(Attr.java:773)
>     at com.sun.tools.javac.comp.Attr.visitLambda(Attr.java:2751)
>     at com.sun.tools.javac.tree.JCTree$JCLambda.accept(JCTree.java:1813)
>     at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:673)
>     at com.sun.tools.javac.comp.DeferredAttr$4.complete(DeferredAttr.java:379)
>     at 
> com.sun.tools.javac.comp.DeferredAttr$DeferredType.check(DeferredAttr.java:340)
>     at 
> com.sun.tools.javac.comp.DeferredAttr$DeferredType.check(DeferredAttr.java:326)
>     at 
> com.sun.tools.javac.comp.Resolve$MethodResultInfo.check(Resolve.java:1062)
>     at com.sun.tools.javac.comp.Resolve$4.checkArg(Resolve.java:889)
>     at 
> com.sun.tools.javac.comp.Resolve$AbstractMethodCheck.argumentsAcceptable(Resolve.java:777)
>     at 
> com.sun.tools.javac.comp.Resolve$4.argumentsAcceptable(Resolve.java:898)
>     at com.sun.tools.javac.comp.Resolve.rawInstantiate(Resolve.java:620)
>     at com.sun.tools.javac.comp.Resolve.checkMethod(Resolve.java:646)
>     at com.sun.tools.javac.comp.Attr.checkMethod(Attr.java:4378)
>     at com.sun.tools.javac.comp.Attr.checkIdInternal(Attr.java:4166)
>     at com.sun.tools.javac.comp.Attr.checkMethodIdInternal(Attr.java:4067)
>     at com.sun.tools.javac.comp.Attr.checkId(Attr.java:4056)
>     at com.sun.tools.javac.comp.Attr.visitSelect(Attr.java:3949)
>     at com.sun.tools.javac.tree.JCTree$JCFieldAccess.

[jira] [Updated] (NETBEANS-1139) AssertionError in org.netbeans.modules.editor.java.JavaCodeTemplateProcessor.getProposedValue

2018-08-15 Thread Austin Stephens (JIRA)


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

Austin Stephens updated NETBEANS-1139:
--
Priority: Critical  (was: Major)

> AssertionError in 
> org.netbeans.modules.editor.java.JavaCodeTemplateProcessor.getProposedValue
> -
>
> Key: NETBEANS-1139
> URL: https://issues.apache.org/jira/browse/NETBEANS-1139
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Editor
>Affects Versions: 9.0, Next
>Reporter: Austin Stephens
>Priority: Critical
> Attachments: AutoCompleteBug1.java
>
>
> Attempting to Autocomplete the constructor after new in the attached file 
> throws an AssertionError.
> StackTrace:
> {noformat}
> java.lang.AssertionError
>     at com.sun.tools.javac.util.Assert.error(Assert.java:155)
>     at com.sun.tools.javac.util.Assert.check(Assert.java:46)
>     at com.sun.tools.javac.code.Scope$ScopeImpl.dble(Scope.java:410)
>     at com.sun.tools.javac.code.Scope$ScopeImpl.enter(Scope.java:433)
>     at com.sun.tools.javac.comp.MemberEnter.visitVarDef(MemberEnter.java:476)
>     at 
> com.sun.tools.javadoc.main.JavadocMemberEnter.visitVarDef(JavadocMemberEnter.java:83)
>     at 
> org.netbeans.lib.nbjavac.services.NBJavadocMemberEnter.visitVarDef(NBJavadocMemberEnter.java:92)
>     at com.sun.tools.javac.tree.JCTree$JCVariableDecl.accept(JCTree.java:962)
>     at com.sun.tools.javac.comp.MemberEnter.memberEnter(MemberEnter.java:171)
>     at com.sun.tools.javac.comp.Attr.visitVarDef(Attr.java:1171)
>     at com.sun.tools.javac.tree.JCTree$JCVariableDecl.accept(JCTree.java:962)
>     at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:660)
>     at com.sun.tools.javac.comp.Attr.attribStat(Attr.java:736)
>     at com.sun.tools.javac.comp.Attr.attribStats(Attr.java:760)
>     at com.sun.tools.javac.comp.Attr.visitBlock(Attr.java:1337)
>     at org.netbeans.lib.nbjavac.services.NBAttr.visitBlock(NBAttr.java:73)
>     at com.sun.tools.javac.tree.JCTree$JCBlock.accept(JCTree.java:1026)
>     at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:660)
>     at com.sun.tools.javac.comp.Attr.attribStat(Attr.java:736)
>     at 
> org.netbeans.api.java.source.TreeUtilities.attributeTree(TreeUtilities.java:878)
>     at 
> org.netbeans.api.java.source.TreeUtilities.attributeTree(TreeUtilities.java:808)
>     at 
> org.netbeans.modules.editor.java.JavaCodeTemplateProcessor.type(JavaCodeTemplateProcessor.java:716)
>     at 
> org.netbeans.modules.editor.java.JavaCodeTemplateProcessor.getProposedValue(JavaCodeTemplateProcessor.java:431)
>     at 
> org.netbeans.modules.editor.java.JavaCodeTemplateProcessor.updateDefaultValues(JavaCodeTemplateProcessor.java:143)
>     at 
> org.netbeans.lib.editor.codetemplates.CodeTemplateInsertHandler.processTemplate(CodeTemplateInsertHandler.java:225)
>     at 
> org.netbeans.lib.editor.codetemplates.CodeTemplateManagerOperation.insert(CodeTemplateManagerOperation.java:273)
>     at 
> org.netbeans.lib.editor.codetemplates.api.CodeTemplate.insert(CodeTemplate.java:82)
>     at 
> org.netbeans.modules.editor.java.JavaCompletionItem.process(JavaCompletionItem.java:566)
>     at 
> org.netbeans.modules.editor.java.JavaCompletionItem.defaultAction(JavaCompletionItem.java:286)
>     at 
> org.netbeans.modules.editor.completion.CompletionImpl.dispatchKeyEvent(CompletionImpl.java:785)
>     at 
> org.netbeans.modules.editor.completion.CompletionImpl.keyPressed(CompletionImpl.java:386)
>     at 
> java.desktop/java.awt.AWTEventMulticaster.keyPressed(AWTEventMulticaster.java:258)
>     at 
> java.desktop/java.awt.AWTEventMulticaster.keyPressed(AWTEventMulticaster.java:257)
>     at 
> java.desktop/java.awt.AWTEventMulticaster.keyPressed(AWTEventMulticaster.java:257)
>     at java.desktop/java.awt.Component.processKeyEvent(Component.java:6547)
>     at 
> java.desktop/javax.swing.JComponent.processKeyEvent(JComponent.java:2849)
>     at java.desktop/java.awt.Component.processEvent(Component.java:6366)
>     at java.desktop/java.awt.Container.processEvent(Container.java:2261)
>     at java.desktop/java.awt.Component.dispatchEventImpl(Component.java:4966)
>     at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2319)
>     at java.desktop/java.awt.Component.dispatchEvent(Component.java:4798)
>     at 
> java.desktop/java.awt.KeyboardFocusManager.redispatchEvent(KeyboardFocusManager.java:1950)
>     at 
> java.desktop/java.awt.DefaultKeyboardFocusManager.dispatchKeyEvent(DefaultKeyboardFocusManager.java:871)
>     at 
> java.desktop/java.awt.DefaultKeyboardFocusManager.preDispatchKeyEvent(DefaultKeyboardFocusManager.java:1140)
>     at 
> java.desktop/java.awt.DefaultKeyboardFocusManager.typeAheadAssertions(DefaultKeyboardFocusManager.java:1010)
>     at 
> ja

[jira] [Commented] (NETBEANS-1139) AssertionError in org.netbeans.modules.editor.java.JavaCodeTemplateProcessor.getProposedValue

2018-08-15 Thread Austin Stephens (JIRA)


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

Austin Stephens commented on NETBEANS-1139:
---

It appears to happen when there are many variables in the scope of completion? 
That is what I gather from the stack trace and it popping up all of the time... 
The AssertionError also occurs when it looks like it is trying to increase the 
size of the table for the scope.

> AssertionError in 
> org.netbeans.modules.editor.java.JavaCodeTemplateProcessor.getProposedValue
> -
>
> Key: NETBEANS-1139
> URL: https://issues.apache.org/jira/browse/NETBEANS-1139
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Editor
>Affects Versions: 9.0, Next
>Reporter: Austin Stephens
>Priority: Critical
> Attachments: AutoCompleteBug1.java
>
>
> Attempting to Autocomplete the constructor after new in the attached file 
> throws an AssertionError.
> StackTrace:
> {noformat}
> java.lang.AssertionError
>     at com.sun.tools.javac.util.Assert.error(Assert.java:155)
>     at com.sun.tools.javac.util.Assert.check(Assert.java:46)
>     at com.sun.tools.javac.code.Scope$ScopeImpl.dble(Scope.java:410)
>     at com.sun.tools.javac.code.Scope$ScopeImpl.enter(Scope.java:433)
>     at com.sun.tools.javac.comp.MemberEnter.visitVarDef(MemberEnter.java:476)
>     at 
> com.sun.tools.javadoc.main.JavadocMemberEnter.visitVarDef(JavadocMemberEnter.java:83)
>     at 
> org.netbeans.lib.nbjavac.services.NBJavadocMemberEnter.visitVarDef(NBJavadocMemberEnter.java:92)
>     at com.sun.tools.javac.tree.JCTree$JCVariableDecl.accept(JCTree.java:962)
>     at com.sun.tools.javac.comp.MemberEnter.memberEnter(MemberEnter.java:171)
>     at com.sun.tools.javac.comp.Attr.visitVarDef(Attr.java:1171)
>     at com.sun.tools.javac.tree.JCTree$JCVariableDecl.accept(JCTree.java:962)
>     at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:660)
>     at com.sun.tools.javac.comp.Attr.attribStat(Attr.java:736)
>     at com.sun.tools.javac.comp.Attr.attribStats(Attr.java:760)
>     at com.sun.tools.javac.comp.Attr.visitBlock(Attr.java:1337)
>     at org.netbeans.lib.nbjavac.services.NBAttr.visitBlock(NBAttr.java:73)
>     at com.sun.tools.javac.tree.JCTree$JCBlock.accept(JCTree.java:1026)
>     at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:660)
>     at com.sun.tools.javac.comp.Attr.attribStat(Attr.java:736)
>     at 
> org.netbeans.api.java.source.TreeUtilities.attributeTree(TreeUtilities.java:878)
>     at 
> org.netbeans.api.java.source.TreeUtilities.attributeTree(TreeUtilities.java:808)
>     at 
> org.netbeans.modules.editor.java.JavaCodeTemplateProcessor.type(JavaCodeTemplateProcessor.java:716)
>     at 
> org.netbeans.modules.editor.java.JavaCodeTemplateProcessor.getProposedValue(JavaCodeTemplateProcessor.java:431)
>     at 
> org.netbeans.modules.editor.java.JavaCodeTemplateProcessor.updateDefaultValues(JavaCodeTemplateProcessor.java:143)
>     at 
> org.netbeans.lib.editor.codetemplates.CodeTemplateInsertHandler.processTemplate(CodeTemplateInsertHandler.java:225)
>     at 
> org.netbeans.lib.editor.codetemplates.CodeTemplateManagerOperation.insert(CodeTemplateManagerOperation.java:273)
>     at 
> org.netbeans.lib.editor.codetemplates.api.CodeTemplate.insert(CodeTemplate.java:82)
>     at 
> org.netbeans.modules.editor.java.JavaCompletionItem.process(JavaCompletionItem.java:566)
>     at 
> org.netbeans.modules.editor.java.JavaCompletionItem.defaultAction(JavaCompletionItem.java:286)
>     at 
> org.netbeans.modules.editor.completion.CompletionImpl.dispatchKeyEvent(CompletionImpl.java:785)
>     at 
> org.netbeans.modules.editor.completion.CompletionImpl.keyPressed(CompletionImpl.java:386)
>     at 
> java.desktop/java.awt.AWTEventMulticaster.keyPressed(AWTEventMulticaster.java:258)
>     at 
> java.desktop/java.awt.AWTEventMulticaster.keyPressed(AWTEventMulticaster.java:257)
>     at 
> java.desktop/java.awt.AWTEventMulticaster.keyPressed(AWTEventMulticaster.java:257)
>     at java.desktop/java.awt.Component.processKeyEvent(Component.java:6547)
>     at 
> java.desktop/javax.swing.JComponent.processKeyEvent(JComponent.java:2849)
>     at java.desktop/java.awt.Component.processEvent(Component.java:6366)
>     at java.desktop/java.awt.Container.processEvent(Container.java:2261)
>     at java.desktop/java.awt.Component.dispatchEventImpl(Component.java:4966)
>     at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2319)
>     at java.desktop/java.awt.Component.dispatchEvent(Component.java:4798)
>     at 
> java.desktop/java.awt.KeyboardFocusManager.redispatchEvent(KeyboardFocusManager.java:1950)
>     at 
> java.desktop/java.awt.DefaultKeyboardFocusManager.dispatchKeyEvent

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

2018-08-25 Thread Austin Stephens (JIRA)


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

Austin Stephens commented on NETBEANS-346:
--

I don't recall the resolution of the mac computer off of my head. I would have 
to get it when I go back to work, but it is smaller than 1920x1080 per screen. 
There are 4 of them arranged in a 2x2 grid. I found a font that it works with 
on the Mac computer, but I will need to get that also when I go back to work.

> 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: Major
> 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-344) org.netbeans.core.windows.service.PresenterDecorator is not publicly accessible

2018-08-31 Thread Austin Stephens (JIRA)


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

Austin Stephens commented on NETBEANS-344:
--

Shouldn't it at least be made public(er)?

> org.netbeans.core.windows.service.PresenterDecorator is not publicly 
> accessible
> ---
>
> Key: NETBEANS-344
> URL: https://issues.apache.org/jira/browse/NETBEANS-344
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - Window System
>Affects Versions: 8.2, 9.0
>Reporter: Austin Stephens
>Assignee: Jaroslav Tulach
>Priority: Trivial
> Fix For: Next
>
>
> The commit message for adding it states that it was added so other modules 
> could customize the displayed dialog, but it is module private.



--
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-1202) Add support for bundling and updating the bundled JRE for Platform applications (for Java 9+)

2018-08-31 Thread Austin Stephens (JIRA)
Austin Stephens created NETBEANS-1202:
-

 Summary: Add support for bundling and updating the bundled JRE for 
Platform applications (for Java 9+)
 Key: NETBEANS-1202
 URL: https://issues.apache.org/jira/browse/NETBEANS-1202
 Project: NetBeans
  Issue Type: New Feature
  Components: platform - Other
Reporter: Austin Stephens


According to [Oracle ("End of Public 
Updates")|http://www.oracle.com/technetwork/java/eol-135779.html], they do not 
plan on migrating desktops from Java 8 to a later version via auto-update and 
"... encourage application developers to [use the packaging options introduced 
with Java SE 
9|https://blogs.oracle.com/java-platform-group/the-future-of-javafx-and-other-java-client-roadmap-updates]
 to repackage and deliver their Java applications as stand-alone applications 
that include their own custom runtimes."

It would be wonderful if the NetBeans Platform could handle updating the 
bundled JRE (as if it was a Netbeans Module) so it would be less of a head-ache 
to get Java Security updates out and such.



--
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-1202) Add support for bundling and updating the bundled JRE for Platform applications (for Java 9+)

2018-09-01 Thread Austin Stephens (JIRA)


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

Austin Stephens commented on NETBEANS-1202:
---

I was thinking more like, instead of Netbeans being bundled with the JRE, that 
Netbeans should have the capability to bundle a JRE (from the current machine) 
for a Netbeans Platform product and (possibly) be able to handle JRE updates as 
if they were Netbeans modules. Does that make more sense?

> Add support for bundling and updating the bundled JRE for Platform 
> applications (for Java 9+)
> -
>
> Key: NETBEANS-1202
> URL: https://issues.apache.org/jira/browse/NETBEANS-1202
> Project: NetBeans
>  Issue Type: New Feature
>  Components: platform - Other
>Reporter: Austin Stephens
>Priority: Critical
>
> According to [Oracle ("End of Public 
> Updates")|http://www.oracle.com/technetwork/java/eol-135779.html], they do 
> not plan on migrating desktops from Java 8 to a later version via auto-update 
> and "... encourage application developers to [use the packaging options 
> introduced with Java SE 
> 9|https://blogs.oracle.com/java-platform-group/the-future-of-javafx-and-other-java-client-roadmap-updates]
>  to repackage and deliver their Java applications as stand-alone applications 
> that include their own custom runtimes."
> It would be wonderful if the NetBeans Platform could handle updating the 
> bundled JRE (as if it was a Netbeans Module) so it would be less of a 
> head-ache to get Java Security updates out and such.



--
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-1202) Add support for bundling and updating the bundled JRE for Platform applications (for Java 9+)

2018-09-01 Thread Austin Stephens (JIRA)


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

Austin Stephens edited comment on NETBEANS-1202 at 9/1/18 8:13 PM:
---

I was thinking more like, instead of Netbeans being bundled with the JRE, that 
Netbeans should have the capability to bundle a JRE (from the current machine) 
for a Netbeans Platform product and (possibly) be able to handle JRE updates 
(for the platform application) as if they were Netbeans modules. Does that make 
more sense?


was (Author: sir intellegence):
I was thinking more like, instead of Netbeans being bundled with the JRE, that 
Netbeans should have the capability to bundle a JRE (from the current machine) 
for a Netbeans Platform product and (possibly) be able to handle JRE updates as 
if they were Netbeans modules. Does that make more sense?

> Add support for bundling and updating the bundled JRE for Platform 
> applications (for Java 9+)
> -
>
> Key: NETBEANS-1202
> URL: https://issues.apache.org/jira/browse/NETBEANS-1202
> Project: NetBeans
>  Issue Type: New Feature
>  Components: platform - Other
>Reporter: Austin Stephens
>Priority: Critical
>
> According to [Oracle ("End of Public 
> Updates")|http://www.oracle.com/technetwork/java/eol-135779.html], they do 
> not plan on migrating desktops from Java 8 to a later version via auto-update 
> and "... encourage application developers to [use the packaging options 
> introduced with Java SE 
> 9|https://blogs.oracle.com/java-platform-group/the-future-of-javafx-and-other-java-client-roadmap-updates]
>  to repackage and deliver their Java applications as stand-alone applications 
> that include their own custom runtimes."
> It would be wonderful if the NetBeans Platform could handle updating the 
> bundled JRE (as if it was a Netbeans Module) so it would be less of a 
> head-ache to get Java Security updates out and such.



--
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-1202) Add support for bundling and updating the bundled JRE for Platform applications (for Java 9+)

2018-09-04 Thread Austin Stephens (JIRA)


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

Austin Stephens commented on NETBEANS-1202:
---

RightI see you point. Maybe add an option to not export java modules?

> Add support for bundling and updating the bundled JRE for Platform 
> applications (for Java 9+)
> -
>
> Key: NETBEANS-1202
> URL: https://issues.apache.org/jira/browse/NETBEANS-1202
> Project: NetBeans
>  Issue Type: New Feature
>  Components: platform - Other
>Reporter: Austin Stephens
>Priority: Critical
>
> According to [Oracle ("End of Public 
> Updates")|http://www.oracle.com/technetwork/java/eol-135779.html], they do 
> not plan on migrating desktops from Java 8 to a later version via auto-update 
> and "... encourage application developers to [use the packaging options 
> introduced with Java SE 
> 9|https://blogs.oracle.com/java-platform-group/the-future-of-javafx-and-other-java-client-roadmap-updates]
>  to repackage and deliver their Java applications as stand-alone applications 
> that include their own custom runtimes."
> It would be wonderful if the NetBeans Platform could handle updating the 
> bundled JRE (as if it was a Netbeans Module) so it would be less of a 
> head-ache to get Java Security updates out and such.



--
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-1246) ToolbarWithOverflow does not override getMinimumSize()

2018-09-13 Thread Austin Stephens (JIRA)
Austin Stephens created NETBEANS-1246:
-

 Summary: ToolbarWithOverflow does not override getMinimumSize()
 Key: NETBEANS-1246
 URL: https://issues.apache.org/jira/browse/NETBEANS-1246
 Project: NetBeans
  Issue Type: Bug
  Components: platform - Window System
Affects Versions: 9.0, Next
Reporter: Austin Stephens


The default implementation for minimumSize (last I checked) for 
`ToolbarWithOverflow` effectively returns the current size of the toolbar. As a 
result, any custom layout manager doesn't know how much it can squeeze it.

Details:

The default call to `getMinimumSize` calls `layoutMgr.minimumLayoutSize`. The 
layout for the toolbar is a `BoxLayout`. `BoxLayout.minimumLayoutSize` returns 
the combined width of the current buttons, which is effectively the current 
size of the toolbar, regardless of whether or not any icons have overflowed.



--
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-1246) ToolbarWithOverflow does not override getMinimumSize()

2018-09-13 Thread Austin Stephens (JIRA)


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

Austin Stephens commented on NETBEANS-1246:
---

We should probably have it override `getMaximumSize` as well

> ToolbarWithOverflow does not override getMinimumSize()
> --
>
> Key: NETBEANS-1246
> URL: https://issues.apache.org/jira/browse/NETBEANS-1246
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - Window System
>Affects Versions: 9.0, Next
>Reporter: Austin Stephens
>Priority: Major
>
> The default implementation for minimumSize (last I checked) for 
> `ToolbarWithOverflow` effectively returns the current size of the toolbar. As 
> a result, any custom layout manager doesn't know how much it can squeeze it.
> Details:
> The default call to `getMinimumSize` calls `layoutMgr.minimumLayoutSize`. The 
> layout for the toolbar is a `BoxLayout`. `BoxLayout.minimumLayoutSize` 
> returns the combined width of the current buttons, which is effectively the 
> current size of the toolbar, regardless of whether or not any icons have 
> overflowed.



--
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-1247) ToolbarWithOverflow popup menu doesn't stay visible if it pops-up over the overflow button

2018-09-13 Thread Austin Stephens (JIRA)
Austin Stephens created NETBEANS-1247:
-

 Summary: ToolbarWithOverflow popup menu doesn't stay visible if it 
pops-up over the overflow button
 Key: NETBEANS-1247
 URL: https://issues.apache.org/jira/browse/NETBEANS-1247
 Project: NetBeans
  Issue Type: Bug
  Components: platform - Window System
Affects Versions: 9.0, Next
Reporter: Austin Stephens


This will result in the popup menu flickering in out out of existence. This is 
most likely to happen with a horizontal toolbar with a large number of 
overflowed buttons.



--
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-1202) Add support for bundling and updating the bundled JRE for Platform applications (for Java 9+)

2018-09-27 Thread Austin Stephens (JIRA)


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

Austin Stephens commented on NETBEANS-1202:
---

That is right. I would add that the JRE comes with it's own modules, so you 
could just deploy the parts that you use and Netbeans would keep track of which 
ones you need (as if they are Netbeans Modules), thus reducing the the amount 
of space the JRE takes.

> Add support for bundling and updating the bundled JRE for Platform 
> applications (for Java 9+)
> -
>
> Key: NETBEANS-1202
> URL: https://issues.apache.org/jira/browse/NETBEANS-1202
> Project: NetBeans
>  Issue Type: New Feature
>  Components: platform - Other
>Reporter: Austin Stephens
>Priority: Critical
>
> According to [Oracle ("End of Public 
> Updates")|http://www.oracle.com/technetwork/java/eol-135779.html], they do 
> not plan on migrating desktops from Java 8 to a later version via auto-update 
> and "... encourage application developers to [use the packaging options 
> introduced with Java SE 
> 9|https://blogs.oracle.com/java-platform-group/the-future-of-javafx-and-other-java-client-roadmap-updates]
>  to repackage and deliver their Java applications as stand-alone applications 
> that include their own custom runtimes."
> It would be wonderful if the NetBeans Platform could handle updating the 
> bundled JRE (as if it was a Netbeans Module) so it would be less of a 
> head-ache to get Java Security updates out and such.



--
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-1202) Add support for bundling and updating the bundled JRE for Platform applications (for Java 9+)

2018-09-27 Thread Austin Stephens (JIRA)


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

Austin Stephens commented on NETBEANS-1202:
---

So, basically treat the JRE modules as if they were Netbeans modules.

> Add support for bundling and updating the bundled JRE for Platform 
> applications (for Java 9+)
> -
>
> Key: NETBEANS-1202
> URL: https://issues.apache.org/jira/browse/NETBEANS-1202
> Project: NetBeans
>  Issue Type: New Feature
>  Components: platform - Other
>Reporter: Austin Stephens
>Priority: Critical
>
> According to [Oracle ("End of Public 
> Updates")|http://www.oracle.com/technetwork/java/eol-135779.html], they do 
> not plan on migrating desktops from Java 8 to a later version via auto-update 
> and "... encourage application developers to [use the packaging options 
> introduced with Java SE 
> 9|https://blogs.oracle.com/java-platform-group/the-future-of-javafx-and-other-java-client-roadmap-updates]
>  to repackage and deliver their Java applications as stand-alone applications 
> that include their own custom runtimes."
> It would be wonderful if the NetBeans Platform could handle updating the 
> bundled JRE (as if it was a Netbeans Module) so it would be less of a 
> head-ache to get Java Security updates out and such.



--
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-1337) Add multiline support for breadcrumbs

2018-10-02 Thread Austin Stephens (JIRA)
Austin Stephens created NETBEANS-1337:
-

 Summary: Add multiline support for breadcrumbs
 Key: NETBEANS-1337
 URL: https://issues.apache.org/jira/browse/NETBEANS-1337
 Project: NetBeans
  Issue Type: Wish
  Components: java - Editor
Reporter: Austin Stephens
 Attachments: Screen Shot 2018-10-02 at 11.33.33 AM.png

It would be nice if the contents of the breadcrumbs component wrapped onto 
another line if it wouldn't fit normally. This would likely happen if one 
wanted to have multiple files open side-by-side (see attached image). The bread 
crumbs component is not wide enough to display all of the items.



--
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-1386) Jdk parsing errors

2018-10-08 Thread Austin Stephens (JIRA)
Austin Stephens created NETBEANS-1386:
-

 Summary: Jdk parsing errors
 Key: NETBEANS-1386
 URL: https://issues.apache.org/jira/browse/NETBEANS-1386
 Project: NetBeans
  Issue Type: Bug
  Components: platform - JDK Problems
Affects Versions: 9.0
Reporter: Austin Stephens
 Attachments: log.7z

I just start the latest development version of Netbeans, and I get all of these 
errors. I haven't tested it with the 10 rc. I have 7 zipped the log folder and 
attached it.



--
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-1386) Jdk parsing errors

2018-10-08 Thread Austin Stephens (JIRA)


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

Austin Stephens updated NETBEANS-1386:
--
Fix Version/s: 10.0
   Next

> Jdk parsing errors
> --
>
> Key: NETBEANS-1386
> URL: https://issues.apache.org/jira/browse/NETBEANS-1386
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - JDK Problems
>Affects Versions: 9.0
>Reporter: Austin Stephens
>Priority: Critical
> Fix For: Next, 10.0
>
> Attachments: log.7z
>
>
> I just start the latest development version of Netbeans, and I get all of 
> these errors. I haven't tested it with the 10 rc. I have 7 zipped the log 
> folder and attached it.



--
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-1386) Jdk parsing errors

2018-10-08 Thread Austin Stephens (JIRA)


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

Austin Stephens commented on NETBEANS-1386:
---

It appears to have gone away when I removed the JDK (mercurial) sources from 
the platform sources. I still get parsing and nullpointer errors...

> Jdk parsing errors
> --
>
> Key: NETBEANS-1386
> URL: https://issues.apache.org/jira/browse/NETBEANS-1386
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - JDK Problems
>Affects Versions: 9.0
>Reporter: Austin Stephens
>Priority: Critical
> Fix For: Next, 10.0
>
> Attachments: log.7z
>
>
> I just start the latest development version of Netbeans, and I get all of 
> these errors. I haven't tested it with the 10 rc. I have 7 zipped the log 
> folder and attached it.



--
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-1386) Jdk parsing errors

2018-10-08 Thread Austin Stephens (JIRA)


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

Austin Stephens updated NETBEANS-1386:
--
Priority: Minor  (was: Critical)

> Jdk parsing errors
> --
>
> Key: NETBEANS-1386
> URL: https://issues.apache.org/jira/browse/NETBEANS-1386
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - JDK Problems
>Affects Versions: 9.0
>Reporter: Austin Stephens
>Priority: Minor
> Attachments: log.7z
>
>
> I just start the latest development version of Netbeans, and I get all of 
> these errors. I haven't tested it with the 10 rc. I have 7 zipped the log 
> folder and attached it.



--
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-1386) Jdk parsing errors

2018-10-08 Thread Austin Stephens (JIRA)


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

Austin Stephens updated NETBEANS-1386:
--
Fix Version/s: (was: 10.0)
   (was: Next)

> Jdk parsing errors
> --
>
> Key: NETBEANS-1386
> URL: https://issues.apache.org/jira/browse/NETBEANS-1386
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - JDK Problems
>Affects Versions: 9.0
>Reporter: Austin Stephens
>Priority: Critical
> Attachments: log.7z
>
>
> I just start the latest development version of Netbeans, and I get all of 
> these errors. I haven't tested it with the 10 rc. I have 7 zipped the log 
> folder and attached it.



--
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-1386) Jdk parsing errors

2018-10-08 Thread Austin Stephens (JIRA)


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

Austin Stephens commented on NETBEANS-1386:
---

It appears that combining the previous comment with having nbjavac seems to 
have resolved the issue, but I am going to leave it open in case someone would 
find failures to parse java.lang source files as interesting.

> Jdk parsing errors
> --
>
> Key: NETBEANS-1386
> URL: https://issues.apache.org/jira/browse/NETBEANS-1386
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - JDK Problems
>Affects Versions: 9.0
>Reporter: Austin Stephens
>Priority: Critical
> Attachments: log.7z
>
>
> I just start the latest development version of Netbeans, and I get all of 
> these errors. I haven't tested it with the 10 rc. I have 7 zipped the log 
> folder and attached it.



--
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-1398) Attach profiler to existing process fails

2018-10-10 Thread Austin Stephens (JIRA)
Austin Stephens created NETBEANS-1398:
-

 Summary: Attach profiler to existing process fails
 Key: NETBEANS-1398
 URL: https://issues.apache.org/jira/browse/NETBEANS-1398
 Project: NetBeans
  Issue Type: Bug
  Components: profiler - Attach
Affects Versions: 9.0, Next
 Environment: Mac 10.10 JDK 10.0.2
Reporter: Austin Stephens


It seems to succeed, but HotSpotVirtualMachine.loadAgentLibrary is expecting 
execute to return "return code: 0". It is instead returning "0", so it thinks 
it failed.

Call Stack:
{noformat}
HotSpotVirtualMachine.loadAgentLibrary:98    
HotSpotVirtualMachine.loadAgentLibrary:115    
HotSpotVirtualMachine.loadAgent:139    
NetBeansProfiler.loadAgentIntoTargetJVM:791    
NetBeansProfiler.attachToApp:759    
ProfilerLauncher$ProfilerSessionImpl$1.run:112    
RequestProcessor$Task.run:1418    
GlobalLookup.execute:45    
Lookups.executeWith:278    
RequestProcessor$Processor.run:2033   {noformat}



--
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-530) No Bind option on the popup to create Bindings

2018-10-15 Thread Austin Stephens (JIRA)


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

Austin Stephens commented on NETBEANS-530:
--

I haven't worked on it at all (and don't really plan on it at the moment). I 
mostly did that so someone else won't have to go through the work of bringing 
back the Netbeans sources. It is just sitting there, waiting for someone to fix 
it.

> No Bind option on the popup to create Bindings 
> ---
>
> Key: NETBEANS-530
> URL: https://issues.apache.org/jira/browse/NETBEANS-530
> Project: NetBeans
>  Issue Type: Bug
>  Components: ide - Code
>Affects Versions: 9.0
> Environment: Window 8.1, MacOs 10.11.6
>Reporter: efrem mccrimon
>Priority: Major
> Attachments: Screenshot from 2018-08-02 21-18-53.png, 
> no_bind_popup_item.JPG
>
>
> Trying to create bindings, created a textfield and Slider to demonstrate and 
> test basic bean binding.  From the Design view, I wanted to bind the slider 
> to the text field.
> Right-click the text field component and wanted to choose Bind.  There is not 
> Bind option on the popup menu.  It is not present in build #375, or #378.  It 
> is on NB 8.2 and NB 8.02.



--
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-4295) No console output when debugging platform on Windows

2020-05-01 Thread Austin Stephens (Jira)
Austin Stephens created NETBEANS-4295:
-

 Summary: No console output when debugging platform on Windows
 Key: NETBEANS-4295
 URL: https://issues.apache.org/jira/browse/NETBEANS-4295
 Project: NetBeans
  Issue Type: Bug
  Components: platform - Launchers&CLI
Affects Versions: 11.2, 11.1, 11.0, 10.0, 9.0, 11.3
 Environment: Windows
Reporter: Austin Stephens


When you run Netbeans on a Mac or Linux, you can see the console output when 
debugging a Netbeans platform application, likely because they inherit std in 
and out. This does not happen on Windows. This makes it much harder to do 
debugging because operations (such as `Throwable.printStackTrace()`) produce no 
output in the output window.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
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-4295) No console output when debugging platform on Windows

2020-05-01 Thread Austin Stephens (Jira)


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

Austin Stephens updated NETBEANS-4295:
--
Description: 
When you run Netbeans on a Mac or Linux, you can see the console output when 
debugging a Netbeans platform application, likely because they inherit std in 
and out. This does not happen on Windows. This makes it much harder to do 
debugging because operations (such as `Throwable.printStackTrace()`) produce no 
output in the output window.

This can easily be reproduced by creating a new Netbeans Platform Application 
and debugging it. You will see logger output on Mac and Linux, but not in 
Windows.

  was:When you run Netbeans on a Mac or Linux, you can see the console output 
when debugging a Netbeans platform application, likely because they inherit std 
in and out. This does not happen on Windows. This makes it much harder to do 
debugging because operations (such as `Throwable.printStackTrace()`) produce no 
output in the output window.


> No console output when debugging platform on Windows
> 
>
> Key: NETBEANS-4295
> URL: https://issues.apache.org/jira/browse/NETBEANS-4295
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - Launchers&CLI
>Affects Versions: 9.0, 10.0, 11.0, 11.1, 11.2, 11.3
> Environment: Windows
>Reporter: Austin Stephens
>Priority: Major
>  Labels: console, debug, output
>
> When you run Netbeans on a Mac or Linux, you can see the console output when 
> debugging a Netbeans platform application, likely because they inherit std in 
> and out. This does not happen on Windows. This makes it much harder to do 
> debugging because operations (such as `Throwable.printStackTrace()`) produce 
> no output in the output window.
> This can easily be reproduced by creating a new Netbeans Platform Application 
> and debugging it. You will see logger output on Mac and Linux, but not in 
> Windows.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
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-4304) Incorrect return type on "Refactor->Create Method" inside lambda

2020-05-04 Thread Austin Stephens (Jira)
Austin Stephens created NETBEANS-4304:
-

 Summary: Incorrect return type on "Refactor->Create Method" inside 
lambda
 Key: NETBEANS-4304
 URL: https://issues.apache.org/jira/browse/NETBEANS-4304
 Project: NetBeans
  Issue Type: Bug
  Components: java - Refactoring
Affects Versions: 11.2, 11.3
Reporter: Austin Stephens


Using the following source code:
{code:java}
public class BugKiller {
public static void kill(){
Function> logic;
logic = item->doThingWithString(item, 5, true);
}
}
{code}
Invoking "Create Method" on `doThingWithString` will create a method with the 
return type of "Function>" instead of "List"



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
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-4716) Netbeans source will not build under Java 13 (Ambigous reference)

2020-08-14 Thread Austin Stephens (Jira)
Austin Stephens created NETBEANS-4716:
-

 Summary: Netbeans source will not build under Java 13 (Ambigous 
reference)
 Key: NETBEANS-4716
 URL: https://issues.apache.org/jira/browse/NETBEANS-4716
 Project: NetBeans
  Issue Type: Bug
  Components: platform - Other
Affects Versions: 12.0, 12.1
Reporter: Austin Stephens


When attempting to build from netbeans source, I get a compile error when it 
goes to build langtools. Here are the details:
{noformat}
D:\netbeans\incubator-netbeans\nbbuild\build\langtools\src\jdk.compiler\share\classes\com\sun\tools\javac\file\JavacFileManager.java:519:
 error: reference to newFileSystem is ambiguous
this.fileSystem = FileSystems.newFileSystem(archivePath, null);
  both method newFileSystem(Path,ClassLoader) in FileSystems and method 
newFileSystem(Path,Map) in FileSystems match
D:\netbeans\incubator-netbeans\nbbuild\build\langtools\src\jdk.compiler\share\classes\com\sun\tools\javac\file\Locations.java:383:
 error: reference to newFileSystem is ambiguous
FileSystems.newFileSystem(file, null).close();
  both method newFileSystem(Path,ClassLoader) in FileSystems and method 
newFileSystem(Path,Map) in FileSystems match
D:\netbeans\incubator-netbeans\nbbuild\build\langtools\src\jdk.compiler\share\classes\com\sun\tools\javac\platform\JDKPlatformProvider.java:80:
 error: reference to newFileSystem is ambiguous
try (FileSystem fs = FileSystems.newFileSystem(ctSymFile, null);
  both method newFileSystem(Path,ClassLoader) in FileSystems and method 
newFileSystem(Path,Map) in FileSystems match
D:\netbeans\incubator-netbeans\nbbuild\build\langtools\src\jdk.compiler\share\classes\com\sun\tools\javac\platform\JDKPlatformProvider.java:120:
 error: reference to newFileSystem is ambiguous
ctSym2FileSystem.put(file, fs = 
FileSystems.newFileSystem(file, null));
  both method newFileSystem(Path,ClassLoader) in FileSystems and method 
newFileSystem(Path,Map) in FileSystems match{noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
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-4716) Netbeans source will not build under Java 13 (Ambigous reference)

2020-08-14 Thread Austin Stephens (Jira)


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

Austin Stephens commented on NETBEANS-4716:
---

Wait, we are still using Java 8 to build everything? It didn't get to the 
warning with 13... Is there a reason we haven't started using newer versions of 
Java?

> Netbeans source will not build under Java 13 (Ambigous reference)
> -
>
> Key: NETBEANS-4716
> URL: https://issues.apache.org/jira/browse/NETBEANS-4716
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - Other
>Affects Versions: 12.0, 12.1
>Reporter: Austin Stephens
>Priority: Major
>
> When attempting to build from netbeans source, I get a compile error when it 
> goes to build langtools. Here are the details:
> {noformat}
> D:\netbeans\incubator-netbeans\nbbuild\build\langtools\src\jdk.compiler\share\classes\com\sun\tools\javac\file\JavacFileManager.java:519:
>  error: reference to newFileSystem is ambiguous
> this.fileSystem = FileSystems.newFileSystem(archivePath, 
> null);
>   both method newFileSystem(Path,ClassLoader) in FileSystems and method 
> newFileSystem(Path,Map) in FileSystems match
> D:\netbeans\incubator-netbeans\nbbuild\build\langtools\src\jdk.compiler\share\classes\com\sun\tools\javac\file\Locations.java:383:
>  error: reference to newFileSystem is ambiguous
> FileSystems.newFileSystem(file, null).close();
>   both method newFileSystem(Path,ClassLoader) in FileSystems and method 
> newFileSystem(Path,Map) in FileSystems match
> D:\netbeans\incubator-netbeans\nbbuild\build\langtools\src\jdk.compiler\share\classes\com\sun\tools\javac\platform\JDKPlatformProvider.java:80:
>  error: reference to newFileSystem is ambiguous
> try (FileSystem fs = FileSystems.newFileSystem(ctSymFile, null);
>   both method newFileSystem(Path,ClassLoader) in FileSystems and method 
> newFileSystem(Path,Map) in FileSystems match
> D:\netbeans\incubator-netbeans\nbbuild\build\langtools\src\jdk.compiler\share\classes\com\sun\tools\javac\platform\JDKPlatformProvider.java:120:
>  error: reference to newFileSystem is ambiguous
> ctSym2FileSystem.put(file, fs = 
> FileSystems.newFileSystem(file, null));
>   both method newFileSystem(Path,ClassLoader) in FileSystems and method 
> newFileSystem(Path,Map) in FileSystems match{noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
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-4716) Netbeans source will not build under Java 13 (Ambigous reference)

2020-08-15 Thread Austin Stephens (Jira)


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

Austin Stephens commented on NETBEANS-4716:
---

Have you tried doing a very clean build like what you would get after checking 
out a new copy? The error occurs while building "langtools" which occurs before 
the script has a chance to warn you about building with newer versions of Java.

> Netbeans source will not build under Java 13 (Ambigous reference)
> -
>
> Key: NETBEANS-4716
> URL: https://issues.apache.org/jira/browse/NETBEANS-4716
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - Other
>Affects Versions: 12.0, 12.1
>Reporter: Austin Stephens
>Priority: Major
>
> When attempting to build from netbeans source, I get a compile error when it 
> goes to build langtools. Here are the details:
> {noformat}
> D:\netbeans\incubator-netbeans\nbbuild\build\langtools\src\jdk.compiler\share\classes\com\sun\tools\javac\file\JavacFileManager.java:519:
>  error: reference to newFileSystem is ambiguous
> this.fileSystem = FileSystems.newFileSystem(archivePath, 
> null);
>   both method newFileSystem(Path,ClassLoader) in FileSystems and method 
> newFileSystem(Path,Map) in FileSystems match
> D:\netbeans\incubator-netbeans\nbbuild\build\langtools\src\jdk.compiler\share\classes\com\sun\tools\javac\file\Locations.java:383:
>  error: reference to newFileSystem is ambiguous
> FileSystems.newFileSystem(file, null).close();
>   both method newFileSystem(Path,ClassLoader) in FileSystems and method 
> newFileSystem(Path,Map) in FileSystems match
> D:\netbeans\incubator-netbeans\nbbuild\build\langtools\src\jdk.compiler\share\classes\com\sun\tools\javac\platform\JDKPlatformProvider.java:80:
>  error: reference to newFileSystem is ambiguous
> try (FileSystem fs = FileSystems.newFileSystem(ctSymFile, null);
>   both method newFileSystem(Path,ClassLoader) in FileSystems and method 
> newFileSystem(Path,Map) in FileSystems match
> D:\netbeans\incubator-netbeans\nbbuild\build\langtools\src\jdk.compiler\share\classes\com\sun\tools\javac\platform\JDKPlatformProvider.java:120:
>  error: reference to newFileSystem is ambiguous
> ctSym2FileSystem.put(file, fs = 
> FileSystems.newFileSystem(file, null));
>   both method newFileSystem(Path,ClassLoader) in FileSystems and method 
> newFileSystem(Path,Map) in FileSystems match{noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
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-4716) Netbeans source will not build under Java 13 (Ambigous reference)

2020-08-15 Thread Austin Stephens (Jira)


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

Austin Stephens edited comment on NETBEANS-4716 at 8/15/20, 7:39 PM:
-

[~lkishalmi] Have you tried doing a very clean build like what you would get 
after checking out a new copy? The error occurs while building "langtools" 
which occurs before the script has a chance to warn you about building with 
newer versions of Java.


was (Author: sir intellegence):
Have you tried doing a very clean build like what you would get after checking 
out a new copy? The error occurs while building "langtools" which occurs before 
the script has a chance to warn you about building with newer versions of Java.

> Netbeans source will not build under Java 13 (Ambigous reference)
> -
>
> Key: NETBEANS-4716
> URL: https://issues.apache.org/jira/browse/NETBEANS-4716
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - Other
>Affects Versions: 12.0, 12.1
>Reporter: Austin Stephens
>Priority: Major
>
> When attempting to build from netbeans source, I get a compile error when it 
> goes to build langtools. Here are the details:
> {noformat}
> D:\netbeans\incubator-netbeans\nbbuild\build\langtools\src\jdk.compiler\share\classes\com\sun\tools\javac\file\JavacFileManager.java:519:
>  error: reference to newFileSystem is ambiguous
> this.fileSystem = FileSystems.newFileSystem(archivePath, 
> null);
>   both method newFileSystem(Path,ClassLoader) in FileSystems and method 
> newFileSystem(Path,Map) in FileSystems match
> D:\netbeans\incubator-netbeans\nbbuild\build\langtools\src\jdk.compiler\share\classes\com\sun\tools\javac\file\Locations.java:383:
>  error: reference to newFileSystem is ambiguous
> FileSystems.newFileSystem(file, null).close();
>   both method newFileSystem(Path,ClassLoader) in FileSystems and method 
> newFileSystem(Path,Map) in FileSystems match
> D:\netbeans\incubator-netbeans\nbbuild\build\langtools\src\jdk.compiler\share\classes\com\sun\tools\javac\platform\JDKPlatformProvider.java:80:
>  error: reference to newFileSystem is ambiguous
> try (FileSystem fs = FileSystems.newFileSystem(ctSymFile, null);
>   both method newFileSystem(Path,ClassLoader) in FileSystems and method 
> newFileSystem(Path,Map) in FileSystems match
> D:\netbeans\incubator-netbeans\nbbuild\build\langtools\src\jdk.compiler\share\classes\com\sun\tools\javac\platform\JDKPlatformProvider.java:120:
>  error: reference to newFileSystem is ambiguous
> ctSym2FileSystem.put(file, fs = 
> FileSystems.newFileSystem(file, null));
>   both method newFileSystem(Path,ClassLoader) in FileSystems and method 
> newFileSystem(Path,Map) in FileSystems match{noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
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-4716) Netbeans source will not build under Java 13 (Ambigous reference)

2020-08-17 Thread Austin Stephens (Jira)


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

Austin Stephens commented on NETBEANS-4716:
---

[~lkishalmi] Have you tried doing a build from a fresh clean checkout?

> Netbeans source will not build under Java 13 (Ambigous reference)
> -
>
> Key: NETBEANS-4716
> URL: https://issues.apache.org/jira/browse/NETBEANS-4716
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - Other
>Affects Versions: 12.0, 12.1
>Reporter: Austin Stephens
>Priority: Major
>
> When attempting to build from netbeans source, I get a compile error when it 
> goes to build langtools. Here are the details:
> {noformat}
> D:\netbeans\incubator-netbeans\nbbuild\build\langtools\src\jdk.compiler\share\classes\com\sun\tools\javac\file\JavacFileManager.java:519:
>  error: reference to newFileSystem is ambiguous
> this.fileSystem = FileSystems.newFileSystem(archivePath, 
> null);
>   both method newFileSystem(Path,ClassLoader) in FileSystems and method 
> newFileSystem(Path,Map) in FileSystems match
> D:\netbeans\incubator-netbeans\nbbuild\build\langtools\src\jdk.compiler\share\classes\com\sun\tools\javac\file\Locations.java:383:
>  error: reference to newFileSystem is ambiguous
> FileSystems.newFileSystem(file, null).close();
>   both method newFileSystem(Path,ClassLoader) in FileSystems and method 
> newFileSystem(Path,Map) in FileSystems match
> D:\netbeans\incubator-netbeans\nbbuild\build\langtools\src\jdk.compiler\share\classes\com\sun\tools\javac\platform\JDKPlatformProvider.java:80:
>  error: reference to newFileSystem is ambiguous
> try (FileSystem fs = FileSystems.newFileSystem(ctSymFile, null);
>   both method newFileSystem(Path,ClassLoader) in FileSystems and method 
> newFileSystem(Path,Map) in FileSystems match
> D:\netbeans\incubator-netbeans\nbbuild\build\langtools\src\jdk.compiler\share\classes\com\sun\tools\javac\platform\JDKPlatformProvider.java:120:
>  error: reference to newFileSystem is ambiguous
> ctSym2FileSystem.put(file, fs = 
> FileSystems.newFileSystem(file, null));
>   both method newFileSystem(Path,ClassLoader) in FileSystems and method 
> newFileSystem(Path,Map) in FileSystems match{noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
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-4716) Netbeans source will not build under Java 13+ (Ambigous reference)

2020-08-28 Thread Austin Stephens (Jira)


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

Austin Stephens updated NETBEANS-4716:
--
Summary: Netbeans source will not build under Java 13+ (Ambigous reference) 
 (was: Netbeans source will not build under Java 13 (Ambigous reference))

> Netbeans source will not build under Java 13+ (Ambigous reference)
> --
>
> Key: NETBEANS-4716
> URL: https://issues.apache.org/jira/browse/NETBEANS-4716
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - Other
>Affects Versions: 12.0, 12.1
>Reporter: Austin Stephens
>Priority: Major
>
> When attempting to build from netbeans source, I get a compile error when it 
> goes to build langtools. Here are the details:
> {noformat}
> D:\netbeans\incubator-netbeans\nbbuild\build\langtools\src\jdk.compiler\share\classes\com\sun\tools\javac\file\JavacFileManager.java:519:
>  error: reference to newFileSystem is ambiguous
> this.fileSystem = FileSystems.newFileSystem(archivePath, 
> null);
>   both method newFileSystem(Path,ClassLoader) in FileSystems and method 
> newFileSystem(Path,Map) in FileSystems match
> D:\netbeans\incubator-netbeans\nbbuild\build\langtools\src\jdk.compiler\share\classes\com\sun\tools\javac\file\Locations.java:383:
>  error: reference to newFileSystem is ambiguous
> FileSystems.newFileSystem(file, null).close();
>   both method newFileSystem(Path,ClassLoader) in FileSystems and method 
> newFileSystem(Path,Map) in FileSystems match
> D:\netbeans\incubator-netbeans\nbbuild\build\langtools\src\jdk.compiler\share\classes\com\sun\tools\javac\platform\JDKPlatformProvider.java:80:
>  error: reference to newFileSystem is ambiguous
> try (FileSystem fs = FileSystems.newFileSystem(ctSymFile, null);
>   both method newFileSystem(Path,ClassLoader) in FileSystems and method 
> newFileSystem(Path,Map) in FileSystems match
> D:\netbeans\incubator-netbeans\nbbuild\build\langtools\src\jdk.compiler\share\classes\com\sun\tools\javac\platform\JDKPlatformProvider.java:120:
>  error: reference to newFileSystem is ambiguous
> ctSym2FileSystem.put(file, fs = 
> FileSystems.newFileSystem(file, null));
>   both method newFileSystem(Path,ClassLoader) in FileSystems and method 
> newFileSystem(Path,Map) in FileSystems match{noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
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] [Reopened] (NETBEANS-4716) Netbeans source will not build under Java 13+ (Ambigous reference)

2020-08-28 Thread Austin Stephens (Jira)


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

Austin Stephens reopened NETBEANS-4716:
---

I have reproduced this on multiple systems. Check out the release 12 branch, 
run the following git commands:
{noformat}
git reset --hard
git clean -fxd{noformat}
Add the allow Java 9+ property and run ant with Java 13+ (happens on 14 as 
well). It won't build.

> Netbeans source will not build under Java 13+ (Ambigous reference)
> --
>
> Key: NETBEANS-4716
> URL: https://issues.apache.org/jira/browse/NETBEANS-4716
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - Other
>Affects Versions: 12.0, 12.1
>Reporter: Austin Stephens
>Priority: Major
>
> When attempting to build from netbeans source, I get a compile error when it 
> goes to build langtools. Here are the details:
> {noformat}
> D:\netbeans\incubator-netbeans\nbbuild\build\langtools\src\jdk.compiler\share\classes\com\sun\tools\javac\file\JavacFileManager.java:519:
>  error: reference to newFileSystem is ambiguous
> this.fileSystem = FileSystems.newFileSystem(archivePath, 
> null);
>   both method newFileSystem(Path,ClassLoader) in FileSystems and method 
> newFileSystem(Path,Map) in FileSystems match
> D:\netbeans\incubator-netbeans\nbbuild\build\langtools\src\jdk.compiler\share\classes\com\sun\tools\javac\file\Locations.java:383:
>  error: reference to newFileSystem is ambiguous
> FileSystems.newFileSystem(file, null).close();
>   both method newFileSystem(Path,ClassLoader) in FileSystems and method 
> newFileSystem(Path,Map) in FileSystems match
> D:\netbeans\incubator-netbeans\nbbuild\build\langtools\src\jdk.compiler\share\classes\com\sun\tools\javac\platform\JDKPlatformProvider.java:80:
>  error: reference to newFileSystem is ambiguous
> try (FileSystem fs = FileSystems.newFileSystem(ctSymFile, null);
>   both method newFileSystem(Path,ClassLoader) in FileSystems and method 
> newFileSystem(Path,Map) in FileSystems match
> D:\netbeans\incubator-netbeans\nbbuild\build\langtools\src\jdk.compiler\share\classes\com\sun\tools\javac\platform\JDKPlatformProvider.java:120:
>  error: reference to newFileSystem is ambiguous
> ctSym2FileSystem.put(file, fs = 
> FileSystems.newFileSystem(file, null));
>   both method newFileSystem(Path,ClassLoader) in FileSystems and method 
> newFileSystem(Path,Map) in FileSystems match{noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
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-4818) New Module system build-impl.xml doesn't work on windows

2020-09-18 Thread Austin Stephens (Jira)
Austin Stephens created NETBEANS-4818:
-

 Summary: New Module system build-impl.xml doesn't work on windows
 Key: NETBEANS-4818
 URL: https://issues.apache.org/jira/browse/NETBEANS-4818
 Project: NetBeans
  Issue Type: Bug
  Components: java - Compiler
Affects Versions: 12.2
Reporter: Austin Stephens


To fix the issue of Nashorn being removed, someone is having ant compile 
scripts. They apparently did this without using a debugger since they are 
comparing strings with "==" and "!=", which is why it doesn't work on Windows. 
I have fixed it but am too lazy to check it in. Here is the new fixed method as 
it appears in build-impl.xml:
{noformat}
private String toRegexp2(String spec, String filepattern, String separator) 
{
List prefixes = new ArrayList<>();
List suffixes = new ArrayList<>();
pathVariants(spec).forEach(item -> {
suffixes.add(item);
});
String tail = "";
String separatorString = separator;
if ("\\".equals(separatorString)) {
separatorString = "";
}
if (filepattern != null && !filepattern.equals(tail)) {
tail = separatorString + filepattern;
}
return "([^" + separatorString +"]+)\\Q" + separator + "\\E(" + 
suffixes.stream().collect(Collectors.joining("|")) + ")" + tail;
}{noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
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-4818) New Module system build-impl.xml doesn't work on windows

2020-09-18 Thread Austin Stephens (Jira)


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

Austin Stephens updated NETBEANS-4818:
--
Description: 
To fix the issue of Nashorn being removed, someone is having ant compile 
scripts. They apparently did this without using an IDE since they are comparing 
strings with "==" and "!=", which is why it doesn't work on Windows. I have 
fixed it but am too lazy to check it in. Here is the new fixed method as it 
appears in build-impl.xml:
{noformat}
private String toRegexp2(String spec, String filepattern, String separator) 
{
List prefixes = new ArrayList<>();
List suffixes = new ArrayList<>();
pathVariants(spec).forEach(item -> {
suffixes.add(item);
});
String tail = "";
String separatorString = separator;
if ("\\".equals(separatorString)) {
separatorString = "";
}
if (filepattern != null && !filepattern.equals(tail)) {
tail = separatorString + filepattern;
}
return "([^" + separatorString +"]+)\\Q" + separator + "\\E(" + 
suffixes.stream().collect(Collectors.joining("|")) + ")" + tail;
}{noformat}

  was:
To fix the issue of Nashorn being removed, someone is having ant compile 
scripts. They apparently did this without using a debugger since they are 
comparing strings with "==" and "!=", which is why it doesn't work on Windows. 
I have fixed it but am too lazy to check it in. Here is the new fixed method as 
it appears in build-impl.xml:
{noformat}
private String toRegexp2(String spec, String filepattern, String separator) 
{
List prefixes = new ArrayList<>();
List suffixes = new ArrayList<>();
pathVariants(spec).forEach(item -> {
suffixes.add(item);
});
String tail = "";
String separatorString = separator;
if ("\\".equals(separatorString)) {
separatorString = "";
}
if (filepattern != null && !filepattern.equals(tail)) {
tail = separatorString + filepattern;
}
return "([^" + separatorString +"]+)\\Q" + separator + "\\E(" + 
suffixes.stream().collect(Collectors.joining("|")) + ")" + tail;
}{noformat}


> New Module system build-impl.xml doesn't work on windows
> 
>
> Key: NETBEANS-4818
> URL: https://issues.apache.org/jira/browse/NETBEANS-4818
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Compiler
>Affects Versions: 12.2
>Reporter: Austin Stephens
>Priority: Critical
>
> To fix the issue of Nashorn being removed, someone is having ant compile 
> scripts. They apparently did this without using an IDE since they are 
> comparing strings with "==" and "!=", which is why it doesn't work on 
> Windows. I have fixed it but am too lazy to check it in. Here is the new 
> fixed method as it appears in build-impl.xml:
> {noformat}
> private String toRegexp2(String spec, String filepattern, String 
> separator) {
> List prefixes = new ArrayList<>();
> List suffixes = new ArrayList<>();
> pathVariants(spec).forEach(item -> {
> suffixes.add(item);
> });
> String tail = "";
> String separatorString = separator;
> if ("\\".equals(separatorString)) {
> separatorString = "";
> }
> if (filepattern != null && !filepattern.equals(tail)) {
> tail = separatorString + filepattern;
> }
> return "([^" + separatorString +"]+)\\Q" + separator + "\\E(" + 
> suffixes.stream().collect(Collectors.joining("|")) + ")" + tail;
> }{noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
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-4819) Missing support of time-stamp authority in NBM jar signing

2020-09-18 Thread Austin Stephens (Jira)
Austin Stephens created NETBEANS-4819:
-

 Summary: Missing support of time-stamp authority in NBM jar signing
 Key: NETBEANS-4819
 URL: https://issues.apache.org/jira/browse/NETBEANS-4819
 Project: NetBeans
  Issue Type: Bug
  Components: platform - Module System
Affects Versions: 12.1, 12.2
Reporter: Austin Stephens


Apparently this still hasn't been fixed? There is no way to pass a TSA 
(time-stamp authority) url to the Jar signer when building NBM files. [~emi] 
has a post related to this off yonder: 
http://blog.emilianbold.ro/2016/08/signing-netbeans-modules-with-time.html



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
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-4819) Missing support of time-stamp authority in NBM jar signing

2020-10-01 Thread Austin Stephens (Jira)


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

Austin Stephens commented on NETBEANS-4819:
---

Pull request made at https://github.com/apache/netbeans/pull/2413

> Missing support of time-stamp authority in NBM jar signing
> --
>
> Key: NETBEANS-4819
> URL: https://issues.apache.org/jira/browse/NETBEANS-4819
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - Module System
>Affects Versions: 12.1, 12.2
>Reporter: Austin Stephens
>Priority: Major
>
> Apparently this still hasn't been fixed? There is no way to pass a TSA 
> (time-stamp authority) url to the Jar signer when building NBM files. [~emi] 
> has a post related to this off yonder: 
> http://blog.emilianbold.ro/2016/08/signing-netbeans-modules-with-time.html



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
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-4892) Platform installer doesn't consider java 15 valid

2020-10-09 Thread Austin Stephens (Jira)
Austin Stephens created NETBEANS-4892:
-

 Summary: Platform installer doesn't consider java 15 valid
 Key: NETBEANS-4892
 URL: https://issues.apache.org/jira/browse/NETBEANS-4892
 Project: NetBeans
  Issue Type: Bug
  Components: platform - installer
Affects Versions: 12.0, Next, 12.1
Reporter: Austin Stephens


Apparently the method of formatting Java versions has changed at Java 15? I am 
using the AdoptOpenJdk version and it has gone from jdk-14.0.2+12 to jdk-15+32. 
As you could imagine, those two parse differently and `compareVersions` comes 
to the conclusion that "15+32" is less than 15.0.0 (The expected version it 
generates for java 15). This results in any bundle java (or possibly any java 
in general, I haven't tested that yet) from passing the verification test and 
the installer will never find a java to use.

The best work around I can currently think of (other than building your own 
copy of Java 15) is to use Java <=14, which may significantly complicate the 
building process...



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
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-4892) Platform installer doesn't consider java 15 valid

2020-10-09 Thread Austin Stephens (Jira)


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

Austin Stephens updated NETBEANS-4892:
--
Description: 
Apparently the method of formatting Java versions has changed at Java 15? I am 
using the AdoptOpenJdk version and it has gone from jdk-14.0.2+12 to jdk-15+32. 
As you could imagine, those two parse differently and `compareVersions` comes 
to the conclusion that "15+32" is less than 15.0.0 (The expected version it 
generates for java 15). This results in any bundle java (or possibly any java 
in general, I haven't tested that yet) from passing the verification test and 
the installer will never find a java to use.

The best work around I can currently think of (other than building your own 
copy of Java 15) is to use Java <=14, which may significantly complicate the 
building process...

For reference, an easy way to possibly test if your solution fixed the problem 
is to source nbi/engine/native

  was:
Apparently the method of formatting Java versions has changed at Java 15? I am 
using the AdoptOpenJdk version and it has gone from jdk-14.0.2+12 to jdk-15+32. 
As you could imagine, those two parse differently and `compareVersions` comes 
to the conclusion that "15+32" is less than 15.0.0 (The expected version it 
generates for java 15). This results in any bundle java (or possibly any java 
in general, I haven't tested that yet) from passing the verification test and 
the installer will never find a java to use.

The best work around I can currently think of (other than building your own 
copy of Java 15) is to use Java <=14, which may significantly complicate the 
building process...


> Platform installer doesn't consider java 15 valid
> -
>
> Key: NETBEANS-4892
> URL: https://issues.apache.org/jira/browse/NETBEANS-4892
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - installer
>Affects Versions: Next, 12.0, 12.1
>Reporter: Austin Stephens
>Priority: Major
>
> Apparently the method of formatting Java versions has changed at Java 15? I 
> am using the AdoptOpenJdk version and it has gone from jdk-14.0.2+12 to 
> jdk-15+32. As you could imagine, those two parse differently and 
> `compareVersions` comes to the conclusion that "15+32" is less than 15.0.0 
> (The expected version it generates for java 15). This results in any bundle 
> java (or possibly any java in general, I haven't tested that yet) from 
> passing the verification test and the installer will never find a java to use.
> The best work around I can currently think of (other than building your own 
> copy of Java 15) is to use Java <=14, which may significantly complicate the 
> building process...
> For reference, an easy way to possibly test if your solution fixed the 
> problem is to source nbi/engine/native



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
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-4892) Platform installer doesn't consider java 15 valid

2020-10-09 Thread Austin Stephens (Jira)


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

Austin Stephens updated NETBEANS-4892:
--
Environment: 
Unix
Windows?

> Platform installer doesn't consider java 15 valid
> -
>
> Key: NETBEANS-4892
> URL: https://issues.apache.org/jira/browse/NETBEANS-4892
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - installer
>Affects Versions: Next, 12.0, 12.1
> Environment: Unix
> Windows?
>Reporter: Austin Stephens
>Priority: Major
>
> Apparently the method of formatting Java versions has changed at Java 15? I 
> am using the AdoptOpenJdk version and it has gone from jdk-14.0.2+12 to 
> jdk-15+32. As you could imagine, those two parse differently and 
> `compareVersions` comes to the conclusion that "15+32" is less than 15.0.0 
> (The expected version it generates for java 15). This results in any bundle 
> java (or possibly any java in general, I haven't tested that yet) from 
> passing the verification test and the installer will never find a java to use.
> The best work around I can currently think of (other than building your own 
> copy of Java 15) is to use Java <=14, which may significantly complicate the 
> building process...
> For reference, an easy way to possibly test if your solution fixed the 
> problem is to source nbi/engine/native/launcher/unix/src/launcher.sh and run 
> `compareVersions 15+36 15.0.0`
> This bug may also happen on windows, but I haven't checked since the 
> installer is a bit more complicated on windows...



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
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-4892) Platform installer doesn't consider java 15 valid

2020-10-09 Thread Austin Stephens (Jira)


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

Austin Stephens updated NETBEANS-4892:
--
Description: 
Apparently the method of formatting Java versions has changed at Java 15? I am 
using the AdoptOpenJdk version and it has gone from jdk-14.0.2+12 to jdk-15+32. 
As you could imagine, those two parse differently and `compareVersions` comes 
to the conclusion that "15+32" is less than 15.0.0 (The expected version it 
generates for java 15). This results in any bundle java (or possibly any java 
in general, I haven't tested that yet) from passing the verification test and 
the installer will never find a java to use.

The best work around I can currently think of (other than building your own 
copy of Java 15) is to use Java <=14, which may significantly complicate the 
building process...

For reference, an easy way to possibly test if your solution fixed the problem 
is to source nbi/engine/native/launcher/unix/src/launcher.sh and run 
`compareVersions 15+36 15.0.0`

This bug may also happen on windows, but I haven't checked since the installer 
is a bit more complicated on windows...

  was:
Apparently the method of formatting Java versions has changed at Java 15? I am 
using the AdoptOpenJdk version and it has gone from jdk-14.0.2+12 to jdk-15+32. 
As you could imagine, those two parse differently and `compareVersions` comes 
to the conclusion that "15+32" is less than 15.0.0 (The expected version it 
generates for java 15). This results in any bundle java (or possibly any java 
in general, I haven't tested that yet) from passing the verification test and 
the installer will never find a java to use.

The best work around I can currently think of (other than building your own 
copy of Java 15) is to use Java <=14, which may significantly complicate the 
building process...

For reference, an easy way to possibly test if your solution fixed the problem 
is to source nbi/engine/native


> Platform installer doesn't consider java 15 valid
> -
>
> Key: NETBEANS-4892
> URL: https://issues.apache.org/jira/browse/NETBEANS-4892
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - installer
>Affects Versions: Next, 12.0, 12.1
>Reporter: Austin Stephens
>Priority: Major
>
> Apparently the method of formatting Java versions has changed at Java 15? I 
> am using the AdoptOpenJdk version and it has gone from jdk-14.0.2+12 to 
> jdk-15+32. As you could imagine, those two parse differently and 
> `compareVersions` comes to the conclusion that "15+32" is less than 15.0.0 
> (The expected version it generates for java 15). This results in any bundle 
> java (or possibly any java in general, I haven't tested that yet) from 
> passing the verification test and the installer will never find a java to use.
> The best work around I can currently think of (other than building your own 
> copy of Java 15) is to use Java <=14, which may significantly complicate the 
> building process...
> For reference, an easy way to possibly test if your solution fixed the 
> problem is to source nbi/engine/native/launcher/unix/src/launcher.sh and run 
> `compareVersions 15+36 15.0.0`
> This bug may also happen on windows, but I haven't checked since the 
> installer is a bit more complicated on windows...



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
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-4892) Platform installer doesn't consider java 15 valid

2020-10-09 Thread Austin Stephens (Jira)


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

Austin Stephens commented on NETBEANS-4892:
---

Here is a possible workaround in launcher.sh, but it seems a bit hacky. We 
might want a proper fix at some time?

@@ -310,6 +310,7 @@
 formatVersion() {
 formatted=`echo "$1" | sed 
"s/-ea//g;s/-rc[0-9]*//g;s/-beta[0-9]*//g;s/-preview[0-9]*//g;s/-dp[0-9]*//g;s/-alpha[0-9]*//g;s/-fcs//g;s/_/./g;s/-/\./g"`
 formatted=`echo "$formatted" | sed 
"s/^\(\([0-9][0-9]*\)\.\([0-9][0-9]*\)\.\([0-9][0-9]*\)\)\.b\([0-9][0-9]*\)/\1\.0\.\5/g"`
+ formatted=`echo "$formatted" | sed 
"s/^\([0-9][0-9]*\)+\([0-9][0-9]*\)$/\1.0.\2/g"`
 formatted=`echo "$formatted" | sed "s/\.b\([0-9][0-9]*\)/\.\1/g"`
 echo "$formatted"

> Platform installer doesn't consider java 15 valid
> -
>
> Key: NETBEANS-4892
> URL: https://issues.apache.org/jira/browse/NETBEANS-4892
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - installer
>Affects Versions: Next, 12.0, 12.1
> Environment: Unix
> Windows?
>Reporter: Austin Stephens
>Priority: Major
>
> Apparently the method of formatting Java versions has changed at Java 15? I 
> am using the AdoptOpenJdk version and it has gone from jdk-14.0.2+12 to 
> jdk-15+32. As you could imagine, those two parse differently and 
> `compareVersions` comes to the conclusion that "15+32" is less than 15.0.0 
> (The expected version it generates for java 15). This results in any bundle 
> java (or possibly any java in general, I haven't tested that yet) from 
> passing the verification test and the installer will never find a java to use.
> The best work around I can currently think of (other than building your own 
> copy of Java 15) is to use Java <=14, which may significantly complicate the 
> building process...
> For reference, an easy way to possibly test if your solution fixed the 
> problem is to source nbi/engine/native/launcher/unix/src/launcher.sh and run 
> `compareVersions 15+36 15.0.0`
> This bug may also happen on windows, but I haven't checked since the 
> installer is a bit more complicated on windows...



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
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-4892) Platform installer doesn't consider java 15 valid

2020-10-09 Thread Austin Stephens (Jira)


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

Austin Stephens edited comment on NETBEANS-4892 at 10/9/20, 6:56 PM:
-

Here is a possible workaround in launcher.sh, but it seems a bit hacky. We 
might want a proper fix at some time?
{noformat}
@@ -310,6 +310,7 @@
 formatVersion() {
 formatted=`echo "$1" | sed 
"s/-ea//g;s/-rc[0-9]*//g;s/-beta[0-9]*//g;s/-preview[0-9]*//g;s/-dp[0-9]*//g;s/-alpha[0-9]*//g;s/-fcs//g;s/_/./g;s/-/\./g"`
 formatted=`echo "$formatted" | sed 
"s/^\(\([0-9][0-9]*\)\.\([0-9][0-9]*\)\.\([0-9][0-9]*\)\)\.b\([0-9][0-9]*\)/\1\.0\.\5/g"`
+formatted=`echo "$formatted" | sed 
"s/^\([0-9][0-9]*\)+\([0-9][0-9]*\)$/\1.0.\2/g"`
 formatted=`echo "$formatted" | sed "s/\.b\([0-9][0-9]*\)/\.\1/g"`
echo "$formatted"
{noformat}


was (Author: sir intellegence):
Here is a possible workaround in launcher.sh, but it seems a bit hacky. We 
might want a proper fix at some time?

@@ -310,6 +310,7 @@
 formatVersion() {
 formatted=`echo "$1" | sed 
"s/-ea//g;s/-rc[0-9]*//g;s/-beta[0-9]*//g;s/-preview[0-9]*//g;s/-dp[0-9]*//g;s/-alpha[0-9]*//g;s/-fcs//g;s/_/./g;s/-/\./g"`
 formatted=`echo "$formatted" | sed 
"s/^\(\([0-9][0-9]*\)\.\([0-9][0-9]*\)\.\([0-9][0-9]*\)\)\.b\([0-9][0-9]*\)/\1\.0\.\5/g"`
+ formatted=`echo "$formatted" | sed 
"s/^\([0-9][0-9]*\)+\([0-9][0-9]*\)$/\1.0.\2/g"`
 formatted=`echo "$formatted" | sed "s/\.b\([0-9][0-9]*\)/\.\1/g"`
 echo "$formatted"

> Platform installer doesn't consider java 15 valid
> -
>
> Key: NETBEANS-4892
> URL: https://issues.apache.org/jira/browse/NETBEANS-4892
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - installer
>Affects Versions: Next, 12.0, 12.1
> Environment: Unix
> Windows?
>Reporter: Austin Stephens
>Priority: Major
>
> Apparently the method of formatting Java versions has changed at Java 15? I 
> am using the AdoptOpenJdk version and it has gone from jdk-14.0.2+12 to 
> jdk-15+32. As you could imagine, those two parse differently and 
> `compareVersions` comes to the conclusion that "15+32" is less than 15.0.0 
> (The expected version it generates for java 15). This results in any bundle 
> java (or possibly any java in general, I haven't tested that yet) from 
> passing the verification test and the installer will never find a java to use.
> The best work around I can currently think of (other than building your own 
> copy of Java 15) is to use Java <=14, which may significantly complicate the 
> building process...
> For reference, an easy way to possibly test if your solution fixed the 
> problem is to source nbi/engine/native/launcher/unix/src/launcher.sh and run 
> `compareVersions 15+36 15.0.0`
> This bug may also happen on windows, but I haven't checked since the 
> installer is a bit more complicated on windows...



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
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] [Resolved] (NETBEANS-4818) New Module system build-impl.xml doesn't work on windows

2020-10-09 Thread Austin Stephens (Jira)


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

Austin Stephens resolved NETBEANS-4818.
---
Resolution: Fixed

Pull request was accepted

> New Module system build-impl.xml doesn't work on windows
> 
>
> Key: NETBEANS-4818
> URL: https://issues.apache.org/jira/browse/NETBEANS-4818
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Compiler
>Affects Versions: 12.2
>Reporter: Austin Stephens
>Priority: Critical
>  Labels: pull-request-available
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> To fix the issue of Nashorn being removed, someone is having ant compile 
> scripts. They apparently did this without using an IDE since they are 
> comparing strings with "==" and "!=", which is why it doesn't work on 
> Windows. I have fixed it but am too lazy to check it in. Here is the new 
> fixed method as it appears in build-impl.xml:
> {noformat}
> private String toRegexp2(String spec, String filepattern, String 
> separator) {
> List prefixes = new ArrayList<>();
> List suffixes = new ArrayList<>();
> pathVariants(spec).forEach(item -> {
> suffixes.add(item);
> });
> String tail = "";
> String separatorString = separator;
> if ("\\".equals(separatorString)) {
> separatorString = "";
> }
> if (filepattern != null && !filepattern.equals(tail)) {
> tail = separatorString + filepattern;
> }
> return "([^" + separatorString +"]+)\\Q" + separator + "\\E(" + 
> suffixes.stream().collect(Collectors.joining("|")) + ")" + tail;
> }{noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
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] [Resolved] (NETBEANS-4819) Missing support of time-stamp authority in NBM jar signing

2020-10-09 Thread Austin Stephens (Jira)


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

Austin Stephens resolved NETBEANS-4819.
---
Resolution: Fixed

Pull request accepted

> Missing support of time-stamp authority in NBM jar signing
> --
>
> Key: NETBEANS-4819
> URL: https://issues.apache.org/jira/browse/NETBEANS-4819
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - Module System
>Affects Versions: 12.1, 12.2
>Reporter: Austin Stephens
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> Apparently this still hasn't been fixed? There is no way to pass a TSA 
> (time-stamp authority) url to the Jar signer when building NBM files. [~emi] 
> has a post related to this off yonder: 
> http://blog.emilianbold.ro/2016/08/signing-netbeans-modules-with-time.html



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
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-5005) There is no KeyStoreProvider for built in trusted certificates

2020-11-10 Thread Austin Stephens (Jira)
Austin Stephens created NETBEANS-5005:
-

 Summary: There is no KeyStoreProvider for built in trusted 
certificates
 Key: NETBEANS-5005
 URL: https://issues.apache.org/jira/browse/NETBEANS-5005
 Project: NetBeans
  Issue Type: Bug
  Components: platform - Autoupdate
Affects Versions: 12.0, Next, 12.1, 12.2, 12.3
 Environment: All
Reporter: Austin Stephens


Java has a keystore that it uses to verify signatures when it loads classes 
(last I checked) as well for other things. This keystore is not considered when 
checking signatures on nbm files and updates. This results in a properly signed 
jar with a well known certificate root appearing as self signed when doing an 
update. This is rather troubling if one was releasing a platform application 
and was expecting the auto-update logic to consider such things as properly 
signed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
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-5920) org.netbeans.api.java.source.TreeUtilities$5 does not implement method 'abstract java.lang.Object visitSwitchExpression(com.sun.source.tree.SwitchExpressionTree, java.

2021-08-12 Thread Austin Stephens (Jira)
Austin Stephens created NETBEANS-5920:
-

 Summary: org.netbeans.api.java.source.TreeUtilities$5 does not 
implement method 'abstract java.lang.Object 
visitSwitchExpression(com.sun.source.tree.SwitchExpressionTree, 
java.lang.Object)' of interface com.sun.source.tree.TreeVisitor
 Key: NETBEANS-5920
 URL: https://issues.apache.org/jira/browse/NETBEANS-5920
 Project: NetBeans
  Issue Type: Bug
  Components: java - Refactoring
Affects Versions: 12.4
Reporter: Austin Stephens


Error from the refactoring dialog:

 
{noformat}
Module Java Refactoring threw java.lang.AbstractMethodError: Receiver class 
org.netbeans.api.java.source.TreeUtilities$5 does not define or inherit an 
implementation of the resolved method 'abstract java.lang.Object 
visitSwitchExpression(com.sun.source.tree.SwitchExpressionTree, 
java.lang.Object)' of interface com.sun.source.tree.TreeVisitor.. Please report 
a bug against Java Refactoring module and attach your 
var/log/messages.log.{noformat}
All you need to do to break this is to try to refactor->move this method to 
another class

 
{code:java}
private int moveMe(){
String s = "foo";
int num = switch(s){
case "foo" -> 0;
case "bar" -> 1;
default -> -1;
};
return num;
}
{code}
 

 

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
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-5967) The pictures after #6 in the hint tutorial are incorrect

2021-09-01 Thread Austin Stephens (Jira)
Austin Stephens created NETBEANS-5967:
-

 Summary: The pictures after #6 in the hint tutorial are incorrect
 Key: NETBEANS-5967
 URL: https://issues.apache.org/jira/browse/NETBEANS-5967
 Project: NetBeans
  Issue Type: Bug
  Components: website
Reporter: Austin Stephens


Page: [https://netbeans.apache.org/tutorials/nbm-java-hint.html]

The screenshot images after point #6 are completely irrelevant. Is there a 
reason for this?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
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-1129) Add Git worktree support

2021-09-07 Thread Austin Stephens (Jira)


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

Austin Stephens updated NETBEANS-1129:
--
Affects Version/s: 12.5
   12.4

> Add Git worktree support
> 
>
> Key: NETBEANS-1129
> URL: https://issues.apache.org/jira/browse/NETBEANS-1129
> Project: NetBeans
>  Issue Type: Bug
>  Components: versioncontrol - Git
>Affects Versions: 9.0, 12.4, 12.5
>Reporter: Austin Stephens
>Priority: Major
>
> Currently, Netbeans says that all files in a different work-tree are new, 
> even if they are not.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
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



<    1   2   3   >