[jira] [Commented] (NETBEANS-4341) Maven project reload does not work from [unloadable] state
[
https://issues.apache.org/jira/browse/NETBEANS-4341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17130457#comment-17130457
]
Alessandro Falappa commented on NETBEANS-4341:
--
Great job [~oyarzun]!
I confirm that adding the property you mention in {{netbeans.conf}} solves my
use cases (both the reproduction steps and the wizard in my plugin). This can
be considered as a workaround.
I also thank [~matthiasblaesing] for working on a proper fix on master.
> Maven project reload does not work from [unloadable] state
> --
>
> Key: NETBEANS-4341
> URL: https://issues.apache.org/jira/browse/NETBEANS-4341
> Project: NetBeans
> Issue Type: Bug
>Affects Versions: 12.0
>Reporter: Michal Hlavac
>Priority: Major
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> I did these steps in spring boot maven application:
> # Changed version of spring boot in {{}} element from
> {{2.2.7.RELEASE}} to {{2.3.0.RELEASE}}. This makes project unloadable.
> # Then I did clean & build, all dependencies were downloaded.
> # Project is still unloadable and right click -> reload pom.xml do nothing.
> # I have to close & run netbeans. Then project is back to normal
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Comment Edited] (NETBEANS-4341) Maven project reload does not work from [unloadable] state
[
https://issues.apache.org/jira/browse/NETBEANS-4341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17128569#comment-17128569
]
Alessandro Falappa edited comment on NETBEANS-4341 at 6/8/20, 7:39 PM:
---
[~matthiasblaesing] My educated guess would be
{{java/maven.embedder/src/org/netbeans/modules/maven/embedder/NBRepositoryModelResolver.java}}
in that PR. The other modifications are mainly adaptations to a refactoring in
the MavenCli class.
was (Author: alexfalappa):
[~matthiasblaesing] My educated guess would be
{{java/maven.embedder/src/org/netbeans/modules/maven/embedder/NBRepositoryModelResolver.java}}.
The other modifications are mainly adaptations to a refactoring in the
MavenCli class.
> Maven project reload does not work from [unloadable] state
> --
>
> Key: NETBEANS-4341
> URL: https://issues.apache.org/jira/browse/NETBEANS-4341
> Project: NetBeans
> Issue Type: Bug
>Affects Versions: 12.0
>Reporter: Michal Hlavac
>Priority: Major
>
> I did these steps in spring boot maven application:
> # Changed version of spring boot in {{}} element from
> {{2.2.7.RELEASE}} to {{2.3.0.RELEASE}}. This makes project unloadable.
> # Then I did clean & build, all dependencies were downloaded.
> # Project is still unloadable and right click -> reload pom.xml do nothing.
> # I have to close & run netbeans. Then project is back to normal
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-4341) Maven project reload does not work from [unloadable] state
[
https://issues.apache.org/jira/browse/NETBEANS-4341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17128569#comment-17128569
]
Alessandro Falappa commented on NETBEANS-4341:
--
[~matthiasblaesing] My educated guess would be
{{java/maven.embedder/src/org/netbeans/modules/maven/embedder/NBRepositoryModelResolver.java}}.
The other modifications are mainly adaptations to a refactoring in the
MavenCli class.
> Maven project reload does not work from [unloadable] state
> --
>
> Key: NETBEANS-4341
> URL: https://issues.apache.org/jira/browse/NETBEANS-4341
> Project: NetBeans
> Issue Type: Bug
>Affects Versions: 12.0
>Reporter: Michal Hlavac
>Priority: Major
>
> I did these steps in spring boot maven application:
> # Changed version of spring boot in {{}} element from
> {{2.2.7.RELEASE}} to {{2.3.0.RELEASE}}. This makes project unloadable.
> # Then I did clean & build, all dependencies were downloaded.
> # Project is still unloadable and right click -> reload pom.xml do nothing.
> # I have to close & run netbeans. Then project is back to normal
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Comment Edited] (NETBEANS-4341) Maven project reload does not work from [unloadable] state
[
https://issues.apache.org/jira/browse/NETBEANS-4341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17128009#comment-17128009
]
Alessandro Falappa edited comment on NETBEANS-4341 at 6/8/20, 8:22 AM:
---
These steps show the problem on a linux box:
# Remove the local maven cache ($HOME/.m2/repository folder)
# Go to [https://start.spring.io/] and click on _Generate_, this should
download a basic Spring Boot project in a zip archive named {{demo.zip}}
# Open NetBeans 12.0 and choose File > Import Project > From Zip select the
downloaded archive, this should open a maven project named _demo_ in unloadable
state and offer to _Resolve Problems_
# Click on _Resolve_ to start the priming build
# After the build completes the project remains in unloadable state
On NetBeans 11.3 after the last step a reindex is triggered
({{org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater}} and the maven
project moves to loaded state.
Likely this is what is also missing in the use case of the original reporter.
was (Author: alexfalappa):
These steps show the problem on a linux box:
# Remove the local maven cache ($HOME/.m2/repository folder)
# Go to [https://start.spring.io/] and click on _Generate_, this should
download a basic Spring Boot project in a zip archive named {{demo.zip}}
# Open NetBeans 12.0 and choose File > Import Project > From Zip select the
downloaded archive, this should open a maven project named _demo_ in unloadable
state and offer to _Resolve Problems_
# Click on _Resolve_ to start the priming build
# After the build completes the project remains in unloadable state
On NetBeans 11.3 after the last step a reindex is triggered
({{org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater}}.
Likely this is what is also missing in the use case of the original reporter.
> Maven project reload does not work from [unloadable] state
> --
>
> Key: NETBEANS-4341
> URL: https://issues.apache.org/jira/browse/NETBEANS-4341
> Project: NetBeans
> Issue Type: Bug
>Affects Versions: 12.0
>Reporter: Michal Hlavac
>Priority: Major
>
> I did these steps in spring boot maven application:
> # Changed version of spring boot in {{}} element from
> {{2.2.7.RELEASE}} to {{2.3.0.RELEASE}}. This makes project unloadable.
> # Then I did clean & build, all dependencies were downloaded.
> # Project is still unloadable and right click -> reload pom.xml do nothing.
> # I have to close & run netbeans. Then project is back to normal
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-4341) Maven project reload does not work from [unloadable] state
[
https://issues.apache.org/jira/browse/NETBEANS-4341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17128009#comment-17128009
]
Alessandro Falappa commented on NETBEANS-4341:
--
These steps show the problem on a linux box:
# Remove the local maven cache ($HOME/.m2/repository folder)
# Go to [https://start.spring.io/] and click on _Generate_, this should
download a basic Spring Boot project in a zip archive named {{demo.zip}}
# Open NetBeans 12.0 and choose File > Import Project > From Zip select the
downloaded archive, this should open a maven project named _demo_ in unloadable
state and offer to _Resolve Problems_
# Click on _Resolve_ to start the priming build
# After the build completes the project remains in unloadable state
On NetBeans 11.3 after the last step a reindex is triggered
({{org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater}}.
Likely this is what is also missing in the use case of the original reporter.
> Maven project reload does not work from [unloadable] state
> --
>
> Key: NETBEANS-4341
> URL: https://issues.apache.org/jira/browse/NETBEANS-4341
> Project: NetBeans
> Issue Type: Bug
>Affects Versions: 12.0
>Reporter: Michal Hlavac
>Priority: Major
>
> I did these steps in spring boot maven application:
> # Changed version of spring boot in {{}} element from
> {{2.2.7.RELEASE}} to {{2.3.0.RELEASE}}. This makes project unloadable.
> # Then I did clean & build, all dependencies were downloaded.
> # Project is still unloadable and right click -> reload pom.xml do nothing.
> # I have to close & run netbeans. Then project is back to normal
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Comment Edited] (NETBEANS-4341) Maven project reload does not work from [unloadable] state
[
https://issues.apache.org/jira/browse/NETBEANS-4341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127371#comment-17127371
]
Alessandro Falappa edited comment on NETBEANS-4341 at 6/6/20, 3:17 PM:
---
*Confirmed*.
NetBeans 12.0 on Oracle JDK 8 on Ubuntu 18.04.
I am the author of *NBSpringBoot* plugin and this manifests when creating new
projects with the plugin _"new project from Initializr"_ wizard.
Somehow after a clean & build the maven model is not refreshed and the project
remains unloadable.
was (Author: alexfalappa):
Confirmed.
NetBeans 12.0 on Oracle JDK 8 on Ubuntu 18.04.
I am the author of NBSpringBoot plugin and this manifests when creating new
projects with the plugin "new project from Initializr" wizard.
Somehow after a clean & build the maven model is not refreshed and the project
remains unloadable.
> Maven project reload does not work from [unloadable] state
> --
>
> Key: NETBEANS-4341
> URL: https://issues.apache.org/jira/browse/NETBEANS-4341
> Project: NetBeans
> Issue Type: Bug
>Affects Versions: 12.0
>Reporter: Michal Hlavac
>Priority: Major
>
> I did these steps in spring boot maven application:
> # Changed version of spring boot in {{}} element from
> {{2.2.7.RELEASE}} to {{2.3.0.RELEASE}}. This makes project unloadable.
> # Then I did clean & build, all dependencies were downloaded.
> # Project is still unloadable and right click -> reload pom.xml do nothing.
> # I have to close & run netbeans. Then project is back to normal
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-4341) Maven project reload does not work from [unloadable] state
[
https://issues.apache.org/jira/browse/NETBEANS-4341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127371#comment-17127371
]
Alessandro Falappa commented on NETBEANS-4341:
--
Confirmed.
NetBeans 12.0 on Oracle JDK 8 on Ubuntu 18.04.
I am the author of NBSpringBoot plugin and this manifests when creating new
projects with the plugin "new project from Initializr" wizard.
Somehow after a clean & build the maven model is not refreshed and the project
remains unloadable.
> Maven project reload does not work from [unloadable] state
> --
>
> Key: NETBEANS-4341
> URL: https://issues.apache.org/jira/browse/NETBEANS-4341
> Project: NetBeans
> Issue Type: Bug
>Affects Versions: 12.0
>Reporter: Michal Hlavac
>Priority: Major
>
> I did these steps in spring boot maven application:
> # Changed version of spring boot in {{}} element from
> {{2.2.7.RELEASE}} to {{2.3.0.RELEASE}}. This makes project unloadable.
> # Then I did clean & build, all dependencies were downloaded.
> # Project is still unloadable and right click -> reload pom.xml do nothing.
> # I have to close & run netbeans. Then project is back to normal
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Comment Edited] (NETBEANS-3942) Breakpoint background color in FlatLaF prevents reading text
[ https://issues.apache.org/jira/browse/NETBEANS-3942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061724#comment-17061724 ] Alessandro Falappa edited comment on NETBEANS-3942 at 3/18/20, 1:28 PM: I can confirm [~DevCharly] investigation. For reference here are the colors of enabled/disabled breakpoint lines and execution point line as defined in FlatLaf Dark color profile: !nb-breakpoints.png! was (Author: alexfalappa): I can confirm [~DevCharly] investigation. For reference here is the right color of enabled/disabled breakpoint lines and execution point line: !nb-breakpoints.png! > Breakpoint background color in FlatLaF prevents reading text > > > Key: NETBEANS-3942 > URL: https://issues.apache.org/jira/browse/NETBEANS-3942 > Project: NetBeans > Issue Type: Bug >Affects Versions: 11.3 >Reporter: Jaroslav Tulach >Assignee: Karl Tauber >Priority: Minor > Attachments: image-2020-03-17-18-16-27-097.png, nb-breakpoints.png > > > I am trying NetBeans 11.3 and FlatLaF dark and I have a feeling that colors > of various debugging background lines were not adjusted. At least I have hard > time reading text under a breakpoint (too red) or current line (too green). -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-3942) Breakpoint background color in FlatLaF prevents reading text
[ https://issues.apache.org/jira/browse/NETBEANS-3942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Falappa updated NETBEANS-3942: - Attachment: (was: nb-breakpoints.png) > Breakpoint background color in FlatLaF prevents reading text > > > Key: NETBEANS-3942 > URL: https://issues.apache.org/jira/browse/NETBEANS-3942 > Project: NetBeans > Issue Type: Bug >Affects Versions: 11.3 >Reporter: Jaroslav Tulach >Assignee: Karl Tauber >Priority: Minor > Attachments: image-2020-03-17-18-16-27-097.png, nb-breakpoints.png > > > I am trying NetBeans 11.3 and FlatLaF dark and I have a feeling that colors > of various debugging background lines were not adjusted. At least I have hard > time reading text under a breakpoint (too red) or current line (too green). -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-3942) Breakpoint background color in FlatLaF prevents reading text
[ https://issues.apache.org/jira/browse/NETBEANS-3942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Falappa updated NETBEANS-3942: - Attachment: nb-breakpoints.png > Breakpoint background color in FlatLaF prevents reading text > > > Key: NETBEANS-3942 > URL: https://issues.apache.org/jira/browse/NETBEANS-3942 > Project: NetBeans > Issue Type: Bug >Affects Versions: 11.3 >Reporter: Jaroslav Tulach >Assignee: Karl Tauber >Priority: Minor > Attachments: image-2020-03-17-18-16-27-097.png, nb-breakpoints.png > > > I am trying NetBeans 11.3 and FlatLaF dark and I have a feeling that colors > of various debugging background lines were not adjusted. At least I have hard > time reading text under a breakpoint (too red) or current line (too green). -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-3942) Breakpoint background color in FlatLaF prevents reading text
[ https://issues.apache.org/jira/browse/NETBEANS-3942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Falappa updated NETBEANS-3942: - Attachment: nb-breakpoints.png > Breakpoint background color in FlatLaF prevents reading text > > > Key: NETBEANS-3942 > URL: https://issues.apache.org/jira/browse/NETBEANS-3942 > Project: NetBeans > Issue Type: Bug >Affects Versions: 11.3 >Reporter: Jaroslav Tulach >Assignee: Karl Tauber >Priority: Minor > Attachments: image-2020-03-17-18-16-27-097.png, nb-breakpoints.png > > > I am trying NetBeans 11.3 and FlatLaF dark and I have a feeling that colors > of various debugging background lines were not adjusted. At least I have hard > time reading text under a breakpoint (too red) or current line (too green). -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-3942) Breakpoint background color in FlatLaF prevents reading text
[ https://issues.apache.org/jira/browse/NETBEANS-3942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061724#comment-17061724 ] Alessandro Falappa commented on NETBEANS-3942: -- I can confirm [~DevCharly] investigation. For reference here is the right color of enabled/disabled breakpoint lines and execution point line: !nb-breakpoints.png! > Breakpoint background color in FlatLaF prevents reading text > > > Key: NETBEANS-3942 > URL: https://issues.apache.org/jira/browse/NETBEANS-3942 > Project: NetBeans > Issue Type: Bug >Affects Versions: 11.3 >Reporter: Jaroslav Tulach >Assignee: Karl Tauber >Priority: Minor > Attachments: image-2020-03-17-18-16-27-097.png, nb-breakpoints.png > > > I am trying NetBeans 11.3 and FlatLaF dark and I have a feeling that colors > of various debugging background lines were not adjusted. At least I have hard > time reading text under a breakpoint (too red) or current line (too green). -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Resolved] (NETBEANS-3943) Ctrl+PgUp/PgDown doesn't switch tabs in FlatLaf
[ https://issues.apache.org/jira/browse/NETBEANS-3943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Falappa resolved NETBEANS-3943. -- Resolution: Duplicate > Ctrl+PgUp/PgDown doesn't switch tabs in FlatLaf > --- > > Key: NETBEANS-3943 > URL: https://issues.apache.org/jira/browse/NETBEANS-3943 > Project: NetBeans > Issue Type: Bug >Affects Versions: 11.3 >Reporter: Jaroslav Tulach >Assignee: Karl Tauber >Priority: Major > > When in editor I am used to Ctrl+PgUp and Ctrl+PgDn to move to next and > previous tabs. This is not working with FlatLaF (dark). -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Created] (NETBEANS-3902) Tomcat manager role credentials not remembered
Alessandro Falappa created NETBEANS-3902:
Summary: Tomcat manager role credentials not remembered
Key: NETBEANS-3902
URL: https://issues.apache.org/jira/browse/NETBEANS-3902
Project: NetBeans
Issue Type: Bug
Components: serverplugins - Tomcat
Affects Versions: 11.3
Reporter: Alessandro Falappa
*Steps*:
# Tools > Server
# Select Add Server
# Select Apache Tomcat or TomEE
# Press Next
# Fill location of Tomcat installation
# Specify existing manager role username ({{manager}} in my case)
# Specify existing manager role password
# Press Finish
# Create a new Maven Web project
# Create a servlet class in the project
# Run project
*Expected*: the project is compiled, Tomcat started, the project is deployed
and the browser opened on the project context URL
*Actual*: the project is compiled, Tomcat is started, a dialog asking for
manager role credentials is displayed. Once the credentials are re-entered the
project is deployed and the browser opened
# dd a new Tomcat server
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-3902) Tomcat manager role credentials not remembered
[
https://issues.apache.org/jira/browse/NETBEANS-3902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alessandro Falappa updated NETBEANS-3902:
-
Description:
*Steps*:
# Tools > Server
# Select Add Server
# Select Apache Tomcat or TomEE
# Press Next
# Fill location of Tomcat installation
# Specify existing manager role username ({{manager}} in my case)
# Specify existing manager role password
# Press Finish
# Create a new Maven Web project
# Create a servlet class in the project
# Run project
*Expected*: the project is compiled, Tomcat started, the project is deployed
and the browser opened on the project context URL
*Actual*: the project is compiled, Tomcat is started, a dialog asking for
manager role credentials is displayed. Once the credentials are re-entered the
project is deployed and the browser opened
was:
*Steps*:
# Tools > Server
# Select Add Server
# Select Apache Tomcat or TomEE
# Press Next
# Fill location of Tomcat installation
# Specify existing manager role username ({{manager}} in my case)
# Specify existing manager role password
# Press Finish
# Create a new Maven Web project
# Create a servlet class in the project
# Run project
*Expected*: the project is compiled, Tomcat started, the project is deployed
and the browser opened on the project context URL
*Actual*: the project is compiled, Tomcat is started, a dialog asking for
manager role credentials is displayed. Once the credentials are re-entered the
project is deployed and the browser opened
# dd a new Tomcat server
> Tomcat manager role credentials not remembered
> --
>
> Key: NETBEANS-3902
> URL: https://issues.apache.org/jira/browse/NETBEANS-3902
> Project: NetBeans
> Issue Type: Bug
> Components: serverplugins - Tomcat
>Affects Versions: 11.3
>Reporter: Alessandro Falappa
>Priority: Minor
>
> *Steps*:
> # Tools > Server
> # Select Add Server
> # Select Apache Tomcat or TomEE
> # Press Next
> # Fill location of Tomcat installation
> # Specify existing manager role username ({{manager}} in my case)
> # Specify existing manager role password
> # Press Finish
> # Create a new Maven Web project
> # Create a servlet class in the project
> # Run project
> *Expected*: the project is compiled, Tomcat started, the project is deployed
> and the browser opened on the project context URL
> *Actual*: the project is compiled, Tomcat is started, a dialog asking for
> manager role credentials is displayed. Once the credentials are re-entered
> the project is deployed and the browser opened
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-3889) Hardcoded color in New Servlet wizard
[ https://issues.apache.org/jira/browse/NETBEANS-3889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Falappa updated NETBEANS-3889: - Attachment: (was: image-2020-02-17-14-13-06-590.png) > Hardcoded color in New Servlet wizard > - > > Key: NETBEANS-3889 > URL: https://issues.apache.org/jira/browse/NETBEANS-3889 > Project: NetBeans > Issue Type: Bug > Components: ide - UI >Affects Versions: 11.3 >Reporter: Alessandro Falappa >Priority: Minor > Attachments: image-2020-02-17-14-13-17-971.png > > > The third step of the _New Servlet_ wizard has a table with an hardcoded > light background. > This is most noticeable on a dark LAF: > !image-2020-02-17-14-13-17-971.png! -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Created] (NETBEANS-3889) Hardcoded color in New Servlet wizard
Alessandro Falappa created NETBEANS-3889: Summary: Hardcoded color in New Servlet wizard Key: NETBEANS-3889 URL: https://issues.apache.org/jira/browse/NETBEANS-3889 Project: NetBeans Issue Type: Bug Components: ide - UI Affects Versions: 11.3 Reporter: Alessandro Falappa Attachments: image-2020-02-17-14-13-06-590.png, image-2020-02-17-14-13-17-971.png The third step of the _New Servlet_ wizard has a table with an hardcoded light background. This is most noticeable on a dark LAF: !image-2020-02-17-14-13-17-971.png! -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-3889) Hardcoded color in New Servlet wizard
[ https://issues.apache.org/jira/browse/NETBEANS-3889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Falappa updated NETBEANS-3889: - Description: The third step of the _New Servlet_ wizard has a table with an hardcoded light background. This is most noticeable on a dark LAF: !image-2020-02-17-14-13-17-971.png! was: The third step of the _New Servlet_ wizard has a table with an hardcoded light background. This is most noticeable on a dark LAF: !image-2020-02-17-14-13-17-971.png! > Hardcoded color in New Servlet wizard > - > > Key: NETBEANS-3889 > URL: https://issues.apache.org/jira/browse/NETBEANS-3889 > Project: NetBeans > Issue Type: Bug > Components: ide - UI >Affects Versions: 11.3 >Reporter: Alessandro Falappa >Priority: Minor > Attachments: image-2020-02-17-14-13-06-590.png, > image-2020-02-17-14-13-17-971.png > > > The third step of the _New Servlet_ wizard has a table with an hardcoded > light background. > This is most noticeable on a dark LAF: > !image-2020-02-17-14-13-17-971.png! -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Assigned] (NETBEANS-3873) Hardcoded color in New Project from Maven Archetype
[ https://issues.apache.org/jira/browse/NETBEANS-3873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Falappa reassigned NETBEANS-3873: Assignee: Alessandro Falappa > Hardcoded color in New Project from Maven Archetype > --- > > Key: NETBEANS-3873 > URL: https://issues.apache.org/jira/browse/NETBEANS-3873 > Project: NetBeans > Issue Type: Bug > Components: projects - Maven >Affects Versions: 11.3 >Reporter: Alessandro Falappa >Assignee: Alessandro Falappa >Priority: Minor > Labels: pull-request-available > Attachments: image-2020-02-13-13-43-28-516.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > In step 2 of _New Project from Maven Archetype_ the description text area has > probably an hardcoded white background, the description text is barely > visible in dark LAFs like FlatDark: > !image-2020-02-13-13-43-28-516.png! -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Created] (NETBEANS-3875) Jersey project creation from archetype fails
Alessandro Falappa created NETBEANS-3875:
Summary: Jersey project creation from archetype fails
Key: NETBEANS-3875
URL: https://issues.apache.org/jira/browse/NETBEANS-3875
Project: NetBeans
Issue Type: Bug
Components: projects - Maven
Affects Versions: 11.3
Reporter: Alessandro Falappa
# New Project > Java with Maven > Project from Archetype
# Search for *jersey*
# Select the first {{jersey-quickstart-archetype}} archetype item (group id:
{{org.glassfish.jersey.archetypes}} version: {{2.30}})
# Press _Next_
# Choose foobar as *Project Name*
# Fill the other field and choose an empty directory as *Project Location*
# Press _Finish_
The project generation fails complaining a folder with name foobar exists. An
empty foobar folder is left in the choosen project location.
{code:java}
Building Maven Stub Project (No POM) 1
>>>
maven-archetype-plugin:2.4:generate (default-cli) > generate-sources @
standalone-pom >>><<< maven-archetype-plugin:2.4:generate (default-cli) <
generate-sources @ standalone-pom <<<--- maven-archetype-plugin:2.4:generate
(default-cli) @ standalone-pom ---
Generating project in Batch mode
Archetype defined by properties
Using following parameters for creating project from Old (1.x) Archetype:
jersey-quickstart-webapp:2.30
Parameter: basedir, Value: C:\Users\falappa\Documents\NetBeansProjects
Parameter: package, Value: af.foobar
Parameter: groupId, Value: af
Parameter: artifactId, Value: foobar
Parameter: packageName, Value: af.foobar
Parameter: version, Value: 1.0-SNAPSHOT
BUILD FAILURE
Total time: 1.484 s
Finished at: 2020-02-13T14:16:58+01:00
Final Memory: 11M/40M
Failed to execute goal
org.apache.maven.plugins:maven-archetype-plugin:2.4:generate (default-cli) on
project standalone-pom: Directory foobar already exists - please run from a
clean directory -> [Help 1]To see the full stack trace of the errors, re-run
Maven with the -e switch.
Re-run Maven using the -X switch to enable full debug logging.For more
information about the errors and possible solutions, please read the following
articles:
[Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException{code}
Probably the Maven from archetype wizard creates the folder prior to maven
archetype execution.
Not sure if this can be considered a bug in the jersey archetype instead.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-3873) Hardcoded color in New Project from Maven Archetype
[ https://issues.apache.org/jira/browse/NETBEANS-3873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Falappa updated NETBEANS-3873: - Description: In step 2 of _New Project from Maven Archetype_ the description text area has probably an hardcoded white background, the description text is barely visible in dark LAFs like FlatDark: !image-2020-02-13-13-43-28-516.png! was: In step 2 of _New Project from Maven Archetype_ the description text area has probably an hardcoded white background. The description text is barely visible in dark LAFs like FlatDark: !image-2020-02-13-13-43-28-516.png! > Hardcoded color in New Project from Maven Archetype > --- > > Key: NETBEANS-3873 > URL: https://issues.apache.org/jira/browse/NETBEANS-3873 > Project: NetBeans > Issue Type: Bug > Components: projects - Maven >Affects Versions: 11.3 >Reporter: Alessandro Falappa >Priority: Minor > Attachments: image-2020-02-13-13-43-28-516.png > > > In step 2 of _New Project from Maven Archetype_ the description text area has > probably an hardcoded white background, the description text is barely > visible in dark LAFs like FlatDark: > !image-2020-02-13-13-43-28-516.png! -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-3873) Hardcoded color in New Project from Maven Archetype
[ https://issues.apache.org/jira/browse/NETBEANS-3873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Falappa updated NETBEANS-3873: - Attachment: (was: bug-maven-archetype.png) > Hardcoded color in New Project from Maven Archetype > --- > > Key: NETBEANS-3873 > URL: https://issues.apache.org/jira/browse/NETBEANS-3873 > Project: NetBeans > Issue Type: Bug > Components: projects - Maven >Affects Versions: 11.3 >Reporter: Alessandro Falappa >Priority: Minor > Attachments: image-2020-02-13-13-43-28-516.png > > > In step 2 of _New Project from Maven Archetype_ the description text area has > probably an hardcoded white background. > The description text is barely visible in dark LAFs like FlatDark: > !image-2020-02-13-13-43-28-516.png! -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-3873) Hardcoded color in New Project from Maven Archetype
[ https://issues.apache.org/jira/browse/NETBEANS-3873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Falappa updated NETBEANS-3873: - Description: In step 2 of _New Project from Maven Archetype_ the description text area has probably an hardcoded white background. The description text is barely visible in dark LAFs like FlatDark: !image-2020-02-13-13-43-28-516.png! was: In step 2 of _New Project from Maven Archetype_ the description text area has probably an hardcoded white background. The description text is barely visible in dark LAFs like FlatDark, see attachment. > Hardcoded color in New Project from Maven Archetype > --- > > Key: NETBEANS-3873 > URL: https://issues.apache.org/jira/browse/NETBEANS-3873 > Project: NetBeans > Issue Type: Bug > Components: projects - Maven >Affects Versions: 11.3 >Reporter: Alessandro Falappa >Priority: Minor > Attachments: image-2020-02-13-13-43-28-516.png > > > In step 2 of _New Project from Maven Archetype_ the description text area has > probably an hardcoded white background. > The description text is barely visible in dark LAFs like FlatDark: > !image-2020-02-13-13-43-28-516.png! -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-3873) Hardcoded color in New Project from Maven Archetype
[ https://issues.apache.org/jira/browse/NETBEANS-3873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Falappa updated NETBEANS-3873: - Attachment: bug-maven-archetype.png > Hardcoded color in New Project from Maven Archetype > --- > > Key: NETBEANS-3873 > URL: https://issues.apache.org/jira/browse/NETBEANS-3873 > Project: NetBeans > Issue Type: Bug > Components: projects - Maven >Affects Versions: 11.3 >Reporter: Alessandro Falappa >Priority: Minor > Attachments: image-2020-02-13-13-43-28-516.png > > > In step 2 of _New Project from Maven Archetype_ the description text area has > probably an hardcoded white background. > The description text is barely visible in dark LAFs like FlatDark, see > attachment. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-3873) Hardcoded color in New Project from Maven Archetype
[ https://issues.apache.org/jira/browse/NETBEANS-3873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Falappa updated NETBEANS-3873: - Attachment: image-2020-02-13-13-43-28-516.png > Hardcoded color in New Project from Maven Archetype > --- > > Key: NETBEANS-3873 > URL: https://issues.apache.org/jira/browse/NETBEANS-3873 > Project: NetBeans > Issue Type: Bug > Components: projects - Maven >Affects Versions: 11.3 >Reporter: Alessandro Falappa >Priority: Minor > Attachments: image-2020-02-13-13-43-28-516.png > > > In step 2 of _New Project from Maven Archetype_ the description text area has > probably an hardcoded white background. > The description text is barely visible in dark LAFs like FlatDark, see > attachment. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Created] (NETBEANS-3873) Hardcoded color in New Project from Maven Archetype
Alessandro Falappa created NETBEANS-3873: Summary: Hardcoded color in New Project from Maven Archetype Key: NETBEANS-3873 URL: https://issues.apache.org/jira/browse/NETBEANS-3873 Project: NetBeans Issue Type: Bug Components: projects - Maven Affects Versions: 11.3 Reporter: Alessandro Falappa Attachments: bug-maven-archetype.png In step 2 of _New Project from Maven Archetype_ the description text area has probably an hardcoded white background. The description text is barely visible in dark LAFs like FlatDark, see attachment. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-3760) cannot load java.lang
[ https://issues.apache.org/jira/browse/NETBEANS-3760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17031757#comment-17031757 ] Alessandro Falappa commented on NETBEANS-3760: -- You are likely running NetBeans on a Java Runtime (JRE). NetBeans needs a Java Development Kit (JDK) > cannot load java.lang > - > > Key: NETBEANS-3760 > URL: https://issues.apache.org/jira/browse/NETBEANS-3760 > Project: NetBeans > Issue Type: Bug >Reporter: Jorge M Morales >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Resolved] (NETBEANS-3701) Color setting for changed and ignored files is not used in Projects and Files views with FlatLaf Dark
[ https://issues.apache.org/jira/browse/NETBEANS-3701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Falappa resolved NETBEANS-3701. -- Resolution: Duplicate > Color setting for changed and ignored files is not used in Projects and Files > views with FlatLaf Dark > - > > Key: NETBEANS-3701 > URL: https://issues.apache.org/jira/browse/NETBEANS-3701 > Project: NetBeans > Issue Type: Bug > Components: editor - Settings, FlatLaf >Affects Versions: 11.3 > Environment: Product Version: Apache NetBeans IDE DEV (Build > dev-71270e6cd2ac4daf7bfd1baf3727aa90735c60fc) > Java: 1.8.0_201; Java HotSpot(TM) 64-Bit Server VM 25.201-b09 > Runtime: Java(TM) SE Runtime Environment 1.8.0_201-b09 > System: Linux version 4.15.0-74-generic running on amd64; UTF-8; en_US (nb) >Reporter: Tomáš Procházka >Priority: Minor > > Files changed and ignored Under FlatLaf Dark look and feel are displayed in > white color in Projects and Files views instead of dark grey as in editor > tab. Problem seems to be that color setting is used only for editor tab and > not for views Projects and Files. > Steps to reproduce: > # Open project from Git. > # Create file, add it to ignored files, open that file. > # Use look and feel "FlatLaf Dark". > # Under Fonts & Colors set Versioning - Git - Ignored color to Magenta. > # Name of ignored file in editor tab will be magenta. > # Name of file in Projects and Files views will be white - it should be also > magenta. > Another places with white instead of magenta are list of files opened by > Ctrl+Tab and list of open files opened by button at the right side of open > tabs. > Same problem is with changed files - tab title shows blue filename for > changed file, but list in Projects, Files, swithing file with Ctrl+Tab and > list of open files in tab bar show file name in white color. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-3735) FlatLaf: Desktop does not repaint after closing the last editor tab.
[ https://issues.apache.org/jira/browse/NETBEANS-3735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Falappa updated NETBEANS-3735: - Labels: ide-ui (was: ) > FlatLaf: Desktop does not repaint after closing the last editor tab. > > > Key: NETBEANS-3735 > URL: https://issues.apache.org/jira/browse/NETBEANS-3735 > Project: NetBeans > Issue Type: Bug >Reporter: Laszlo Kishalmi >Assignee: Karl Tauber >Priority: Major > Labels: ide-ui > Attachments: FlatLafNoRepaint.mp4 > > > When all the side comonents are minimized and the last editor window is > closed the focus is moved to the global search, in this case the desktop does > not repaint. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-3758) "Run File" is often disabled after introducing a main() method
[ https://issues.apache.org/jira/browse/NETBEANS-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17029931#comment-17029931 ] Alessandro Falappa commented on NETBEANS-3758: -- Another guess is that your projects are on a filesystem where the file watching mechanism is not working properly, i.e. network mounted share. > "Run File" is often disabled after introducing a main() method > -- > > Key: NETBEANS-3758 > URL: https://issues.apache.org/jira/browse/NETBEANS-3758 > Project: NetBeans > Issue Type: Bug > Components: editor - Actions/Menu/Toolbar >Affects Versions: 11.1 >Reporter: Marco Herrn >Priority: Major > Labels: run > Attachments: main.png > > > Often when introducing a new `main` method into an existing class, the "Run > File" and "Debug File" menu entries are still disabled and is therefore > impossible to execute this `main` method. > In most cases it is necessary to closes netbeans and clear the netbeans cache > to be able to execute it, which is absolutely counterproductive if such a > method is only temporarily inserted for testing purposes. > It may be that this only happens with Maven projects, since all my projects > are maven based. > Please see the attached screenshot that shows the context menu after > introducing a new `main` method. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-3758) "Run File" is often disabled after introducing a main() method
[ https://issues.apache.org/jira/browse/NETBEANS-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17029928#comment-17029928 ] Alessandro Falappa commented on NETBEANS-3758: -- Have you saved the file after adding the main method? >From my experiments the entries are disabled until the file is saved. Works for me on maven projects. > "Run File" is often disabled after introducing a main() method > -- > > Key: NETBEANS-3758 > URL: https://issues.apache.org/jira/browse/NETBEANS-3758 > Project: NetBeans > Issue Type: Bug > Components: editor - Actions/Menu/Toolbar >Affects Versions: 11.1 >Reporter: Marco Herrn >Priority: Major > Labels: run > Attachments: main.png > > > Often when introducing a new `main` method into an existing class, the "Run > File" and "Debug File" menu entries are still disabled and is therefore > impossible to execute this `main` method. > In most cases it is necessary to closes netbeans and clear the netbeans cache > to be able to execute it, which is absolutely counterproductive if such a > method is only temporarily inserted for testing purposes. > It may be that this only happens with Maven projects, since all my projects > are maven based. > Please see the attached screenshot that shows the context menu after > introducing a new `main` method. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Resolved] (NETBEANS-3760) cannot load java.lang
[ https://issues.apache.org/jira/browse/NETBEANS-3760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Falappa resolved NETBEANS-3760. -- Resolution: Incomplete No description of problem > cannot load java.lang > - > > Key: NETBEANS-3760 > URL: https://issues.apache.org/jira/browse/NETBEANS-3760 > Project: NetBeans > Issue Type: Bug >Reporter: Jorge M Morales >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-3781) java运行不了
[ https://issues.apache.org/jira/browse/NETBEANS-3781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17029925#comment-17029925 ] Alessandro Falappa commented on NETBEANS-3781: -- Please rewrite the issue in english > java运行不了 > > > Key: NETBEANS-3781 > URL: https://issues.apache.org/jira/browse/NETBEANS-3781 > Project: NetBeans > Issue Type: Bug >Reporter: 鲍禹含 >Priority: Major > Attachments: messages.log, messages.log.1, messages.log.2, metrics, > uigestures, uigestures.1, updater.log.0 > > > 同样的程序前段时间在单位可以运行，回家之后点击运行，出现一个对话框，里面写着：Available Main Classes: > Initializing view,please wait... > 然后就一直卡在这不动了，不知道什么原因。 > 应该是哪里配置出了问题，不是程序的问题。 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-3792) Hardcoded colors for "Remove Surrounding Code" action
[ https://issues.apache.org/jira/browse/NETBEANS-3792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Falappa updated NETBEANS-3792: - Attachment: remove-surrounding-on-darktheme.png > Hardcoded colors for "Remove Surrounding Code" action > - > > Key: NETBEANS-3792 > URL: https://issues.apache.org/jira/browse/NETBEANS-3792 > Project: NetBeans > Issue Type: Bug > Components: editor - Painting Printing, ide - UI >Affects Versions: 11.2 >Reporter: Alessandro Falappa >Priority: Minor > Attachments: remove-surrounding-on-darktheme.png > > > The RemoveSurroundingCode action contains hardcoded colors here: > > [https://github.com/apache/netbeans/blob/accdbada0a9c5105bd3f06e435024230c1618316/java/java.editor/src/org/netbeans/modules/java/editor/codegen/RemoveSurroundingCodeAction.java#L215] > The choosen colors look too bright on dark themes. The colors should be taken > from the LAF's defaults or better exposed in the editor color profile and > made customizable. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Created] (NETBEANS-3792) Hardcoded colors for "Remove Surrounding Code" action
Alessandro Falappa created NETBEANS-3792: Summary: Hardcoded colors for "Remove Surrounding Code" action Key: NETBEANS-3792 URL: https://issues.apache.org/jira/browse/NETBEANS-3792 Project: NetBeans Issue Type: Bug Components: editor - Painting Printing, ide - UI Affects Versions: 11.2 Reporter: Alessandro Falappa The RemoveSurroundingCode action contains hardcoded colors here: [https://github.com/apache/netbeans/blob/accdbada0a9c5105bd3f06e435024230c1618316/java/java.editor/src/org/netbeans/modules/java/editor/codegen/RemoveSurroundingCodeAction.java#L215] The choosen colors look too bright on dark themes. The colors should be taken from the LAF's defaults or better exposed in the editor color profile and made customizable. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-3283) POM graph creation freezes NetBeans
[
https://issues.apache.org/jira/browse/NETBEANS-3283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16957924#comment-16957924
]
Alessandro Falappa commented on NETBEANS-3283:
--
This freeze does not happen with all maven projects but only with that
particular maven project.
Major priority cause only way out is to terminate IDE.
> POM graph creation freezes NetBeans
> ---
>
> Key: NETBEANS-3283
> URL: https://issues.apache.org/jira/browse/NETBEANS-3283
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Maven
>Affects Versions: 11.2
>Reporter: Alessandro Falappa
>Priority: Major
> Attachments: nb-graph-bug-thread-dump.txt
>
>
> NetBeans freezes when creating the graph of dependencies for a NetBeans
> Plugin maven project.
> Steps:
> * Clone [https://github.com/AlexFalappa/nb-springboot.git]
> * Open {{pom.xml}} file
> * Click on _Show Graph_
> The JVM process running NetBeans consumes about 30-40% of CPU but the UI is
> completely frozen with no other option than terminate NetBeans from the OS
> process manager.
> Took a stacktrace dump of the process (attached) but I am not sure how to
> diagnose the problem.
> The problematic part could be:
> {code}
> "AWT-EventQueue-0" #23 prio=6 os_prio=0 cpu=774656.25ms elapsed=18594.28s
> tid=0x2a2af800 nid=0x3a9c runnable [0x2b87c000]
>java.lang.Thread.State: RUNNABLE
> at
> java.util.Collections$UnmodifiableCollection$1.hasNext(java.base@11.0.4/Collections.java:1046)
> at
> org.netbeans.modules.java.graph.FruchtermanReingoldLayout.isThereFreeSpaceNonFixedSpace(FruchtermanReingoldLayout.java:351)
> at
> org.netbeans.modules.java.graph.FruchtermanReingoldLayout.relayoutNonFixed(FruchtermanReingoldLayout.java:391)
> at
> org.netbeans.modules.java.graph.FruchtermanReingoldLayout.doRelayoutNonFixed(FruchtermanReingoldLayout.java:371)
> at
> org.netbeans.modules.java.graph.FruchtermanReingoldLayout.performLayout(FruchtermanReingoldLayout.java:117)
> at
> org.netbeans.modules.java.graph.FruchtermanReingoldLayout.performLayout(FruchtermanReingoldLayout.java:69)
> at
> org.netbeans.api.visual.layout.SceneLayout$LayoutSceneListener.sceneValidated(SceneLayout.java:100)
> at org.netbeans.api.visual.widget.Scene.validate(Scene.java:378)
> at
> org.netbeans.modules.java.graph.DependencyGraphScene.highlightDepth(DependencyGraphScene.java:691)
> at
> org.netbeans.modules.maven.graph.DependencyGraphTopComponent.maxPathSpinnerStateChanged(DependencyGraphTopComponent.java:468)
> at
> org.netbeans.modules.maven.graph.DependencyGraphTopComponent.access$1100(DependencyGraphTopComponent.java:97)
> at
> org.netbeans.modules.maven.graph.DependencyGraphTopComponent$9.stateChanged(DependencyGraphTopComponent.java:431)
> at
> javax.swing.JSpinner.fireStateChanged(java.desktop@11.0.4/JSpinner.java:461)
> at
> javax.swing.JSpinner$ModelListener.stateChanged(java.desktop@11.0.4/JSpinner.java:388)
> at
> javax.swing.AbstractSpinnerModel.fireStateChanged(java.desktop@11.0.4/AbstractSpinnerModel.java:120)
> at
> javax.swing.SpinnerNumberModel.setMaximum(java.desktop@11.0.4/SpinnerNumberModel.java:278)
> at
> org.netbeans.modules.maven.graph.DependencyGraphTopComponent$10$3.run(DependencyGraphTopComponent.java:636)
> at
> java.awt.event.InvocationEvent.dispatch(java.desktop@11.0.4/InvocationEvent.java:313)
> at
> java.awt.EventQueue.dispatchEventImpl(java.desktop@11.0.4/EventQueue.java:770)
> at java.awt.EventQueue$4.run(java.desktop@11.0.4/EventQueue.java:721)
> at java.awt.EventQueue$4.run(java.desktop@11.0.4/EventQueue.java:715)
> at java.security.AccessController.doPrivileged(java.base@11.0.4/Native
> Method)
> at
> java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(java.base@11.0.4/ProtectionDomain.java:85)
> at
> java.awt.EventQueue.dispatchEvent(java.desktop@11.0.4/EventQueue.java:740)
> at
> org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:136)
> at
> java.awt.EventDispatchThread.pumpOneEventForFilters(java.desktop@11.0.4/EventDispatchThread.java:203)
> at
> java.awt.EventDispatchThread.pumpEventsForFilter(java.desktop@11.0.4/EventDispatchThread.java:124)
> at
> java.awt.EventDispatchThread.pumpEventsForHierarchy(java.desktop@11.0.4/EventDispatchThread.java:113)
> at
> java.awt.EventDispatchThread.pumpEvents(java.desktop@11.0.4/EventDispatchThread.java:109)
> at
> java.awt.EventDispatchThread.pumpEvents(java.desktop@11.0.4/EventDispatchThread.java:101)
> at
> java.awt.EventDispatchThread.run(java.desktop@11.0.4/EventDispatchThread.java:90)
> {code}
>
--
This message was sent by
[jira] [Updated] (NETBEANS-3283) POM graph creation freezes NetBeans
[
https://issues.apache.org/jira/browse/NETBEANS-3283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alessandro Falappa updated NETBEANS-3283:
-
Description:
NetBeans freezes when creating the graph of dependencies for a NetBeans Plugin
maven project.
Steps:
* Clone [https://github.com/AlexFalappa/nb-springboot.git]
* Open {{pom.xml}} file
* Click on _Show Graph_
The JVM process running NetBeans consumes about 30-40% of CPU but the UI is
completely frozen with no other option than terminate NetBeans from the OS
process manager.
Took a stacktrace dump of the process (attached) but I am not sure how to
diagnose the problem.
The problematic part could be:
{code}
"AWT-EventQueue-0" #23 prio=6 os_prio=0 cpu=774656.25ms elapsed=18594.28s
tid=0x2a2af800 nid=0x3a9c runnable [0x2b87c000]
java.lang.Thread.State: RUNNABLE
at
java.util.Collections$UnmodifiableCollection$1.hasNext(java.base@11.0.4/Collections.java:1046)
at
org.netbeans.modules.java.graph.FruchtermanReingoldLayout.isThereFreeSpaceNonFixedSpace(FruchtermanReingoldLayout.java:351)
at
org.netbeans.modules.java.graph.FruchtermanReingoldLayout.relayoutNonFixed(FruchtermanReingoldLayout.java:391)
at
org.netbeans.modules.java.graph.FruchtermanReingoldLayout.doRelayoutNonFixed(FruchtermanReingoldLayout.java:371)
at
org.netbeans.modules.java.graph.FruchtermanReingoldLayout.performLayout(FruchtermanReingoldLayout.java:117)
at
org.netbeans.modules.java.graph.FruchtermanReingoldLayout.performLayout(FruchtermanReingoldLayout.java:69)
at
org.netbeans.api.visual.layout.SceneLayout$LayoutSceneListener.sceneValidated(SceneLayout.java:100)
at org.netbeans.api.visual.widget.Scene.validate(Scene.java:378)
at
org.netbeans.modules.java.graph.DependencyGraphScene.highlightDepth(DependencyGraphScene.java:691)
at
org.netbeans.modules.maven.graph.DependencyGraphTopComponent.maxPathSpinnerStateChanged(DependencyGraphTopComponent.java:468)
at
org.netbeans.modules.maven.graph.DependencyGraphTopComponent.access$1100(DependencyGraphTopComponent.java:97)
at
org.netbeans.modules.maven.graph.DependencyGraphTopComponent$9.stateChanged(DependencyGraphTopComponent.java:431)
at
javax.swing.JSpinner.fireStateChanged(java.desktop@11.0.4/JSpinner.java:461)
at
javax.swing.JSpinner$ModelListener.stateChanged(java.desktop@11.0.4/JSpinner.java:388)
at
javax.swing.AbstractSpinnerModel.fireStateChanged(java.desktop@11.0.4/AbstractSpinnerModel.java:120)
at
javax.swing.SpinnerNumberModel.setMaximum(java.desktop@11.0.4/SpinnerNumberModel.java:278)
at
org.netbeans.modules.maven.graph.DependencyGraphTopComponent$10$3.run(DependencyGraphTopComponent.java:636)
at
java.awt.event.InvocationEvent.dispatch(java.desktop@11.0.4/InvocationEvent.java:313)
at
java.awt.EventQueue.dispatchEventImpl(java.desktop@11.0.4/EventQueue.java:770)
at java.awt.EventQueue$4.run(java.desktop@11.0.4/EventQueue.java:721)
at java.awt.EventQueue$4.run(java.desktop@11.0.4/EventQueue.java:715)
at java.security.AccessController.doPrivileged(java.base@11.0.4/Native
Method)
at
java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(java.base@11.0.4/ProtectionDomain.java:85)
at
java.awt.EventQueue.dispatchEvent(java.desktop@11.0.4/EventQueue.java:740)
at
org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:136)
at
java.awt.EventDispatchThread.pumpOneEventForFilters(java.desktop@11.0.4/EventDispatchThread.java:203)
at
java.awt.EventDispatchThread.pumpEventsForFilter(java.desktop@11.0.4/EventDispatchThread.java:124)
at
java.awt.EventDispatchThread.pumpEventsForHierarchy(java.desktop@11.0.4/EventDispatchThread.java:113)
at
java.awt.EventDispatchThread.pumpEvents(java.desktop@11.0.4/EventDispatchThread.java:109)
at
java.awt.EventDispatchThread.pumpEvents(java.desktop@11.0.4/EventDispatchThread.java:101)
at
java.awt.EventDispatchThread.run(java.desktop@11.0.4/EventDispatchThread.java:90)
{code}
was:
NetBeans freezes when creating the graph of dependencies for a NetBeans Plugin
maven project.
Steps:
* Clone [https://github.com/AlexFalappa/nb-springboot.git]
* Open {{pom.xml}} file
* Click on _Show Graph_
The JVM process running NetBeans consumes about 30-40% of CPU but the UI is
completely frozen.
Took a stacktrace dump of the process (attached) but I am not sure how to
diagnose the problem.
The problematic part could be:
{code}
"AWT-EventQueue-0" #23 prio=6 os_prio=0 cpu=774656.25ms elapsed=18594.28s
tid=0x2a2af800 nid=0x3a9c runnable [0x2b87c000]
java.lang.Thread.State: RUNNABLE
at
java.util.Collections$UnmodifiableCollection$1.hasNext(java.base@11.0.4/Collections.java:1046)
[jira] [Updated] (NETBEANS-3283) POM graph creation freezes NetBeans
[
https://issues.apache.org/jira/browse/NETBEANS-3283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alessandro Falappa updated NETBEANS-3283:
-
Description:
NetBeans freezes when creating the graph of dependencies for a NetBeans Plugin
maven project.
Steps:
* Clone [https://github.com/AlexFalappa/nb-springboot.git]
* Open {{pom.xml}} file
* Click on _Show Graph_
The JVM process running NetBeans consumes about 30-40% of CPU but the UI is
completely frozen.
Took a stacktrace dump of the process (attached) but I am not sure how to
diagnose the problem.
The problematic part could be:
{code}
"AWT-EventQueue-0" #23 prio=6 os_prio=0 cpu=774656.25ms elapsed=18594.28s
tid=0x2a2af800 nid=0x3a9c runnable [0x2b87c000]
java.lang.Thread.State: RUNNABLE
at
java.util.Collections$UnmodifiableCollection$1.hasNext(java.base@11.0.4/Collections.java:1046)
at
org.netbeans.modules.java.graph.FruchtermanReingoldLayout.isThereFreeSpaceNonFixedSpace(FruchtermanReingoldLayout.java:351)
at
org.netbeans.modules.java.graph.FruchtermanReingoldLayout.relayoutNonFixed(FruchtermanReingoldLayout.java:391)
at
org.netbeans.modules.java.graph.FruchtermanReingoldLayout.doRelayoutNonFixed(FruchtermanReingoldLayout.java:371)
at
org.netbeans.modules.java.graph.FruchtermanReingoldLayout.performLayout(FruchtermanReingoldLayout.java:117)
at
org.netbeans.modules.java.graph.FruchtermanReingoldLayout.performLayout(FruchtermanReingoldLayout.java:69)
at
org.netbeans.api.visual.layout.SceneLayout$LayoutSceneListener.sceneValidated(SceneLayout.java:100)
at org.netbeans.api.visual.widget.Scene.validate(Scene.java:378)
at
org.netbeans.modules.java.graph.DependencyGraphScene.highlightDepth(DependencyGraphScene.java:691)
at
org.netbeans.modules.maven.graph.DependencyGraphTopComponent.maxPathSpinnerStateChanged(DependencyGraphTopComponent.java:468)
at
org.netbeans.modules.maven.graph.DependencyGraphTopComponent.access$1100(DependencyGraphTopComponent.java:97)
at
org.netbeans.modules.maven.graph.DependencyGraphTopComponent$9.stateChanged(DependencyGraphTopComponent.java:431)
at
javax.swing.JSpinner.fireStateChanged(java.desktop@11.0.4/JSpinner.java:461)
at
javax.swing.JSpinner$ModelListener.stateChanged(java.desktop@11.0.4/JSpinner.java:388)
at
javax.swing.AbstractSpinnerModel.fireStateChanged(java.desktop@11.0.4/AbstractSpinnerModel.java:120)
at
javax.swing.SpinnerNumberModel.setMaximum(java.desktop@11.0.4/SpinnerNumberModel.java:278)
at
org.netbeans.modules.maven.graph.DependencyGraphTopComponent$10$3.run(DependencyGraphTopComponent.java:636)
at
java.awt.event.InvocationEvent.dispatch(java.desktop@11.0.4/InvocationEvent.java:313)
at
java.awt.EventQueue.dispatchEventImpl(java.desktop@11.0.4/EventQueue.java:770)
at java.awt.EventQueue$4.run(java.desktop@11.0.4/EventQueue.java:721)
at java.awt.EventQueue$4.run(java.desktop@11.0.4/EventQueue.java:715)
at java.security.AccessController.doPrivileged(java.base@11.0.4/Native
Method)
at
java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(java.base@11.0.4/ProtectionDomain.java:85)
at
java.awt.EventQueue.dispatchEvent(java.desktop@11.0.4/EventQueue.java:740)
at
org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:136)
at
java.awt.EventDispatchThread.pumpOneEventForFilters(java.desktop@11.0.4/EventDispatchThread.java:203)
at
java.awt.EventDispatchThread.pumpEventsForFilter(java.desktop@11.0.4/EventDispatchThread.java:124)
at
java.awt.EventDispatchThread.pumpEventsForHierarchy(java.desktop@11.0.4/EventDispatchThread.java:113)
at
java.awt.EventDispatchThread.pumpEvents(java.desktop@11.0.4/EventDispatchThread.java:109)
at
java.awt.EventDispatchThread.pumpEvents(java.desktop@11.0.4/EventDispatchThread.java:101)
at
java.awt.EventDispatchThread.run(java.desktop@11.0.4/EventDispatchThread.java:90)
{code}
was:
NetBeans freezes when creating the graph of dependencies for a NetBeans Plugin
maven project.
Steps:
* Clone [https://github.com/AlexFalappa/nb-springboot.git]
* Open {{pom.xml}} file
* Click on _Show Graph_
Took a stacktrace dump of the process (attached) the relevant part should be:
{code}
"AWT-EventQueue-0" #23 prio=6 os_prio=0 cpu=774656.25ms elapsed=18594.28s
tid=0x2a2af800 nid=0x3a9c runnable [0x2b87c000]
java.lang.Thread.State: RUNNABLE
at
java.util.Collections$UnmodifiableCollection$1.hasNext(java.base@11.0.4/Collections.java:1046)
at
org.netbeans.modules.java.graph.FruchtermanReingoldLayout.isThereFreeSpaceNonFixedSpace(FruchtermanReingoldLayout.java:351)
at
[jira] [Updated] (NETBEANS-3283) POM graph creation freezes NetBeans
[
https://issues.apache.org/jira/browse/NETBEANS-3283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alessandro Falappa updated NETBEANS-3283:
-
Attachment: nb-graph-bug-thread-dump.txt
> POM graph creation freezes NetBeans
> ---
>
> Key: NETBEANS-3283
> URL: https://issues.apache.org/jira/browse/NETBEANS-3283
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Maven
>Affects Versions: 11.2
>Reporter: Alessandro Falappa
>Priority: Major
> Attachments: nb-graph-bug-thread-dump.txt
>
>
> NetBeans freezes when creating the graph of dependencies for a NetBeans
> Plugin maven project.
> Steps:
> * Clone [https://github.com/AlexFalappa/nb-springboot.git]
> * Open {{pom.xml}} file
> * Click on _Show Graph_
> Took a stacktrace dump of the process (attached) the relevant part should be:
> {code}
> "AWT-EventQueue-0" #23 prio=6 os_prio=0 cpu=774656.25ms elapsed=18594.28s
> tid=0x2a2af800 nid=0x3a9c runnable [0x2b87c000]
>java.lang.Thread.State: RUNNABLE
> at
> java.util.Collections$UnmodifiableCollection$1.hasNext(java.base@11.0.4/Collections.java:1046)
> at
> org.netbeans.modules.java.graph.FruchtermanReingoldLayout.isThereFreeSpaceNonFixedSpace(FruchtermanReingoldLayout.java:351)
> at
> org.netbeans.modules.java.graph.FruchtermanReingoldLayout.relayoutNonFixed(FruchtermanReingoldLayout.java:391)
> at
> org.netbeans.modules.java.graph.FruchtermanReingoldLayout.doRelayoutNonFixed(FruchtermanReingoldLayout.java:371)
> at
> org.netbeans.modules.java.graph.FruchtermanReingoldLayout.performLayout(FruchtermanReingoldLayout.java:117)
> at
> org.netbeans.modules.java.graph.FruchtermanReingoldLayout.performLayout(FruchtermanReingoldLayout.java:69)
> at
> org.netbeans.api.visual.layout.SceneLayout$LayoutSceneListener.sceneValidated(SceneLayout.java:100)
> at org.netbeans.api.visual.widget.Scene.validate(Scene.java:378)
> at
> org.netbeans.modules.java.graph.DependencyGraphScene.highlightDepth(DependencyGraphScene.java:691)
> at
> org.netbeans.modules.maven.graph.DependencyGraphTopComponent.maxPathSpinnerStateChanged(DependencyGraphTopComponent.java:468)
> at
> org.netbeans.modules.maven.graph.DependencyGraphTopComponent.access$1100(DependencyGraphTopComponent.java:97)
> at
> org.netbeans.modules.maven.graph.DependencyGraphTopComponent$9.stateChanged(DependencyGraphTopComponent.java:431)
> at
> javax.swing.JSpinner.fireStateChanged(java.desktop@11.0.4/JSpinner.java:461)
> at
> javax.swing.JSpinner$ModelListener.stateChanged(java.desktop@11.0.4/JSpinner.java:388)
> at
> javax.swing.AbstractSpinnerModel.fireStateChanged(java.desktop@11.0.4/AbstractSpinnerModel.java:120)
> at
> javax.swing.SpinnerNumberModel.setMaximum(java.desktop@11.0.4/SpinnerNumberModel.java:278)
> at
> org.netbeans.modules.maven.graph.DependencyGraphTopComponent$10$3.run(DependencyGraphTopComponent.java:636)
> at
> java.awt.event.InvocationEvent.dispatch(java.desktop@11.0.4/InvocationEvent.java:313)
> at
> java.awt.EventQueue.dispatchEventImpl(java.desktop@11.0.4/EventQueue.java:770)
> at java.awt.EventQueue$4.run(java.desktop@11.0.4/EventQueue.java:721)
> at java.awt.EventQueue$4.run(java.desktop@11.0.4/EventQueue.java:715)
> at java.security.AccessController.doPrivileged(java.base@11.0.4/Native
> Method)
> at
> java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(java.base@11.0.4/ProtectionDomain.java:85)
> at
> java.awt.EventQueue.dispatchEvent(java.desktop@11.0.4/EventQueue.java:740)
> at
> org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:136)
> at
> java.awt.EventDispatchThread.pumpOneEventForFilters(java.desktop@11.0.4/EventDispatchThread.java:203)
> at
> java.awt.EventDispatchThread.pumpEventsForFilter(java.desktop@11.0.4/EventDispatchThread.java:124)
> at
> java.awt.EventDispatchThread.pumpEventsForHierarchy(java.desktop@11.0.4/EventDispatchThread.java:113)
> at
> java.awt.EventDispatchThread.pumpEvents(java.desktop@11.0.4/EventDispatchThread.java:109)
> at
> java.awt.EventDispatchThread.pumpEvents(java.desktop@11.0.4/EventDispatchThread.java:101)
> at
> java.awt.EventDispatchThread.run(java.desktop@11.0.4/EventDispatchThread.java:90)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Created] (NETBEANS-3283) POM graph creation freezes NetBeans
Alessandro Falappa created NETBEANS-3283:
Summary: POM graph creation freezes NetBeans
Key: NETBEANS-3283
URL: https://issues.apache.org/jira/browse/NETBEANS-3283
Project: NetBeans
Issue Type: Bug
Components: projects - Maven
Affects Versions: 11.2
Reporter: Alessandro Falappa
NetBeans freezes when creating the graph of dependencies for a NetBeans Plugin
maven project.
Steps:
* Clone [https://github.com/AlexFalappa/nb-springboot.git]
* Open {{pom.xml}} file
* Click on _Show Graph_
Took a stacktrace dump of the process (attached) the relevant part should be:
{code}
"AWT-EventQueue-0" #23 prio=6 os_prio=0 cpu=774656.25ms elapsed=18594.28s
tid=0x2a2af800 nid=0x3a9c runnable [0x2b87c000]
java.lang.Thread.State: RUNNABLE
at
java.util.Collections$UnmodifiableCollection$1.hasNext(java.base@11.0.4/Collections.java:1046)
at
org.netbeans.modules.java.graph.FruchtermanReingoldLayout.isThereFreeSpaceNonFixedSpace(FruchtermanReingoldLayout.java:351)
at
org.netbeans.modules.java.graph.FruchtermanReingoldLayout.relayoutNonFixed(FruchtermanReingoldLayout.java:391)
at
org.netbeans.modules.java.graph.FruchtermanReingoldLayout.doRelayoutNonFixed(FruchtermanReingoldLayout.java:371)
at
org.netbeans.modules.java.graph.FruchtermanReingoldLayout.performLayout(FruchtermanReingoldLayout.java:117)
at
org.netbeans.modules.java.graph.FruchtermanReingoldLayout.performLayout(FruchtermanReingoldLayout.java:69)
at
org.netbeans.api.visual.layout.SceneLayout$LayoutSceneListener.sceneValidated(SceneLayout.java:100)
at org.netbeans.api.visual.widget.Scene.validate(Scene.java:378)
at
org.netbeans.modules.java.graph.DependencyGraphScene.highlightDepth(DependencyGraphScene.java:691)
at
org.netbeans.modules.maven.graph.DependencyGraphTopComponent.maxPathSpinnerStateChanged(DependencyGraphTopComponent.java:468)
at
org.netbeans.modules.maven.graph.DependencyGraphTopComponent.access$1100(DependencyGraphTopComponent.java:97)
at
org.netbeans.modules.maven.graph.DependencyGraphTopComponent$9.stateChanged(DependencyGraphTopComponent.java:431)
at
javax.swing.JSpinner.fireStateChanged(java.desktop@11.0.4/JSpinner.java:461)
at
javax.swing.JSpinner$ModelListener.stateChanged(java.desktop@11.0.4/JSpinner.java:388)
at
javax.swing.AbstractSpinnerModel.fireStateChanged(java.desktop@11.0.4/AbstractSpinnerModel.java:120)
at
javax.swing.SpinnerNumberModel.setMaximum(java.desktop@11.0.4/SpinnerNumberModel.java:278)
at
org.netbeans.modules.maven.graph.DependencyGraphTopComponent$10$3.run(DependencyGraphTopComponent.java:636)
at
java.awt.event.InvocationEvent.dispatch(java.desktop@11.0.4/InvocationEvent.java:313)
at
java.awt.EventQueue.dispatchEventImpl(java.desktop@11.0.4/EventQueue.java:770)
at java.awt.EventQueue$4.run(java.desktop@11.0.4/EventQueue.java:721)
at java.awt.EventQueue$4.run(java.desktop@11.0.4/EventQueue.java:715)
at java.security.AccessController.doPrivileged(java.base@11.0.4/Native
Method)
at
java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(java.base@11.0.4/ProtectionDomain.java:85)
at
java.awt.EventQueue.dispatchEvent(java.desktop@11.0.4/EventQueue.java:740)
at
org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:136)
at
java.awt.EventDispatchThread.pumpOneEventForFilters(java.desktop@11.0.4/EventDispatchThread.java:203)
at
java.awt.EventDispatchThread.pumpEventsForFilter(java.desktop@11.0.4/EventDispatchThread.java:124)
at
java.awt.EventDispatchThread.pumpEventsForHierarchy(java.desktop@11.0.4/EventDispatchThread.java:113)
at
java.awt.EventDispatchThread.pumpEvents(java.desktop@11.0.4/EventDispatchThread.java:109)
at
java.awt.EventDispatchThread.pumpEvents(java.desktop@11.0.4/EventDispatchThread.java:101)
at
java.awt.EventDispatchThread.run(java.desktop@11.0.4/EventDispatchThread.java:90)
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Resolved] (NETBEANS-572) non existing dependencies are not shown under the Dependencies node
[
https://issues.apache.org/jira/browse/NETBEANS-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alessandro Falappa resolved NETBEANS-572.
-
Fix Version/s: 11.2
Resolution: Fixed
> non existing dependencies are not shown under the Dependencies node
> ---
>
> Key: NETBEANS-572
> URL: https://issues.apache.org/jira/browse/NETBEANS-572
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Maven
>Affects Versions: 9.0, 10.0
> Environment: Product Version: Apache NetBeans IDE Dev (Build
> incubator-netbeans-linux-386-on-20180402)
> Java: 10; Java HotSpot(TM) 64-Bit Server VM 10+46
> Runtime: Java(TM) SE Runtime Environment 10+46
> System: Linux version 4.15.14 running on amd64; UTF-8; en_US (nb)
> User directory: /home/alied/.netbeans/beta
> Cache directory: /home/alied/.cache/netbeans/beta
>Reporter: Alied Pérez Martínez
>Priority: Major
> Fix For: 11.2
>
> Attachments: image-2018-04-02-18-50-59-832.png,
> image-2018-04-02-18-52-29-308.png
>
>
> While testing Manually Install Artifact Test Case I added a non-existing
> dependency to the POM in order to manually add an artifact:
> {code:xml}
>
> org-apache-batik
> parser
> 1.7
>
> {code}
> *Expected:* A new node for the non-existing dependency should appear under
> the Dependencies node with an overlaid warning sign as Netbeans 8.2:
> !image-2018-04-02-18-52-29-308.png!
> *Actual:* The newly-added dependency does not appear under the Dependencies
> node:
> !image-2018-04-02-18-50-59-832.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-572) non existing dependencies are not shown under the Dependencies node
[
https://issues.apache.org/jira/browse/NETBEANS-572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16955855#comment-16955855
]
Alessandro Falappa commented on NETBEANS-572:
-
Also reported as NETBEANS-2783
Fixed in NB11.2, closing
> non existing dependencies are not shown under the Dependencies node
> ---
>
> Key: NETBEANS-572
> URL: https://issues.apache.org/jira/browse/NETBEANS-572
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Maven
>Affects Versions: 9.0, 10.0
> Environment: Product Version: Apache NetBeans IDE Dev (Build
> incubator-netbeans-linux-386-on-20180402)
> Java: 10; Java HotSpot(TM) 64-Bit Server VM 10+46
> Runtime: Java(TM) SE Runtime Environment 10+46
> System: Linux version 4.15.14 running on amd64; UTF-8; en_US (nb)
> User directory: /home/alied/.netbeans/beta
> Cache directory: /home/alied/.cache/netbeans/beta
>Reporter: Alied Pérez Martínez
>Priority: Major
> Attachments: image-2018-04-02-18-50-59-832.png,
> image-2018-04-02-18-52-29-308.png
>
>
> While testing Manually Install Artifact Test Case I added a non-existing
> dependency to the POM in order to manually add an artifact:
> {code:xml}
>
> org-apache-batik
> parser
> 1.7
>
> {code}
> *Expected:* A new node for the non-existing dependency should appear under
> the Dependencies node with an overlaid warning sign as Netbeans 8.2:
> !image-2018-04-02-18-52-29-308.png!
> *Actual:* The newly-added dependency does not appear under the Dependencies
> node:
> !image-2018-04-02-18-50-59-832.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-3198) Import of previous set options configuration not possible in 11.2-beta2
[
https://issues.apache.org/jira/browse/NETBEANS-3198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16954359#comment-16954359
]
Alessandro Falappa commented on NETBEANS-3198:
--
Verified, solved in 11.2-beta3
> Import of previous set options configuration not possible in 11.2-beta2
> ---
>
> Key: NETBEANS-3198
> URL: https://issues.apache.org/jira/browse/NETBEANS-3198
> Project: NetBeans
> Issue Type: Bug
>Affects Versions: 11.2
>Reporter: Miguel
>Assignee: Neil C Smith
>Priority: Critical
> Labels: pull-request-available
> Fix For: 11.2
>
> Attachments: options_import.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The configurations from a previous NetBeans version (11) cannot be imported
> in 11.2-beta2, via "_Tools -> Options -> Import_".
> The UI freezes, see attached screenshot
>
> The following exception is shown in the IDE log.
> It worked in the previous beta version.
>
> {code:java}
> java.lang.NullPointerExceptionjava.lang.NullPointerException at
> java.base/jdk.internal.math.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:1838)
> at
> java.base/jdk.internal.math.FloatingDecimal.parseDouble(FloatingDecimal.java:110)
> at java.base/java.lang.Double.parseDouble(Double.java:549) at
> org.netbeans.modules.options.export.OptionsChooserPanel.createOptionsTreeModel(OptionsChooserPanel.java:415)
> at
> org.netbeans.modules.options.export.OptionsChooserPanel.access$700(OptionsChooserPanel.java:72)[catch]
> at
> org.netbeans.modules.options.export.OptionsChooserPanel$6.run(OptionsChooserPanel.java:339)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-3198) Import of previous set options configuration not possible in 11.2-beta2
[
https://issues.apache.org/jira/browse/NETBEANS-3198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16945874#comment-16945874
]
Alessandro Falappa commented on NETBEANS-3198:
--
Confirmed. It happened to me as well with same exception.
Configuration settings were exported from NB8.2 and included only java
formatting options.
> Import of previous set options configuration not possible in 11.2-beta2
> ---
>
> Key: NETBEANS-3198
> URL: https://issues.apache.org/jira/browse/NETBEANS-3198
> Project: NetBeans
> Issue Type: Bug
>Affects Versions: 11.2
>Reporter: Miguel
>Priority: Major
> Attachments: options_import.png
>
>
> The configurations from a previous NetBeans version (11) cannot be imported
> in 11.2-beta2, via "_Tools -> Options -> Import_".
> The UI freezes, see attached screenshot
>
> The following exception is shown in the IDE log.
> It worked in the previous beta version.
>
> {code:java}
> java.lang.NullPointerExceptionjava.lang.NullPointerException at
> java.base/jdk.internal.math.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:1838)
> at
> java.base/jdk.internal.math.FloatingDecimal.parseDouble(FloatingDecimal.java:110)
> at java.base/java.lang.Double.parseDouble(Double.java:549) at
> org.netbeans.modules.options.export.OptionsChooserPanel.createOptionsTreeModel(OptionsChooserPanel.java:415)
> at
> org.netbeans.modules.options.export.OptionsChooserPanel.access$700(OptionsChooserPanel.java:72)[catch]
> at
> org.netbeans.modules.options.export.OptionsChooserPanel$6.run(OptionsChooserPanel.java:339)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Resolved] (NETBEANS-2783) Maven dependencies node does not show dependencies added editing POM
[
https://issues.apache.org/jira/browse/NETBEANS-2783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alessandro Falappa resolved NETBEANS-2783.
--
Resolution: Fixed
Fix Version/s: 11.2
Pull request has been merged. Will be in NB 11.2.
> Maven dependencies node does not show dependencies added editing POM
>
>
> Key: NETBEANS-2783
> URL: https://issues.apache.org/jira/browse/NETBEANS-2783
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Generic Projects UI, projects - Maven
>Affects Versions: 11.0, 11.1
> Environment: Product Version: Apache NetBeans IDE 11.1
> Updates: Updates available
> Java: 1.8.0_202; OpenJDK 64-Bit Server VM 25.202-b08
> Runtime: OpenJDK Runtime Environment 1.8.0_202-b08
> System: Windows 10 version 10.0 running on amd64; Cp1252; en_IE (nb)
> User directory: C:\Users\falappa\AppData\Roaming\NetBeans\11.1
> Cache directory: C:\Users\falappa\AppData\Local\NetBeans\Cache\11.1
>Reporter: Alessandro Falappa
>Assignee: Alessandro Falappa
>Priority: Major
> Labels: pull-request-available, regression
> Fix For: 11.2
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Steps:
> # Open or create a new maven project
> # Expand the Dependencies node in Projects view
> # Open pom.xml and add a dependency that has never been used before, i.e. is
> not in the local maven repository (.m2/repository)
> # Save pom.xml
> _Expected_ (works in NB 8.2): a jar entry with the name of the dependency
> artifact appears under the Dependencies node of the project with a yellow
> triangle badge indicating new dependency detected but missing local copy.
> _Actual_ (broken in NB11.0 and NB11.1-beta2): no jar entry appears, the log
> contains the following warning (here for commons-math3 dependency):
> {code:java}
> // WARNING [org.netbeans.modules.maven.nodes.DependenciesNode]: Could not
> determine module name for artifact
> jar:file:/C:/Users/falappa/.m2/repository/org/apache/commons/commons-math3/3.6.1/commons-math3-3.6.1.jar!/
> {code}
> In NB11.0 and NB11.1-beta2 after rebuilding the project the dependencies node
> gets updated and a regular jar entry appears. In NB8.2 after rebuilding the
> project the yellow triangle badge disappears.
> I had a look at the code and it looks like something got broken when adding
> modular Java support, i.e. in NB 9.0, as the code is trying to determine Java
> module names for each dependency.
> This is a regression, NetBeans 8.2 works, NetBeans 11.0 and NetBeans
> 11.1-beta2 do not, NetBeans 9.0 and 10.0 not tested.
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
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-2836) Cannot deploy gradle web application project if version not specified
[
https://issues.apache.org/jira/browse/NETBEANS-2836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alessandro Falappa resolved NETBEANS-2836.
--
Resolution: Fixed
Fix Version/s: 11.1
Does not reproduce in NB 11.1-beta4, neither on Linux nor on Windows
> Cannot deploy gradle web application project if version not specified
> -
>
> Key: NETBEANS-2836
> URL: https://issues.apache.org/jira/browse/NETBEANS-2836
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Gradle Java EE
>Affects Versions: 11.1
>Reporter: Alessandro Falappa
>Assignee: Laszlo Kishalmi
>Priority: Major
> Fix For: 11.1
>
>
> Steps:
> # New Project > Java with Gradle > Web Application (do NOT assign a version
> in the first step of the wizard) with a Tomcat application server
> # Run created project
> Exception in application server log:
> {code:java}
> 12-Jul-2019 11:43:31.330 SEVERE [main]
> org.apache.catalina.startup.ContextConfig.beforeStart Exception fixing
> docBase for context [/ee-gradle]
> java.io.FileNotFoundException:
> C:\Users\falappa\Documents\NetBeansProjects\ee7-gradle\build\exploded\ee7-gradle-1.0-SNAPSHOT.war
> (The system cannot find the file specified)
> at java.io.FileInputStream.open0(Native Method)
> at java.io.FileInputStream.open(FileInputStream.java:195)
> at java.io.FileInputStream.(FileInputStream.java:138)
> at java.io.FileInputStream.(FileInputStream.java:93)
> at
> sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:90)
> at
> sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:188)
> at org.apache.catalina.startup.ExpandWar.expand(ExpandWar.java:90)
> at
> org.apache.catalina.startup.ContextConfig.fixDocBase(ContextConfig.java:615)
> at
> org.apache.catalina.startup.ContextConfig.beforeStart(ContextConfig.java:748)
> at
> org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:303)
> at
> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:123)
> at
> org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:423)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:182)
> at
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:717)
> at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:690)
> at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:705)
> at
> org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:631)
> at
> org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1831)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
> at
> java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:112)
> at
> org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:526)
> at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:425)
> at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1576)
> at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:309)
> at
> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:123)
> at
> org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:423)
> at org.apache.catalina.util.LifecycleBase.setState(LifecycleBase.java:366)
> at
> org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:936)
> at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:841)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
> at
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1384)
> at
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1374)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
> at
> java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:134)
> at
> org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:909)
> at
> org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:262)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
> at
> org.apache.catalina.core.StandardService.startInternal(StandardService.java:421)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
> at
> org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:932)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
> at
[jira] [Resolved] (NETBEANS-2791) Glassfish and Payara servers download leaves spurious directory on filesystem
[ https://issues.apache.org/jira/browse/NETBEANS-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Falappa resolved NETBEANS-2791. -- Resolution: Resolved Fix Version/s: 11.1 Does not reproduce anymore in 11.1-beta4, on Linux and on Windows. > Glassfish and Payara servers download leaves spurious directory on filesystem > - > > Key: NETBEANS-2791 > URL: https://issues.apache.org/jira/browse/NETBEANS-2791 > Project: NetBeans > Issue Type: Bug > Components: serverplugins - GlassFish, serverplugins - Infrastructure >Affects Versions: 11.1 > Environment: Product Version: Apache NetBeans IDE 11.1 > Updates: Updates available > Java: 1.8.0_202; OpenJDK 64-Bit Server VM 25.202-b08 > Runtime: OpenJDK Runtime Environment 1.8.0_202-b08 > System: Windows 10 version 10.0 running on amd64; Cp1252; en_IE (nb) > User directory: C:\Users\falappa\AppData\Roaming\NetBeans\11.1 > Cache directory: C:\Users\falappa\AppData\Local\NetBeans\Cache\11.1 >Reporter: Alessandro Falappa >Priority: Minor > Fix For: 11.1 > > > Steps: > # Open Servers dialog via menu Tools > Server > # Click Add Server... > # Choose "GlassFish Server" or "Payara Server" > # Click "Next" button > # Specify an install location different from proposed one > # Choose a version > # Click on accept license checkbox > # Click Download Now button > _Observed_: The chosen GlassFish or Payara server distribution is downloaded > and installed in the chosen location but an additional sibling folder is > created containing a temporary 0 bytes file. The sibling folder is named > __*1* (note the final 1) and temporary file is named > _foo.tmp_ . > _Expected_: The chosen GlassFish or Payara server distribution is downloaded > and installed in the chosen location and no additional folders/files are > created or maybe created but removed at the end of installation process. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - 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-2791) Glassfish and Payara servers download leaves spurious directory on filesystem
[ https://issues.apache.org/jira/browse/NETBEANS-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16884746#comment-16884746 ] Alessandro Falappa commented on NETBEANS-2791: -- Seems fixed in NB11.1-beta4 (on Linux). Will try also on Windows then close. * [|https://issues.apache.org/jira/secure/AddComment!default.jspa?id=13244572] > Glassfish and Payara servers download leaves spurious directory on filesystem > - > > Key: NETBEANS-2791 > URL: https://issues.apache.org/jira/browse/NETBEANS-2791 > Project: NetBeans > Issue Type: Bug > Components: serverplugins - GlassFish, serverplugins - Infrastructure >Affects Versions: 11.1 > Environment: Product Version: Apache NetBeans IDE 11.1 > Updates: Updates available > Java: 1.8.0_202; OpenJDK 64-Bit Server VM 25.202-b08 > Runtime: OpenJDK Runtime Environment 1.8.0_202-b08 > System: Windows 10 version 10.0 running on amd64; Cp1252; en_IE (nb) > User directory: C:\Users\falappa\AppData\Roaming\NetBeans\11.1 > Cache directory: C:\Users\falappa\AppData\Local\NetBeans\Cache\11.1 >Reporter: Alessandro Falappa >Priority: Minor > > Steps: > # Open Servers dialog via menu Tools > Server > # Click Add Server... > # Choose "GlassFish Server" or "Payara Server" > # Click "Next" button > # Specify an install location different from proposed one > # Choose a version > # Click on accept license checkbox > # Click Download Now button > _Observed_: The chosen GlassFish or Payara server distribution is downloaded > and installed in the chosen location but an additional sibling folder is > created containing a temporary 0 bytes file. The sibling folder is named > __*1* (note the final 1) and temporary file is named > _foo.tmp_ . > _Expected_: The chosen GlassFish or Payara server distribution is downloaded > and installed in the chosen location and no additional folders/files are > created or maybe created but removed at the end of installation process. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - 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-2791) Glassfish and Payara servers download leaves spurious directory on filesystem
[ https://issues.apache.org/jira/browse/NETBEANS-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16884746#comment-16884746 ] Alessandro Falappa edited comment on NETBEANS-2791 at 7/14/19 7:59 PM: --- Seems fixed in NB11.1-beta4 (on Linux). Will try also on Windows then close. was (Author: alexfalappa): Seems fixed in NB11.1-beta4 (on Linux). Will try also on Windows then close. * [|https://issues.apache.org/jira/secure/AddComment!default.jspa?id=13244572] > Glassfish and Payara servers download leaves spurious directory on filesystem > - > > Key: NETBEANS-2791 > URL: https://issues.apache.org/jira/browse/NETBEANS-2791 > Project: NetBeans > Issue Type: Bug > Components: serverplugins - GlassFish, serverplugins - Infrastructure >Affects Versions: 11.1 > Environment: Product Version: Apache NetBeans IDE 11.1 > Updates: Updates available > Java: 1.8.0_202; OpenJDK 64-Bit Server VM 25.202-b08 > Runtime: OpenJDK Runtime Environment 1.8.0_202-b08 > System: Windows 10 version 10.0 running on amd64; Cp1252; en_IE (nb) > User directory: C:\Users\falappa\AppData\Roaming\NetBeans\11.1 > Cache directory: C:\Users\falappa\AppData\Local\NetBeans\Cache\11.1 >Reporter: Alessandro Falappa >Priority: Minor > > Steps: > # Open Servers dialog via menu Tools > Server > # Click Add Server... > # Choose "GlassFish Server" or "Payara Server" > # Click "Next" button > # Specify an install location different from proposed one > # Choose a version > # Click on accept license checkbox > # Click Download Now button > _Observed_: The chosen GlassFish or Payara server distribution is downloaded > and installed in the chosen location but an additional sibling folder is > created containing a temporary 0 bytes file. The sibling folder is named > __*1* (note the final 1) and temporary file is named > _foo.tmp_ . > _Expected_: The chosen GlassFish or Payara server distribution is downloaded > and installed in the chosen location and no additional folders/files are > created or maybe created but removed at the end of installation process. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - 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-2836) Cannot deploy gradle web application project if version not specified
[
https://issues.apache.org/jira/browse/NETBEANS-2836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16884744#comment-16884744
]
Alessandro Falappa commented on NETBEANS-2836:
--
Seems fixed in NB11.1-beta4 (on Linux).
Will try also on Windows then close.
> Cannot deploy gradle web application project if version not specified
> -
>
> Key: NETBEANS-2836
> URL: https://issues.apache.org/jira/browse/NETBEANS-2836
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Gradle Java EE
>Affects Versions: 11.1
>Reporter: Alessandro Falappa
>Assignee: Laszlo Kishalmi
>Priority: Major
>
> Steps:
> # New Project > Java with Gradle > Web Application (do NOT assign a version
> in the first step of the wizard) with a Tomcat application server
> # Run created project
> Exception in application server log:
> {code:java}
> 12-Jul-2019 11:43:31.330 SEVERE [main]
> org.apache.catalina.startup.ContextConfig.beforeStart Exception fixing
> docBase for context [/ee-gradle]
> java.io.FileNotFoundException:
> C:\Users\falappa\Documents\NetBeansProjects\ee7-gradle\build\exploded\ee7-gradle-1.0-SNAPSHOT.war
> (The system cannot find the file specified)
> at java.io.FileInputStream.open0(Native Method)
> at java.io.FileInputStream.open(FileInputStream.java:195)
> at java.io.FileInputStream.(FileInputStream.java:138)
> at java.io.FileInputStream.(FileInputStream.java:93)
> at
> sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:90)
> at
> sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:188)
> at org.apache.catalina.startup.ExpandWar.expand(ExpandWar.java:90)
> at
> org.apache.catalina.startup.ContextConfig.fixDocBase(ContextConfig.java:615)
> at
> org.apache.catalina.startup.ContextConfig.beforeStart(ContextConfig.java:748)
> at
> org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:303)
> at
> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:123)
> at
> org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:423)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:182)
> at
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:717)
> at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:690)
> at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:705)
> at
> org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:631)
> at
> org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1831)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
> at
> java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:112)
> at
> org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:526)
> at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:425)
> at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1576)
> at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:309)
> at
> org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:123)
> at
> org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:423)
> at org.apache.catalina.util.LifecycleBase.setState(LifecycleBase.java:366)
> at
> org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:936)
> at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:841)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
> at
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1384)
> at
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1374)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
> at
> java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:134)
> at
> org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:909)
> at
> org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:262)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
> at
> org.apache.catalina.core.StandardService.startInternal(StandardService.java:421)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
> at
> org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:932)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
> at
[jira] [Commented] (NETBEANS-2822) unable to open maven project settings dialog using netbeans 11.1 vc1
[
https://issues.apache.org/jira/browse/NETBEANS-2822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16883739#comment-16883739
]
Alessandro Falappa commented on NETBEANS-2822:
--
I think it would be better, the number of issues is already big and getting
bigger...
> unable to open maven project settings dialog using netbeans 11.1 vc1
>
>
> Key: NETBEANS-2822
> URL: https://issues.apache.org/jira/browse/NETBEANS-2822
> Project: NetBeans
> Issue Type: Bug
>Affects Versions: 11.1
> Environment: Netbeans 11.1 Vc1
> some java maven project
>Reporter: Tobias Warneke
>Priority: Major
>
> Using beta3 it works.
> If I try to open the dialog I get a payara module exception.
> The same happens if I have a configured payara server within netbeans.
> This happens after using Netbeans 11.1 Vc1 for the first time. Just taking
> over some configurations from Netbeans 11.0.
>
>
> {{java.lang.NullPointerException}}
> {{ at
> org.netbeans.modules.fish.payara.micro.project.MicroApplication.getInstance(MicroApplication.java:149)}}
> {{ at
> org.netbeans.modules.fish.payara.micro.project.MicroPropertiesPanelProvider.createCategory(MicroPropertiesPanelProvider.java:44)}}
> {{ at
> org.netbeans.spi.project.ui.support.ProjectCustomizer$DelegateCategoryProvider.readCategories(ProjectCustomizer.java:647)}}
> {{ at
> org.netbeans.spi.project.ui.support.ProjectCustomizer$DelegateCategoryProvider.getSubCategories(ProjectCustomizer.java:608)}}
> {{ at
> org.netbeans.spi.project.ui.support.ProjectCustomizer.createCustomizerDialog(ProjectCustomizer.java:235)}}
> {{ at
> org.netbeans.modules.maven.customizer.CustomizerProviderImpl$1.run(CustomizerProviderImpl.java:155)}}
> {{ at
> org.netbeans.modules.openide.util.NbMutexEventProvider$Event.doEvent(NbMutexEventProvider.java:95)}}
> {{ at
> org.netbeans.modules.openide.util.NbMutexEventProvider$Event.readAccess(NbMutexEventProvider.java:70)}}
> {{ at
> org.netbeans.modules.openide.util.LazyMutexImplementation.readAccess(LazyMutexImplementation.java:66)}}
> {{ at org.openide.util.Mutex.readAccess(Mutex.java:235)}}
> {{ at
> org.netbeans.modules.maven.customizer.CustomizerProviderImpl.showCustomizer(CustomizerProviderImpl.java:147)}}
> {{ at
> org.netbeans.modules.maven.customizer.CustomizerProviderImpl.showCustomizer(CustomizerProviderImpl.java:115)}}
> {{ at
> org.netbeans.modules.maven.customizer.CustomizerProviderImpl.showCustomizer(CustomizerProviderImpl.java:110)}}
> {{ at
> org.netbeans.modules.project.ui.actions.CustomizeProject$1$1.run(CustomizeProject.java:135)}}
> {{ at
> java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:313)}}
> {{ at
> java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:770)}}
> {{ at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721)}}
> {{ at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715)}}
> {{ at java.base/java.security.AccessController.doPrivileged(Native Method)}}
> {{ at
> java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)}}
> {{ at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:740)}}
> {{ at
> org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:136)}}
> {{[catch] at
> java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)}}
> {{ at
> java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)}}
> {{ at
> java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)}}
> {{ at
> java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109)}}
> {{ at
> java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)}}
> {{ at
> java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90)}}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
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-2822) unable to open maven project settings dialog using netbeans 11.1 vc1
[
https://issues.apache.org/jira/browse/NETBEANS-2822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16883730#comment-16883730
]
Alessandro Falappa commented on NETBEANS-2822:
--
I think this is a duplicate of NETBEANS-2824
The fix will be in next releases.
> unable to open maven project settings dialog using netbeans 11.1 vc1
>
>
> Key: NETBEANS-2822
> URL: https://issues.apache.org/jira/browse/NETBEANS-2822
> Project: NetBeans
> Issue Type: Bug
>Affects Versions: 11.1
> Environment: Netbeans 11.1 Vc1
> some java maven project
>Reporter: Tobias Warneke
>Priority: Major
>
> Using beta3 it works.
> If I try to open the dialog I get a payara module exception.
> The same happens if I have a configured payara server within netbeans.
> This happens after using Netbeans 11.1 Vc1 for the first time. Just taking
> over some configurations from Netbeans 11.0.
>
>
> {{java.lang.NullPointerException}}
> {{ at
> org.netbeans.modules.fish.payara.micro.project.MicroApplication.getInstance(MicroApplication.java:149)}}
> {{ at
> org.netbeans.modules.fish.payara.micro.project.MicroPropertiesPanelProvider.createCategory(MicroPropertiesPanelProvider.java:44)}}
> {{ at
> org.netbeans.spi.project.ui.support.ProjectCustomizer$DelegateCategoryProvider.readCategories(ProjectCustomizer.java:647)}}
> {{ at
> org.netbeans.spi.project.ui.support.ProjectCustomizer$DelegateCategoryProvider.getSubCategories(ProjectCustomizer.java:608)}}
> {{ at
> org.netbeans.spi.project.ui.support.ProjectCustomizer.createCustomizerDialog(ProjectCustomizer.java:235)}}
> {{ at
> org.netbeans.modules.maven.customizer.CustomizerProviderImpl$1.run(CustomizerProviderImpl.java:155)}}
> {{ at
> org.netbeans.modules.openide.util.NbMutexEventProvider$Event.doEvent(NbMutexEventProvider.java:95)}}
> {{ at
> org.netbeans.modules.openide.util.NbMutexEventProvider$Event.readAccess(NbMutexEventProvider.java:70)}}
> {{ at
> org.netbeans.modules.openide.util.LazyMutexImplementation.readAccess(LazyMutexImplementation.java:66)}}
> {{ at org.openide.util.Mutex.readAccess(Mutex.java:235)}}
> {{ at
> org.netbeans.modules.maven.customizer.CustomizerProviderImpl.showCustomizer(CustomizerProviderImpl.java:147)}}
> {{ at
> org.netbeans.modules.maven.customizer.CustomizerProviderImpl.showCustomizer(CustomizerProviderImpl.java:115)}}
> {{ at
> org.netbeans.modules.maven.customizer.CustomizerProviderImpl.showCustomizer(CustomizerProviderImpl.java:110)}}
> {{ at
> org.netbeans.modules.project.ui.actions.CustomizeProject$1$1.run(CustomizeProject.java:135)}}
> {{ at
> java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:313)}}
> {{ at
> java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:770)}}
> {{ at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721)}}
> {{ at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715)}}
> {{ at java.base/java.security.AccessController.doPrivileged(Native Method)}}
> {{ at
> java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)}}
> {{ at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:740)}}
> {{ at
> org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:136)}}
> {{[catch] at
> java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)}}
> {{ at
> java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)}}
> {{ at
> java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)}}
> {{ at
> java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109)}}
> {{ at
> java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)}}
> {{ at
> java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90)}}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
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-2836) Cannot deploy gradle web application project if version not specified
Alessandro Falappa created NETBEANS-2836:
Summary: Cannot deploy gradle web application project if version
not specified
Key: NETBEANS-2836
URL: https://issues.apache.org/jira/browse/NETBEANS-2836
Project: NetBeans
Issue Type: Bug
Components: projects - Gradle Java EE
Affects Versions: 11.1
Reporter: Alessandro Falappa
Assignee: Laszlo Kishalmi
Steps:
# New Project > Java with Gradle > Web Application (do NOT assign a version in
the first step of the wizard) with a Tomcat application server
# Run created project
Exception in application server log:
{code:java}
12-Jul-2019 11:43:31.330 SEVERE [main]
org.apache.catalina.startup.ContextConfig.beforeStart Exception fixing docBase
for context [/ee-gradle]
java.io.FileNotFoundException:
C:\Users\falappa\Documents\NetBeansProjects\ee7-gradle\build\exploded\ee7-gradle-1.0-SNAPSHOT.war
(The system cannot find the file specified)
at java.io.FileInputStream.open0(Native Method)
at java.io.FileInputStream.open(FileInputStream.java:195)
at java.io.FileInputStream.(FileInputStream.java:138)
at java.io.FileInputStream.(FileInputStream.java:93)
at
sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:90)
at
sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:188)
at org.apache.catalina.startup.ExpandWar.expand(ExpandWar.java:90)
at org.apache.catalina.startup.ContextConfig.fixDocBase(ContextConfig.java:615)
at org.apache.catalina.startup.ContextConfig.beforeStart(ContextConfig.java:748)
at
org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:303)
at
org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:123)
at
org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:423)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:182)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:717)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:690)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:705)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:631)
at
org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1831)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
at
java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:112)
at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:526)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:425)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1576)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:309)
at
org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:123)
at
org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:423)
at org.apache.catalina.util.LifecycleBase.setState(LifecycleBase.java:366)
at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:936)
at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:841)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1384)
at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1374)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
at
java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:134)
at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:909)
at
org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:262)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
at
org.apache.catalina.core.StandardService.startInternal(StandardService.java:421)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
at
org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:932)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
at org.apache.catalina.startup.Catalina.start(Catalina.java:633)
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.apache.catalina.startup.Bootstrap.start(Bootstrap.java:344)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:475)
{code}
It seems the application server is indicated to run a
[jira] [Created] (NETBEANS-2835) Assign context equal to project name in newly created Gradle Web Application projects
Alessandro Falappa created NETBEANS-2835:
Summary: Assign context equal to project name in newly created
Gradle Web Application projects
Key: NETBEANS-2835
URL: https://issues.apache.org/jira/browse/NETBEANS-2835
Project: NetBeans
Issue Type: Improvement
Components: projects - Gradle Java EE
Affects Versions: 11.1
Reporter: Alessandro Falappa
Assignee: Laszlo Kishalmi
Newly created Gradle Web Application projects have by default an empty context
path in {{src/main/webapp/WEB-INF/context.xml}}:
{code:xml}
{code}
I think it would be better to use the project name prepended with a slash.
{code:xml}
{code}
This is more consistent with the analogous maven web application project and
moreover it is a saner default when multiple projects are deployed on the same
application server.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
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-2824) No Properties dialog showing in 11.1vc1 for Java Application
[
https://issues.apache.org/jira/browse/NETBEANS-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16883583#comment-16883583
]
Alessandro Falappa commented on NETBEANS-2824:
--
I can reproduce.
Product Version: Apache NetBeans IDE 11.1
Java: 1.8.0_202; OpenJDK 64-Bit Server VM 25.202-b08
Runtime: OpenJDK Runtime Environment 1.8.0_202-b08
System: Windows 10 version 10.0 running on amd64; Cp1252; en_IE (nb)
User directory: C:\Users\falappa\AppData\Roaming\NetBeans\11.1
Cache directory: C:\Users\falappa\AppData\Local\NetBeans\Cache\11.1
> No Properties dialog showing in 11.1vc1 for Java Application
>
>
> Key: NETBEANS-2824
> URL: https://issues.apache.org/jira/browse/NETBEANS-2824
> Project: NetBeans
> Issue Type: Bug
> Components: editor - Options
>Affects Versions: 11.1
> Environment: Windows 10, AdoptOpenJDK 11.0.3
>Reporter: Benjamin Graf
>Assignee: Gaurav Gupta
>Priority: Critical
> Labels: pull-request-available
> Attachments: messages.log
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> mOpen project properties dialog on plain Java Application Maven project ends
> with:
> {code:java}
> java.lang.NullPointerException
> at
> org.netbeans.modules.fish.payara.micro.project.MicroApplication.getInstance(MicroApplication.java:149)
> at
> org.netbeans.modules.fish.payara.micro.project.MicroPropertiesPanelProvider.createCategory(MicroPropertiesPanelProvider.java:44)
> at
> org.netbeans.spi.project.ui.support.ProjectCustomizer$DelegateCategoryProvider.readCategories(ProjectCustomizer.java:647)
> at
> org.netbeans.spi.project.ui.support.ProjectCustomizer$DelegateCategoryProvider.getSubCategories(ProjectCustomizer.java:608)
> at
> org.netbeans.spi.project.ui.support.ProjectCustomizer.createCustomizerDialog(ProjectCustomizer.java:235)
> at
> org.netbeans.modules.maven.customizer.CustomizerProviderImpl$1.run(CustomizerProviderImpl.java:155)
> at
> org.netbeans.modules.openide.util.NbMutexEventProvider$Event.doEvent(NbMutexEventProvider.java:95)
> at
> org.netbeans.modules.openide.util.NbMutexEventProvider$Event.readAccess(NbMutexEventProvider.java:70)
> at
> org.netbeans.modules.openide.util.LazyMutexImplementation.readAccess(LazyMutexImplementation.java:66)
> at org.openide.util.Mutex.readAccess(Mutex.java:235)
> at
> org.netbeans.modules.maven.customizer.CustomizerProviderImpl.showCustomizer(CustomizerProviderImpl.java:147)
> at
> org.netbeans.modules.maven.customizer.CustomizerProviderImpl.showCustomizer(CustomizerProviderImpl.java:115)
> at
> org.netbeans.modules.maven.customizer.CustomizerProviderImpl.showCustomizer(CustomizerProviderImpl.java:110)
> at
> org.netbeans.modules.project.ui.actions.CustomizeProject$1$1.run(CustomizeProject.java:135)
> at
> java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:313)
> at
> java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:770)
> at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721)
> at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715)
> at java.base/java.security.AccessController.doPrivileged(Native Method)
> at
> java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
> at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:740)
> at
> org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:136)
> [catch] at
> java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
> at
> java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
> at
> java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
> at
> java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109)
> at
> java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
> at
> java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90)
> {code}
> Reproducable with following steps:
> * Install a fresh installation from scratch by using zip and deleting profile
> * Start Netbeans Application
> * Start "New project dialog"
> ** Create a new Java with Maven - Java Application project
> *** Download and Activate modules (nb-javac-impl!)
> *** Finish project creating
> * Open Properties on created project -> {color:#14892c}*it works!*{color}
> * Start "New project dialog"
> ** Create a new Java with Maven - Web Application project
> ** Cancel dialog after modules have been activated
> * Open Properties on previously created project ->
[jira] [Commented] (NETBEANS-2807) Installer: Failed to load module "canberra-gtk-module"
[
https://issues.apache.org/jira/browse/NETBEANS-2807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16882752#comment-16882752
]
Alessandro Falappa commented on NETBEANS-2807:
--
Ultimately, I think the GTK related message may be due to the fact that the
installer runs with the system look and feel which is
{{GtkLookAndFeel}} under Ubuntu.
We could fix this by having the installer use a cross platform look and feel
such as Nimbus or the ugly Metal.
> Installer: Failed to load module "canberra-gtk-module"
> --
>
> Key: NETBEANS-2807
> URL: https://issues.apache.org/jira/browse/NETBEANS-2807
> Project: NetBeans
> Issue Type: Bug
>Affects Versions: 11.1
> Environment: Ubuntu 18.04 64 bit
>Reporter: Ulf Zibis
>Priority: Minor
>
> $ sudo -H bash Apache-NetBeans-11.1-bin-linux-x64.sh
> Configuring the installer...
> Searching for JVM on the system...
> Extracting installation data...
> Running the installer wizard...
> Gtk-Message: 00:21:49.287: Failed to load module "canberra-gtk-module"
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
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-2783) Maven dependencies node does not show dependencies added editing POM
[
https://issues.apache.org/jira/browse/NETBEANS-2783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alessandro Falappa reassigned NETBEANS-2783:
Assignee: Alessandro Falappa
> Maven dependencies node does not show dependencies added editing POM
>
>
> Key: NETBEANS-2783
> URL: https://issues.apache.org/jira/browse/NETBEANS-2783
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Generic Projects UI, projects - Maven
>Affects Versions: 11.0, 11.1
> Environment: Product Version: Apache NetBeans IDE 11.1
> Updates: Updates available
> Java: 1.8.0_202; OpenJDK 64-Bit Server VM 25.202-b08
> Runtime: OpenJDK Runtime Environment 1.8.0_202-b08
> System: Windows 10 version 10.0 running on amd64; Cp1252; en_IE (nb)
> User directory: C:\Users\falappa\AppData\Roaming\NetBeans\11.1
> Cache directory: C:\Users\falappa\AppData\Local\NetBeans\Cache\11.1
>Reporter: Alessandro Falappa
>Assignee: Alessandro Falappa
>Priority: Major
> Labels: regression
>
> Steps:
> # Open or create a new maven project
> # Expand the Dependencies node in Projects view
> # Open pom.xml and add a dependency that has never been used before, i.e. is
> not in the local maven repository (.m2/repository)
> # Save pom.xml
> _Expected_ (works in NB 8.2): a jar entry with the name of the dependency
> artifact appears under the Dependencies node of the project with a yellow
> triangle badge indicating new dependency detected but missing local copy.
> _Actual_ (broken in NB11.0 and NB11.1-beta2): no jar entry appears, the log
> contains the following warning (here for commons-math3 dependency):
> {code:java}
> // WARNING [org.netbeans.modules.maven.nodes.DependenciesNode]: Could not
> determine module name for artifact
> jar:file:/C:/Users/falappa/.m2/repository/org/apache/commons/commons-math3/3.6.1/commons-math3-3.6.1.jar!/
> {code}
> In NB11.0 and NB11.1-beta2 after rebuilding the project the dependencies node
> gets updated and a regular jar entry appears. In NB8.2 after rebuilding the
> project the yellow triangle badge disappears.
> I had a look at the code and it looks like something got broken when adding
> modular Java support, i.e. in NB 9.0, as the code is trying to determine Java
> module names for each dependency.
> This is a regression, NetBeans 8.2 works, NetBeans 11.0 and NetBeans
> 11.1-beta2 do not, NetBeans 9.0 and 10.0 not tested.
>
--
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-2807) Installer: Failed to load module "canberra-gtk-module"
[ https://issues.apache.org/jira/browse/NETBEANS-2807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16882113#comment-16882113 ] Alessandro Falappa commented on NETBEANS-2807: -- As I said is a matter of preferences, moreover I always work in scenarios where I am the only user of a personal PC, system wide installation could be indeed useful for use cases like programming teaching classrooms where the IDE is installed globally for every user. The risk I am concerned about, besides the installer having the power to write/overwrite anything while installing, is not knowing how exactly NetBeans behaves once running as normal user: what about installing plugins for example? Anyway I didn't intended to be rude. > Installer: Failed to load module "canberra-gtk-module" > -- > > Key: NETBEANS-2807 > URL: https://issues.apache.org/jira/browse/NETBEANS-2807 > Project: NetBeans > Issue Type: Bug >Affects Versions: 11.1 > Environment: Ubuntu 18.04 64 bit >Reporter: Ulf Zibis >Priority: Minor > > $ sudo -H bash Apache-NetBeans-11.1-bin-linux-x64.sh > Configuring the installer... > Searching for JVM on the system... > Extracting installation data... > Running the installer wizard... > Gtk-Message: 00:21:49.287: Failed to load module "canberra-gtk-module" -- 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-2752) java.lang.IllegalStateException: JsIndexer.postScanTask on startup
[
https://issues.apache.org/jira/browse/NETBEANS-2752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alessandro Falappa updated NETBEANS-2752:
-
Description:
Using 11.1 beta 2
{code:java}
java.lang.IllegalStateException: JsIndexer.postScanTask can be called only from
scanner thread.
at
org.netbeans.modules.javascript2.editor.index.JsIndexer$Factory.addPostScanTask(JsIndexer.java:421)
at
org.netbeans.modules.javascript2.editor.index.JsIndexer$PostScanProvider.addPostScanTask(JsIndexer.java:456)
at
org.netbeans.modules.html.angular.index.AngularJsIndexer.index(AngularJsIndexer.java:163)
at
org.netbeans.modules.parsing.spi.indexing.Indexable$MyAccessor$3.run(Indexable.java:225)
at
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.runIndexer(RepositoryUpdater.java:275)
at
org.netbeans.modules.parsing.spi.indexing.Indexable$MyAccessor.index(Indexable.java:223)
[catch] at
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work$2.run(RepositoryUpdater.java:3209)
at
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work$2.run(RepositoryUpdater.java:3231)
at
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work$2.run(RepositoryUpdater.java:3231)
at
org.netbeans.modules.parsing.impl.TaskProcessor.callUserTask(TaskProcessor.java:586)
at
org.netbeans.modules.parsing.api.ParserManager$UserTaskAction.run(ParserManager.java:130)
at
org.netbeans.modules.parsing.api.ParserManager$UserTaskAction.run(ParserManager.java:114)
at
org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:181)
at
org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:178)
at
org.netbeans.modules.masterfs.filebasedfs.utils.FileChangedManager.priorityIO(FileChangedManager.java:153)
at
org.netbeans.modules.masterfs.providers.ProvidedExtensions.priorityIO(ProvidedExtensions.java:335)
at
org.netbeans.modules.parsing.nb.DataObjectEnvFactory.runPriorityIO(DataObjectEnvFactory.java:118)
at org.netbeans.modules.parsing.impl.Utilities.runPriorityIO(Utilities.java:67)
at
org.netbeans.modules.parsing.impl.TaskProcessor.runUserTask(TaskProcessor.java:178)
at org.netbeans.modules.parsing.api.ParserManager.parse(ParserManager.java:81)
at
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work.indexEmbedding(RepositoryUpdater.java:3143)
at
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$RefreshEifIndices$1.call(RepositoryUpdater.java:4341)
at
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$RefreshEifIndices$1.call(RepositoryUpdater.java:4289)
at
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$4.run(RepositoryUpdater.java:2127)
at org.openide.util.lookup.Lookups.executeWith(Lookups.java:279)
at
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.runInContext(RepositoryUpdater.java:2123)
at
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.runInContext(RepositoryUpdater.java:2104)
at
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.access$1500(RepositoryUpdater.java:136)
at
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$RefreshEifIndices.getDone(RepositoryUpdater.java:4375)
at
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work.doTheWork(RepositoryUpdater.java:3420)
at
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Task._run(RepositoryUpdater.java:6183)
at
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Task.access$4300(RepositoryUpdater.java:5834)
at
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Task$2$1.run(RepositoryUpdater.java:6099)
at org.openide.util.lookup.Lookups.executeWith(Lookups.java:279)
at
org.netbeans.modules.parsing.impl.RunWhenScanFinishedSupport.performScan(RunWhenScanFinishedSupport.java:83)
at
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Task$2.call(RepositoryUpdater.java:6095)
at
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Task$2.call(RepositoryUpdater.java:6091)
at
org.netbeans.modules.masterfs.filebasedfs.utils.FileChangedManager.priorityIO(FileChangedManager.java:153)
at
org.netbeans.modules.masterfs.providers.ProvidedExtensions.priorityIO(ProvidedExtensions.java:335)
at
org.netbeans.modules.parsing.nb.DataObjectEnvFactory.runPriorityIO(DataObjectEnvFactory.java:118)
at org.netbeans.modules.parsing.impl.Utilities.runPriorityIO(Utilities.java:67)
at
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Task.run(RepositoryUpdater.java:6091)
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1418)
at org.netbeans.modules.openide.util.GlobalLookup.execute(GlobalLookup.java:45)
at org.openide.util.lookup.Lookups.executeWith(Lookups.java:278)
at
[jira] [Updated] (NETBEANS-2752) java.lang.IllegalStateException: JsIndexer.postScanTask on startup
[
https://issues.apache.org/jira/browse/NETBEANS-2752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alessandro Falappa updated NETBEANS-2752:
-
Environment:
Java: 11.0.2; OpenJDK 64-Bit Server VM 11.0.2+9
Runtime: OpenJDK Runtime Environment 11.0.2+9
System: Linux version 4.19.26-1-CHAKRA running on amd64; UTF-8; en_US (nb)
was:
Java: 11.0.2; OpenJDK 64-Bit Server VM 11.0.2+9
Runtime: OpenJDK Runtime Environment 11.0.2+9
System: Linux version 4.19.26-1-CHAKRA running on amd64; UTF-8; en_US (nb)
> java.lang.IllegalStateException: JsIndexer.postScanTask on startup
> --
>
> Key: NETBEANS-2752
> URL: https://issues.apache.org/jira/browse/NETBEANS-2752
> Project: NetBeans
> Issue Type: Bug
>Affects Versions: 11.1
> Environment: Java: 11.0.2; OpenJDK 64-Bit Server VM 11.0.2+9
> Runtime: OpenJDK Runtime Environment 11.0.2+9
> System: Linux version 4.19.26-1-CHAKRA running on amd64; UTF-8; en_US (nb)
>Reporter: Eric Schwarzenbach
>Priority: Major
>
> Using 11.1 beta 2
>
> {{java.lang.IllegalStateException: JsIndexer.postScanTask can be called only
> from scanner thread.}}
> {{ at
> org.netbeans.modules.javascript2.editor.index.JsIndexer$Factory.addPostScanTask(JsIndexer.java:421)}}
> {{ at
> org.netbeans.modules.javascript2.editor.index.JsIndexer$PostScanProvider.addPostScanTask(JsIndexer.java:456)}}
> {{ at
> org.netbeans.modules.html.angular.index.AngularJsIndexer.index(AngularJsIndexer.java:163)}}
> {{ at
> org.netbeans.modules.parsing.spi.indexing.Indexable$MyAccessor$3.run(Indexable.java:225)}}
> {{ at
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.runIndexer(RepositoryUpdater.java:275)}}
> {{ at
> org.netbeans.modules.parsing.spi.indexing.Indexable$MyAccessor.index(Indexable.java:223)}}
> {{[catch] at
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work$2.run(RepositoryUpdater.java:3209)}}
> {{ at
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work$2.run(RepositoryUpdater.java:3231)}}
> {{ at
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work$2.run(RepositoryUpdater.java:3231)}}
> {{ at
> org.netbeans.modules.parsing.impl.TaskProcessor.callUserTask(TaskProcessor.java:586)}}
> {{ at
> org.netbeans.modules.parsing.api.ParserManager$UserTaskAction.run(ParserManager.java:130)}}
> {{ at
> org.netbeans.modules.parsing.api.ParserManager$UserTaskAction.run(ParserManager.java:114)}}
> {{ at
> org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:181)}}
> {{ at
> org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:178)}}
> {{ at
> org.netbeans.modules.masterfs.filebasedfs.utils.FileChangedManager.priorityIO(FileChangedManager.java:153)}}
> {{ at
> org.netbeans.modules.masterfs.providers.ProvidedExtensions.priorityIO(ProvidedExtensions.java:335)}}
> {{ at
> org.netbeans.modules.parsing.nb.DataObjectEnvFactory.runPriorityIO(DataObjectEnvFactory.java:118)}}
> {{ at
> org.netbeans.modules.parsing.impl.Utilities.runPriorityIO(Utilities.java:67)}}
> {{ at
> org.netbeans.modules.parsing.impl.TaskProcessor.runUserTask(TaskProcessor.java:178)}}
> {{ at
> org.netbeans.modules.parsing.api.ParserManager.parse(ParserManager.java:81)}}
> {{ at
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work.indexEmbedding(RepositoryUpdater.java:3143)}}
> {{ at
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$RefreshEifIndices$1.call(RepositoryUpdater.java:4341)}}
> {{ at
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$RefreshEifIndices$1.call(RepositoryUpdater.java:4289)}}
> {{ at
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$4.run(RepositoryUpdater.java:2127)}}
> {{ at org.openide.util.lookup.Lookups.executeWith(Lookups.java:279)}}
> {{ at
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.runInContext(RepositoryUpdater.java:2123)}}
> {{ at
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.runInContext(RepositoryUpdater.java:2104)}}
> {{ at
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.access$1500(RepositoryUpdater.java:136)}}
> {{ at
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$RefreshEifIndices.getDone(RepositoryUpdater.java:4375)}}
> {{ at
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work.doTheWork(RepositoryUpdater.java:3420)}}
> {{ at
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Task._run(RepositoryUpdater.java:6183)}}
> {{ at
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Task.access$4300(RepositoryUpdater.java:5834)}}
> {{ at
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Task$2$1.run(RepositoryUpdater.java:6099)}}
> {{ at
[jira] [Updated] (NETBEANS-2766) AssertionError: Incorrect number of arguments
[
https://issues.apache.org/jira/browse/NETBEANS-2766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alessandro Falappa updated NETBEANS-2766:
-
Description:
This is 11.1 beta 2, and this error occurs just when starting netbeans
{code:java}
java.lang.AssertionError: Incorrect number of arguments; expected 1, found 0
at jdk.compiler/com.sun.tools.javac.util.Assert.error(Assert.java:162)
at
jdk.compiler/com.sun.tools.javac.comp.TransTypes.visitApply(TransTypes.java:636)
at
jdk.compiler/com.sun.tools.javac.tree.JCTree$JCMethodInvocation.accept(JCTree.java:1634)
at
jdk.compiler/com.sun.tools.javac.tree.TreeTranslator.translate(TreeTranslator.java:58)
at
jdk.compiler/com.sun.tools.javac.comp.TransTypes.translate(TransTypes.java:454)
at
jdk.compiler/com.sun.tools.javac.comp.TransTypes.visitExec(TransTypes.java:599)
at
jdk.compiler/com.sun.tools.javac.tree.JCTree$JCExpressionStatement.accept(JCTree.java:1452)
at
jdk.compiler/com.sun.tools.javac.tree.TreeTranslator.translate(TreeTranslator.java:58)
at
jdk.compiler/com.sun.tools.javac.tree.TreeTranslator.translate(TreeTranslator.java:70)
at
jdk.compiler/com.sun.tools.javac.tree.TreeTranslator.visitBlock(TreeTranslator.java:167)
at jdk.compiler/com.sun.tools.javac.tree.JCTree$JCBlock.accept(JCTree.java:1020)
at
jdk.compiler/com.sun.tools.javac.tree.TreeTranslator.translate(TreeTranslator.java:58)
at
jdk.compiler/com.sun.tools.javac.tree.TreeTranslator.translate(TreeTranslator.java:70)
at
jdk.compiler/com.sun.tools.javac.tree.TreeTranslator.visitClassDef(TreeTranslator.java:139)
at
jdk.compiler/com.sun.tools.javac.comp.TransTypes.translateClass(TransTypes.java:918)
at
jdk.compiler/com.sun.tools.javac.comp.TransTypes.visitClassDef(TransTypes.java:475)
at
jdk.compiler/com.sun.tools.javac.tree.JCTree$JCClassDecl.accept(JCTree.java:774)
at
jdk.compiler/com.sun.tools.javac.tree.TreeTranslator.translate(TreeTranslator.java:58)
at
jdk.compiler/com.sun.tools.javac.comp.TransTypes.translate(TransTypes.java:454)
at
jdk.compiler/com.sun.tools.javac.comp.TransTypes.translateTopLevelClass(TransTypes.java:942)
at
jdk.compiler/com.sun.tools.javac.main.JavaCompiler.desugar(JavaCompiler.java:1553)
at
jdk.compiler/com.sun.tools.javac.main.JavaCompiler.desugar(JavaCompiler.java:1432)
at
jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl$2.process(JavacTaskImpl.java:458)
at
jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl$Filter.run(JavacTaskImpl.java:506)
at
jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl.generate(JavacTaskImpl.java:461)
at
org.netbeans.modules.java.source.indexing.VanillaCompileWorker$2.run(VanillaCompileWorker.java:317)
at
org.netbeans.modules.java.source.parsing.FileManagerTransaction.runConcurrent(FileManagerTransaction.java:180)
[catch] at
org.netbeans.modules.java.source.indexing.VanillaCompileWorker.compile(VanillaCompileWorker.java:308)
at
org.netbeans.modules.java.source.indexing.JavaCustomIndexer.index(JavaCustomIndexer.java:361)
at
org.netbeans.modules.parsing.spi.indexing.Indexable$MyAccessor$2.run(Indexable.java:138)
at
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.runIndexer(RepositoryUpdater.java:275)
at
org.netbeans.modules.parsing.spi.indexing.Indexable$MyAccessor.index(Indexable.java:136)
at
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work.doIndex(RepositoryUpdater.java:2750)
at
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work.access$800(RepositoryUpdater.java:2154)
at
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work$1.run(RepositoryUpdater.java:2636)
at
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work$1.run(RepositoryUpdater.java:2634)
at
org.netbeans.modules.parsing.impl.indexing.errors.TaskCache.refreshTransaction(TaskCache.java:540)
at
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work.index(RepositoryUpdater.java:2634)
at
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$AbstractRootsWork$4.call(RepositoryUpdater.java:5714)
at
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$AbstractRootsWork$4.call(RepositoryUpdater.java:5622)
at
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$4.run(RepositoryUpdater.java:2127)
at org.openide.util.lookup.Lookups.executeWith(Lookups.java:279)
at
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.runInContext(RepositoryUpdater.java:2123)
at
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.runInContext(RepositoryUpdater.java:2104)
at
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.access$1500(RepositoryUpdater.java:136)
at
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$AbstractRootsWork.scanSource(RepositoryUpdater.java:5749)
at
org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$AbstractRootsWork.scanSources(RepositoryUpdater.java:5419)
at
[jira] [Commented] (NETBEANS-2791) Glassfish and Payara servers download leaves spurious directory on filesystem
[ https://issues.apache.org/jira/browse/NETBEANS-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16880379#comment-16880379 ] Alessandro Falappa commented on NETBEANS-2791: -- Tried again with beta3 now I end up with two complete installations in __ and __*1*. The second is useless, duplicated and wastes filesystem space. > Glassfish and Payara servers download leaves spurious directory on filesystem > - > > Key: NETBEANS-2791 > URL: https://issues.apache.org/jira/browse/NETBEANS-2791 > Project: NetBeans > Issue Type: Bug > Components: serverplugins - GlassFish, serverplugins - Infrastructure >Affects Versions: 11.1 > Environment: Product Version: Apache NetBeans IDE 11.1 > Updates: Updates available > Java: 1.8.0_202; OpenJDK 64-Bit Server VM 25.202-b08 > Runtime: OpenJDK Runtime Environment 1.8.0_202-b08 > System: Windows 10 version 10.0 running on amd64; Cp1252; en_IE (nb) > User directory: C:\Users\falappa\AppData\Roaming\NetBeans\11.1 > Cache directory: C:\Users\falappa\AppData\Local\NetBeans\Cache\11.1 >Reporter: Alessandro Falappa >Priority: Minor > > Steps: > # Open Servers dialog via menu Tools > Server > # Click Add Server... > # Choose "GlassFish Server" or "Payara Server" > # Click "Next" button > # Specify an install location different from proposed one > # Choose a version > # Click on accept license checkbox > # Click Download Now button > _Observed_: The chosen GlassFish or Payara server distribution is downloaded > and installed in the chosen location but an additional sibling folder is > created containing a temporary 0 bytes file. The sibling folder is named > __*1* (note the final 1) and temporary file is named > _foo.tmp_ . > _Expected_: The chosen GlassFish or Payara server distribution is downloaded > and installed in the chosen location and no additional folders/files are > created or maybe created but removed at the end of installation process. -- 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-2803) Installer doesn't value given install path correctly
[ https://issues.apache.org/jira/browse/NETBEANS-2803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16880374#comment-16880374 ] Alessandro Falappa commented on NETBEANS-2803: -- I think I understood why it is that way. After installation in __ you have all the installed files in __/netbeans and the uninstaller shell script in __/uninstall.sh. I don't know if the uninstaller shell script can be safely moved around or it is tied to the installation location. > Installer doesn't value given install path correctly > > > Key: NETBEANS-2803 > URL: https://issues.apache.org/jira/browse/NETBEANS-2803 > Project: NetBeans > Issue Type: Bug >Affects Versions: 11.1 > Environment: Ubuntu 18.04 64 bit >Reporter: Ulf Zibis >Priority: Major > Fix For: 11.1 > > > I said the installer (as root) to install into: > /opt/netbeans/11.1/ > but it installed into: > /opt/netbeans/11.1/netbeans/ > And please remember https://netbeans.org/bugzilla/show_bug.cgi?id=196072 > When using or even testing several NB versions, It's better to have them in > one root folder "netbeans", to not flood the OS programs folder so much. > Would also be convenient: > https://netbeans.org/bugzilla/show_bug.cgi?id=211531 -- 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-2807) Installer: Failed to load module "canberra-gtk-module"
[ https://issues.apache.org/jira/browse/NETBEANS-2807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16880365#comment-16880365 ] Alessandro Falappa commented on NETBEANS-2807: -- I have encountered that message too, but it doesn't affect installation and subsequent runs of NetBeans at all. I think it can be safely ignored. On a side note, I think system wide installation (installer running as root or via sudo like in this report) is a bit risky, I prefer installing locally with an unprivileged user and inside that user home dir. > Installer: Failed to load module "canberra-gtk-module" > -- > > Key: NETBEANS-2807 > URL: https://issues.apache.org/jira/browse/NETBEANS-2807 > Project: NetBeans > Issue Type: Bug >Affects Versions: 11.1 > Environment: Ubuntu 18.04 64 bit >Reporter: Ulf Zibis >Priority: Minor > > $ sudo -H bash Apache-NetBeans-11.1-bin-linux-x64.sh > Configuring the installer... > Searching for JVM on the system... > Extracting installation data... > Running the installer wizard... > Gtk-Message: 00:21:49.287: Failed to load module "canberra-gtk-module" -- 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-2801) IllegalSateException thrown when installing nbjavac plugin with OpenJDK11
[
https://issues.apache.org/jira/browse/NETBEANS-2801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16879043#comment-16879043
]
Alessandro Falappa edited comment on NETBEANS-2801 at 7/5/19 7:37 AM:
--
On dev mailing linst it was noted that this is a duplicate of
!/jira/secure/viewavatar?size=xsmall=21133=issuetype|width=16,height=16!
NETBEANS-2548IllegalStateException after installing nb-javac module .
Closing.
was (Author: alexfalappa):
On dev mailing linst it was noted that this is a duplicate of
!https://issues.apache.org/jira/secure/viewavatar?size=xsmall=21133=issuetype|width=16,height=16!
NETBEANS-2548IllegalStateException after installing nb-javac module .
Please close.
> IllegalSateException thrown when installing nbjavac plugin with OpenJDK11
> -
>
> Key: NETBEANS-2801
> URL: https://issues.apache.org/jira/browse/NETBEANS-2801
> Project: NetBeans
> Issue Type: Bug
> Components: java - Compiler
>Affects Versions: 11.1
> Environment: Product Version: Apache NetBeans IDE 11.1
> Java: 11.0.2; OpenJDK 64-Bit Server VM 11.0.2+9
> Runtime: OpenJDK Runtime Environment 11.0.2+9
> System: Windows 10 version 10.0 running on amd64; Cp1252; en_IE (nb)
> User directory: C:\Users\falappa\AppData\Roaming\NetBeans\11.1
> Cache directory: C:\Users\falappa\AppData\Local\NetBeans\Cache\11.1
>Reporter: Alessandro Falappa
>Priority: Major
>
> Steps:
> # Download NB 11.1-beta3 binary zip
> # Unpack
> # Edit etc/netbeans.conf and specify an OpenJDK11 in netbeans_jdkhome
> property
> # Run bin/netbeans64.exe
> # Click on My NetBenas on the Start Page
> # Click on Activate Features
> # Select JavaSE checkbox and click Activate
> # Close Plugins dialog
> # There should be a notification suggesting to install nbjavac
> # Open notification and follow instructions to install nbjavac plugin
> # After installation an exception is notified and the IDE log contains
> {code:java}
> // SEVERE [org.openide.util.RequestProcessor]: Error in RequestProcessor
> org.netbeans.core.startup.ModuleList$Listener
> java.lang.IllegalStateException: Host module
> StandardModule:org.netbeans.libs.javacapi jarFile:
> C:\Users\falappa\PortableApps\netbeans-11.1-beta3\java\modules\org-netbeans-libs-javacapi.jar
> was enabled before, will not accept fragment
> StandardModule:org.netbeans.modules.nbjavac.api jarFile:
> C:\Users\falappa\AppData\Roaming\NetBeans\11.1\modules\org-netbeans-modules-nbjavac-api.jar
> at org.netbeans.ModuleManager.attachModuleFragment(ModuleManager.java:1104)
> at org.netbeans.ModuleManager.maybeAddToEnableList(ModuleManager.java:1708)
> at org.netbeans.ModuleManager.simulateEnable(ModuleManager.java:1632)
> at org.netbeans.ModuleManager.simulateEnable(ModuleManager.java:1605)
> at org.netbeans.core.startup.ModuleList.installNew(ModuleList.java:289)
> at org.netbeans.core.startup.ModuleList.access$2400(ModuleList.java:93)
> at
> org.netbeans.core.startup.ModuleList$Listener.stepEnable(ModuleList.java:1384)
> at
> org.netbeans.core.startup.ModuleList$Listener.access$1400(ModuleList.java:982)
> at org.netbeans.core.startup.ModuleList$Listener$1.run(ModuleList.java:1206)
> at org.openide.filesystems.EventControl.runAtomicAction(EventControl.java:102)
> at org.openide.filesystems.FileSystem.runAtomicAction(FileSystem.java:494)
> at org.netbeans.core.startup.ModuleList$Listener.run(ModuleList.java:1182)
> at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1418)
> at
> org.netbeans.modules.openide.util.GlobalLookup.execute(GlobalLookup.java:45)
> at org.openide.util.lookup.Lookups.executeWith(Lookups.java:278)
> [catch] at
> org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2033)
> usage: ActivateFeatures
> {code}
> I have not experienced this exception when running NetBeans on OpenJDK 8
--
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-2801) IllegalSateException thrown when installing nbjavac plugin with OpenJDK11
[
https://issues.apache.org/jira/browse/NETBEANS-2801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alessandro Falappa resolved NETBEANS-2801.
--
Resolution: Duplicate
> IllegalSateException thrown when installing nbjavac plugin with OpenJDK11
> -
>
> Key: NETBEANS-2801
> URL: https://issues.apache.org/jira/browse/NETBEANS-2801
> Project: NetBeans
> Issue Type: Bug
> Components: java - Compiler
>Affects Versions: 11.1
> Environment: Product Version: Apache NetBeans IDE 11.1
> Java: 11.0.2; OpenJDK 64-Bit Server VM 11.0.2+9
> Runtime: OpenJDK Runtime Environment 11.0.2+9
> System: Windows 10 version 10.0 running on amd64; Cp1252; en_IE (nb)
> User directory: C:\Users\falappa\AppData\Roaming\NetBeans\11.1
> Cache directory: C:\Users\falappa\AppData\Local\NetBeans\Cache\11.1
>Reporter: Alessandro Falappa
>Priority: Major
>
> Steps:
> # Download NB 11.1-beta3 binary zip
> # Unpack
> # Edit etc/netbeans.conf and specify an OpenJDK11 in netbeans_jdkhome
> property
> # Run bin/netbeans64.exe
> # Click on My NetBenas on the Start Page
> # Click on Activate Features
> # Select JavaSE checkbox and click Activate
> # Close Plugins dialog
> # There should be a notification suggesting to install nbjavac
> # Open notification and follow instructions to install nbjavac plugin
> # After installation an exception is notified and the IDE log contains
> {code:java}
> // SEVERE [org.openide.util.RequestProcessor]: Error in RequestProcessor
> org.netbeans.core.startup.ModuleList$Listener
> java.lang.IllegalStateException: Host module
> StandardModule:org.netbeans.libs.javacapi jarFile:
> C:\Users\falappa\PortableApps\netbeans-11.1-beta3\java\modules\org-netbeans-libs-javacapi.jar
> was enabled before, will not accept fragment
> StandardModule:org.netbeans.modules.nbjavac.api jarFile:
> C:\Users\falappa\AppData\Roaming\NetBeans\11.1\modules\org-netbeans-modules-nbjavac-api.jar
> at org.netbeans.ModuleManager.attachModuleFragment(ModuleManager.java:1104)
> at org.netbeans.ModuleManager.maybeAddToEnableList(ModuleManager.java:1708)
> at org.netbeans.ModuleManager.simulateEnable(ModuleManager.java:1632)
> at org.netbeans.ModuleManager.simulateEnable(ModuleManager.java:1605)
> at org.netbeans.core.startup.ModuleList.installNew(ModuleList.java:289)
> at org.netbeans.core.startup.ModuleList.access$2400(ModuleList.java:93)
> at
> org.netbeans.core.startup.ModuleList$Listener.stepEnable(ModuleList.java:1384)
> at
> org.netbeans.core.startup.ModuleList$Listener.access$1400(ModuleList.java:982)
> at org.netbeans.core.startup.ModuleList$Listener$1.run(ModuleList.java:1206)
> at org.openide.filesystems.EventControl.runAtomicAction(EventControl.java:102)
> at org.openide.filesystems.FileSystem.runAtomicAction(FileSystem.java:494)
> at org.netbeans.core.startup.ModuleList$Listener.run(ModuleList.java:1182)
> at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1418)
> at
> org.netbeans.modules.openide.util.GlobalLookup.execute(GlobalLookup.java:45)
> at org.openide.util.lookup.Lookups.executeWith(Lookups.java:278)
> [catch] at
> org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2033)
> usage: ActivateFeatures
> {code}
> I have not experienced this exception when running NetBeans on OpenJDK 8
--
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-2801) IllegalSateException thrown when installing nbjavac plugin with OpenJDK11
[
https://issues.apache.org/jira/browse/NETBEANS-2801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16878675#comment-16878675
]
Alessandro Falappa commented on NETBEANS-2801:
--
Normal use seems to be unaffected, i.e. completion, error highlighting and
refactoring seems to work normally in the java editor.
I cannot however tell if nbjavac was really installed or not.
> IllegalSateException thrown when installing nbjavac plugin with OpenJDK11
> -
>
> Key: NETBEANS-2801
> URL: https://issues.apache.org/jira/browse/NETBEANS-2801
> Project: NetBeans
> Issue Type: Bug
> Components: java - Compiler
>Affects Versions: 11.1
> Environment: Product Version: Apache NetBeans IDE 11.1
> Java: 11.0.2; OpenJDK 64-Bit Server VM 11.0.2+9
> Runtime: OpenJDK Runtime Environment 11.0.2+9
> System: Windows 10 version 10.0 running on amd64; Cp1252; en_IE (nb)
> User directory: C:\Users\falappa\AppData\Roaming\NetBeans\11.1
> Cache directory: C:\Users\falappa\AppData\Local\NetBeans\Cache\11.1
>Reporter: Alessandro Falappa
>Priority: Major
>
> Steps:
> # Download NB 11.1-beta3 binary zip
> # Unpack
> # Edit etc/netbeans.conf and specify an OpenJDK11 in netbeans_jdkhome
> property
> # Run bin/netbeans64.exe
> # Click on My NetBenas on the Start Page
> # Click on Activate Features
> # Select JavaSE checkbox and click Activate
> # Close Plugins dialog
> # There should be a notification suggesting to install nbjavac
> # Open notification and follow instructions to install nbjavac plugin
> # After installation an exception is notified and the IDE log contains
> {code:java}
> // SEVERE [org.openide.util.RequestProcessor]: Error in RequestProcessor
> org.netbeans.core.startup.ModuleList$Listener
> java.lang.IllegalStateException: Host module
> StandardModule:org.netbeans.libs.javacapi jarFile:
> C:\Users\falappa\PortableApps\netbeans-11.1-beta3\java\modules\org-netbeans-libs-javacapi.jar
> was enabled before, will not accept fragment
> StandardModule:org.netbeans.modules.nbjavac.api jarFile:
> C:\Users\falappa\AppData\Roaming\NetBeans\11.1\modules\org-netbeans-modules-nbjavac-api.jar
> at org.netbeans.ModuleManager.attachModuleFragment(ModuleManager.java:1104)
> at org.netbeans.ModuleManager.maybeAddToEnableList(ModuleManager.java:1708)
> at org.netbeans.ModuleManager.simulateEnable(ModuleManager.java:1632)
> at org.netbeans.ModuleManager.simulateEnable(ModuleManager.java:1605)
> at org.netbeans.core.startup.ModuleList.installNew(ModuleList.java:289)
> at org.netbeans.core.startup.ModuleList.access$2400(ModuleList.java:93)
> at
> org.netbeans.core.startup.ModuleList$Listener.stepEnable(ModuleList.java:1384)
> at
> org.netbeans.core.startup.ModuleList$Listener.access$1400(ModuleList.java:982)
> at org.netbeans.core.startup.ModuleList$Listener$1.run(ModuleList.java:1206)
> at org.openide.filesystems.EventControl.runAtomicAction(EventControl.java:102)
> at org.openide.filesystems.FileSystem.runAtomicAction(FileSystem.java:494)
> at org.netbeans.core.startup.ModuleList$Listener.run(ModuleList.java:1182)
> at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1418)
> at
> org.netbeans.modules.openide.util.GlobalLookup.execute(GlobalLookup.java:45)
> at org.openide.util.lookup.Lookups.executeWith(Lookups.java:278)
> [catch] at
> org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2033)
> usage: ActivateFeatures
> {code}
> I have not experienced this exception when running NetBeans on OpenJDK 8
--
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-2801) IllegalSateException thrown when installing nbjavac plugin with OpenJDK11
[
https://issues.apache.org/jira/browse/NETBEANS-2801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alessandro Falappa updated NETBEANS-2801:
-
Environment:
Product Version: Apache NetBeans IDE 11.1
Java: 11.0.2; OpenJDK 64-Bit Server VM 11.0.2+9
Runtime: OpenJDK Runtime Environment 11.0.2+9
System: Windows 10 version 10.0 running on amd64; Cp1252; en_IE (nb)
User directory: C:\Users\falappa\AppData\Roaming\NetBeans\11.1
Cache directory: C:\Users\falappa\AppData\Local\NetBeans\Cache\11.1
> IllegalSateException thrown when installing nbjavac plugin with OpenJDK11
> -
>
> Key: NETBEANS-2801
> URL: https://issues.apache.org/jira/browse/NETBEANS-2801
> Project: NetBeans
> Issue Type: Bug
> Components: java - Compiler
>Affects Versions: 11.1
> Environment: Product Version: Apache NetBeans IDE 11.1
> Java: 11.0.2; OpenJDK 64-Bit Server VM 11.0.2+9
> Runtime: OpenJDK Runtime Environment 11.0.2+9
> System: Windows 10 version 10.0 running on amd64; Cp1252; en_IE (nb)
> User directory: C:\Users\falappa\AppData\Roaming\NetBeans\11.1
> Cache directory: C:\Users\falappa\AppData\Local\NetBeans\Cache\11.1
>Reporter: Alessandro Falappa
>Priority: Major
>
> Steps:
> # Download NB 11.1-beta3 binary zip
> # Unpack
> # Edit etc/netbeans.conf and specify an OpenJDK11 in netbeans_jdkhome
> property
> # Run bin/netbeans64.exe
> # Click on My NetBenas on the Start Page
> # Click on Activate Features
> # Select JavaSE checkbox and click Activate
> # Close Plugins dialog
> # There should be a notification suggesting to install nbjavac
> # Open notification and follow instructions to install nbjavac plugin
> # After installation an exception is notified and the IDE log contains
> {code:java}
> // SEVERE [org.openide.util.RequestProcessor]: Error in RequestProcessor
> org.netbeans.core.startup.ModuleList$Listener
> java.lang.IllegalStateException: Host module
> StandardModule:org.netbeans.libs.javacapi jarFile:
> C:\Users\falappa\PortableApps\netbeans-11.1-beta3\java\modules\org-netbeans-libs-javacapi.jar
> was enabled before, will not accept fragment
> StandardModule:org.netbeans.modules.nbjavac.api jarFile:
> C:\Users\falappa\AppData\Roaming\NetBeans\11.1\modules\org-netbeans-modules-nbjavac-api.jar
> at org.netbeans.ModuleManager.attachModuleFragment(ModuleManager.java:1104)
> at org.netbeans.ModuleManager.maybeAddToEnableList(ModuleManager.java:1708)
> at org.netbeans.ModuleManager.simulateEnable(ModuleManager.java:1632)
> at org.netbeans.ModuleManager.simulateEnable(ModuleManager.java:1605)
> at org.netbeans.core.startup.ModuleList.installNew(ModuleList.java:289)
> at org.netbeans.core.startup.ModuleList.access$2400(ModuleList.java:93)
> at
> org.netbeans.core.startup.ModuleList$Listener.stepEnable(ModuleList.java:1384)
> at
> org.netbeans.core.startup.ModuleList$Listener.access$1400(ModuleList.java:982)
> at org.netbeans.core.startup.ModuleList$Listener$1.run(ModuleList.java:1206)
> at org.openide.filesystems.EventControl.runAtomicAction(EventControl.java:102)
> at org.openide.filesystems.FileSystem.runAtomicAction(FileSystem.java:494)
> at org.netbeans.core.startup.ModuleList$Listener.run(ModuleList.java:1182)
> at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1418)
> at
> org.netbeans.modules.openide.util.GlobalLookup.execute(GlobalLookup.java:45)
> at org.openide.util.lookup.Lookups.executeWith(Lookups.java:278)
> [catch] at
> org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2033)
> usage: ActivateFeatures
> {code}
> I have not experienced this exception when running NetBeans on OpenJDK 8
--
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-2801) IllegalSateException thrown when installing nbjavac plugin with OpenJDK11
Alessandro Falappa created NETBEANS-2801:
Summary: IllegalSateException thrown when installing nbjavac
plugin with OpenJDK11
Key: NETBEANS-2801
URL: https://issues.apache.org/jira/browse/NETBEANS-2801
Project: NetBeans
Issue Type: Bug
Components: java - Compiler
Affects Versions: 11.1
Reporter: Alessandro Falappa
Steps:
# Download NB 11.1-beta3 binary zip
# Unpack
# Edit etc/netbeans.conf and specify an OpenJDK11 in netbeans_jdkhome property
# Run bin/netbeans64.exe
# Click on My NetBenas on the Start Page
# Click on Activate Features
# Select JavaSE checkbox and click Activate
# Close Plugins dialog
# There should be a notification suggesting to install nbjavac
# Open notification and follow instructions to install nbjavac plugin
# After installation an exception is notified and the IDE log contains
{code:java}
// SEVERE [org.openide.util.RequestProcessor]: Error in RequestProcessor
org.netbeans.core.startup.ModuleList$Listener
java.lang.IllegalStateException: Host module
StandardModule:org.netbeans.libs.javacapi jarFile:
C:\Users\falappa\PortableApps\netbeans-11.1-beta3\java\modules\org-netbeans-libs-javacapi.jar
was enabled before, will not accept fragment
StandardModule:org.netbeans.modules.nbjavac.api jarFile:
C:\Users\falappa\AppData\Roaming\NetBeans\11.1\modules\org-netbeans-modules-nbjavac-api.jar
at org.netbeans.ModuleManager.attachModuleFragment(ModuleManager.java:1104)
at org.netbeans.ModuleManager.maybeAddToEnableList(ModuleManager.java:1708)
at org.netbeans.ModuleManager.simulateEnable(ModuleManager.java:1632)
at org.netbeans.ModuleManager.simulateEnable(ModuleManager.java:1605)
at org.netbeans.core.startup.ModuleList.installNew(ModuleList.java:289)
at org.netbeans.core.startup.ModuleList.access$2400(ModuleList.java:93)
at
org.netbeans.core.startup.ModuleList$Listener.stepEnable(ModuleList.java:1384)
at
org.netbeans.core.startup.ModuleList$Listener.access$1400(ModuleList.java:982)
at org.netbeans.core.startup.ModuleList$Listener$1.run(ModuleList.java:1206)
at org.openide.filesystems.EventControl.runAtomicAction(EventControl.java:102)
at org.openide.filesystems.FileSystem.runAtomicAction(FileSystem.java:494)
at org.netbeans.core.startup.ModuleList$Listener.run(ModuleList.java:1182)
at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1418)
at org.netbeans.modules.openide.util.GlobalLookup.execute(GlobalLookup.java:45)
at org.openide.util.lookup.Lookups.executeWith(Lookups.java:278)
[catch] at
org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2033)
usage: ActivateFeatures
{code}
I have not experienced this exception when running NetBeans on OpenJDK 8
--
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-2790) java.nio.file.ClosedWatchServiceException
[ https://issues.apache.org/jira/browse/NETBEANS-2790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16877838#comment-16877838 ] Alessandro Falappa commented on NETBEANS-2790: -- I have got a similar exception but it is raised when closing NetBeans thus un-harmful. Sure it would be better to properly close the file watcher service. > java.nio.file.ClosedWatchServiceException > - > > Key: NETBEANS-2790 > URL: https://issues.apache.org/jira/browse/NETBEANS-2790 > Project: NetBeans > Issue Type: Bug >Affects Versions: 11.0 > Environment: openjdk version "1.8.0_212" > OpenJDK Runtime Environment (build 1.8.0_212-8u212-b03-0ubuntu1.19.04.2-b03) > OpenJDK 64-Bit Server VM (build 25.212-b03, mixed mode) > No LSB modules are available. > Distributor ID: Ubuntu > Description:Ubuntu 19.04 > Release:19.04 > Codename: disco >Reporter: Shevek >Priority: Major > > Running with nio masterfs per NETBEANS-2291: > WARNING [org.netbeans.modules.masterfs.watcher.Watcher]: Cannot remove > filesystem watch for /[filename-removed] > INFO [org.netbeans.modules.masterfs.watcher.Watcher]: Exception > java.nio.file.ClosedWatchServiceException > at sun.nio.fs.AbstractPoller.invoke(AbstractPoller.java:216) > at sun.nio.fs.AbstractPoller.cancel(AbstractPoller.java:133) > at > sun.nio.fs.LinuxWatchService$LinuxWatchKey.cancel(LinuxWatchService.java:138) > at > org.netbeans.modules.masterfs.watcher.nio2.NioNotifier.removeWatch(NioNotifier.java:62) > Caused: java.io.IOException > at > org.netbeans.modules.masterfs.watcher.nio2.NioNotifier.removeWatch(NioNotifier.java:64) > at > org.netbeans.modules.masterfs.watcher.nio2.NioNotifier.removeWatch(NioNotifier.java:40) > at > org.netbeans.modules.masterfs.providers.Notifier$1.removeWatch(Notifier.java:95) > at > org.netbeans.modules.masterfs.watcher.NotifierKeyRef.removeWatch(NotifierKeyRef.java:73) > [catch] at > org.netbeans.modules.masterfs.watcher.Watcher$Ext.unregister(Watcher.java:297) > at > org.netbeans.modules.masterfs.watcher.Watcher.unregister(Watcher.java:111) > at > org.netbeans.modules.masterfs.filebasedfs.fileobjects.BaseFileObj.removeFileChangeListener(BaseFileObj.java:539) > at > org.netbeans.modules.masterfs.filebasedfs.fileobjects.FileObjectKeeper.listenTo(FileObjectKeeper.java:191) > at > org.netbeans.modules.masterfs.filebasedfs.fileobjects.FileObjectKeeper.listenNoMore(FileObjectKeeper.java:272) > at > org.netbeans.modules.masterfs.filebasedfs.fileobjects.FileObjectKeeper.removeRecursiveListener(FileObjectKeeper.java:102) > at > org.netbeans.modules.masterfs.filebasedfs.fileobjects.FolderObj.removeRecursiveListener(FolderObj.java:662) > at org.openide.filesystems.DeepListener.run(DeepListener.java:70) > at > org.openide.filesystems.FileChangeImpl.removeRecursiveListener(FileChangeImpl.java:255) > at > org.openide.filesystems.FileUtil.removeRecursiveListener(FileUtil.java:380) > at > org.netbeans.modules.parsing.impl.indexing.RootsListener.lambda$safeRemoveRecursiveListener$5(RootsListener.java:260) > at > org.netbeans.modules.parsing.impl.indexing.RootsListener.performSave(RootsListener.java:276) > at > org.netbeans.modules.parsing.impl.indexing.RootsListener.lambda$performAsync$6(RootsListener.java:268) > at > org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1418) > at > org.netbeans.modules.openide.util.GlobalLookup.execute(GlobalLookup.java:45) > at org.openide.util.lookup.Lookups.executeWith(Lookups.java:278) > at > org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2033) -- 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-2791) Glassfish and Payara servers download leaves spurious directory on filesystem
[ https://issues.apache.org/jira/browse/NETBEANS-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Falappa updated NETBEANS-2791: - Description: Steps: # Open Servers dialog via menu Tools > Server # Click Add Server... # Choose "GlassFish Server" or "Payara Server" # Click "Next" button # Specify an install location different from proposed one # Choose a version # Click on accept license checkbox # Click Download Now button _Observed_: The chosen GlassFish or Payara server distribution is downloaded and installed in the chosen location but an additional sibling folder is created containing a temporary 0 bytes file. The sibling folder is named __*1* (note the final 1) and temporary file is named _foo.tmp_ . _Expected_: The chosen GlassFish or Payara server distribution is downloaded and installed in the chosen location and no additional folders/files are created or maybe created but removed at the end of installation process. was: Steps: # Open Servers dialog via menu Tools > Server # Click Add Server... # Choose "GlassFish Server" or "Payara Server" # Click "Next" button # Specify an install location different from proposed one # Choose a version # Click on accept license checkbox # Click Download Now button The choosen GlassFish or Payara server distribution is downloaded and installed in the choosen location but an additional sibling folder is created containing a temporary 0 bytes file. The sibling folder is named __*1* note the final 1 and contains an empty _foo.tmp_ file. > Glassfish and Payara servers download leaves spurious directory on filesystem > - > > Key: NETBEANS-2791 > URL: https://issues.apache.org/jira/browse/NETBEANS-2791 > Project: NetBeans > Issue Type: Bug > Components: serverplugins - GlassFish, serverplugins - Infrastructure >Affects Versions: 11.1 > Environment: Product Version: Apache NetBeans IDE 11.1 > Updates: Updates available > Java: 1.8.0_202; OpenJDK 64-Bit Server VM 25.202-b08 > Runtime: OpenJDK Runtime Environment 1.8.0_202-b08 > System: Windows 10 version 10.0 running on amd64; Cp1252; en_IE (nb) > User directory: C:\Users\falappa\AppData\Roaming\NetBeans\11.1 > Cache directory: C:\Users\falappa\AppData\Local\NetBeans\Cache\11.1 >Reporter: Alessandro Falappa >Priority: Minor > > Steps: > # Open Servers dialog via menu Tools > Server > # Click Add Server... > # Choose "GlassFish Server" or "Payara Server" > # Click "Next" button > # Specify an install location different from proposed one > # Choose a version > # Click on accept license checkbox > # Click Download Now button > _Observed_: The chosen GlassFish or Payara server distribution is downloaded > and installed in the chosen location but an additional sibling folder is > created containing a temporary 0 bytes file. The sibling folder is named > __*1* (note the final 1) and temporary file is named > _foo.tmp_ . > _Expected_: The chosen GlassFish or Payara server distribution is downloaded > and installed in the chosen location and no additional folders/files are > created or maybe created but removed at the end of installation process. -- 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-2792) Gradle EE Run output tab remains in running state (bold title) after deployment
[ https://issues.apache.org/jira/browse/NETBEANS-2792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Falappa updated NETBEANS-2792: - Environment: Product Version: Apache NetBeans IDE 11.1 Updates: Updates available Java: 1.8.0_202; OpenJDK 64-Bit Server VM 25.202-b08 Runtime: OpenJDK Runtime Environment 1.8.0_202-b08 System: Windows 10 version 10.0 running on amd64; Cp1252; en_IE (nb) User directory: C:\Users\falappa\AppData\Roaming\NetBeans\11.1 Cache directory: C:\Users\falappa\AppData\Local\NetBeans\Cache\11.1 > Gradle EE Run output tab remains in running state (bold title) after > deployment > --- > > Key: NETBEANS-2792 > URL: https://issues.apache.org/jira/browse/NETBEANS-2792 > Project: NetBeans > Issue Type: Bug > Components: projects - Gradle Java EE >Affects Versions: 11.1 > Environment: Product Version: Apache NetBeans IDE 11.1 > Updates: Updates available > Java: 1.8.0_202; OpenJDK 64-Bit Server VM 25.202-b08 > Runtime: OpenJDK Runtime Environment 1.8.0_202-b08 > System: Windows 10 version 10.0 running on amd64; Cp1252; en_IE (nb) > User directory: C:\Users\falappa\AppData\Roaming\NetBeans\11.1 > Cache directory: C:\Users\falappa\AppData\Local\NetBeans\Cache\11.1 >Reporter: Alessandro Falappa >Assignee: Laszlo Kishalmi >Priority: Minor > > Steps > # Create a Gradle Web application project > # Run project (F6) > _Expected_: after launching the application server of the project (if not > running already) and deploying the project WAR artifact the output tab should > stop (normal title) > _Observed_: the application server is launched (if not running already) and > the WAR artifact of the project is deployed but the output tab remains in > running state (bold title) -- 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-2792) Gradle EE Run output tab remains in running state (bold title) after deployment
Alessandro Falappa created NETBEANS-2792: Summary: Gradle EE Run output tab remains in running state (bold title) after deployment Key: NETBEANS-2792 URL: https://issues.apache.org/jira/browse/NETBEANS-2792 Project: NetBeans Issue Type: Bug Components: projects - Gradle Java EE Affects Versions: 11.1 Reporter: Alessandro Falappa Assignee: Laszlo Kishalmi Steps # Create a Gradle Web application project # Run project (F6) _Expected_: after launching the application server of the project (if not running already) and deploying the project WAR artifact the output tab should stop (normal title) _Observed_: the application server is launched (if not running already) and the WAR artifact of the project is deployed but the output tab remains in running state (bold title) -- 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-2791) Glassfish and Payara servers download leaves spurious directory on filesystem
[ https://issues.apache.org/jira/browse/NETBEANS-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Falappa updated NETBEANS-2791: - Environment: Product Version: Apache NetBeans IDE 11.1 Updates: Updates available Java: 1.8.0_202; OpenJDK 64-Bit Server VM 25.202-b08 Runtime: OpenJDK Runtime Environment 1.8.0_202-b08 System: Windows 10 version 10.0 running on amd64; Cp1252; en_IE (nb) User directory: C:\Users\falappa\AppData\Roaming\NetBeans\11.1 Cache directory: C:\Users\falappa\AppData\Local\NetBeans\Cache\11.1 Description: Steps: # Open Servers dialog via menu Tools > Server # Click Add Server... # Choose "GlassFish Server" or "Payara Server" # Click "Next" button # Specify an install location different from proposed one # Choose a version # Click on accept license checkbox # Click Download Now button The choosen GlassFish or Payara server distribution is downloaded and installed in the choosen location but an additional sibling folder is created containing a temporary 0 bytes file. The sibling folder is named __*1* note the final 1 and contains an empty _foo.tmp_ file. was: Steps: # Open Servers dialog via menu Tools > Server # Click Add Server... # Choose "GlassFish Server" or "Payara Server" # Click "Next" button # Specify an install location different from proposed one # Choose a version # Click on accept license checkbox # Click Download Now button The choosen GlassFish or Payara server distribution is downloaded and installed in the choosen location but an additional sibling folder is created containing a temporary 0 bytes file. The sibling folder is named __*1* note the final 1 and contains an empty _foo.tmp_ file. *Product Version:* Apache NetBeans IDE 11.1 *Updates:* Updates available *Java:* 1.8.0_202; OpenJDK 64-Bit Server VM 25.202-b08 *Runtime:* OpenJDK Runtime Environment 1.8.0_202-b08 *System:* Windows 10 version 10.0 running on amd64; Cp1252; en_IE (nb) *User directory:* C:\Users\falappa\AppData\Roaming\NetBeans\11.1 *Cache directory:* C:\Users\falappa\AppData\Local\NetBeans\Cache\11.1 > Glassfish and Payara servers download leaves spurious directory on filesystem > - > > Key: NETBEANS-2791 > URL: https://issues.apache.org/jira/browse/NETBEANS-2791 > Project: NetBeans > Issue Type: Bug > Components: serverplugins - GlassFish, serverplugins - Infrastructure >Affects Versions: 11.1 > Environment: Product Version: Apache NetBeans IDE 11.1 > Updates: Updates available > Java: 1.8.0_202; OpenJDK 64-Bit Server VM 25.202-b08 > Runtime: OpenJDK Runtime Environment 1.8.0_202-b08 > System: Windows 10 version 10.0 running on amd64; Cp1252; en_IE (nb) > User directory: C:\Users\falappa\AppData\Roaming\NetBeans\11.1 > Cache directory: C:\Users\falappa\AppData\Local\NetBeans\Cache\11.1 >Reporter: Alessandro Falappa >Priority: Minor > > Steps: > # Open Servers dialog via menu Tools > Server > # Click Add Server... > # Choose "GlassFish Server" or "Payara Server" > # Click "Next" button > # Specify an install location different from proposed one > # Choose a version > # Click on accept license checkbox > # Click Download Now button > The choosen GlassFish or Payara server distribution is downloaded and > installed in the choosen location but an additional sibling folder is created > containing a temporary 0 bytes file. > The sibling folder is named __*1* note the final 1 and > contains an empty _foo.tmp_ file. -- 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-2791) Glassfish and Payara servers download leaves spurious directory on filesystem
[ https://issues.apache.org/jira/browse/NETBEANS-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Falappa updated NETBEANS-2791: - Description: Steps: # Open Servers dialog via menu Tools > Server # Click Add Server... # Choose "GlassFish Server" or "Payara Server" # Click "Next" button # Specify an install location different from proposed one # Choose a version # Click on accept license checkbox # Click Download Now button The choosen GlassFish or Payara server distribution is downloaded and installed in the choosen location but an additional sibling folder is created containing a temporary 0 bytes file. The sibling folder is named __*1* note the final 1 and contains an empty _foo.tmp_ file. *Product Version:* Apache NetBeans IDE 11.1 *Updates:* Updates available *Java:* 1.8.0_202; OpenJDK 64-Bit Server VM 25.202-b08 *Runtime:* OpenJDK Runtime Environment 1.8.0_202-b08 *System:* Windows 10 version 10.0 running on amd64; Cp1252; en_IE (nb) *User directory:* C:\Users\falappa\AppData\Roaming\NetBeans\11.1 *Cache directory:* C:\Users\falappa\AppData\Local\NetBeans\Cache\11.1 was: Steps: # Open Servers dialog via menu Tools > Server # Click Add Server... # Choose "GlassFish Server" or "Payara Server" # Click "Next" button # Specify an install location different from proposed one # Choose a version # Click on accept license checkbox # Click Download Now button The choosen GlassFish or Payara server distribution is downloaded and installed in the choosen location but an additional sibling folder is created containing a temporary 0 bytes file. The sibling folder is named __*1* note the final 1 and contains an empty _foo.tmp_ file. > Glassfish and Payara servers download leaves spurious directory on filesystem > - > > Key: NETBEANS-2791 > URL: https://issues.apache.org/jira/browse/NETBEANS-2791 > Project: NetBeans > Issue Type: Bug > Components: serverplugins - GlassFish, serverplugins - Infrastructure >Affects Versions: 11.1 >Reporter: Alessandro Falappa >Priority: Minor > > Steps: > # Open Servers dialog via menu Tools > Server > # Click Add Server... > # Choose "GlassFish Server" or "Payara Server" > # Click "Next" button > # Specify an install location different from proposed one > # Choose a version > # Click on accept license checkbox > # Click Download Now button > The choosen GlassFish or Payara server distribution is downloaded and > installed in the choosen location but an additional sibling folder is created > containing a temporary 0 bytes file. > The sibling folder is named __*1* note the final 1 and > contains an empty _foo.tmp_ file. > > *Product Version:* Apache NetBeans IDE 11.1 > *Updates:* Updates available > *Java:* 1.8.0_202; OpenJDK 64-Bit Server VM 25.202-b08 > *Runtime:* OpenJDK Runtime Environment 1.8.0_202-b08 > *System:* Windows 10 version 10.0 running on amd64; Cp1252; en_IE (nb) > *User directory:* C:\Users\falappa\AppData\Roaming\NetBeans\11.1 > *Cache directory:* C:\Users\falappa\AppData\Local\NetBeans\Cache\11.1 > -- 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-2791) Glassfish and Payara servers download leaves spurious directory on filesystem
Alessandro Falappa created NETBEANS-2791: Summary: Glassfish and Payara servers download leaves spurious directory on filesystem Key: NETBEANS-2791 URL: https://issues.apache.org/jira/browse/NETBEANS-2791 Project: NetBeans Issue Type: Bug Components: serverplugins - GlassFish, serverplugins - Infrastructure Affects Versions: 11.1 Reporter: Alessandro Falappa Steps: # Open Servers dialog via menu Tools > Server # Click Add Server... # Choose "GlassFish Server" or "Payara Server" # Click "Next" button # Specify an install location different from proposed one # Choose a version # Click on accept license checkbox # Click Download Now button The choosen GlassFish or Payara server distribution is downloaded and installed in the choosen location but an additional sibling folder is created containing a temporary 0 bytes file. The sibling folder is named __*1* note the final 1 and contains an empty _foo.tmp_ file. -- 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-2783) Maven dependencies node does not show dependencies added editing POM
[
https://issues.apache.org/jira/browse/NETBEANS-2783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alessandro Falappa updated NETBEANS-2783:
-
Environment:
Product Version: Apache NetBeans IDE 11.1
Updates: Updates available
Java: 1.8.0_202; OpenJDK 64-Bit Server VM 25.202-b08
Runtime: OpenJDK Runtime Environment 1.8.0_202-b08
System: Windows 10 version 10.0 running on amd64; Cp1252; en_IE (nb)
User directory: C:\Users\falappa\AppData\Roaming\NetBeans\11.1
Cache directory: C:\Users\falappa\AppData\Local\NetBeans\Cache\11.1
Labels: regression (was: )
> Maven dependencies node does not show dependencies added editing POM
>
>
> Key: NETBEANS-2783
> URL: https://issues.apache.org/jira/browse/NETBEANS-2783
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Generic Projects UI, projects - Maven
>Affects Versions: 11.0, 11.1
> Environment: Product Version: Apache NetBeans IDE 11.1
> Updates: Updates available
> Java: 1.8.0_202; OpenJDK 64-Bit Server VM 25.202-b08
> Runtime: OpenJDK Runtime Environment 1.8.0_202-b08
> System: Windows 10 version 10.0 running on amd64; Cp1252; en_IE (nb)
> User directory: C:\Users\falappa\AppData\Roaming\NetBeans\11.1
> Cache directory: C:\Users\falappa\AppData\Local\NetBeans\Cache\11.1
>Reporter: Alessandro Falappa
>Priority: Major
> Labels: regression
>
> Steps:
> # Open or create a new maven project
> # Expand the Dependencies node in Projects view
> # Open pom.xml and add a dependency that has never been used before, i.e. is
> not in the local maven repository (.m2/repository)
> # Save pom.xml
> _Expected_ (works in NB 8.2): a jar entry with the name of the dependency
> artifact appears under the Dependencies node of the project with a yellow
> triangle badge indicating new dependency detected but missing local copy.
> _Actual_ (broken in NB11.0 and NB11.1-beta2): no jar entry appears, the log
> contains the following warning (here for commons-math3 dependency):
> {code:java}
> // WARNING [org.netbeans.modules.maven.nodes.DependenciesNode]: Could not
> determine module name for artifact
> jar:file:/C:/Users/falappa/.m2/repository/org/apache/commons/commons-math3/3.6.1/commons-math3-3.6.1.jar!/
> {code}
> In NB11.0 and NB11.1-beta2 after rebuilding the project the dependencies node
> gets updated and a regular jar entry appears. In NB8.2 after rebuilding the
> project the yellow triangle badge disappears.
> I had a look at the code and it looks like something got broken when adding
> modular Java support, i.e. in NB 9.0, as the code is trying to determine Java
> module names for each dependency.
> This is a regression, NetBeans 8.2 works, NetBeans 11.0 and NetBeans
> 11.1-beta2 do not, NetBeans 9.0 and 10.0 not tested.
>
--
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-2783) Maven dependencies node does not show dependencies added editing POM
Alessandro Falappa created NETBEANS-2783:
Summary: Maven dependencies node does not show dependencies added
editing POM
Key: NETBEANS-2783
URL: https://issues.apache.org/jira/browse/NETBEANS-2783
Project: NetBeans
Issue Type: Bug
Components: projects - Generic Projects UI, projects - Maven
Affects Versions: 11.0, 11.1
Reporter: Alessandro Falappa
Steps:
# Open or create a new maven project
# Expand the Dependencies node in Projects view
# Open pom.xml and add a dependency that has never been used before, i.e. is
not in the local maven repository (.m2/repository)
# Save pom.xml
_Expected_ (works in NB 8.2): a jar entry with the name of the dependency
artifact appears under the Dependencies node of the project with a yellow
triangle badge indicating new dependency detected but missing local copy.
_Actual_ (broken in NB11.0 and NB11.1-beta2): no jar entry appears, the log
contains the following warning (here for commons-math3 dependency):
{code:java}
// WARNING [org.netbeans.modules.maven.nodes.DependenciesNode]: Could not
determine module name for artifact
jar:file:/C:/Users/falappa/.m2/repository/org/apache/commons/commons-math3/3.6.1/commons-math3-3.6.1.jar!/
{code}
In NB11.0 and NB11.1-beta2 after rebuilding the project the dependencies node
gets updated and a regular jar entry appears. In NB8.2 after rebuilding the
project the yellow triangle badge disappears.
I had a look at the code and it looks like something got broken when adding
modular Java support, i.e. in NB 9.0, as the code is trying to determine Java
module names for each dependency.
This is a regression, NetBeans 8.2 works, NetBeans 11.0 and NetBeans 11.1-beta2
do not, NetBeans 9.0 and 10.0 not tested.
--
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-2374) Editor does not show UTF-8 codepoint as Unicode character
[ https://issues.apache.org/jira/browse/NETBEANS-2374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16814256#comment-16814256 ] Alessandro Falappa edited comment on NETBEANS-2374 at 4/10/19 9:47 AM: --- I stumbled upon this behaviour just now. >From my investigation the problem is limited to Gradle projects, where there >is no way to set the file encoding at project level like in Maven projects. >All the files in a Gradle project inherit the platform encoding (i.e. under >Windows the win-1252 encoding, under Linux the issue is not as obvious because >the platform encoding is frequently UTF-8). As a workaround one could install the [Encoding Support plugin|http://plugins.netbeans.org/plugin/60487/encoding-support] and change the encoding for the files you are interested in but that is not very practical. A more sensible solution should be to have a file encoding setting at project level and the various editor should use that when opening all kind of files in the project. was (Author: alexfalappa): I stumbled upon this behaviour just now. >From my investigation the problem is limited to Gradle projects, where there >is no way to set the file encoding at project level like in Maven projects. >All the files in a Gradle project inherit the platform encoding (i.e. under >Windows the win-1252 encoding). As a workaround one could install the [Encoding Support plugin|http://plugins.netbeans.org/plugin/60487/encoding-support] and change the encoding for the files you are interested in but that is not very practical. A more sensible solution should be to have a file encoding setting at project level and the various editor should use that when opening all kind of files in the project. > Editor does not show UTF-8 codepoint as Unicode character > - > > Key: NETBEANS-2374 > URL: https://issues.apache.org/jira/browse/NETBEANS-2374 > Project: NetBeans > Issue Type: Bug > Components: editor - Other, projects - Gradle >Affects Versions: 11.0 > Environment: Netbeans 11 > Gradle 5 > Java 11 >Reporter: Netbeans User 2019 >Priority: Critical > > There is additional issue (or not reported new feature on Netbeans 11) as > seems that Netbeans "Editor" stop understand UTF-8 so presents all characters > instead of showing just exact Unicode character of that codepoint. -- 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-2387) Gradle tasks (Navigator) do not scroll down and show recents at the top
[ https://issues.apache.org/jira/browse/NETBEANS-2387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Falappa reassigned NETBEANS-2387: Assignee: Laszlo Kishalmi > Gradle tasks (Navigator) do not scroll down and show recents at the top > --- > > Key: NETBEANS-2387 > URL: https://issues.apache.org/jira/browse/NETBEANS-2387 > Project: NetBeans > Issue Type: Improvement > Components: projects - Gradle >Affects Versions: 11.0 > Environment: Netbeans 11 > Gradle 5 > Java 11 >Reporter: Netbeans User 2019 >Assignee: Laszlo Kishalmi >Priority: Major > > Navigator is always scroll down so it is needed at least in my case scroll up > mostly to the right task to run. > Could you add a category recent tasks and scroll to that category or just > give a option to show that always collapsed? -- 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-2387) Gradle tasks (Navigator) do not scroll down and show recents at the top
[ https://issues.apache.org/jira/browse/NETBEANS-2387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16814264#comment-16814264 ] Alessandro Falappa commented on NETBEANS-2387: -- Noticed that myself too. I vote this, the behaviour is a bit annoying. > Gradle tasks (Navigator) do not scroll down and show recents at the top > --- > > Key: NETBEANS-2387 > URL: https://issues.apache.org/jira/browse/NETBEANS-2387 > Project: NetBeans > Issue Type: Improvement > Components: projects - Gradle >Affects Versions: 11.0 > Environment: Netbeans 11 > Gradle 5 > Java 11 >Reporter: Netbeans User 2019 >Priority: Major > > Navigator is always scroll down so it is needed at least in my case scroll up > mostly to the right task to run. > Could you add a category recent tasks and scroll to that category or just > give a option to show that always collapsed? -- 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-2374) Editor does not show UTF-8 codepoint as Unicode character
[
https://issues.apache.org/jira/browse/NETBEANS-2374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16814261#comment-16814261
]
Alessandro Falappa edited comment on NETBEANS-2374 at 4/10/19 9:39 AM:
---
To reproduce the issue generate a gradle project with the [Spring
Initializr|http://start.spring.io/] scaffolding web service and open the
{{HELP.md}} file, the last line shows some garbled chars after "_Gradle Build
Scans_" text instead of a hyphen.
The {{HELP.md}} file should be opened with *UTF-8* encoding while it has
*Windows-1252* encoding.
was (Author: alexfalappa):
To reproduce the issue generate a gradle project with the [Spring
Initializr|http://start.spring.io/] scaffolding web service and open the
{{HELP.md}} file, the last line shows some garbled chars after "Gradle Build
Scans" text instead of a hyphen.
> Editor does not show UTF-8 codepoint as Unicode character
> -
>
> Key: NETBEANS-2374
> URL: https://issues.apache.org/jira/browse/NETBEANS-2374
> Project: NetBeans
> Issue Type: Bug
> Components: editor - Other, java - Editor, projects - Gradle
>Affects Versions: 11.0
> Environment: Netbeans 11
> Gradle 5
> Java 11
>Reporter: Netbeans User 2019
>Priority: Critical
>
> There is additional issue (or not reported new feature on Netbeans 11) as
> seems that Netbeans "Editor" stop understand UTF-8 so presents all characters
> instead of showing just exact Unicode character of that codepoint.
--
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-2374) Editor does not show UTF-8 codepoint as Unicode character
[
https://issues.apache.org/jira/browse/NETBEANS-2374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16814261#comment-16814261
]
Alessandro Falappa commented on NETBEANS-2374:
--
To reproduce the issue generate a gradle project with the [Spring
Initializr|http://start.spring.io/] scaffolding web service and open the
{{HELP.md}} file, the last line shows some garbled chars after "Gradle Build
Scans" text instead of a hyphen.
> Editor does not show UTF-8 codepoint as Unicode character
> -
>
> Key: NETBEANS-2374
> URL: https://issues.apache.org/jira/browse/NETBEANS-2374
> Project: NetBeans
> Issue Type: Bug
> Components: editor - Other, java - Editor, projects - Gradle
>Affects Versions: 11.0
> Environment: Netbeans 11
> Gradle 5
> Java 11
>Reporter: Netbeans User 2019
>Priority: Critical
>
> There is additional issue (or not reported new feature on Netbeans 11) as
> seems that Netbeans "Editor" stop understand UTF-8 so presents all characters
> instead of showing just exact Unicode character of that codepoint.
--
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-2374) Editor does not show UTF-8 codepoint as Unicode character
[ https://issues.apache.org/jira/browse/NETBEANS-2374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16814256#comment-16814256 ] Alessandro Falappa commented on NETBEANS-2374: -- I stumbled upon this behaviour just now. >From my investigation the problem is limited to Gradle projects, where there >is no way to set the file encoding at project level like in Maven projects. >All the files in a Gradle project inherit the platform encoding (i.e. under >Windows the win-1252 encoding). As a workaround one could install the [Encoding Support plugin|http://plugins.netbeans.org/plugin/60487/encoding-support] and change the encoding for the files you are interested in but that is not very practical. A more sensible solution should be to have a file encoding setting at project level and the various editor should use that when opening all kind of files in the project. > Editor does not show UTF-8 codepoint as Unicode character > - > > Key: NETBEANS-2374 > URL: https://issues.apache.org/jira/browse/NETBEANS-2374 > Project: NetBeans > Issue Type: Bug > Components: editor - Other, java - Editor, projects - Gradle >Affects Versions: 11.0 > Environment: Netbeans 11 > Gradle 5 > Java 11 >Reporter: Netbeans User 2019 >Priority: Critical > > There is additional issue (or not reported new feature on Netbeans 11) as > seems that Netbeans "Editor" stop understand UTF-8 so presents all characters > instead of showing just exact Unicode character of that codepoint. -- 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-2374) Editor does not show UTF-8 codepoint as Unicode character
[ https://issues.apache.org/jira/browse/NETBEANS-2374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Falappa updated NETBEANS-2374: - Description: There is additional issue (or not reported new feature on Netbeans 11) as seems that Netbeans "Editor" stop understand UTF-8 so presents all characters instead of showing just exact Unicode character of that codepoint. (was: There is additional issue (or not reported new feature on Netbeans 11) as seems that Netbeans "Editor" stop understand UTF-8 so presents all characters instead of showing just exact Unicode character of that codepoint.) > Editor does not show UTF-8 codepoint as Unicode character > - > > Key: NETBEANS-2374 > URL: https://issues.apache.org/jira/browse/NETBEANS-2374 > Project: NetBeans > Issue Type: Bug > Components: editor - Other, java - Editor, projects - Gradle >Affects Versions: 11.0 > Environment: Netbeans 11 > Gradle 5 > Java 11 >Reporter: Netbeans User 2019 >Priority: Critical > > There is additional issue (or not reported new feature on Netbeans 11) as > seems that Netbeans "Editor" stop understand UTF-8 so presents all characters > instead of showing just exact Unicode character of that codepoint. -- 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-2374) Editor does not show UTF-8 codepoint as Unicode character
[ https://issues.apache.org/jira/browse/NETBEANS-2374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Falappa updated NETBEANS-2374: - Component/s: projects - Gradle > Editor does not show UTF-8 codepoint as Unicode character > - > > Key: NETBEANS-2374 > URL: https://issues.apache.org/jira/browse/NETBEANS-2374 > Project: NetBeans > Issue Type: Bug > Components: editor - Other, java - Editor, projects - Gradle >Affects Versions: 11.0 > Environment: Netbeans 11 > Gradle 5 > Java 11 >Reporter: Netbeans User 2019 >Priority: Critical > > There is additional issue (or not reported new feature on Netbeans 11) as > seems that Netbeans "Editor" stop understand UTF-8 > so presents all characters instead of showing just exact Unicode character of > that > codepoint. -- 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-2288) Project license header not used when creating new files in Gradle projects
Alessandro Falappa created NETBEANS-2288: Summary: Project license header not used when creating new files in Gradle projects Key: NETBEANS-2288 URL: https://issues.apache.org/jira/browse/NETBEANS-2288 Project: NetBeans Issue Type: Bug Components: projects - Gradle Affects Versions: 11.0 Reporter: Alessandro Falappa Assignee: Laszlo Kishalmi # Create a new gradle project for a Java application # Open the Project properties dialog (right click on project node) # In the _License Headers_ secion choose *Global License* and select for example _Apache 2.0_ license # Create a new Java class Problem: the newly created class has the *Default License* header text not the *Apache 2.0* license header -- 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-2036) Output tab remain active after gradle build finishes
[ https://issues.apache.org/jira/browse/NETBEANS-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16780283#comment-16780283 ] Alessandro Falappa commented on NETBEANS-2036: -- Glad to have aided in improving the quality of Gradle support in NetBeans and thank you for your swift reaction. I am going to test VC2 soon. > Output tab remain active after gradle build finishes > > > Key: NETBEANS-2036 > URL: https://issues.apache.org/jira/browse/NETBEANS-2036 > Project: NetBeans > Issue Type: Bug > Components: projects - Gradle >Affects Versions: 11.0 >Reporter: Alessandro Falappa >Assignee: Laszlo Kishalmi >Priority: Minor > Labels: 11.0-vc1, pull-request-available > Fix For: 11.0 > > Time Spent: 20m > Remaining Estimate: 0h > > After a gradle build finishes the tab in the output window remain in 'active' > or 'running' state. > With Nimbus LAF the title of the tab is rendered with a bold font. The issue > is more evident wen having several tabs (try building several projects). > Maven and Ant builds deactivate the tab when finished. -- 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-2129) New Gradle Java Application doesn't check if Application exists in Path
[ https://issues.apache.org/jira/browse/NETBEANS-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Falappa updated NETBEANS-2129: - Component/s: projects - Gradle > New Gradle Java Application doesn't check if Application exists in Path > --- > > Key: NETBEANS-2129 > URL: https://issues.apache.org/jira/browse/NETBEANS-2129 > Project: NetBeans > Issue Type: Bug > Components: projects - Gradle >Affects Versions: 11.0 >Reporter: michael anderl >Priority: Major > > When I create a new gradle java application, NB doesn't check if there is an > existing java gradle application in the project folder. Instead it just > creates a new one inside the existing one. > No error message like in NB9 or before > -- 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-2038) Anomalous termination of gradle task
[
https://issues.apache.org/jira/browse/NETBEANS-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16770859#comment-16770859
]
Alessandro Falappa commented on NETBEANS-2038:
--
Thanks Laszlo!
> Anomalous termination of gradle task
>
>
> Key: NETBEANS-2038
> URL: https://issues.apache.org/jira/browse/NETBEANS-2038
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Gradle
>Affects Versions: 11.0
>Reporter: Alessandro Falappa
>Assignee: Laszlo Kishalmi
>Priority: Minor
> Labels: pull-request-available
> Fix For: 11.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Generate a Gradle Spring Boot project on
> [http://start.spring.io|http://start.spring.io/] adding the *Web* dependency.
> Unzip the download archive and open it in NetBeans.
> In the Navigator right click on the _bootRun_ task and choose _Run Task..._
> from the context menu. The project compiles and starts directly from the
> build folder (the bootRun is a task provided by the spring boot gradle
> plugin) and should run an embedded Tomcat server listening on port 8080.
> Stop the task clicking the red stop button in the output window.
> The task stops but the launched gradle process reports an abnormal
> termination in the output window:
> {code:java}
> Could not read standard output of command
> '/usr/lib/jvm/java-8-oracle/bin/java'.
> java.io.IOException: Stream closed
> at java.io.BufferedInputStream.getBufIfOpen(BufferedInputStream.java:170)
> at java.io.BufferedInputStream.read1(BufferedInputStream.java:291)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:345)
> at java.io.FilterInputStream.read(FilterInputStream.java:107)
> at
> org.gradle.process.internal.streams.ExecOutputHandleRunner.forwardContent(ExecOutputHandleRunner.java:61)
> at
> org.gradle.process.internal.streams.ExecOutputHandleRunner.run(ExecOutputHandleRunner.java:51)
> at
> org.gradle.internal.operations.CurrentBuildOperationPreservingRunnable.run(CurrentBuildOperationPreservingRunnable.java:42)
> at
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
> at
> org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at
> org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)
> at java.lang.Thread.run(Thread.java:748)
> > Task :bootRun FAILED
> FAILURE: Build failed with an exception.
> * What went wrong:
> Execution failed for task ':bootRun'.
> > Process 'command '/usr/lib/jvm/java-8-oracle/bin/java'' finished with
> > non-zero exit value 143
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or
> --debug option to get more log output. Run with --scan to get full insights.
> * Get more help at https://help.gradle.org
> Deprecated Gradle features were used in this build, making it incompatible
> with Gradle 5.0.
> Use '--warning-mode all' to show the individual deprecation warnings.
> See
> https://docs.gradle.org/4.10.2/userguide/command_line_interface.html#sec:command_line_warnings
> BUILD FAILED in 50s
> 3 actionable tasks: 1 executed, 2 up-to-date
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Resolved] (NETBEANS-2105) Tunnel Broker IPV6 then Ipv7
[ https://issues.apache.org/jira/browse/NETBEANS-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Falappa resolved NETBEANS-2105. -- Resolution: Invalid > Tunnel Broker IPV6 then Ipv7 > > > Key: NETBEANS-2105 > URL: https://issues.apache.org/jira/browse/NETBEANS-2105 > Project: NetBeans > Issue Type: Wish > Environment: Red hat cygwin,msys2, Ubuntu, openSUSE,Mandriva,Fedora >Reporter: Victor Corral >Priority: Major > > I I'm trying 2 release the IPv6 to take out the ipv4 using my cellspot router > and tunnel broker with Hurricane Electric I'm currently also signed up with > icann trying to release my ipv7 using Dyne bolic and pure Dyne to respond to > the rfc 0006. I started with trying to make Apache work with VMware along > with hyper-v and I got to the point where I needed to download Windows 7 so > that I can make the disc that I created to make this possible instead of > downloading Windows 7 I ended up leaving that for a second go ahead of myself > and I now have an account with Hurricane Electric in which I am taking > classes so that I can change the ipv4 to a full IPv6 and I am trying to gain > 99.99 percent interconnect partner with Google I am currently trying to > finish the Android open source project by linking the Android open source to > that distribution of dynebolic and to complete my Collective whole let me > explain I am completing also or trying to complete the Hack Book at > HOA-project.net as my collective whole and everything in HOA being my > derivative works. To complete this I first am building my higher command line > the detail in. Then creating a nest using dynebolic 2. There are 3 versions > that I know of of dynebolic and also 3 versions of puredyne. I am using God > wins credential store to issue authentication to all devices and with > kubernetes I will deploy my pods of using Google Dockers to deploy funky m > iOS 1 click install on an iPhone using libimobile device. All of this along > with my media lab that I create with the Xboxes to create netsukuku a p2p > 100% decentralized and distributed network. The hardest part of all of this > would be staying in compliance with all the licenses . you see I am building > crosstool-ng but the issue with crosstool-Mr is to use it everything must be > of the Linux kernel version 2 in order to use their patches. Also using > AS as my cross Asemblers and cross links -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Closed] (NETBEANS-2025) Error w/ Symbolic Link
[ https://issues.apache.org/jira/browse/NETBEANS-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Falappa closed NETBEANS-2025. Resolution: Not A Problem > Error w/ Symbolic Link > -- > > Key: NETBEANS-2025 > URL: https://issues.apache.org/jira/browse/NETBEANS-2025 > Project: NetBeans > Issue Type: Bug >Affects Versions: 10.0 >Reporter: Michael D Billman >Priority: Minor > Attachments: image-2019-01-29-12-29-12-638.png > > > I have installed NB 10 (official release) and am trying to run on Java > 11.0.2. Some of my un-opened projects use symbolic links so that i can view > configuration files on a network/local drive (config for our internal > applications). This has never been a problem previously. My current setup > has no projects opened, but as soon as i try to open a project i see the > following: > !image-2019-01-29-12-29-12-638.png! > I have since removed the symbolic link.. NB 10 VC3 is running fine without > this error on JDK 8. Please let me know if I can provide anything else > helpful or possibly clean a user/cache directory or something like that. -- 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-2090) Image inside tooltip not working any more
[
https://issues.apache.org/jira/browse/NETBEANS-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alessandro Falappa updated NETBEANS-2090:
-
Affects Version/s: 11.0
> Image inside tooltip not working any more
> -
>
> Key: NETBEANS-2090
> URL: https://issues.apache.org/jira/browse/NETBEANS-2090
> Project: NetBeans
> Issue Type: Bug
>Affects Versions: 11.0
> Environment: Product Version: Apache NetBeans IDE Dev (Build
> 20190207-1340caf09590)
> Updates: Updates available
> Java: 13-ea; OpenJDK 64-Bit Server VM 13-ea+6
> Runtime: OpenJDK Runtime Environment 13-ea+6
> System: Mac OS X version 10.13.6 running on x86_64; UTF-8; en_DE (nb)
> User directory: /Users/rami/Library/Application Support/NetBeans/dev
> Cache directory: /Users/rami/Library/Caches/NetBeans/dev
>Reporter: Rami Swailem
>Priority: Major
> Attachments: Screen Shot 2019-02-07 at 11.50.26.png
>
>
> Reproduction steps:
> Open any Java File and make any syntax error
> Expected result:
> NetBeans show an _error badges_ in the _Projects_ window with Tooltip
> contains error badge
> Actual result:
> NetBeans show an _error badges_ in the _Projects_ window with Tooltip
> *without error badge*
>
> Same error in RCP APP
> jLabel.setToolTipText("Hello img.getAbsolutePath() + "'>");
>
> tested with JDK 8 and JDK 13
--
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-2090) Image inside tooltip not working any more
[
https://issues.apache.org/jira/browse/NETBEANS-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alessandro Falappa updated NETBEANS-2090:
-
Component/s: projects - Generic Infrastructure
> Image inside tooltip not working any more
> -
>
> Key: NETBEANS-2090
> URL: https://issues.apache.org/jira/browse/NETBEANS-2090
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Generic Infrastructure
>Affects Versions: 11.0
> Environment: Product Version: Apache NetBeans IDE Dev (Build
> 20190207-1340caf09590)
> Updates: Updates available
> Java: 13-ea; OpenJDK 64-Bit Server VM 13-ea+6
> Runtime: OpenJDK Runtime Environment 13-ea+6
> System: Mac OS X version 10.13.6 running on x86_64; UTF-8; en_DE (nb)
> User directory: /Users/rami/Library/Application Support/NetBeans/dev
> Cache directory: /Users/rami/Library/Caches/NetBeans/dev
>Reporter: Rami Swailem
>Priority: Major
> Attachments: Screen Shot 2019-02-07 at 11.50.26.png
>
>
> Reproduction steps:
> Open any Java File and make any syntax error
> Expected result:
> NetBeans show an _error badges_ in the _Projects_ window with Tooltip
> contains error badge
> Actual result:
> NetBeans show an _error badges_ in the _Projects_ window with Tooltip
> *without error badge*
>
> Same error in RCP APP
> jLabel.setToolTipText("Hello img.getAbsolutePath() + "'>");
>
> tested with JDK 8 and JDK 13
--
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-2035) Open Output window when starting a Gradle build
[ https://issues.apache.org/jira/browse/NETBEANS-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16758048#comment-16758048 ] Alessandro Falappa commented on NETBEANS-2035: -- Doh, didn't check the options carefully. Have you considered to turn the default the other way around? That is to always show output by default, I think users may found it more natural. Unfortunately out of the box ant projects do not always show output while maven projects do, so no general consistent behaviour among the build tools can be adopted. If you think the default is OK please close the issue, otherwise reword it. > Open Output window when starting a Gradle build > --- > > Key: NETBEANS-2035 > URL: https://issues.apache.org/jira/browse/NETBEANS-2035 > Project: NetBeans > Issue Type: Improvement > Components: projects - Gradle >Affects Versions: 11.0 > Environment: Product Version: Apache NetBeans IDE Dev (Build > incubator-netbeans-linux-989-on-20190130) > Java: 1.8.0_201; Java HotSpot(TM) 64-Bit Server VM 25.201-b09 > Runtime: Java(TM) SE Runtime Environment 1.8.0_201-b09 > System: Linux version 4.15.0-43-generic running on amd64; UTF-8; it_IT (nb) > User directory: /home/sasha/.netbeans/dev > Cache directory: /home/sasha/.cache/netbeans/dev >Reporter: Alessandro Falappa >Assignee: Laszlo Kishalmi >Priority: Minor > > When launching a build the Option window with the console output should be > opened or made visible if not open/visible already. -- 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-2037) Prefer slimmer gradle distribution
[
https://issues.apache.org/jira/browse/NETBEANS-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alessandro Falappa reassigned NETBEANS-2037:
Assignee: Laszlo Kishalmi
> Prefer slimmer gradle distribution
> --
>
> Key: NETBEANS-2037
> URL: https://issues.apache.org/jira/browse/NETBEANS-2037
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Gradle
>Affects Versions: 11.0
>Reporter: Alessandro Falappa
>Assignee: Laszlo Kishalmi
>Priority: Minor
>
> When opening Tool | Options | Java | Gradle a gradle 4.10.2 distribution is
> dowloaded and installed.
> The downloaded distribution is the complete one ({{gradle-4.10.2-all.zip}}),
> consider to download the binary only distribution ({{gradle-4.10.2-bin.zip}})
> which is about 40 Mb smaller.
--
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-2029) Unloadable Spring Initializr gradle project
[
https://issues.apache.org/jira/browse/NETBEANS-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16757651#comment-16757651
]
Alessandro Falappa commented on NETBEANS-2029:
--
Confirming that without opening Tools | Options | Java | Gradle and triggering
the distribution download an exception is still raised:
{code:java}
SEVERE [global]
java.lang.NullPointerException
at
org.gradle.tooling.internal.consumer.DistributionFactory$InstalledDistribution.getToolingImplementationClasspath(DistributionFactory.java:169)
at
org.gradle.tooling.internal.consumer.loader.CachingToolingImplementationLoader.create(CachingToolingImplementationLoader.java:40)
at
org.gradle.tooling.internal.consumer.loader.SynchronizedToolingImplementationLoader.create(SynchronizedToolingImplementationLoader.java:43)
at
org.gradle.tooling.internal.consumer.connection.LazyConsumerActionExecutor.onStartAction(LazyConsumerActionExecutor.java:101)
at
org.gradle.tooling.internal.consumer.connection.LazyConsumerActionExecutor.run(LazyConsumerActionExecutor.java:83)
at
org.gradle.tooling.internal.consumer.connection.CancellableConsumerActionExecutor.run(CancellableConsumerActionExecutor.java:45)
at
org.gradle.tooling.internal.consumer.connection.ProgressLoggingConsumerActionExecutor.run(ProgressLoggingConsumerActionExecutor.java:58)
at
org.gradle.tooling.internal.consumer.connection.RethrowingErrorsConsumerActionExecutor.run(RethrowingErrorsConsumerActionExecutor.java:38)
at
org.gradle.tooling.internal.consumer.async.DefaultAsyncConsumerActionExecutor$1$1.run(DefaultAsyncConsumerActionExecutor.java:55)
at
org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
at
org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at
org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)
at java.lang.Thread.run(Thread.java:748)
Caused: org.gradle.tooling.GradleConnectionException: Could not execute build
using Gradle installation 'null'.
at
org.gradle.tooling.internal.consumer.ExceptionTransformer.transform(ExceptionTransformer.java:55)
at
org.gradle.tooling.internal.consumer.ExceptionTransformer.transform(ExceptionTransformer.java:29)
at
org.gradle.tooling.internal.consumer.ResultHandlerAdapter.onFailure(ResultHandlerAdapter.java:41)
at
org.gradle.tooling.internal.consumer.async.DefaultAsyncConsumerActionExecutor$1$1.run(DefaultAsyncConsumerActionExecutor.java:57)
at
org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
at
org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at
org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)
at java.lang.Thread.run(Thread.java:748)
at
org.gradle.tooling.internal.consumer.BlockingResultHandler.getResult(BlockingResultHandler.java:46)
at
org.gradle.tooling.internal.consumer.DefaultBuildLauncher.run(DefaultBuildLauncher.java:77)
at
org.netbeans.modules.gradle.execute.GradleDaemonExecutor.run(GradleDaemonExecutor.java:162)
[catch] at
org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:128)
{code}
> Unloadable Spring Initializr gradle project
> ---
>
> Key: NETBEANS-2029
> URL: https://issues.apache.org/jira/browse/NETBEANS-2029
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Gradle
>Affects Versions: 11.0
> Environment: Product Version: Apache NetBeans IDE Dev (Build
> incubator-netbeans-linux-987-on-20190129)
> Java: 1.8.0_201; Java HotSpot(TM) 64-Bit Server VM 25.201-b09
> Runtime: Java(TM) SE Runtime Environment 1.8.0_201-b09
> System: Linux version 4.15.0-43-generic running on amd64; UTF-8; it_IT (nb)
> User directory: /home/sasha/.netbeans/dev
> Cache directory: /home/sasha/.cache/netbeans/dev
>Reporter: Alessandro Falappa
>Assignee: Laszlo Kishalmi
>Priority: Major
>
> I generated a basic Spring Boot gradle project on
> [http://start.spring.io|http://start.spring.io/] (choose gradle project type
> then press generate, unzip downloaded archive).
> I opened the generated project in NB11.
> The following exception pops-up almost immediately after opening:
> {code:java}
> java.lang.NullPointerException: The file parameter cannot be null
> at org.openide.util.Parameters.notNull(Parameters.java:64)
> at
[jira] [Created] (NETBEANS-2038) Anomalous termination of gradle task
Alessandro Falappa created NETBEANS-2038:
Summary: Anomalous termination of gradle task
Key: NETBEANS-2038
URL: https://issues.apache.org/jira/browse/NETBEANS-2038
Project: NetBeans
Issue Type: Bug
Components: projects - Gradle
Affects Versions: 11.0
Reporter: Alessandro Falappa
Assignee: Laszlo Kishalmi
Generate a Gradle Spring Boot project on
[http://start.spring.io|http://start.spring.io/] adding the *Web* dependency.
Unzip the download archive and open it in NetBeans.
In the Navigator right click on the _bootRun_ task and choose _Run Task..._
from the context menu. The project compiles and starts directly from the build
folder (the bootRun is a task provided by the spring boot gradle plugin) and
should run an embedded Tomcat server listening on port 8080.
Stop the task clicking the red stop button in the output window.
The task stops but the launched gradle process reports an abnormal termination
in the output window:
{code:java}
Could not read standard output of command '/usr/lib/jvm/java-8-oracle/bin/java'.
java.io.IOException: Stream closed
at java.io.BufferedInputStream.getBufIfOpen(BufferedInputStream.java:170)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:291)
at java.io.BufferedInputStream.read(BufferedInputStream.java:345)
at java.io.FilterInputStream.read(FilterInputStream.java:107)
at
org.gradle.process.internal.streams.ExecOutputHandleRunner.forwardContent(ExecOutputHandleRunner.java:61)
at
org.gradle.process.internal.streams.ExecOutputHandleRunner.run(ExecOutputHandleRunner.java:51)
at
org.gradle.internal.operations.CurrentBuildOperationPreservingRunnable.run(CurrentBuildOperationPreservingRunnable.java:42)
at
org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
at
org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at
org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)
at java.lang.Thread.run(Thread.java:748)
> Task :bootRun FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':bootRun'.
> Process 'command '/usr/lib/jvm/java-8-oracle/bin/java'' finished with
> non-zero exit value 143
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug
option to get more log output. Run with --scan to get full insights.
* Get more help at https://help.gradle.org
Deprecated Gradle features were used in this build, making it incompatible with
Gradle 5.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See
https://docs.gradle.org/4.10.2/userguide/command_line_interface.html#sec:command_line_warnings
BUILD FAILED in 50s
3 actionable tasks: 1 executed, 2 up-to-date
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Assigned] (NETBEANS-2036) Output tab remain active after gradle build finishes
[ https://issues.apache.org/jira/browse/NETBEANS-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Falappa reassigned NETBEANS-2036: Assignee: Laszlo Kishalmi > Output tab remain active after gradle build finishes > > > Key: NETBEANS-2036 > URL: https://issues.apache.org/jira/browse/NETBEANS-2036 > Project: NetBeans > Issue Type: Bug > Components: projects - Gradle >Affects Versions: 11.0 >Reporter: Alessandro Falappa >Assignee: Laszlo Kishalmi >Priority: Minor > > After a gradle build finishes the tab in the output window remain in 'active' > or 'running' state. > With Nimbus LAF the title of the tab is rendered with a bold font. The issue > is more evident wen having several tabs (try building several projects). > Maven and Ant builds deactivate the tab when finished. -- 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-2037) Prefer slimmer gradle distribution
Alessandro Falappa created NETBEANS-2037:
Summary: Prefer slimmer gradle distribution
Key: NETBEANS-2037
URL: https://issues.apache.org/jira/browse/NETBEANS-2037
Project: NetBeans
Issue Type: Bug
Components: projects - Gradle
Affects Versions: 11.0
Reporter: Alessandro Falappa
When opening Tool | Options | Java | Gradle a gradle 4.10.2 distribution is
dowloaded and installed.
The downloaded distribution is the complete one ({{gradle-4.10.2-all.zip}}),
consider to download the binary only distribution ({{gradle-4.10.2-bin.zip}})
which is about 40 Mb smaller.
--
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
