[jira] [Updated] (NETBEANS-1765) Cannot install JavaScript Kit
[
https://issues.apache.org/jira/browse/NETBEANS-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach updated NETBEANS-1765:
--
Priority: Minor (was: Major)
> Cannot install JavaScript Kit
> -
>
> Key: NETBEANS-1765
> URL: https://issues.apache.org/jira/browse/NETBEANS-1765
> Project: NetBeans
> Issue Type: Bug
> Components: javascript - Model, platform - Autoupdate
>Affects Versions: 10.0
>Reporter: Jaroslav Tulach
>Assignee: Svatopluk Dedic
>Priority: Minor
>
> Update NetBeans to version
> {code:java}
> commit ab822e2c93541f69bc5e27250f22ba84c4f581ec (HEAD ->
> feature/autoupdate_enable_download, sdedic/feature/autoupdate_enable_download)
> Author: Svata Dedic
> Date: Fri Nov 30 18:33:37 2018 +0100
> {code}
> and then {{ant build}} and start with clean userdir:
> {code:java}
> nbbuild$ rm -rf netbeans/ testuserdir/; unzip
> NetBeans-dev-*-ab822e2c9354-release.zip ; ant tryme{code}
> Go to _Tools/Plugins/Installed_, check the _Show details_ checkbox, so one
> sees not only features, but all AU visible modules and try to activate
> *JavaScript2 Kit*:
> {code:java}
> Activation failed: Not all requested modules can be enabled:
> [StandardModule:org.netbeans.modules.javascript2.kit jarFile:
> nbbuild/netbeans/webcommon/modules/org-netbeans-modules-javascript2-kit.jar]{code}
>
> There is a workaround. One can go into the _Available Plugins_ tab and
> install *Oracle Javascript Parser implementation* first. Then activation of
> *JavaScript2 Kit* (btw. why "2", that is an implementation detail the version
> "1" is buried in history for many years) succeeds.
--
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-1765) Cannot install JavaScript Kit
Jaroslav Tulach created NETBEANS-1765:
-
Summary: Cannot install JavaScript Kit
Key: NETBEANS-1765
URL: https://issues.apache.org/jira/browse/NETBEANS-1765
Project: NetBeans
Issue Type: Bug
Components: javascript - Model, platform - Autoupdate
Affects Versions: 10.0
Reporter: Jaroslav Tulach
Assignee: Svatopluk Dedic
Update NetBeans to version
{code:java}
commit ab822e2c93541f69bc5e27250f22ba84c4f581ec (HEAD ->
feature/autoupdate_enable_download, sdedic/feature/autoupdate_enable_download)
Author: Svata Dedic
Date: Fri Nov 30 18:33:37 2018 +0100
{code}
and then {{ant build}} and start with clean userdir:
{code:java}
nbbuild$ rm -rf netbeans/ testuserdir/; unzip
NetBeans-dev-*-ab822e2c9354-release.zip ; ant tryme{code}
Go to _Tools/Plugins/Installed_, check the _Show details_ checkbox, so one sees
not only features, but all AU visible modules and try to activate *JavaScript2
Kit*:
{code:java}
Activation failed: Not all requested modules can be enabled:
[StandardModule:org.netbeans.modules.javascript2.kit jarFile:
nbbuild/netbeans/webcommon/modules/org-netbeans-modules-javascript2-kit.jar]{code}
There is a workaround. One can go into the _Available Plugins_ tab and install
*Oracle Javascript Parser implementation* first. Then activation of
*JavaScript2 Kit* (btw. why "2", that is an implementation detail the version
"1" is buried in history for many years) succeeds.
--
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-1764) Issue on Netbeans 9 while configuring Github
Satinder SINGH created NETBEANS-1764: Summary: Issue on Netbeans 9 while configuring Github Key: NETBEANS-1764 URL: https://issues.apache.org/jira/browse/NETBEANS-1764 Project: NetBeans Issue Type: Bug Components: javaee - Editor Affects Versions: 9.0 Environment: Mac High Sierra 10.13.6 Reporter: Satinder SINGH Attachments: IDE-Log.txt, UI-Log.txt I have found issues while configuring GitHub. Please see the attached files. -- 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-1159) Relicense nashorn parser
[ https://issues.apache.org/jira/browse/NETBEANS-1159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16704539#comment-16704539 ] Jaroslav Tulach commented on NETBEANS-1159: --- Svatopluk Dědic has just opened [PR-1044|https://github.com/apache/incubator-netbeans/pull/1044] that seems to address the enabling of HTML5 feature. > Relicense nashorn parser > > > Key: NETBEANS-1159 > URL: https://issues.apache.org/jira/browse/NETBEANS-1159 > Project: NetBeans > Issue Type: Bug > Components: javascript - Other >Affects Versions: 10.0 >Reporter: Svatopluk Dedic >Assignee: Geertjan Wielenga >Priority: Blocker > > The nashorn parser uses GPLv2 with classpath exception, which is not > compatible for Apache distribution. > Since the code was fully developed by Oracle (and is committed in > [http://hg.openjdk.java.net/graal/graal-js-parser/file/ba7a8bc42268/graal/com.oracle.js.parser/src/com/oracle/js/parser|http://hg.openjdk.java.net/graal/graal-js-parser/file/ba7a8bc42268/graal/com.oracle.js.parser/src/com/oracle/js/parser),]), > it could be possible (for Oracle) to relicense the code to allow > distribution. > -- 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] [Assigned] (NETBEANS-1159) Relicense nashorn parser
[ https://issues.apache.org/jira/browse/NETBEANS-1159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaroslav Tulach reassigned NETBEANS-1159: - Assignee: Svatopluk Dedic (was: Geertjan Wielenga) > Relicense nashorn parser > > > Key: NETBEANS-1159 > URL: https://issues.apache.org/jira/browse/NETBEANS-1159 > Project: NetBeans > Issue Type: Bug > Components: javascript - Other >Affects Versions: 10.0 >Reporter: Svatopluk Dedic >Assignee: Svatopluk Dedic >Priority: Blocker > > The nashorn parser uses GPLv2 with classpath exception, which is not > compatible for Apache distribution. > Since the code was fully developed by Oracle (and is committed in > [http://hg.openjdk.java.net/graal/graal-js-parser/file/ba7a8bc42268/graal/com.oracle.js.parser/src/com/oracle/js/parser|http://hg.openjdk.java.net/graal/graal-js-parser/file/ba7a8bc42268/graal/com.oracle.js.parser/src/com/oracle/js/parser),]), > it could be possible (for Oracle) to relicense the code to allow > distribution. > -- 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
[
https://issues.apache.org/jira/browse/NETBEANS-635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16704489#comment-16704489
]
jmborer edited comment on NETBEANS-635 at 11/30/18 9:53 AM:
Thank you Arnaud. IMHO, it won't be possible to easily fix
TestOutputListenerProvider to properly support both surefire and failsafe as
they are two different plugins with their own report dirs and specific
behaviors.
A better idea would be to refactor TestOutputListenerProvider into
SurefireOutputListenerProvider and FailsafeOutputListenerProvider that will
respectively process surefire and failsafe outputs.
I have created a Jira entry for that
https://issues.apache.org/jira/browse/NETBEANS-1763
was (Author: jmborer):
Thank you Arnaud. IMHO, it won't be possible to easily fix
TestOutputListenerProvider to properly support both surefire and failsafe as
they are two different plugins with their own report dirs and specific
behaviors.
A better idea would be to refactor TestOutputListenerProvider into
SurefireOutputListenerProvider and FailsafeOutputListenerProvider that will
respectively process surefire and failsafe outputs.
> 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.18.1-logging-output.txt, surefire-2.18.1-output.txt,
> surefire-2.19.1-.png, surefire-2.19.1-logging-output.txt,
> surefire-2.19.1-output.txt, surefire-2.22.1-.png,
> surefire-2.22.1-logging-output.txt, surefire-2.22.1-output.txt,
> surefire-3.0.0-M3-logging-output.txt, surefire-3.0.0-M3-output.txt,
> target-2.18.1.zip, target-2.19.1.zip, target-2.22.1.zip
>
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> 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] [Created] (NETBEANS-1763) Refactor the test output processor to handle both surefire and failsafe plugins
jmborer created NETBEANS-1763: - Summary: Refactor the test output processor to handle both surefire and failsafe plugins Key: NETBEANS-1763 URL: https://issues.apache.org/jira/browse/NETBEANS-1763 Project: NetBeans Issue Type: Improvement Components: projects - Maven Affects Versions: 9.0, 10.0 Reporter: jmborer Currently the Maven test results output processor is mainly focused on handling the Surefire output. The ouput of Failsafe is partly covered. This job is done in a single class called TestOutputListenerProvider. To provide a cleaner and robuster support for both Surefire and Failsafe test results parsing, it becomes necessary to refactor TestOutputListenerProvider into two specialized output processors: one for Surefire and one for Failsafe. -- 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
[
https://issues.apache.org/jira/browse/NETBEANS-635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16704489#comment-16704489
]
jmborer edited comment on NETBEANS-635 at 11/30/18 9:44 AM:
Thank you Arnaud. IMHO, it won't be possible to easily fix
TestOutputListenerProvider to properly support both surefire and failsafe as
they are two different plugins with their own report dirs and specific
behaviors.
A better idea would be to refactor TestOutputListenerProvider into
SurefireOutputListenerProvider and FailsafeOutputListenerProvider that will
respectively process surefire and failsafe outputs.
was (Author: jmborer):
Thank you Arnaud. IMHO, it won't be possible to easily fix
TestOutputListenerProvider to support both surefire and failsafe as they are
two different plugins with their own report dirs and specific behaviors.
A better idea would be to refactor TestOutputListenerProvider into
SurefireOutputListenerProvider and FailsafeOutputListenerProvider that will
respectively process surefire and failsafe outputs.
> 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.18.1-logging-output.txt, surefire-2.18.1-output.txt,
> surefire-2.19.1-.png, surefire-2.19.1-logging-output.txt,
> surefire-2.19.1-output.txt, surefire-2.22.1-.png,
> surefire-2.22.1-logging-output.txt, surefire-2.22.1-output.txt,
> surefire-3.0.0-M3-logging-output.txt, surefire-3.0.0-M3-output.txt,
> target-2.18.1.zip, target-2.19.1.zip, target-2.22.1.zip
>
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> 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] [Comment Edited] (NETBEANS-635) Surefire 2.19.1 (and later) stacktrace hyperlinks don't work with Maven
[
https://issues.apache.org/jira/browse/NETBEANS-635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16704489#comment-16704489
]
jmborer edited comment on NETBEANS-635 at 11/30/18 9:43 AM:
Thank you Arnaud. IMHO, it won't be possible to easily fix
TestOutputListenerProvider to support both surefire and failsafe as they are
two different plugins with their own report dirs and specific behaviors.
A better idea would be to refactor TestOutputListenerProvider into
SurefireOutputListenerProvider and FailsafeOutputListenerProvider that will
respectively process surefire and failsafe outputs.
was (Author: jmborer):
Thank you Arnaud. IMHO, it won't be possible to fix TestOutputListenerProvider
to support both surefire and failsafe as they are two different plugins with
their own report dirs and specific behaviors.
A better idea would be to refactor TestOutputListenerProvider into
SurefireOutputListenerProvider and FailsafeOutputListenerProvider that will
respectively process surefire and failsafe outputs.
> 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.18.1-logging-output.txt, surefire-2.18.1-output.txt,
> surefire-2.19.1-.png, surefire-2.19.1-logging-output.txt,
> surefire-2.19.1-output.txt, surefire-2.22.1-.png,
> surefire-2.22.1-logging-output.txt, surefire-2.22.1-output.txt,
> surefire-3.0.0-M3-logging-output.txt, surefire-3.0.0-M3-output.txt,
> target-2.18.1.zip, target-2.19.1.zip, target-2.22.1.zip
>
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> 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] [Commented] (NETBEANS-635) Surefire 2.19.1 (and later) stacktrace hyperlinks don't work with Maven
[
https://issues.apache.org/jira/browse/NETBEANS-635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16704489#comment-16704489
]
jmborer commented on NETBEANS-635:
--
Thank you Arnaud. IMHO, it won't be possible to fix TestOutputListenerProvider
to support both surefire and failsafe as they are two different plugins with
their own report dirs and specific behaviors.
A better idea would be to refactor TestOutputListenerProvider into
SurefireOutputListenerProvider and FailsafeOutputListenerProvider that will
respectively process surefire and failsafe outputs.
> 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.18.1-logging-output.txt, surefire-2.18.1-output.txt,
> surefire-2.19.1-.png, surefire-2.19.1-logging-output.txt,
> surefire-2.19.1-output.txt, surefire-2.22.1-.png,
> surefire-2.22.1-logging-output.txt, surefire-2.22.1-output.txt,
> surefire-3.0.0-M3-logging-output.txt, surefire-3.0.0-M3-output.txt,
> target-2.18.1.zip, target-2.19.1.zip, target-2.22.1.zip
>
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> 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] [Commented] (NETBEANS-7) Provide basic editor features (syntax highlighting, braces matching, completion, etc) for more file types
[ https://issues.apache.org/jira/browse/NETBEANS-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16704428#comment-16704428 ] Christian Lenz commented on NETBEANS-7: --- And what I can think of is that we have maybe one or 2 config files like a json file or XML (More the NetBeans way) where I choose the extension, the mimetype, some other config like braces matching as you can see it here: https://github.com/rust-lang/rls-vscode/blob/master/language-configuration.json This will be very easy to put such files inside of a folder where NetBeans reads them out, for only - simple coloring - pair/braces matching - code snippets - formatting. The other stuff like code completion and go to whatever and find usage I know that this is not that easy possible w/o doing stuff with Java. But for the other stuff, it should be easy to not make much work with java. Only one or 2 json/xml/whatever file with the config/tokens/braces matching/snippets and thats it. > 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-7) Provide basic editor features (syntax highlighting, braces matching, completion, etc) for more file types
[ https://issues.apache.org/jira/browse/NETBEANS-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16704422#comment-16704422 ] Christian Lenz commented on NETBEANS-7: --- That is nice, in the end, it doesn't matter what we have but I would prefer, a more generic version what is used in other editors. I mean the initial solution with NBS was nice, but there is no full supported list of languages. I only know one which is gherkin/cucumber. Hope to find a full list of textmate languages in the bundles. I communicate with the texmate support to figure out whether there is a list/repo of language files or not. > 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-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16704418#comment-16704418 ] Christian Lenz commented on NETBEANS-168: - Hey [~lkishalmi] let me know how I can help here with testing and identifing this problem. > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > Labels: ca_survey > Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 > vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z > > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > 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-635) Surefire 2.19.1 (and later) stacktrace hyperlinks don't work with Maven
[
https://issues.apache.org/jira/browse/NETBEANS-635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16704383#comment-16704383
]
Arnaud Bourrée commented on NETBEANS-635:
-
Report folders are respectively:
* surefire-reports
* failsafe-reports
> 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.18.1-logging-output.txt, surefire-2.18.1-output.txt,
> surefire-2.19.1-.png, surefire-2.19.1-logging-output.txt,
> surefire-2.19.1-output.txt, surefire-2.22.1-.png,
> surefire-2.22.1-logging-output.txt, surefire-2.22.1-output.txt,
> surefire-3.0.0-M3-logging-output.txt, surefire-3.0.0-M3-output.txt,
> target-2.18.1.zip, target-2.19.1.zip, target-2.22.1.zip
>
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> 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
