[jira] [Assigned] (NETBEANS-1675) Java Hint to fix error :different case kinds used in the switch in switch expressions

2018-11-28 Thread vikas kumar prabhakar (JIRA)


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

vikas kumar prabhakar reassigned NETBEANS-1675:
---

Assignee: vikas kumar prabhakar  (was: ARUNAVA SINHA)

> Java Hint to fix error :different case kinds used in the switch in switch 
> expressions
> -
>
> Key: NETBEANS-1675
> URL: https://issues.apache.org/jira/browse/NETBEANS-1675
> Project: NetBeans
>  Issue Type: Improvement
>Reporter: ARUNAVA SINHA
>Assignee: vikas kumar prabhakar
>Priority: Major
>  Labels: NB-JDK12
>
> Code:
> int i=10;
>  final String val = 
>  switch (i) 
>  { 
>  case 1 : break "one"; 
>  case 2 -> "two"; 
>  };
> Error will be displayed in editor 'different case kinds used in the switch' 
> Proposed fix:
> int i=10;
>  final String val = 
>  switch (i) 
>  { 
>  case 1 -> "one"; 
>  case 2 -> "two"; 
>  };
>  



--
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-1761) Fix issues of "Convert switch to rule switch" hints

2018-11-28 Thread vikas kumar prabhakar (JIRA)
vikas kumar prabhakar created NETBEANS-1761:
---

 Summary: Fix issues of "Convert switch to rule switch" hints
 Key: NETBEANS-1761
 URL: https://issues.apache.org/jira/browse/NETBEANS-1761
 Project: NetBeans
  Issue Type: Bug
Reporter: vikas kumar prabhakar
Assignee: vikas kumar prabhakar


Following errors observe while verifying the "Convert switch to rule switch" 
hints
 # Currently it is throwing NullPointer exception while fixing the hints.
 # No hints showing while remove any break statement (i.e //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-635) Surefire 2.19.1 (and later) stacktrace hyperlinks don't work with Maven

2018-11-28 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot updated NETBEANS-635:

Labels: pull-request-available  (was: )

> Surefire 2.19.1 (and later) stacktrace hyperlinks don't work with Maven
> ---
>
> Key: NETBEANS-635
> URL: https://issues.apache.org/jira/browse/NETBEANS-635
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Maven
>Affects Versions: 8.2, 9.0
>Reporter: jmborer
>Priority: Major
>  Labels: pull-request-available
> Attachments: mavenproject3.zip, surefire-2.18.1-.png, 
> surefire-2.19.1-.png, surefire-2.22.1-.png, target-2.18.1.zip, 
> target-2.19.1.zip, target-2.22.1.zip
>
>
> When running tests with surefire 2.19.1, to see the stacktrace, make sure the 
> plugin is configured as following:
> {code:java}
> 
>     org.apache.maven.plugins
>     maven-surefire-plugin
>      2.19.1
>      
>          false
>      
>  {code}
> Then you will see the stacktraces in the output. Even though they are 
> recognized as being hyperlinks, when you click on them, nothing happens and 
> in the status bar of Netbeans it says that the source file cannot be found.
> This works perfectly with surefire 2.18.1. Something changed between these 
> versions.
> Related topics:
> [1] [https://netbeans.org/bugzilla/show_bug.cgi?id=257563]
> [2] [https://netbeans.org/bugzilla/show_bug.cgi?id=222587]
> [3] [https://netbeans.org/bugzilla/show_bug.cgi?id=262207]
>  
>  



--
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-1760) Git blame/annotation customization

2018-11-28 Thread Matthew Dunlap (JIRA)


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

Matthew Dunlap updated NETBEANS-1760:
-
Description: 
My team at [Dataverse|https://dataverse.org/] (open source research data 
repository application) uses Netbeans for development. We lean heavily on the 
"show annotations" feature to navigate our codebase. We've been wanting to do 
more code cleanup but major formatting changes destroy our visible history 
through annotations.

git-blame which underlies this functionality supports a number of flags for 
this sort of problem (ignore whitespaces, moved code, etc). As far as I can 
tell these flags cannot be configured for use by the netbeans integration. Some 
way to add these flags would provide a lot of value to users with large code 
bases.

  was:
My team at Dataverse (open source research data repository application) uses 
Netbeans for development. We lean heavily on the "show annotations" feature to 
navigate our codebase. We've been wanting to do more code cleanup but major 
formatting changes destroy our visible history through annotations.

git-blame which underlies this functionality supports a number of flags for 
this sort of problem (ignore whitespaces, moved code, etc). As far as I can 
tell these flags cannot be configured for use by the netbeans integration. Some 
way to add these flags would provide a lot of value to users with large code 
bases.


> Git blame/annotation customization
> --
>
> Key: NETBEANS-1760
> URL: https://issues.apache.org/jira/browse/NETBEANS-1760
> Project: NetBeans
>  Issue Type: Improvement
>  Components: versioncontrol - Git
>Reporter: Matthew Dunlap
>Priority: Minor
>
> My team at [Dataverse|https://dataverse.org/] (open source research data 
> repository application) uses Netbeans for development. We lean heavily on the 
> "show annotations" feature to navigate our codebase. We've been wanting to do 
> more code cleanup but major formatting changes destroy our visible history 
> through annotations.
> git-blame which underlies this functionality supports a number of flags for 
> this sort of problem (ignore whitespaces, moved code, etc). As far as I can 
> tell these flags cannot be configured for use by the netbeans integration. 
> Some way to add these flags would provide a lot of value to users with large 
> code bases.



--
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-1760) Git blame/annotation customization

2018-11-28 Thread Matthew Dunlap (JIRA)


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

Matthew Dunlap updated NETBEANS-1760:
-
Description: 
My team at [Dataverse|https://dataverse.org/] (open source research data 
repository application) uses Netbeans for development. We lean heavily on the 
"show annotations" feature to navigate our codebase. We've been wanting to do 
more code cleanup but major formatting changes destroy our visible history 
through annotations (the formatting change shows up when we'd rather see the 
last functional change).

[git-blame|https://git-scm.com/docs/git-blame] which underlies this 
functionality supports a number of flags for this sort of problem (ignore 
whitespaces, moved code, etc). As far as I can tell these flags cannot be 
configured for use by the netbeans integration. Some way to add these flags 
would provide a lot of value to users with large code bases.

  was:
My team at [Dataverse|https://dataverse.org/] (open source research data 
repository application) uses Netbeans for development. We lean heavily on the 
"show annotations" feature to navigate our codebase. We've been wanting to do 
more code cleanup but major formatting changes destroy our visible history 
through annotations (the formatting change shows up when we'd rather see the 
last functional change).

git-blame which underlies this functionality supports a number of flags for 
this sort of problem (ignore whitespaces, moved code, etc). As far as I can 
tell these flags cannot be configured for use by the netbeans integration. Some 
way to add these flags would provide a lot of value to users with large code 
bases.


> Git blame/annotation customization
> --
>
> Key: NETBEANS-1760
> URL: https://issues.apache.org/jira/browse/NETBEANS-1760
> Project: NetBeans
>  Issue Type: Improvement
>  Components: versioncontrol - Git
>Reporter: Matthew Dunlap
>Priority: Minor
>
> My team at [Dataverse|https://dataverse.org/] (open source research data 
> repository application) uses Netbeans for development. We lean heavily on the 
> "show annotations" feature to navigate our codebase. We've been wanting to do 
> more code cleanup but major formatting changes destroy our visible history 
> through annotations (the formatting change shows up when we'd rather see the 
> last functional change).
> [git-blame|https://git-scm.com/docs/git-blame] which underlies this 
> functionality supports a number of flags for this sort of problem (ignore 
> whitespaces, moved code, etc). As far as I can tell these flags cannot be 
> configured for use by the netbeans integration. Some way to add these flags 
> would provide a lot of value to users with large code bases.



--
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-1760) Git blame/annotation customization

2018-11-28 Thread Matthew Dunlap (JIRA)


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

Matthew Dunlap updated NETBEANS-1760:
-
Description: 
My team at [Dataverse|https://dataverse.org/] (open source research data 
repository application) uses Netbeans for development. We lean heavily on the 
"show annotations" feature to navigate our codebase. We've been wanting to do 
more code cleanup but major formatting changes destroy our visible history 
through annotations (the formatting change shows up when we'd rather see the 
last functional change).

git-blame which underlies this functionality supports a number of flags for 
this sort of problem (ignore whitespaces, moved code, etc). As far as I can 
tell these flags cannot be configured for use by the netbeans integration. Some 
way to add these flags would provide a lot of value to users with large code 
bases.

  was:
My team at [Dataverse|https://dataverse.org/] (open source research data 
repository application) uses Netbeans for development. We lean heavily on the 
"show annotations" feature to navigate our codebase. We've been wanting to do 
more code cleanup but major formatting changes destroy our visible history 
through annotations.

git-blame which underlies this functionality supports a number of flags for 
this sort of problem (ignore whitespaces, moved code, etc). As far as I can 
tell these flags cannot be configured for use by the netbeans integration. Some 
way to add these flags would provide a lot of value to users with large code 
bases.


> Git blame/annotation customization
> --
>
> Key: NETBEANS-1760
> URL: https://issues.apache.org/jira/browse/NETBEANS-1760
> Project: NetBeans
>  Issue Type: Improvement
>  Components: versioncontrol - Git
>Reporter: Matthew Dunlap
>Priority: Minor
>
> My team at [Dataverse|https://dataverse.org/] (open source research data 
> repository application) uses Netbeans for development. We lean heavily on the 
> "show annotations" feature to navigate our codebase. We've been wanting to do 
> more code cleanup but major formatting changes destroy our visible history 
> through annotations (the formatting change shows up when we'd rather see the 
> last functional change).
> git-blame which underlies this functionality supports a number of flags for 
> this sort of problem (ignore whitespaces, moved code, etc). As far as I can 
> tell these flags cannot be configured for use by the netbeans integration. 
> Some way to add these flags would provide a lot of value to users with large 
> code bases.



--
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-1760) Git blame/annotation customization

2018-11-28 Thread Matthew Dunlap (JIRA)
Matthew Dunlap created NETBEANS-1760:


 Summary: Git blame/annotation customization
 Key: NETBEANS-1760
 URL: https://issues.apache.org/jira/browse/NETBEANS-1760
 Project: NetBeans
  Issue Type: Improvement
  Components: versioncontrol - Git
Reporter: Matthew Dunlap


My team at Dataverse (open source research data repository application) uses 
Netbeans for development. We lean heavily on the "show annotations" feature to 
navigate our codebase. We've been wanting to do more code cleanup but major 
formatting changes destroy our visible history through annotations.

git-blame which underlies this functionality supports a number of flags for 
this sort of problem (ignore whitespaces, moved code, etc). As far as I can 
tell these flags cannot be configured for use by the netbeans integration. Some 
way to add these flags would provide a lot of value to users with large code 
bases.



--
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-503) Please support blade template engine for laravel

2018-11-28 Thread Los Vitaly (JIRA)


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

Los Vitaly commented on NETBEANS-503:
-

I am a humble junior PHP developer who only made first step in IT. I'm just 
using NB, and report bugs :) 

I can't be very helpfully nowadays, so maybe in year or two. 

> Please support blade template engine for laravel
> 
>
> Key: NETBEANS-503
> URL: https://issues.apache.org/jira/browse/NETBEANS-503
> Project: NetBeans
>  Issue Type: Improvement
>  Components: php - Editor, php - Formatting & Indentation
>Affects Versions: Next
>Reporter: Christian Lenz
>Priority: Major
> Attachments: blade-phpstorm.png
>
>
> Atm, NetBeans does not support laravel out of the box, therefore, NetBeans 
> does not support the blade template engine. Blade templates are set to 
> foo.blade.php.
> So therefore, we need a new filetype which has the extension .blade.php and 
> it should support: PHP, Blade Templates, HTML (Don't know whether jade is 
> needed too or not), CSS, JS. See the screenshot from PHPStorm, they already 
> supports Blade.
> Yes it should be possible to have PHP inside too. This is an official 
> statement from the developers:
> *Blade is the simple, yet powerful templating engine provided with Laravel. 
> Unlike other popular PHP templating engines, Blade does not restrict you from 
> using plain PHP code in your views. In fact, all Blade views are compiled 
> into plain PHP code and cached until they are modified, meaning Blade adds 
> essentially zero overhead to your application. Blade view files use the  
> .blade.php file extension and are typically stored in the resources/views 
> directory.*
> The folder is not relevant, it should be possible in every folder. So Syntax 
> highlighting, code completion for each type of the language should be 
> possible in that filetype, like in a normal HTML file.
> Cheers
> Chris



--
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-503) Please support blade template engine for laravel

2018-11-28 Thread Christian Lenz (JIRA)


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

Christian Lenz commented on NETBEANS-503:
-

Here you can read about the workaround: 
https://netbeans.org/bugzilla/show_bug.cgi?id=255675. This is possible to 
setting icons for specific files like package.json or gwt.xml but what happens 
inside of it, I can't tell.

> Please support blade template engine for laravel
> 
>
> Key: NETBEANS-503
> URL: https://issues.apache.org/jira/browse/NETBEANS-503
> Project: NetBeans
>  Issue Type: Improvement
>  Components: php - Editor, php - Formatting & Indentation
>Affects Versions: Next
>Reporter: Christian Lenz
>Priority: Major
> Attachments: blade-phpstorm.png
>
>
> Atm, NetBeans does not support laravel out of the box, therefore, NetBeans 
> does not support the blade template engine. Blade templates are set to 
> foo.blade.php.
> So therefore, we need a new filetype which has the extension .blade.php and 
> it should support: PHP, Blade Templates, HTML (Don't know whether jade is 
> needed too or not), CSS, JS. See the screenshot from PHPStorm, they already 
> supports Blade.
> Yes it should be possible to have PHP inside too. This is an official 
> statement from the developers:
> *Blade is the simple, yet powerful templating engine provided with Laravel. 
> Unlike other popular PHP templating engines, Blade does not restrict you from 
> using plain PHP code in your views. In fact, all Blade views are compiled 
> into plain PHP code and cached until they are modified, meaning Blade adds 
> essentially zero overhead to your application. Blade view files use the  
> .blade.php file extension and are typically stored in the resources/views 
> directory.*
> The folder is not relevant, it should be possible in every folder. So Syntax 
> highlighting, code completion for each type of the language should be 
> possible in that filetype, like in a normal HTML file.
> Cheers
> Chris



--
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-503) Please support blade template engine for laravel

2018-11-28 Thread Christian Lenz (JIRA)


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

Christian Lenz commented on NETBEANS-503:
-

Unforunately, there is no real core team anymore. We, you, jun, me all of us 
are the devs. I wanted to have a look into it too, but I don't know what the 
unexpected behaviour is I thought it could be easy with the workaround of 
searching inside of the name like some others do it for package.json for 
example. But I don't know. The workaround was written in the external ticket 
which I will add soon.

> Please support blade template engine for laravel
> 
>
> Key: NETBEANS-503
> URL: https://issues.apache.org/jira/browse/NETBEANS-503
> Project: NetBeans
>  Issue Type: Improvement
>  Components: php - Editor, php - Formatting & Indentation
>Affects Versions: Next
>Reporter: Christian Lenz
>Priority: Major
> Attachments: blade-phpstorm.png
>
>
> Atm, NetBeans does not support laravel out of the box, therefore, NetBeans 
> does not support the blade template engine. Blade templates are set to 
> foo.blade.php.
> So therefore, we need a new filetype which has the extension .blade.php and 
> it should support: PHP, Blade Templates, HTML (Don't know whether jade is 
> needed too or not), CSS, JS. See the screenshot from PHPStorm, they already 
> supports Blade.
> Yes it should be possible to have PHP inside too. This is an official 
> statement from the developers:
> *Blade is the simple, yet powerful templating engine provided with Laravel. 
> Unlike other popular PHP templating engines, Blade does not restrict you from 
> using plain PHP code in your views. In fact, all Blade views are compiled 
> into plain PHP code and cached until they are modified, meaning Blade adds 
> essentially zero overhead to your application. Blade view files use the  
> .blade.php file extension and are typically stored in the resources/views 
> directory.*
> The folder is not relevant, it should be possible in every folder. So Syntax 
> highlighting, code completion for each type of the language should be 
> possible in that filetype, like in a normal HTML file.
> Cheers
> Chris



--
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-503) Please support blade template engine for laravel

2018-11-28 Thread Los Vitaly (JIRA)


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

Los Vitaly commented on NETBEANS-503:
-

[~junichi11] thank you for your reply. 

So, we have to wait, maybe next year core team have more free time to work on 
it. I understand everybody are busy with new release, fixing bugs, etc 

> Please support blade template engine for laravel
> 
>
> Key: NETBEANS-503
> URL: https://issues.apache.org/jira/browse/NETBEANS-503
> Project: NetBeans
>  Issue Type: Improvement
>  Components: php - Editor, php - Formatting & Indentation
>Affects Versions: Next
>Reporter: Christian Lenz
>Priority: Major
> Attachments: blade-phpstorm.png
>
>
> Atm, NetBeans does not support laravel out of the box, therefore, NetBeans 
> does not support the blade template engine. Blade templates are set to 
> foo.blade.php.
> So therefore, we need a new filetype which has the extension .blade.php and 
> it should support: PHP, Blade Templates, HTML (Don't know whether jade is 
> needed too or not), CSS, JS. See the screenshot from PHPStorm, they already 
> supports Blade.
> Yes it should be possible to have PHP inside too. This is an official 
> statement from the developers:
> *Blade is the simple, yet powerful templating engine provided with Laravel. 
> Unlike other popular PHP templating engines, Blade does not restrict you from 
> using plain PHP code in your views. In fact, all Blade views are compiled 
> into plain PHP code and cached until they are modified, meaning Blade adds 
> essentially zero overhead to your application. Blade view files use the  
> .blade.php file extension and are typically stored in the resources/views 
> directory.*
> The folder is not relevant, it should be possible in every folder. So Syntax 
> highlighting, code completion for each type of the language should be 
> possible in that filetype, like in a normal HTML file.
> Cheers
> Chris



--
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-7) Provide basic editor features (syntax highlighting, braces matching, completion, etc) for more file types

2018-11-28 Thread Christian Lenz (JIRA)


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

Christian Lenz commented on NETBEANS-7:
---

A bit of research, VS Code uses tmLanguages syntax (TextMate). But 
unfortunately there is no repo/page where I can find all supported TextMate 
language files. There is only a list for NotePad++ which is missing Dart, Go, 
Rust, etc. and a list for UltraEdit which is also missing some other languages.

Syntax of the definition files for NPP is XML, for UltraEdit smth else.

> Provide basic editor features (syntax highlighting, braces matching, 
> completion, etc) for more file types
> -
>
> Key: NETBEANS-7
> URL: https://issues.apache.org/jira/browse/NETBEANS-7
> Project: NetBeans
>  Issue Type: Improvement
>  Components: ide - UI
>Reporter: Emilian Bold
>Priority: Major
>
> We could provide basic editor features (syntax highlighting, braces matching, 
> completion, etc) for more languages based on the existing corpus of 
> definitions from other editors/IDEs. See
> * 
> http://docs.notepad-plus-plus.org/index.php?title=User_Defined_Language_Files
> * http://docs.sublimetext.info/en/latest/extensibility/syntaxdefs.html
> * https://code.visualstudio.com/docs/extensionAPI/language-support
> * http://www.ultraedit.com/downloads/extras/wordfiles.html#wordfiles
> The basic editor features would usually get replaced once more proper plugins 
> are installed for a given language.
> We could even introduce a mechanism to promote to users the full plugins 
> (from the Plugin Portal, etc) once they start editing given file types.



--
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-1757) C++ switching source/header or declaration/definition does not work for implementations in separate included headers

2018-11-28 Thread Sergey Dyachenko (JIRA)


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

Sergey Dyachenko commented on NETBEANS-1757:


Note: going from foo_func declaration  in *"foo.h"* to foo_func implementation 
in *"foo_inl.h"* (included from *"foo.h"* only) with Ctrl+Click works in fact.

But the inverse navigation (from implementation to declaration) does not work 
as I said before.

And switching between these 2 files as between source/header also does not work.

 

> C++ switching source/header or declaration/definition does not work for 
> implementations in separate included headers
> 
>
> Key: NETBEANS-1757
> URL: https://issues.apache.org/jira/browse/NETBEANS-1757
> Project: NetBeans
>  Issue Type: Bug
>  Components: cnd - Code Model, cnd - Editor, cnd - Navigation, cnd - 
> Other
>Affects Versions: 8.2
>Reporter: Sergey Dyachenko
>Priority: Major
>
> C++ switching source/header or declaration/definition does not work for 
> implementations in separate included headers.
> Consider the following pattern rather common for template declarations and 
> implementations. At least this pattern is quite common in our source code.
> *"foo.h"* (normal header included from source files):
> {code:java}
> // declaration
> template <...>
> void foo_func(...);
> // implementation in separate header included from here
> #include "foo_inl.h"
> {code}
> *"foo_inl.h"* (for internal usage only):
> {code:java}
> // implementation
> template <...>
> void foo_func(...)
> {
> ...
> }
> {code}
> If you try to switch between these 2 files as between source/header: that 
> doesn't work.
> If you try to switch between foo_func declaration / implementation with 
> Ctrl+Click: that doesn't work.
> In fact I do not know any convenient way to navigate between foo_func 
> declaration and implementation in NetBeans C++.
> *Note:* for example, both ways mentioned  above work OK in Eclipse CDT 
> without any additional setup.
>  
>  



--
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-48) Please support horizontal scrolling

2018-11-28 Thread Christian Lenz (JIRA)


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

Christian Lenz resolved NETBEANS-48.

Resolution: Fixed

As mentioned before, it is working as expected with JDK > 9.

> Please support horizontal scrolling
> ---
>
> Key: NETBEANS-48
> URL: https://issues.apache.org/jira/browse/NETBEANS-48
> Project: NetBeans
>  Issue Type: Improvement
>  Components: platform - Window System
>Affects Versions: 8.2, Next
>Reporter: Christian Lenz
>Priority: Major
> Fix For: 9.0
>
>
> I use a touchpad each time and in some areas or most of the time, it is 
> possible to hit shift and scroll up and down to scroll horizontal. So it is 
> ok but not really intuitive. In browsers we don't need to hit an extra key 
> for that. As I wrote it here: 
> https://netbeans.org/bugzilla/show_bug.cgi?id=249339 it is still possible in 
> WebStorm, because of the question, does it work in other Java applications. 
> If WebStorm was written in Java than yes, it works there. So it should work 
> everywhere, when I swipe my fingers from the left to the right or vice versa, 
> it should scroll horizontally. W/o any extra key.
> Regards
> Chris



--
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-1759) After migrating to NetBeans 9 it is unable to find the SVN client

2018-11-28 Thread Marcus Walla (JIRA)


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

Marcus Walla commented on NETBEANS-1759:


Seem to be duplicated with number 771 
(https://issues.apache.org/jira/browse/NETBEANS-771) (found under a question of 
YoYo in StackOverflow, 
[https://stackoverflow.com/questions/53163895/netbeans-9-svn-support-broken-on-macos|https://stackoverflow.com/questions/53163895/netbeans-9-svn-support-broken-on-macos).]
 ). You can therefor merge this report.

> After migrating to NetBeans 9 it is unable to find the SVN client
> -
>
> Key: NETBEANS-1759
> URL: https://issues.apache.org/jira/browse/NETBEANS-1759
> Project: NetBeans
>  Issue Type: Bug
>  Components: versioncontrol - Subversion
>Affects Versions: 9.0
> Environment: Model Name:  MacBook Pro
>   Model Identifier:   MacBookPro8,2
>   Processor Name: Intel Core i7
>   Processor Speed:2 GHz
>   Number of Processors:   1
>   Total Number of Cores:  4
>   L2 Cache (per Core):256 KB
>   L3 Cache:   6 MB
>   Memory: 16 GB
> System Version:   macOS 10.13.6 (17G3025)
>   Kernel Version: Darwin 17.7.0
>Reporter: Marcus Walla
>Priority: Minor
> Fix For: 9.0
>
> Attachments: Screen Shot 2018-11-28 at 12.45.28.png, Screen Shot 
> 2018-11-28 at 12.55.57.png, netbeans_9_ide.log
>
>
> Note: for the previous NetBeans 8.2 there exists checked out project from a 
> subversion repository. As version control plugin SvnKit is used 
> (org.netbeans.libs.svnClientAdapter.svnkit/1 [1.24.1 201609300101]).
> - fresh download and installation of NetBeans 9. Used the script of Carl J. 
> Mosca from github ([https://github.com/carljmosca/netbeans-macos-bundle,] 
> install.sh)
> - start NetBeans 9.
> - requires to migrated the configuration from 8.2 to 9, which I did:
> xxx@xxx:~$ ls -l ~/Library/Application\ Support/NetBeans/
> total 7824
> drwxr-xr-x 15 walla 3536 480 Nov 28 09:52 8.2
> drwxr-xr-x 8 walla 3536 256 Nov 28 10:27 9.0
> - then a window pops up and asks to install the nb-javac library which is 
> highly recommended by the NetBeans team. So, library installed.
> - after a restart NetBeans found in the previous version plugins which can be 
> imported to NetBeans 9. One module is Subversion remote plugin 
> org.netbeans.modules.subversion.remote. All of the previous plugins are 
> imported to version 9, including the Subversion remote plugin.
> - after a second restart NetBeans 9 claims in the IDE log file about 
> subversion mismatches: 
> INFO [org.netbeans.libs.svnclientadapter]: Javahl client adapter is not 
> available
> Failed to load JavaHL Library.
> These are the errors that were encountered:
> no libsvnjavahl-1 in java.library.path
> no svnjavahl-1 in java.library.path
> no svnjavahl in java.library.path
> ...
> INFO [org.netbeans.modules.subversion.client.SvnClientFactory]: JavaHL not 
> available. Falling back on SvnKit.
> INFO [org.netbeans.modules.subversion.client.SvnClientFactory]: SvnKit not 
> available. Falling back on commandline.
> INFO [org.netbeans.modules.subversion]: Commandline client version: *1.10.0 
> (r1827917)*
> WARNING [org.netbeans.modules.subversion]: Unsupported svn version. *You need 
> >= 1.5*
> WARNING [org.netbeans.modules.subversion.client.SvnClientFactory]: executable 
> binary path set to /usr/bin yet client not available.
> - on my drive svn is installed and usable:
> walla@mcsmcwalla:~$ which svn
> */usr/bin*/svn
> walla@mcsmcwalla:~$ ls -l $(which svn)
> -rwxr-xr-x 1 root wheel 18288 Jul 4 13:02 /usr/bin/svn
> walla@mcsmcwalla:~$ svn --version
> svn, version *1.10.0 (r1827917)*
>  compiled Sep 25 2018, 18:25:22 on x86_64-apple-darwin17.0.0
> ...
>  
> We can see in the log snippet that the version on my drive is equal to the 
> one which NetBeans found. However, NetBeans claims that the version is 
> incorrect or did not find the client at all. 
> Can somebody comment on this?
> Best regards, Marcus



--
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-635) Surefire 2.19.1 (and later) stacktrace hyperlinks don't work with Maven

2018-11-28 Thread jmborer (JIRA)


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

jmborer edited comment on NETBEANS-635 at 11/28/18 12:09 PM:
-

There are several issues to properly handle the surefire plugin output

Since Surefire 2.19 the line which specifies the output directory (see below) 
is no longer printed:
{noformat}
Surefire report directory: {noformat}
 There is a fallback method to find the reports by trying to parse a line like:
{noformat}
--- maven-surefire-plugin:2.18.1:test (default-test) @ mavenproject3 ---
{noformat}
 which then uses the test name to find the report file name. However the 
regular expression is flawed: it will skip the line above because of the third 
digit: 
{noformat}
^---\smaven-surefire-plugin:\d+\.\d+:test\s.*$ {noformat}
 should be replaced by:  

{{^---\smaven-surefire-plugin:\d+(?:.\d+)+:test\s.*$}}

 However this fallback method won't work either, because depending on the Maven 
settings, the output will be prefixed with the log level (for example [INFO]) 
that will break the matching. It must improved further to take this into 
account:

{{.*---\smaven-surefire-plugin:\d+(?:.\d+)+:test\s.$}}

By looking into the surefire code, it is possible to have the "Surefire report 
directory" line appear again by using the "-e" argument for Maven. However, 
this will produce more output and is not what most users would expect: 
{noformat}
C:\Users\borerjc\NetBeansProjects\mavenproject3>mvn -e install
 [INFO] Error stacktraces are turned on.
 [INFO] Scanning for projects...
 [INFO]
 [INFO] < ch.skyguide.crystal:mavenproject3 >-
 [INFO] Building mavenproject3 6.0-SNAPSHOT
 [INFO] ---[ jar ]
 [INFO]
 [INFO] — maven-resources-plugin:2.6:resources (default-resources) @ 
mavenproject3 —
 [INFO] Using 'UTF-8' encoding to copy filtered resources.
 [INFO] skip non existing resourceDirectory 
C:\Users\borerjc\NetBeansProjects\mavenproject3\src\main\resources
 [INFO]
 [INFO] — maven-compiler-plugin:3.1:compile (default-compile) @ mavenproject3 —
 [INFO] Nothing to compile - all classes are up to date
 [INFO]
 [INFO] — maven-resources-plugin:2.6:testResources (default-testResources) @ 
mavenproject3 —
 [INFO] Using 'UTF-8' encoding to copy filtered resources.
 [INFO] skip non existing resourceDirectory 
C:\Users\borerjc\NetBeansProjects\mavenproject3\src\test\resources
 [INFO]
 [INFO] — maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
mavenproject3 —
 [INFO] Nothing to compile - all classes are up to date
 [INFO]
 [INFO] — maven-surefire-plugin:2.22.1:test (default-test) @ mavenproject3 —
 [INFO] Surefire report directory: 
C:\Users\borerjc\NetBeansProjects\mavenproject3\target\surefire-reports
 [INFO]
 [INFO] ---
 [INFO] T E S T S
 [INFO] ---
 [INFO] Running ch.skyguide.crystal.mavenproject3.TestTest
 [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.042 
s <<< FAILURE! - in ch.skyguide.crystal.mavenproject3.TestTest
 [ERROR] testSomeMethod(ch.skyguide.crystal.mavenproject3.TestTest) Time 
elapsed: 0.006 s <<< FAILURE!
 java.lang.AssertionError: dummy message
 at org.junit.Assert.fail(Assert.java:88)
 at ch.skyguide.crystal.mavenproject3.TestTest.testSomeMethod(TestTest.java:22)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
 at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:498)
 at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
 at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
 at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
 at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
 at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
 at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
 at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
 at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
 at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
 at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
 at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
 at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
 at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
 at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
 at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4

[jira] [Comment Edited] (NETBEANS-635) Surefire 2.19.1 (and later) stacktrace hyperlinks don't work with Maven

2018-11-28 Thread jmborer (JIRA)


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

jmborer edited comment on NETBEANS-635 at 11/28/18 12:10 PM:
-

There are several issues to properly handle the surefire plugin output

Since Surefire 2.19 the line which specifies the output directory (see below) 
is no longer printed:
{noformat}
Surefire report directory: {noformat}
 There is a fallback method to find the reports by trying to parse a line like:
{noformat}
--- maven-surefire-plugin:2.18.1:test (default-test) @ mavenproject3 ---
{noformat}
 which then uses the test name to find the report file name. However the 
regular expression is flawed: it will skip the line above because of the third 
digit: 
{noformat}
^---\smaven-surefire-plugin:\d+\.\d+:test\s.*$ {noformat}
 should be replaced by:  

{{^---\smaven-surefire-plugin:\d+(?:.\d+)+:test\s.*$}}

 However this fallback method won't work either, because depending on the Maven 
settings, the output will be prefixed with the log level (for example [INFO]) 
that will break the matching. It must improved further to take this into 
account:

{{.*---\smaven-surefire-plugin:\d+(?:.\d+)+:test\s.$}}

By looking into the surefire code, it is possible to have the "Surefire report 
directory" line appear again by using the "-e" argument for Maven. However, 
this will produce additional output and is not what most users would expect (a 
clutted or too detailed report): 
{noformat}
C:\Users\borerjc\NetBeansProjects\mavenproject3>mvn -e install
 [INFO] Error stacktraces are turned on.
 [INFO] Scanning for projects...
 [INFO]
 [INFO] < ch.skyguide.crystal:mavenproject3 >-
 [INFO] Building mavenproject3 6.0-SNAPSHOT
 [INFO] ---[ jar ]
 [INFO]
 [INFO] — maven-resources-plugin:2.6:resources (default-resources) @ 
mavenproject3 —
 [INFO] Using 'UTF-8' encoding to copy filtered resources.
 [INFO] skip non existing resourceDirectory 
C:\Users\borerjc\NetBeansProjects\mavenproject3\src\main\resources
 [INFO]
 [INFO] — maven-compiler-plugin:3.1:compile (default-compile) @ mavenproject3 —
 [INFO] Nothing to compile - all classes are up to date
 [INFO]
 [INFO] — maven-resources-plugin:2.6:testResources (default-testResources) @ 
mavenproject3 —
 [INFO] Using 'UTF-8' encoding to copy filtered resources.
 [INFO] skip non existing resourceDirectory 
C:\Users\borerjc\NetBeansProjects\mavenproject3\src\test\resources
 [INFO]
 [INFO] — maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
mavenproject3 —
 [INFO] Nothing to compile - all classes are up to date
 [INFO]
 [INFO] — maven-surefire-plugin:2.22.1:test (default-test) @ mavenproject3 —
 [INFO] Surefire report directory: 
C:\Users\borerjc\NetBeansProjects\mavenproject3\target\surefire-reports
 [INFO]
 [INFO] ---
 [INFO] T E S T S
 [INFO] ---
 [INFO] Running ch.skyguide.crystal.mavenproject3.TestTest
 [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.042 
s <<< FAILURE! - in ch.skyguide.crystal.mavenproject3.TestTest
 [ERROR] testSomeMethod(ch.skyguide.crystal.mavenproject3.TestTest) Time 
elapsed: 0.006 s <<< FAILURE!
 java.lang.AssertionError: dummy message
 at org.junit.Assert.fail(Assert.java:88)
 at ch.skyguide.crystal.mavenproject3.TestTest.testSomeMethod(TestTest.java:22)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
 at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:498)
 at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
 at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
 at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
 at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
 at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
 at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
 at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
 at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
 at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
 at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
 at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
 at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
 at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
 at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
 at 
org.apache.maven.surefire.jun

[jira] [Comment Edited] (NETBEANS-635) Surefire 2.19.1 (and later) stacktrace hyperlinks don't work with Maven

2018-11-28 Thread jmborer (JIRA)


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

jmborer edited comment on NETBEANS-635 at 11/28/18 12:09 PM:
-

There are several issues to properly handle the surefire plugin output

Since Surefire 2.19 the line which specifies the output directory (see below) 
is no longer printed:
{noformat}
Surefire report directory: {noformat}
 There is a fallback method to find the reports by trying to parse a line like:
{noformat}
--- maven-surefire-plugin:2.18.1:test (default-test) @ mavenproject3 ---
{noformat}
 which then uses the test name to find the report file name. However the 
regular expression is flawed: it will skip the line above because of the third 
digit: 
{noformat}
^---\smaven-surefire-plugin:\d+\.\d+:test\s.*$ {noformat}
 should be replaced by:  
{{^---\smaven-surefire-plugin:\d+(?:.\d+)+:test\s.*$}}
 However this fallback method won't work either, because depending on the Maven 
settings, the output will be prefixed with the log level (for example [INFO]) 
that will break the matching. It must improved further to take this into 
account:
{code:java}
 {code}
^.---\smaven-surefire-plugin:\d+(?:.\d+)+:test\s.${code}

By looking into the surefire code, it is possible to have the "Surefire report 
directory" line appear again by using the "-e" argument for Maven. However, 
this will produce more output and is not what most users would expect: 
{noformat}
C:\Users\borerjc\NetBeansProjects\mavenproject3>mvn -e install
 [INFO] Error stacktraces are turned on.
 [INFO] Scanning for projects...
 [INFO]
 [INFO] < ch.skyguide.crystal:mavenproject3 >-
 [INFO] Building mavenproject3 6.0-SNAPSHOT
 [INFO] ---[ jar ]
 [INFO]
 [INFO] — maven-resources-plugin:2.6:resources (default-resources) @ 
mavenproject3 —
 [INFO] Using 'UTF-8' encoding to copy filtered resources.
 [INFO] skip non existing resourceDirectory 
C:\Users\borerjc\NetBeansProjects\mavenproject3\src\main\resources
 [INFO]
 [INFO] — maven-compiler-plugin:3.1:compile (default-compile) @ mavenproject3 —
 [INFO] Nothing to compile - all classes are up to date
 [INFO]
 [INFO] — maven-resources-plugin:2.6:testResources (default-testResources) @ 
mavenproject3 —
 [INFO] Using 'UTF-8' encoding to copy filtered resources.
 [INFO] skip non existing resourceDirectory 
C:\Users\borerjc\NetBeansProjects\mavenproject3\src\test\resources
 [INFO]
 [INFO] — maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
mavenproject3 —
 [INFO] Nothing to compile - all classes are up to date
 [INFO]
 [INFO] — maven-surefire-plugin:2.22.1:test (default-test) @ mavenproject3 —
 [INFO] Surefire report directory: 
C:\Users\borerjc\NetBeansProjects\mavenproject3\target\surefire-reports
 [INFO]
 [INFO] ---
 [INFO] T E S T S
 [INFO] ---
 [INFO] Running ch.skyguide.crystal.mavenproject3.TestTest
 [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.042 
s <<< FAILURE! - in ch.skyguide.crystal.mavenproject3.TestTest
 [ERROR] testSomeMethod(ch.skyguide.crystal.mavenproject3.TestTest) Time 
elapsed: 0.006 s <<< FAILURE!
 java.lang.AssertionError: dummy message
 at org.junit.Assert.fail(Assert.java:88)
 at ch.skyguide.crystal.mavenproject3.TestTest.testSomeMethod(TestTest.java:22)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
 at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:498)
 at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
 at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
 at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
 at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
 at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
 at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
 at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
 at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
 at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
 at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
 at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
 at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
 at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
 at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
 at 
org.apache.maven.surefire.junit4.JUnit4Provider.exec

[jira] [Comment Edited] (NETBEANS-635) Surefire 2.19.1 (and later) stacktrace hyperlinks don't work with Maven

2018-11-28 Thread jmborer (JIRA)


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

jmborer edited comment on NETBEANS-635 at 11/28/18 12:01 PM:
-

There are several issues to properly handle the surefire plugin output

Since Surefire 2.19 the line which specifies the output directory (see below) 
is no longer printed:
{noformat}
Surefire report directory: {noformat}
 There is a fallback method to find the reports by trying to parse a line like:
{noformat}
--- maven-surefire-plugin:2.18.1:test (default-test) @ mavenproject3 ---
{noformat}
 which then uses the test name to find the report file name. However the 
regular expression is flawed: it will skip the line above because of the third 
digit: 
^---\smaven-surefire-plugin:\d+\.\d+:test\s.*$ 
 should be replaced by:  
^---\smaven-surefire-plugin:\d+(?:.\d+)+:test\s.*$
However this fallback method won't work either, because depending on the Maven 
settings, the output will be prefixed with the log level (for example [INFO]) 
that will break the matching. It must improved further to take this into 
account:
 ^.---\smaven-surefire-plugin:\d+(?:.\d+)+:test\s.$
 By looking into the surefire code, it is possible to have the "Surefire report 
directory" line appear again by using the "-e" argument for Maven. However, 
this will produce more output and is not what most users would expect: 
{noformat}
C:\Users\borerjc\NetBeansProjects\mavenproject3>mvn -e install
 [INFO] Error stacktraces are turned on.
 [INFO] Scanning for projects...
 [INFO]
 [INFO] < ch.skyguide.crystal:mavenproject3 >-
 [INFO] Building mavenproject3 6.0-SNAPSHOT
 [INFO] ---[ jar ]
 [INFO]
 [INFO] — maven-resources-plugin:2.6:resources (default-resources) @ 
mavenproject3 —
 [INFO] Using 'UTF-8' encoding to copy filtered resources.
 [INFO] skip non existing resourceDirectory 
C:\Users\borerjc\NetBeansProjects\mavenproject3\src\main\resources
 [INFO]
 [INFO] — maven-compiler-plugin:3.1:compile (default-compile) @ mavenproject3 —
 [INFO] Nothing to compile - all classes are up to date
 [INFO]
 [INFO] — maven-resources-plugin:2.6:testResources (default-testResources) @ 
mavenproject3 —
 [INFO] Using 'UTF-8' encoding to copy filtered resources.
 [INFO] skip non existing resourceDirectory 
C:\Users\borerjc\NetBeansProjects\mavenproject3\src\test\resources
 [INFO]
 [INFO] — maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
mavenproject3 —
 [INFO] Nothing to compile - all classes are up to date
 [INFO]
 [INFO] — maven-surefire-plugin:2.22.1:test (default-test) @ mavenproject3 —
 [INFO] Surefire report directory: 
C:\Users\borerjc\NetBeansProjects\mavenproject3\target\surefire-reports
 [INFO]
 [INFO] ---
 [INFO] T E S T S
 [INFO] ---
 [INFO] Running ch.skyguide.crystal.mavenproject3.TestTest
 [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.042 
s <<< FAILURE! - in ch.skyguide.crystal.mavenproject3.TestTest
 [ERROR] testSomeMethod(ch.skyguide.crystal.mavenproject3.TestTest) Time 
elapsed: 0.006 s <<< FAILURE!
 java.lang.AssertionError: dummy message
 at org.junit.Assert.fail(Assert.java:88)
 at ch.skyguide.crystal.mavenproject3.TestTest.testSomeMethod(TestTest.java:22)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
 at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:498)
 at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
 at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
 at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
 at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
 at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
 at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
 at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
 at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
 at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
 at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
 at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
 at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
 at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
 at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
 at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
 at 
org.apac

[jira] [Comment Edited] (NETBEANS-635) Surefire 2.19.1 (and later) stacktrace hyperlinks don't work with Maven

2018-11-28 Thread jmborer (JIRA)


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

jmborer edited comment on NETBEANS-635 at 11/28/18 12:07 PM:
-

There are several issues to properly handle the surefire plugin output

Since Surefire 2.19 the line which specifies the output directory (see below) 
is no longer printed:
{noformat}
Surefire report directory: {noformat}
 There is a fallback method to find the reports by trying to parse a line like:
{noformat}
--- maven-surefire-plugin:2.18.1:test (default-test) @ mavenproject3 ---
{noformat}
 which then uses the test name to find the report file name. However the 
regular expression is flawed: it will skip the line above because of the third 
digit: 
{noformat}
^---\smaven-surefire-plugin:\d+\.\d+:test\s.*$ {noformat}
 should be replaced by:  
{code:java}
^---\smaven-surefire-plugin:\d+(?:.\d+)+:test\s.*${code}
However this fallback method won't work either, because depending on the Maven 
settings, the output will be prefixed with the log level (for example [INFO]) 
that will break the matching. It must improved further to take this into 
account:
{code:java}
^.---\smaven-surefire-plugin:\d+(?:.\d+)+:test\s.${code}

 By looking into the surefire code, it is possible to have the "Surefire report 
directory" line appear again by using the "-e" argument for Maven. However, 
this will produce more output and is not what most users would expect: 
{noformat}
C:\Users\borerjc\NetBeansProjects\mavenproject3>mvn -e install
 [INFO] Error stacktraces are turned on.
 [INFO] Scanning for projects...
 [INFO]
 [INFO] < ch.skyguide.crystal:mavenproject3 >-
 [INFO] Building mavenproject3 6.0-SNAPSHOT
 [INFO] ---[ jar ]
 [INFO]
 [INFO] — maven-resources-plugin:2.6:resources (default-resources) @ 
mavenproject3 —
 [INFO] Using 'UTF-8' encoding to copy filtered resources.
 [INFO] skip non existing resourceDirectory 
C:\Users\borerjc\NetBeansProjects\mavenproject3\src\main\resources
 [INFO]
 [INFO] — maven-compiler-plugin:3.1:compile (default-compile) @ mavenproject3 —
 [INFO] Nothing to compile - all classes are up to date
 [INFO]
 [INFO] — maven-resources-plugin:2.6:testResources (default-testResources) @ 
mavenproject3 —
 [INFO] Using 'UTF-8' encoding to copy filtered resources.
 [INFO] skip non existing resourceDirectory 
C:\Users\borerjc\NetBeansProjects\mavenproject3\src\test\resources
 [INFO]
 [INFO] — maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
mavenproject3 —
 [INFO] Nothing to compile - all classes are up to date
 [INFO]
 [INFO] — maven-surefire-plugin:2.22.1:test (default-test) @ mavenproject3 —
 [INFO] Surefire report directory: 
C:\Users\borerjc\NetBeansProjects\mavenproject3\target\surefire-reports
 [INFO]
 [INFO] ---
 [INFO] T E S T S
 [INFO] ---
 [INFO] Running ch.skyguide.crystal.mavenproject3.TestTest
 [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.042 
s <<< FAILURE! - in ch.skyguide.crystal.mavenproject3.TestTest
 [ERROR] testSomeMethod(ch.skyguide.crystal.mavenproject3.TestTest) Time 
elapsed: 0.006 s <<< FAILURE!
 java.lang.AssertionError: dummy message
 at org.junit.Assert.fail(Assert.java:88)
 at ch.skyguide.crystal.mavenproject3.TestTest.testSomeMethod(TestTest.java:22)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
 at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:498)
 at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
 at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
 at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
 at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
 at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
 at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
 at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
 at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
 at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
 at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
 at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
 at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
 at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
 at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
 at 
org.apache.maven.surefire.junit4.JUnit4Provide

[jira] [Comment Edited] (NETBEANS-635) Surefire 2.19.1 (and later) stacktrace hyperlinks don't work with Maven

2018-11-28 Thread jmborer (JIRA)


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

jmborer edited comment on NETBEANS-635 at 11/28/18 12:02 PM:
-

There are several issues to properly handle the surefire plugin output

Since Surefire 2.19 the line which specifies the output directory (see below) 
is no longer printed:
{noformat}
Surefire report directory: {noformat}
 There is a fallback method to find the reports by trying to parse a line like:
{noformat}
--- maven-surefire-plugin:2.18.1:test (default-test) @ mavenproject3 ---
{noformat}
 which then uses the test name to find the report file name. However the 
regular expression is flawed: it will skip the line above because of the third 
digit: 
{noformat}
^---\smaven-surefire-plugin:\d+\.\d+:test\s.*$ {noformat}
 should be replaced by:  
{noformat}
^---\smaven-surefire-plugin:\d+(?:.\d+)+:test\s.*${noformat}

 However this fallback method won't work either, because depending on the Maven 
settings, the output will be prefixed with the log level (for example [INFO]) 
that will break the matching. It must improved further to take this into 
account:
 ^.---\smaven-surefire-plugin:\d+(?:.\d+)+:test\s.$
 By looking into the surefire code, it is possible to have the "Surefire report 
directory" line appear again by using the "-e" argument for Maven. However, 
this will produce more output and is not what most users would expect: 
{noformat}
C:\Users\borerjc\NetBeansProjects\mavenproject3>mvn -e install
 [INFO] Error stacktraces are turned on.
 [INFO] Scanning for projects...
 [INFO]
 [INFO] < ch.skyguide.crystal:mavenproject3 >-
 [INFO] Building mavenproject3 6.0-SNAPSHOT
 [INFO] ---[ jar ]
 [INFO]
 [INFO] — maven-resources-plugin:2.6:resources (default-resources) @ 
mavenproject3 —
 [INFO] Using 'UTF-8' encoding to copy filtered resources.
 [INFO] skip non existing resourceDirectory 
C:\Users\borerjc\NetBeansProjects\mavenproject3\src\main\resources
 [INFO]
 [INFO] — maven-compiler-plugin:3.1:compile (default-compile) @ mavenproject3 —
 [INFO] Nothing to compile - all classes are up to date
 [INFO]
 [INFO] — maven-resources-plugin:2.6:testResources (default-testResources) @ 
mavenproject3 —
 [INFO] Using 'UTF-8' encoding to copy filtered resources.
 [INFO] skip non existing resourceDirectory 
C:\Users\borerjc\NetBeansProjects\mavenproject3\src\test\resources
 [INFO]
 [INFO] — maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
mavenproject3 —
 [INFO] Nothing to compile - all classes are up to date
 [INFO]
 [INFO] — maven-surefire-plugin:2.22.1:test (default-test) @ mavenproject3 —
 [INFO] Surefire report directory: 
C:\Users\borerjc\NetBeansProjects\mavenproject3\target\surefire-reports
 [INFO]
 [INFO] ---
 [INFO] T E S T S
 [INFO] ---
 [INFO] Running ch.skyguide.crystal.mavenproject3.TestTest
 [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.042 
s <<< FAILURE! - in ch.skyguide.crystal.mavenproject3.TestTest
 [ERROR] testSomeMethod(ch.skyguide.crystal.mavenproject3.TestTest) Time 
elapsed: 0.006 s <<< FAILURE!
 java.lang.AssertionError: dummy message
 at org.junit.Assert.fail(Assert.java:88)
 at ch.skyguide.crystal.mavenproject3.TestTest.testSomeMethod(TestTest.java:22)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
 at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:498)
 at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
 at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
 at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
 at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
 at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
 at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
 at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
 at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
 at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
 at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
 at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
 at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
 at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
 at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
 at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeWith

[jira] [Comment Edited] (NETBEANS-635) Surefire 2.19.1 (and later) stacktrace hyperlinks don't work with Maven

2018-11-28 Thread jmborer (JIRA)


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

jmborer edited comment on NETBEANS-635 at 11/28/18 12:02 PM:
-

There are several issues to properly handle the surefire plugin output

Since Surefire 2.19 the line which specifies the output directory (see below) 
is no longer printed:
{noformat}
Surefire report directory: {noformat}
 There is a fallback method to find the reports by trying to parse a line like:
{noformat}
--- maven-surefire-plugin:2.18.1:test (default-test) @ mavenproject3 ---
{noformat}
 which then uses the test name to find the report file name. However the 
regular expression is flawed: it will skip the line above because of the third 
digit: 
{noformat}
^---\smaven-surefire-plugin:\d+\.\d+:test\s.*$ {noformat}


  should be replaced by:  
 ^---\smaven-surefire-plugin:\d+(?:.\d+)+:test\s.*$
 However this fallback method won't work either, because depending on the Maven 
settings, the output will be prefixed with the log level (for example [INFO]) 
that will break the matching. It must improved further to take this into 
account:
 ^.---\smaven-surefire-plugin:\d+(?:.\d+)+:test\s.$
 By looking into the surefire code, it is possible to have the "Surefire report 
directory" line appear again by using the "-e" argument for Maven. However, 
this will produce more output and is not what most users would expect: 
{noformat}
C:\Users\borerjc\NetBeansProjects\mavenproject3>mvn -e install
 [INFO] Error stacktraces are turned on.
 [INFO] Scanning for projects...
 [INFO]
 [INFO] < ch.skyguide.crystal:mavenproject3 >-
 [INFO] Building mavenproject3 6.0-SNAPSHOT
 [INFO] ---[ jar ]
 [INFO]
 [INFO] — maven-resources-plugin:2.6:resources (default-resources) @ 
mavenproject3 —
 [INFO] Using 'UTF-8' encoding to copy filtered resources.
 [INFO] skip non existing resourceDirectory 
C:\Users\borerjc\NetBeansProjects\mavenproject3\src\main\resources
 [INFO]
 [INFO] — maven-compiler-plugin:3.1:compile (default-compile) @ mavenproject3 —
 [INFO] Nothing to compile - all classes are up to date
 [INFO]
 [INFO] — maven-resources-plugin:2.6:testResources (default-testResources) @ 
mavenproject3 —
 [INFO] Using 'UTF-8' encoding to copy filtered resources.
 [INFO] skip non existing resourceDirectory 
C:\Users\borerjc\NetBeansProjects\mavenproject3\src\test\resources
 [INFO]
 [INFO] — maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
mavenproject3 —
 [INFO] Nothing to compile - all classes are up to date
 [INFO]
 [INFO] — maven-surefire-plugin:2.22.1:test (default-test) @ mavenproject3 —
 [INFO] Surefire report directory: 
C:\Users\borerjc\NetBeansProjects\mavenproject3\target\surefire-reports
 [INFO]
 [INFO] ---
 [INFO] T E S T S
 [INFO] ---
 [INFO] Running ch.skyguide.crystal.mavenproject3.TestTest
 [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.042 
s <<< FAILURE! - in ch.skyguide.crystal.mavenproject3.TestTest
 [ERROR] testSomeMethod(ch.skyguide.crystal.mavenproject3.TestTest) Time 
elapsed: 0.006 s <<< FAILURE!
 java.lang.AssertionError: dummy message
 at org.junit.Assert.fail(Assert.java:88)
 at ch.skyguide.crystal.mavenproject3.TestTest.testSomeMethod(TestTest.java:22)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
 at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:498)
 at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
 at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
 at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
 at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
 at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
 at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
 at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
 at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
 at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
 at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
 at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
 at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
 at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
 at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
 at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provid

[jira] [Comment Edited] (NETBEANS-635) Surefire 2.19.1 (and later) stacktrace hyperlinks don't work with Maven

2018-11-28 Thread jmborer (JIRA)


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

jmborer edited comment on NETBEANS-635 at 11/28/18 11:59 AM:
-

There are several issues to properly handle the surefire plugin output

Since Surefire 2.19 the line which specifies the output directory (see below) 
is no longer printed:
{noformat}
Surefire report directory: {noformat}
 There is a fallback method to find the reports by trying to parse a line like:
{noformat}
--- maven-surefire-plugin:2.18.1:test (default-test) @ mavenproject3 ---
{noformat}
 which then uses the test name to find the report file name. However the 
regular expression is flawed: it will skip the line above because of the third 
digit: 
{noformat}
^---\smaven-surefire-plugin:\d+\.\d+:test\s.*$ {noformat}
 should be replaced by:  
{noformat}
^---\smaven-surefire-plugin:\d+(?:.\d+)+:test\s.*${noformat}
However this fallback method won't work either, because depending on the Maven 
settings, the output will be prefixed with the log level (for example [INFO]) 
that will break the matching. It must improved further to take this into 
account:
 ^.---\smaven-surefire-plugin:\d+(?:.\d+)+:test\s.$
 By looking into the surefire code, it is possible to have the "Surefire report 
directory" line appear again by using the "-e" argument for Maven. However, 
this will produce more output and is not what most users would expect: 
{noformat}
C:\Users\borerjc\NetBeansProjects\mavenproject3>mvn -e install
 [INFO] Error stacktraces are turned on.
 [INFO] Scanning for projects...
 [INFO]
 [INFO] < ch.skyguide.crystal:mavenproject3 >-
 [INFO] Building mavenproject3 6.0-SNAPSHOT
 [INFO] ---[ jar ]
 [INFO]
 [INFO] — maven-resources-plugin:2.6:resources (default-resources) @ 
mavenproject3 —
 [INFO] Using 'UTF-8' encoding to copy filtered resources.
 [INFO] skip non existing resourceDirectory 
C:\Users\borerjc\NetBeansProjects\mavenproject3\src\main\resources
 [INFO]
 [INFO] — maven-compiler-plugin:3.1:compile (default-compile) @ mavenproject3 —
 [INFO] Nothing to compile - all classes are up to date
 [INFO]
 [INFO] — maven-resources-plugin:2.6:testResources (default-testResources) @ 
mavenproject3 —
 [INFO] Using 'UTF-8' encoding to copy filtered resources.
 [INFO] skip non existing resourceDirectory 
C:\Users\borerjc\NetBeansProjects\mavenproject3\src\test\resources
 [INFO]
 [INFO] — maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
mavenproject3 —
 [INFO] Nothing to compile - all classes are up to date
 [INFO]
 [INFO] — maven-surefire-plugin:2.22.1:test (default-test) @ mavenproject3 —
 [INFO] Surefire report directory: 
C:\Users\borerjc\NetBeansProjects\mavenproject3\target\surefire-reports
 [INFO]
 [INFO] ---
 [INFO] T E S T S
 [INFO] ---
 [INFO] Running ch.skyguide.crystal.mavenproject3.TestTest
 [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.042 
s <<< FAILURE! - in ch.skyguide.crystal.mavenproject3.TestTest
 [ERROR] testSomeMethod(ch.skyguide.crystal.mavenproject3.TestTest) Time 
elapsed: 0.006 s <<< FAILURE!
 java.lang.AssertionError: dummy message
 at org.junit.Assert.fail(Assert.java:88)
 at ch.skyguide.crystal.mavenproject3.TestTest.testSomeMethod(TestTest.java:22)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
 at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:498)
 at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
 at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
 at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
 at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
 at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
 at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
 at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
 at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
 at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
 at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
 at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
 at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
 at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
 at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
 at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRe

[jira] [Comment Edited] (NETBEANS-635) Surefire 2.19.1 (and later) stacktrace hyperlinks don't work with Maven

2018-11-28 Thread jmborer (JIRA)


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

jmborer edited comment on NETBEANS-635 at 11/28/18 11:58 AM:
-

There are several issues to properly handle the surefire plugin output

Since Surefire 2.19 the line which specifies the output directory (see below) 
is no longer printed:
{noformat}
Surefire report directory: {noformat}
 There is a fallback method to find the reports by trying to parse a line like:
{noformat}
--- maven-surefire-plugin:2.18.1:test (default-test) @ mavenproject3 ---
{noformat}
 which then uses the test name to find the report file name. However the 
regular expression is flawed: it will skip the line above because of the third 
digit: 
{noformat}
^---\smaven-surefire-plugin:\d+\.\d+:test\s.*$ {noformat}
 should be replaced by: 
 ^---\smaven-surefire-plugin:\d+(?:.\d+)+:test\s.*$
 However this fallback method won't work either, because depending on the Maven 
settings, the output will be prefixed with the log level (for example [INFO]) 
that will break the matching. It must improved further to take this into 
account:
^.---\smaven-surefire-plugin:\d+(?:.\d+)+:test\s.$
 By looking into the surefire code, it is possible to have the "Surefire report 
directory" line appear again by using the "-e" argument for Maven. However, 
this will produce more output and is not what most users would expect: 
{noformat}
C:\Users\borerjc\NetBeansProjects\mavenproject3>mvn -e install
 [INFO] Error stacktraces are turned on.
 [INFO] Scanning for projects...
 [INFO]
 [INFO] < ch.skyguide.crystal:mavenproject3 >-
 [INFO] Building mavenproject3 6.0-SNAPSHOT
 [INFO] ---[ jar ]
 [INFO]
 [INFO] — maven-resources-plugin:2.6:resources (default-resources) @ 
mavenproject3 —
 [INFO] Using 'UTF-8' encoding to copy filtered resources.
 [INFO] skip non existing resourceDirectory 
C:\Users\borerjc\NetBeansProjects\mavenproject3\src\main\resources
 [INFO]
 [INFO] — maven-compiler-plugin:3.1:compile (default-compile) @ mavenproject3 —
 [INFO] Nothing to compile - all classes are up to date
 [INFO]
 [INFO] — maven-resources-plugin:2.6:testResources (default-testResources) @ 
mavenproject3 —
 [INFO] Using 'UTF-8' encoding to copy filtered resources.
 [INFO] skip non existing resourceDirectory 
C:\Users\borerjc\NetBeansProjects\mavenproject3\src\test\resources
 [INFO]
 [INFO] — maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
mavenproject3 —
 [INFO] Nothing to compile - all classes are up to date
 [INFO]
 [INFO] — maven-surefire-plugin:2.22.1:test (default-test) @ mavenproject3 —
 [INFO] Surefire report directory: 
C:\Users\borerjc\NetBeansProjects\mavenproject3\target\surefire-reports
 [INFO]
 [INFO] ---
 [INFO] T E S T S
 [INFO] ---
 [INFO] Running ch.skyguide.crystal.mavenproject3.TestTest
 [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.042 
s <<< FAILURE! - in ch.skyguide.crystal.mavenproject3.TestTest
 [ERROR] testSomeMethod(ch.skyguide.crystal.mavenproject3.TestTest) Time 
elapsed: 0.006 s <<< FAILURE!
 java.lang.AssertionError: dummy message
 at org.junit.Assert.fail(Assert.java:88)
 at ch.skyguide.crystal.mavenproject3.TestTest.testSomeMethod(TestTest.java:22)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
 at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:498)
 at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
 at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
 at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
 at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
 at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
 at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
 at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
 at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
 at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
 at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
 at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
 at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
 at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
 at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
 at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.ja

[jira] [Comment Edited] (NETBEANS-635) Surefire 2.19.1 (and later) stacktrace hyperlinks don't work with Maven

2018-11-28 Thread jmborer (JIRA)


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

jmborer edited comment on NETBEANS-635 at 11/28/18 11:58 AM:
-

There are several issues to properly handle the surefire plugin output

Since Surefire 2.19 the line which specifies the output directory (see below) 
is no longer printed:
{noformat}
Surefire report directory: {noformat}
 There is a fallback method to find the reports by trying to parse a line like:
{noformat}
--- maven-surefire-plugin:2.18.1:test (default-test) @ mavenproject3 ---
{noformat}
 which then uses the test name to find the report file name. However the 
regular expression is flawed: it will skip the line above because of the third 
digit: 
{noformat}
^---\smaven-surefire-plugin:\d+\.\d+:test\s.*$ {noformat}
 should be replaced by: 
{noformat}
 ^---\smaven-surefire-plugin:\d+(?:.\d+)+:test\s.*$
 

However this fallback method won't work either, because depending on the Maven 
settings, the output will be prefixed with the log level (for example [INFO]) 
that will break the matching. It must improved further to take this into 
account:
{noformat}
^.---\smaven-surefire-plugin:\d+(?:.\d+)+:test\s.$


 By looking into the surefire code, it is possible to have the "Surefire report 
directory" line appear again by using the "-e" argument for Maven. However, 
this will produce more output and is not what most users would expect: 
{noformat}
C:\Users\borerjc\NetBeansProjects\mavenproject3>mvn -e install
 [INFO] Error stacktraces are turned on.
 [INFO] Scanning for projects...
 [INFO]
 [INFO] < ch.skyguide.crystal:mavenproject3 >-
 [INFO] Building mavenproject3 6.0-SNAPSHOT
 [INFO] ---[ jar ]
 [INFO]
 [INFO] — maven-resources-plugin:2.6:resources (default-resources) @ 
mavenproject3 —
 [INFO] Using 'UTF-8' encoding to copy filtered resources.
 [INFO] skip non existing resourceDirectory 
C:\Users\borerjc\NetBeansProjects\mavenproject3\src\main\resources
 [INFO]
 [INFO] — maven-compiler-plugin:3.1:compile (default-compile) @ mavenproject3 —
 [INFO] Nothing to compile - all classes are up to date
 [INFO]
 [INFO] — maven-resources-plugin:2.6:testResources (default-testResources) @ 
mavenproject3 —
 [INFO] Using 'UTF-8' encoding to copy filtered resources.
 [INFO] skip non existing resourceDirectory 
C:\Users\borerjc\NetBeansProjects\mavenproject3\src\test\resources
 [INFO]
 [INFO] — maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
mavenproject3 —
 [INFO] Nothing to compile - all classes are up to date
 [INFO]
 [INFO] — maven-surefire-plugin:2.22.1:test (default-test) @ mavenproject3 —
 [INFO] Surefire report directory: 
C:\Users\borerjc\NetBeansProjects\mavenproject3\target\surefire-reports
 [INFO]
 [INFO] ---
 [INFO] T E S T S
 [INFO] ---
 [INFO] Running ch.skyguide.crystal.mavenproject3.TestTest
 [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.042 
s <<< FAILURE! - in ch.skyguide.crystal.mavenproject3.TestTest
 [ERROR] testSomeMethod(ch.skyguide.crystal.mavenproject3.TestTest) Time 
elapsed: 0.006 s <<< FAILURE!
 java.lang.AssertionError: dummy message
 at org.junit.Assert.fail(Assert.java:88)
 at ch.skyguide.crystal.mavenproject3.TestTest.testSomeMethod(TestTest.java:22)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
 at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:498)
 at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
 at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
 at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
 at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
 at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
 at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
 at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
 at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
 at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
 at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
 at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
 at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
 at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
 at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
 at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeW

[jira] [Comment Edited] (NETBEANS-635) Surefire 2.19.1 (and later) stacktrace hyperlinks don't work with Maven

2018-11-28 Thread jmborer (JIRA)


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

jmborer edited comment on NETBEANS-635 at 11/28/18 11:57 AM:
-

There are several issues to properly handle the surefire plugin output

Since Surefire 2.19 the line which specifies the output directory (see below) 
is no longer printed:
{noformat}
Surefire report directory: {noformat}
 There is a fallback method to find the reports by trying to parse a line like:
{noformat}
--- maven-surefire-plugin:2.18.1:test (default-test) @ mavenproject3 ---
{noformat}
 which then uses the test name to find the report file name. However the 
regular expression is flawed: it will skip the line above because of the third 
digit: 
{noformat}
^---\smaven-surefire-plugin:\d+\.\d+:test\s.*$ {noformat}
 should be replaced by: 
{noformat}
 ^---\smaven-surefire-plugin:\d+(?:.\d+)+:test\s.*${noformat}
 

However this fallback method won't work either, because depending on the Maven 
settings, the output will be prefixed with the log level (for example [INFO]) 
that will break the matching. It must improved further to take this into 
account:
{noformat}
^.---\smaven-surefire-plugin:\d+(?:.\d+)+:test\s.${noformat}
 By looking into the surefire code, it is possible to have the "Surefire report 
directory" line appear again by using the "-e" argument for Maven. However, 
this will produce more output and is not what most users would expect: 
{noformat}
C:\Users\borerjc\NetBeansProjects\mavenproject3>mvn -e install
 [INFO] Error stacktraces are turned on.
 [INFO] Scanning for projects...
 [INFO]
 [INFO] < ch.skyguide.crystal:mavenproject3 >-
 [INFO] Building mavenproject3 6.0-SNAPSHOT
 [INFO] ---[ jar ]
 [INFO]
 [INFO] — maven-resources-plugin:2.6:resources (default-resources) @ 
mavenproject3 —
 [INFO] Using 'UTF-8' encoding to copy filtered resources.
 [INFO] skip non existing resourceDirectory 
C:\Users\borerjc\NetBeansProjects\mavenproject3\src\main\resources
 [INFO]
 [INFO] — maven-compiler-plugin:3.1:compile (default-compile) @ mavenproject3 —
 [INFO] Nothing to compile - all classes are up to date
 [INFO]
 [INFO] — maven-resources-plugin:2.6:testResources (default-testResources) @ 
mavenproject3 —
 [INFO] Using 'UTF-8' encoding to copy filtered resources.
 [INFO] skip non existing resourceDirectory 
C:\Users\borerjc\NetBeansProjects\mavenproject3\src\test\resources
 [INFO]
 [INFO] — maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
mavenproject3 —
 [INFO] Nothing to compile - all classes are up to date
 [INFO]
 [INFO] — maven-surefire-plugin:2.22.1:test (default-test) @ mavenproject3 —
 [INFO] Surefire report directory: 
C:\Users\borerjc\NetBeansProjects\mavenproject3\target\surefire-reports
 [INFO]
 [INFO] ---
 [INFO] T E S T S
 [INFO] ---
 [INFO] Running ch.skyguide.crystal.mavenproject3.TestTest
 [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.042 
s <<< FAILURE! - in ch.skyguide.crystal.mavenproject3.TestTest
 [ERROR] testSomeMethod(ch.skyguide.crystal.mavenproject3.TestTest) Time 
elapsed: 0.006 s <<< FAILURE!
 java.lang.AssertionError: dummy message
 at org.junit.Assert.fail(Assert.java:88)
 at ch.skyguide.crystal.mavenproject3.TestTest.testSomeMethod(TestTest.java:22)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
 at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:498)
 at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
 at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
 at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
 at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
 at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
 at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
 at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
 at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
 at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
 at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
 at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
 at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
 at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
 at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
 at 
org.apache.maven.surefire.junit4.JUnit

[jira] [Commented] (NETBEANS-635) Surefire 2.19.1 (and later) stacktrace hyperlinks don't work with Maven

2018-11-28 Thread jmborer (JIRA)


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

jmborer commented on NETBEANS-635:
--

There are several issues to properly handle the surefire plugin output

Since Surefire 2.19 the line which specifies the output directory (see below) 
is no longer printed:
{noformat}
Surefire report directory: {noformat}
 There is a fallback method to find the reports by trying to parse a line like:
{noformat}
--- maven-surefire-plugin:2.18.1:test (default-test) @ mavenproject3 ---
{noformat}
 which then uses the test name to find the report file name. However the 
regular expression is flawed: it will skip the line above because of the third 
digit:

 
{noformat}
^---\smaven-surefire-plugin:\d+\.\d+:test\s.*$ {noformat}
 

should be replaced by

 
{noformat}
 ^---\smaven-surefire-plugin:\d+(?:.\d+)+:test\s.*${noformat}
 

However this fallback method won't work either, because depending on the Maven 
settings, the output will be prefixed with the log level (for example [INFO]) 
that will break the matching. It must improved further to take this into 
account:
{noformat}
^.---\smaven-surefire-plugin:\d+(?:.\d+)+:test\s.${noformat}
By looking into the surefire code, it is possible to have the "Surefire report 
directory" line appear again by using the "-e" argument for Maven. However, 
this will produce more output and is not what most users would expect: 
{noformat}
C:\Users\borerjc\NetBeansProjects\mavenproject3>mvn -e install
 [INFO] Error stacktraces are turned on.
 [INFO] Scanning for projects...
 [INFO]
 [INFO] < ch.skyguide.crystal:mavenproject3 >-
 [INFO] Building mavenproject3 6.0-SNAPSHOT
 [INFO] ---[ jar ]
 [INFO]
 [INFO] — maven-resources-plugin:2.6:resources (default-resources) @ 
mavenproject3 —
 [INFO] Using 'UTF-8' encoding to copy filtered resources.
 [INFO] skip non existing resourceDirectory 
C:\Users\borerjc\NetBeansProjects\mavenproject3\src\main\resources
 [INFO]
 [INFO] — maven-compiler-plugin:3.1:compile (default-compile) @ mavenproject3 —
 [INFO] Nothing to compile - all classes are up to date
 [INFO]
 [INFO] — maven-resources-plugin:2.6:testResources (default-testResources) @ 
mavenproject3 —
 [INFO] Using 'UTF-8' encoding to copy filtered resources.
 [INFO] skip non existing resourceDirectory 
C:\Users\borerjc\NetBeansProjects\mavenproject3\src\test\resources
 [INFO]
 [INFO] — maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
mavenproject3 —
 [INFO] Nothing to compile - all classes are up to date
 [INFO]
 [INFO] — maven-surefire-plugin:2.22.1:test (default-test) @ mavenproject3 —
 [INFO] Surefire report directory: 
C:\Users\borerjc\NetBeansProjects\mavenproject3\target\surefire-reports
 [INFO]
 [INFO] ---
 [INFO] T E S T S
 [INFO] ---
 [INFO] Running ch.skyguide.crystal.mavenproject3.TestTest
 [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.042 
s <<< FAILURE! - in ch.skyguide.crystal.mavenproject3.TestTest
 [ERROR] testSomeMethod(ch.skyguide.crystal.mavenproject3.TestTest) Time 
elapsed: 0.006 s <<< FAILURE!
 java.lang.AssertionError: dummy message
 at org.junit.Assert.fail(Assert.java:88)
 at ch.skyguide.crystal.mavenproject3.TestTest.testSomeMethod(TestTest.java:22)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
 at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:498)
 at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
 at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
 at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
 at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
 at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
 at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
 at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
 at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
 at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
 at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
 at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
 at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
 at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
 at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
 at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:27

[jira] [Created] (NETBEANS-1759) After migrating to NetBeans 9 it is unable to find the SVN client

2018-11-28 Thread Marcus Walla (JIRA)
Marcus Walla created NETBEANS-1759:
--

 Summary: After migrating to NetBeans 9 it is unable to find the 
SVN client
 Key: NETBEANS-1759
 URL: https://issues.apache.org/jira/browse/NETBEANS-1759
 Project: NetBeans
  Issue Type: Bug
  Components: versioncontrol - Subversion
Affects Versions: 9.0
 Environment: Model Name:   MacBook Pro
  Model Identifier: MacBookPro8,2
  Processor Name:   Intel Core i7
  Processor Speed:  2 GHz
  Number of Processors: 1
  Total Number of Cores:4
  L2 Cache (per Core):  256 KB
  L3 Cache: 6 MB
  Memory:   16 GB

System Version: macOS 10.13.6 (17G3025)
  Kernel Version:   Darwin 17.7.0
Reporter: Marcus Walla
 Fix For: 9.0
 Attachments: Screen Shot 2018-11-28 at 12.45.28.png, Screen Shot 
2018-11-28 at 12.55.57.png, netbeans_9_ide.log

Note: for the previous NetBeans 8.2 there exists checked out project from a 
subversion repository. As version control plugin SvnKit is used 
(org.netbeans.libs.svnClientAdapter.svnkit/1 [1.24.1 201609300101]).


- fresh download and installation of NetBeans 9. Used the script of Carl J. 
Mosca from github ([https://github.com/carljmosca/netbeans-macos-bundle,] 
install.sh)
- start NetBeans 9.
- requires to migrated the configuration from 8.2 to 9, which I did:
xxx@xxx:~$ ls -l ~/Library/Application\ Support/NetBeans/
total 7824
drwxr-xr-x 15 walla 3536 480 Nov 28 09:52 8.2
drwxr-xr-x 8 walla 3536 256 Nov 28 10:27 9.0
- then a window pops up and asks to install the nb-javac library which is 
highly recommended by the NetBeans team. So, library installed.
- after a restart NetBeans found in the previous version plugins which can be 
imported to NetBeans 9. One module is Subversion remote plugin 
org.netbeans.modules.subversion.remote. All of the previous plugins are 
imported to version 9, including the Subversion remote plugin.
- after a second restart NetBeans 9 claims in the IDE log file about subversion 
mismatches: 

INFO [org.netbeans.libs.svnclientadapter]: Javahl client adapter is not 
available
Failed to load JavaHL Library.
These are the errors that were encountered:
no libsvnjavahl-1 in java.library.path
no svnjavahl-1 in java.library.path
no svnjavahl in java.library.path
...
INFO [org.netbeans.modules.subversion.client.SvnClientFactory]: JavaHL not 
available. Falling back on SvnKit.
INFO [org.netbeans.modules.subversion.client.SvnClientFactory]: SvnKit not 
available. Falling back on commandline.
INFO [org.netbeans.modules.subversion]: Commandline client version: *1.10.0 
(r1827917)*
WARNING [org.netbeans.modules.subversion]: Unsupported svn version. *You need 
>= 1.5*
WARNING [org.netbeans.modules.subversion.client.SvnClientFactory]: executable 
binary path set to /usr/bin yet client not available.

- on my drive svn is installed and usable:

walla@mcsmcwalla:~$ which svn
*/usr/bin*/svn
walla@mcsmcwalla:~$ ls -l $(which svn)
-rwxr-xr-x 1 root wheel 18288 Jul 4 13:02 /usr/bin/svn
walla@mcsmcwalla:~$ svn --version
svn, version *1.10.0 (r1827917)*
 compiled Sep 25 2018, 18:25:22 on x86_64-apple-darwin17.0.0
...

 

We can see in the log snippet that the version on my drive is equal to the one 
which NetBeans found. However, NetBeans claims that the version is incorrect or 
did not find the client at all. 

Can somebody comment on this?

Best regards, Marcus



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