[jira] [Commented] (NETBEANS-5064) Support for specific NB (feature release) versions
[ https://issues.apache.org/jira/browse/NETBEANS-5064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17420141#comment-17420141 ] Ernie Rael commented on NETBEANS-5064: -- So for example with Xplug that depends on YMod Xplug-v2 depends on YMod [1.2.3,) Leave open ended avoiding changing the dependency for every YMod release. When YMod becomes incompatible, like in a 1.5, Xplug-v2 depends on YMod [1.2.3,1.5) Xplug-v3 depends on YMod [1.5,) All well and good as long as this info is _not_ in the module, but rather in some global catalog. > Support for specific NB (feature release) versions > -- > > Key: NETBEANS-5064 > URL: https://issues.apache.org/jira/browse/NETBEANS-5064 > Project: NetBeans > Issue Type: Wish > Components: updatecenters - Pluginportal >Reporter: Junichi Yamamoto >Priority: Major > > Maybe, currently, URLs for feature versions(e.g. 12.1) are redirected to the > URL for the LTS(e.g. 12.0) version, right? > That has a problem. We can't use an nbm of the LTS version if a feature > version has incompatible changes. > There are incompatible changes for PHP support in NetBeans 12.2. So, some > plugins related to PHP don't work any longer in 12.2 with the nbm for 12.0. > So, I have to provide nbms for 12.2. However, we can't add them to PP at the > moment. So, I have to upload them to another place(e.g. GitHub). > It would be nice for users/developers if we can add nbms for specific > versions. OTOH, it may be hard work for verifiers(/developers) to > verify(/add) them... > e.g. Although I'm not sure whether it is possible, if there is no nbm of > specific versions, it would be nice to be able to use nbms of LTS versions. -- 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-5913) 12.5 beta1 freezes
[ https://issues.apache.org/jira/browse/NETBEANS-5913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17398753#comment-17398753 ] Ernie Rael commented on NETBEANS-5913: -- I haven't looked at any code, so this comment may be off base and included in the general discussion about the hyperlink lock issue. Should the EDT ever unconditionally take even a read lock on the document and/or call into the parsing API? > 12.5 beta1 freezes > -- > > Key: NETBEANS-5913 > URL: https://issues.apache.org/jira/browse/NETBEANS-5913 > Project: NetBeans > Issue Type: Bug >Affects Versions: 12.5 > Environment: Product Version: Apache NetBeans IDE 12.5-beta1 > Java: 11.0.12; OpenJDK 64-Bit Server VM 11.0.12+7-post-Debian-2 > Runtime: OpenJDK Runtime Environment 11.0.12+7-post-Debian-2 > System: Linux version 5.10.0-8-amd64 running on amd64; UTF-8; en_GB (nb) > User directory: /home/chris/.netbeans/12.5-beta1 > Cache directory: /home/chris/.cache/netbeans/12.5-beta1 >Reporter: Chris Wareham >Assignee: Jan Lahoda >Priority: Blocker > Attachments: netbeans-12.5-beta1-azul-messages.log, > netbeans-12.5-beta1-azul-thread-dump.txt, netbeans-12.5-beta1-messages.log, > netbeans-12.5-beta1-thread-dump.txt > > > I'm getting occasional freezes. It can be after a few minutes or a few hours, > and there doesn't seem to be any specific user interaction that causes it. A > thread dump and log file is attached. -- 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-3104) Extend ArchetypeWizards.definedArchetype to include optional nbactions
[ https://issues.apache.org/jira/browse/NETBEANS-3104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17317343#comment-17317343 ] Ernie Rael commented on NETBEANS-3104: -- The openjfx PRs (from a year ago) mentioned in [earlier comment|https://issues.apache.org/jira/browse/NETBEANS-3104?focusedCommentId=17312777&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17312777] : > Add debug execution to the created archetypes > https://github.com/openjfx/javafx-maven-archetypes/pull/10 > comment out module syntax for JDK8 > https://github.com/openjfx/javafx-maven-archetypes/pull/11 have been merged into openjfx; unclear when it might find its way into maven central. So if this issues gets fixed, an nbactions.xml could be provided by NetBeans that uses executions from a stock openjfx archetype. Then the 4th party archetype could be dropped from NetBeans. But note that the openjfx pom.xml do not have profile or jlink execution; so some minor functionality would be lost. [Another earlier comment|https://issues.apache.org/jira/browse/NETBEANS-3104?focusedCommentId=17025192&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17025192] doesn't explicitly say so, but in addition to providing an nbactions.xml if NetBeans provides a mechanism to merge some optional execution into the pom.xml it would be useful when integrating/using 3rd party maven archetypes. > Extend ArchetypeWizards.definedArchetype to include optional nbactions > -- > > Key: NETBEANS-3104 > URL: https://issues.apache.org/jira/browse/NETBEANS-3104 > Project: NetBeans > Issue Type: Improvement >Reporter: Geertjan Wielenga >Assignee: Jaroslav Tulach >Priority: Major > Fix For: 12.2 > > > http://bits.netbeans.org/dev/javadoc/org-netbeans-api-maven/org/netbeans/api/maven/archetype/ArchetypeWizards.html -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-3104) Extend ArchetypeWizards.definedArchetype to include optional nbactions
[ https://issues.apache.org/jira/browse/NETBEANS-3104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17313351#comment-17313351 ] Ernie Rael commented on NETBEANS-3104: -- _Remembering some history..._ Was planning to change the resolution to *Won't Fix*; but, while preparing the comment, that didn't feel like the right thing to do. All I can say is that _fixed_ is not accurate; perhaps some resolution other than "won't fix" is appropriate. This issue is about how 3rd party maven projects can be integrated with NetBeans. The idea with this issue is that to integrate a 3rd party maven based project type into NetBeans you probably need to provide nbactions. NetBeans `New Project` for javafx used to create a project from an example maven artifact from openjfx/gluon. There were a variety of problems with this artifact. One of the problems was that there had to be an nbactions.xml to run/debug the example. This issue is about providing an API so that NetBeans can provide an nbactions with an off the shelf 3rd party artifact. The solution at the time was for a 4th party to modify the 3rd party openjfx example, *and* to include an *nbactions.xml* in the artifact. Including an nbactions in the artifact is not a general 3rd party solution. There were also a variety of changes made by the 4th party, so things would play better in NetBeans, or _any_ IDE, environment; PRs are pending at openjfx. This 4th party solution is taylored to NetBeans, avoiding 3rd party artifact issues. Note that if these PRs are eventually accepted by openjfx, there will still be a need to provide an nbactions. There's https://github.com/apache/netbeans/pull/2036 provides a mechanism for the jfx new project wizards to provide properties to the prototype for the maven project creation; loosely related to this issue. See the previous comment, https://issues.apache.org/jira/browse/NETBEANS-3104?focusedCommentId=17312777&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17312777 for specifics. > Extend ArchetypeWizards.definedArchetype to include optional nbactions > -- > > Key: NETBEANS-3104 > URL: https://issues.apache.org/jira/browse/NETBEANS-3104 > Project: NetBeans > Issue Type: Improvement >Reporter: Geertjan Wielenga >Assignee: Jaroslav Tulach >Priority: Major > Fix For: 12.2 > > > http://bits.netbeans.org/dev/javadoc/org-netbeans-api-maven/org/netbeans/api/maven/archetype/ArchetypeWizards.html -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Reopened] (NETBEANS-3104) Extend ArchetypeWizards.definedArchetype to include optional nbactions
[ https://issues.apache.org/jira/browse/NETBEANS-3104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernie Rael reopened NETBEANS-3104: -- Opening only to change the resolution > Extend ArchetypeWizards.definedArchetype to include optional nbactions > -- > > Key: NETBEANS-3104 > URL: https://issues.apache.org/jira/browse/NETBEANS-3104 > Project: NetBeans > Issue Type: Improvement >Reporter: Geertjan Wielenga >Assignee: Jaroslav Tulach >Priority: Major > Fix For: 12.2 > > > http://bits.netbeans.org/dev/javadoc/org-netbeans-api-maven/org/netbeans/api/maven/archetype/ArchetypeWizards.html -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-3104) Extend ArchetypeWizards.definedArchetype to include optional nbactions
[ https://issues.apache.org/jira/browse/NETBEANS-3104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17312777#comment-17312777 ] Ernie Rael commented on NETBEANS-3104: -- To get this documented somewhere. There are two outstanding PRs at https://github.com/openjfx/javafx-maven-archetypes/pulls Add debug execution to the created archetypes https://github.com/openjfx/javafx-maven-archetypes/pull/10 comment out module syntax for JDK8 https://github.com/openjfx/javafx-maven-archetypes/pull/11 Until these are merged, NB still uses https://github.com/errael/javafx-maven-archetypes-netbeans See the following for more info Default JavaFX archetypes to javafx 1.8 when running on jdk1.8 https://github.com/apache/netbeans/pull/2036 Ignore module-info.java if on jdk1.8 or earlier. https://github.com/apache/netbeans/pull/2037 Update JavaFX archetypes for recent JavaFX/maven PRs https://github.com/apache/netbeans/pull/2057 > Extend ArchetypeWizards.definedArchetype to include optional nbactions > -- > > Key: NETBEANS-3104 > URL: https://issues.apache.org/jira/browse/NETBEANS-3104 > Project: NetBeans > Issue Type: Improvement >Reporter: Geertjan Wielenga >Assignee: Jaroslav Tulach >Priority: Major > Fix For: 12.2 > > > http://bits.netbeans.org/dev/javadoc/org-netbeans-api-maven/org/netbeans/api/maven/archetype/ArchetypeWizards.html -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Closed] (NETBEANS-5287) gradle subprojects can't find imports from different subproject
[
https://issues.apache.org/jira/browse/NETBEANS-5287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ernie Rael closed NETBEANS-5287.
Project uses gradle 5.x, this is not compatible with JDK15, which I'm using to
run NetBeans.
For each project/subproject do
{code}
proj > properties > Build > Compile > JavaPlatform > JDK-11
{code}
Thanks.
> gradle subprojects can't find imports from different subproject
> ---
>
> Key: NETBEANS-5287
> URL: https://issues.apache.org/jira/browse/NETBEANS-5287
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Gradle
>Affects Versions: 12.2
> Environment: NB12.2, jdk15, Win7 (gradle projects under java1.8)
>Reporter: Ernie Rael
>Assignee: Laszlo Kishalmi
>Priority: Major
>
> Opening project https://github.com/glazedlists/glazedlists works, so does
> opening the subproject core, but opening subproject
> "glazedlists:extensions:icu4j" fails with editor errors about package import
> not found for packages from the "core" subproject's jar. Along with other
> subprojects, there's
> * glazedlists:core
> * glazedlists:extensions:icu4j
> all the subproject under glazedlists:extensions that reference core's jar
> have this problem. Things build from the command line. However, the project's
> gradle setup is outdated.
> ./gradlew -v give "Gradle 5.3.1" (and I wonder where that comes from and how
> it got there). There are deprecated warnings
> (https://gradle.com/s/iwj7ksmm72wc2) related to classpath resolution.
> Interestingly, if I open a test through "files" window then the imports are
> found (at least code completion works).
> (I'm new to gradle) I see plenty of activity around NB gradle support in the
> 12.2 release notes. But no docs/notes to help me set my NB gradle
> expectations. I'm looking through gradle issues.
> Should I expect a gradle project that runs from the command line to work with
> NetBeans?
> In particular I'm trying to add some junit tests, which are under
> "glazedlists:extensions:icu4j", but these open with the same package import
> problem.
> I'm (slowly) going through the gradle user manual, 6.8.1, though I have no
> idea that fixing the deprecation will allow the subprojects to work. And then
> there's running the tests from NB.
> In a discussion at the glazedlists' github site, there's the claim that "it
> works in eclipse".
--
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-5287) gradle subprojects can't find imports from different subproject
[ https://issues.apache.org/jira/browse/NETBEANS-5287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernie Rael updated NETBEANS-5287: - Environment: NB12.2, jdk15, Win7 (gradle projects under java1.8) (was: NB12.2, jdk1.8, Win7) > gradle subprojects can't find imports from different subproject > --- > > Key: NETBEANS-5287 > URL: https://issues.apache.org/jira/browse/NETBEANS-5287 > Project: NetBeans > Issue Type: Bug > Components: projects - Gradle >Affects Versions: 12.2 > Environment: NB12.2, jdk15, Win7 (gradle projects under java1.8) >Reporter: Ernie Rael >Assignee: Laszlo Kishalmi >Priority: Major > > Opening project https://github.com/glazedlists/glazedlists works, so does > opening the subproject core, but opening subproject > "glazedlists:extensions:icu4j" fails with editor errors about package import > not found for packages from the "core" subproject's jar. Along with other > subprojects, there's > * glazedlists:core > * glazedlists:extensions:icu4j > all the subproject under glazedlists:extensions that reference core's jar > have this problem. Things build from the command line. However, the project's > gradle setup is outdated. > ./gradlew -v give "Gradle 5.3.1" (and I wonder where that comes from and how > it got there). There are deprecated warnings > (https://gradle.com/s/iwj7ksmm72wc2) related to classpath resolution. > Interestingly, if I open a test through "files" window then the imports are > found (at least code completion works). > (I'm new to gradle) I see plenty of activity around NB gradle support in the > 12.2 release notes. But no docs/notes to help me set my NB gradle > expectations. I'm looking through gradle issues. > Should I expect a gradle project that runs from the command line to work with > NetBeans? > In particular I'm trying to add some junit tests, which are under > "glazedlists:extensions:icu4j", but these open with the same package import > problem. > I'm (slowly) going through the gradle user manual, 6.8.1, though I have no > idea that fixing the deprecation will allow the subprojects to work. And then > there's running the tests from NB. > In a discussion at the glazedlists' github site, there's the claim that "it > works in eclipse". -- 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-5287) gradle subprojects can't find imports from different subproject
Ernie Rael created NETBEANS-5287: Summary: gradle subprojects can't find imports from different subproject Key: NETBEANS-5287 URL: https://issues.apache.org/jira/browse/NETBEANS-5287 Project: NetBeans Issue Type: Bug Components: projects - Gradle Affects Versions: 12.2 Environment: NB12.2, jdk1.8, Win7 Reporter: Ernie Rael Assignee: Laszlo Kishalmi Opening project https://github.com/glazedlists/glazedlists works, so does opening the subproject core, but opening subproject "glazedlists:extensions:icu4j" fails with editor errors about package import not found for packages from the "core" subproject's jar. Along with other subprojects, there's * glazedlists:core * glazedlists:extensions:icu4j all the subproject under glazedlists:extensions that reference core's jar have this problem. Things build from the command line. However, the project's gradle setup is outdated. ./gradlew -v give "Gradle 5.3.1" (and I wonder where that comes from and how it got there). There are deprecated warnings (https://gradle.com/s/iwj7ksmm72wc2) related to classpath resolution. Interestingly, if I open a test through "files" window then the imports are found (at least code completion works). (I'm new to gradle) I see plenty of activity around NB gradle support in the 12.2 release notes. But no docs/notes to help me set my NB gradle expectations. I'm looking through gradle issues. Should I expect a gradle project that runs from the command line to work with NetBeans? In particular I'm trying to add some junit tests, which are under "glazedlists:extensions:icu4j", but these open with the same package import problem. I'm (slowly) going through the gradle user manual, 6.8.1, though I have no idea that fixing the deprecation will allow the subprojects to work. And then there's running the tests from NB. In a discussion at the glazedlists' github site, there's the claim that "it works in eclipse". -- 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-1823) JavaFX Scene Builder Integration is still broken (Since Java SE 8u40)
[ https://issues.apache.org/jira/browse/NETBEANS-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17268258#comment-17268258 ] Ernie Rael commented on NETBEANS-1823: -- Noting that this comes from [NETBEANS-5258] and has a pending PR https://github.com/apache/netbeans/pull/2688 (I typically ignore requests to download and execute something without additional info) > JavaFX Scene Builder Integration is still broken (Since Java SE 8u40) > - > > Key: NETBEANS-1823 > URL: https://issues.apache.org/jira/browse/NETBEANS-1823 > Project: NetBeans > Issue Type: Bug > Components: javafx - Editor >Affects Versions: 10.0 > Environment: MacOS High Sierra; NetBeans 10.vc5 running on JDK 10.0.1 > >Reporter: r-go >Priority: Major > Labels: 10.0-vc5, clos > Attachments: org-netbeans-modules-javafx2-scenebuilder.jar > > > NetBeans -> Preferences (Options) -> Java ->JavaFX > The only path supported is one that refers to long abandoned (since Java SE > 8u40) Oracle's Scene Builder. JavaFX Scene Builder provided by Gluon can not > be registered and used in NetBeans - which is kind of nonsense as its in fact > the only maintained version of JavaFX scene builder, recommended even by > oracle. > As JavaFX scene builder is effectively "just" an external .fxml file editor - > the integration with NB is trivial (but for some strange reasons it is > missing from NB for years now) - please fix it if possible. -- 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-5197) NetBeans GRADLE_USER_HOME not respected creating daemon
[
https://issues.apache.org/jira/browse/NETBEANS-5197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17256651#comment-17256651
]
Ernie Rael commented on NETBEANS-5197:
--
The one time I don't attach the log...
> NetBeans GRADLE_USER_HOME not respected creating daemon
> ---
>
> Key: NETBEANS-5197
> URL: https://issues.apache.org/jira/browse/NETBEANS-5197
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Gradle
>Reporter: Ernie Rael
>Assignee: Laszlo Kishalmi
>Priority: Major
> Attachments: messages.log
>
>
> (I'm new to gradle)
> Doing clean and build on a project I see
> {noformat}
> GRADLE_USER_HOME="C:\f\err\.gradle"
> JAVA_HOME="C:\f\j\jdk\jdk1.8.0_241"
> cd C:\f\repos\swingset\glazedlists; .\gradlew.bat --configure-on-demand -x
> check clean build
> {noformat}
> in output window. There's an exception (see below) trying to access
> C:\Users\err\.gradle (which I have made inaccessible as a directory) but
> notice above that this is not GRADLE_USER_HOME.
> I'm on window7/cygwin. I have not put GRADLE_USER_HOME into the win7
> environment variable. But as seen above, NetBeans knows what it it supposed
> to be.
> {noformat}
> SEVERE [global]
> org.gradle.api.UncheckedIOException: Cannot create parent directory
> 'C:\Users\err\.gradle\daemon' when creating directory
> 'C:\Users\err\.gradle\daemon\5.3.1' as 'C:\Users\err\.gradle' is not a
> directory
> at org.gradle.util.GFileUtils.mkdirs(GFileUtils.java:323)
> at org.gradle.launcher.daemon.registry.DaemonDir.(DaemonDir.java:33)
> at
> org.gradle.launcher.daemon.registry.DaemonRegistryServices.createDaemonDir(DaemonRegistryServices.java:52)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-5197) NetBeans GRADLE_USER_HOME not respected creating daemon
[
https://issues.apache.org/jira/browse/NETBEANS-5197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ernie Rael updated NETBEANS-5197:
-
Attachment: messages.log
> NetBeans GRADLE_USER_HOME not respected creating daemon
> ---
>
> Key: NETBEANS-5197
> URL: https://issues.apache.org/jira/browse/NETBEANS-5197
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Gradle
>Reporter: Ernie Rael
>Assignee: Laszlo Kishalmi
>Priority: Major
> Attachments: messages.log
>
>
> (I'm new to gradle)
> Doing clean and build on a project I see
> {noformat}
> GRADLE_USER_HOME="C:\f\err\.gradle"
> JAVA_HOME="C:\f\j\jdk\jdk1.8.0_241"
> cd C:\f\repos\swingset\glazedlists; .\gradlew.bat --configure-on-demand -x
> check clean build
> {noformat}
> in output window. There's an exception (see below) trying to access
> C:\Users\err\.gradle (which I have made inaccessible as a directory) but
> notice above that this is not GRADLE_USER_HOME.
> I'm on window7/cygwin. I have not put GRADLE_USER_HOME into the win7
> environment variable. But as seen above, NetBeans knows what it it supposed
> to be.
> {noformat}
> SEVERE [global]
> org.gradle.api.UncheckedIOException: Cannot create parent directory
> 'C:\Users\err\.gradle\daemon' when creating directory
> 'C:\Users\err\.gradle\daemon\5.3.1' as 'C:\Users\err\.gradle' is not a
> directory
> at org.gradle.util.GFileUtils.mkdirs(GFileUtils.java:323)
> at org.gradle.launcher.daemon.registry.DaemonDir.(DaemonDir.java:33)
> at
> org.gradle.launcher.daemon.registry.DaemonRegistryServices.createDaemonDir(DaemonRegistryServices.java:52)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-5197) NetBeans GRADLE_USER_HOME not respected creating daemon
[
https://issues.apache.org/jira/browse/NETBEANS-5197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17256649#comment-17256649
]
Ernie Rael commented on NETBEANS-5197:
--
Added GRADLE_USER_HOME=C:/f/err/.gradle as a Win7 environment variable and now
it works.
> NetBeans GRADLE_USER_HOME not respected creating daemon
> ---
>
> Key: NETBEANS-5197
> URL: https://issues.apache.org/jira/browse/NETBEANS-5197
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Gradle
>Reporter: Ernie Rael
>Assignee: Laszlo Kishalmi
>Priority: Major
>
> (I'm new to gradle)
> Doing clean and build on a project I see
> {noformat}
> GRADLE_USER_HOME="C:\f\err\.gradle"
> JAVA_HOME="C:\f\j\jdk\jdk1.8.0_241"
> cd C:\f\repos\swingset\glazedlists; .\gradlew.bat --configure-on-demand -x
> check clean build
> {noformat}
> in output window. There's an exception (see below) trying to access
> C:\Users\err\.gradle (which I have made inaccessible as a directory) but
> notice above that this is not GRADLE_USER_HOME.
> I'm on window7/cygwin. I have not put GRADLE_USER_HOME into the win7
> environment variable. But as seen above, NetBeans knows what it it supposed
> to be.
> {noformat}
> SEVERE [global]
> org.gradle.api.UncheckedIOException: Cannot create parent directory
> 'C:\Users\err\.gradle\daemon' when creating directory
> 'C:\Users\err\.gradle\daemon\5.3.1' as 'C:\Users\err\.gradle' is not a
> directory
> at org.gradle.util.GFileUtils.mkdirs(GFileUtils.java:323)
> at org.gradle.launcher.daemon.registry.DaemonDir.(DaemonDir.java:33)
> at
> org.gradle.launcher.daemon.registry.DaemonRegistryServices.createDaemonDir(DaemonRegistryServices.java:52)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Created] (NETBEANS-5197) NetBeans GRADLE_USER_HOME not respected creating daemon
Ernie Rael created NETBEANS-5197:
Summary: NetBeans GRADLE_USER_HOME not respected creating daemon
Key: NETBEANS-5197
URL: https://issues.apache.org/jira/browse/NETBEANS-5197
Project: NetBeans
Issue Type: Bug
Components: projects - Gradle
Reporter: Ernie Rael
Assignee: Laszlo Kishalmi
(I'm new to gradle)
Doing clean and build on a project I see
{noformat}
GRADLE_USER_HOME="C:\f\err\.gradle"
JAVA_HOME="C:\f\j\jdk\jdk1.8.0_241"
cd C:\f\repos\swingset\glazedlists; .\gradlew.bat --configure-on-demand -x
check clean build
{noformat}
in output window. There's an exception (see below) trying to access
C:\Users\err\.gradle (which I have made inaccessible as a directory) but
notice above that this is not GRADLE_USER_HOME.
I'm on window7/cygwin. I have not put GRADLE_USER_HOME into the win7
environment variable. But as seen above, NetBeans knows what it it supposed to
be.
{noformat}
SEVERE [global]
org.gradle.api.UncheckedIOException: Cannot create parent directory
'C:\Users\err\.gradle\daemon' when creating directory
'C:\Users\err\.gradle\daemon\5.3.1' as 'C:\Users\err\.gradle' is not a directory
at org.gradle.util.GFileUtils.mkdirs(GFileUtils.java:323)
at org.gradle.launcher.daemon.registry.DaemonDir.(DaemonDir.java:33)
at
org.gradle.launcher.daemon.registry.DaemonRegistryServices.createDaemonDir(DaemonRegistryServices.java:52)
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-4940) Caret drawing problems over a TAB
[
https://issues.apache.org/jira/browse/NETBEANS-4940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17226353#comment-17226353
]
Ernie Rael commented on NETBEANS-4940:
--
One possible solution is to add this method to BaseCaret
{code}
protected void adjustCaretBounds(Rectangle bounds, int offset) {
bounds.width = Math.max(bounds.width, 2);
}
{code}
which is called from udpateCaretBounds.
!CaretCircle.png!
In a BaseCaret subclass, an experiment to draw a circle around the caret
position worked by overriding the above method with a suitable algorithm.
> Caret drawing problems over a TAB
> -
>
> Key: NETBEANS-4940
> URL: https://issues.apache.org/jira/browse/NETBEANS-4940
> Project: NetBeans
> Issue Type: Bug
> Components: editor - Other
>Affects Versions: 12.1
>Reporter: Ernie Rael
>Priority: Minor
> Labels: pull-request-available
> Attachments: CaretCircle.png
>
> Time Spent: 5h 10m
> Remaining Estimate: 0h
>
> To recreate.
> # Open a file in the editor (emptyfile, java file,...)
> # Insert a tab into the file
> # Place the caret over the tab
> Observe the caret as it blinks and notice that it only partially blanks.
> There is a vertical artifact.
> The jVi application uses a block caret (rather than a vertical line) and the
> problem is more more pronounced.
--
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-4940) Caret drawing problems over a TAB
[ https://issues.apache.org/jira/browse/NETBEANS-4940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernie Rael updated NETBEANS-4940: - Attachment: CaretCircle.png > Caret drawing problems over a TAB > - > > Key: NETBEANS-4940 > URL: https://issues.apache.org/jira/browse/NETBEANS-4940 > Project: NetBeans > Issue Type: Bug > Components: editor - Other >Affects Versions: 12.1 >Reporter: Ernie Rael >Priority: Minor > Labels: pull-request-available > Attachments: CaretCircle.png > > Time Spent: 5h 10m > Remaining Estimate: 0h > > To recreate. > # Open a file in the editor (emptyfile, java file,...) > # Insert a tab into the file > # Place the caret over the tab > Observe the caret as it blinks and notice that it only partially blanks. > There is a vertical artifact. > The jVi application uses a block caret (rather than a vertical line) and the > problem is more more pronounced. -- 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-4940) Caret drawing problems over a TAB
[ https://issues.apache.org/jira/browse/NETBEANS-4940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17225552#comment-17225552 ] Ernie Rael commented on NETBEANS-4940: -- editor.lib2's EditorCaret exhibits this problem. This issue was filed after seeing a plugin, using the editor.lib BaseCaret. There is considerable discussion about this issue in the PR #2482 EditorCaret is now the default caret, BaseCaret is no longer used expect by 3rd party plugins. EditorCaret has both single caret and multi-caret and they both exhibit this problem. Switching to multi-caret modes happens by choosing multiple positions by clicking on new positions while CTRL+Shift is held down. To see the multi-caret problem you can do # Starting with a clean userdir/cachedir, start up NetBeans # in Editor>Formatting>AllLang,Tabs... turn off EnableIndent & ExpandTabtoSpaces, set NumSpacePerIndent to 8 (to match tab size) # NewFile>Other>EmptyFile. # I added a line full of regular chars, two lines of just TABs, then a line of regular chars. # Place caret on a TAB in second line, add a second caret on regular char in last line. # Hit the right arrow. # Observe the rendering artifacts over the TAB. > Caret drawing problems over a TAB > - > > Key: NETBEANS-4940 > URL: https://issues.apache.org/jira/browse/NETBEANS-4940 > Project: NetBeans > Issue Type: Bug > Components: editor - Other >Affects Versions: 12.1 >Reporter: Ernie Rael >Priority: Minor > Labels: pull-request-available > Time Spent: 3h 50m > Remaining Estimate: 0h > > To recreate. > # Open a file in the editor (emptyfile, java file,...) > # Insert a tab into the file > # Place the caret over the tab > Observe the caret as it blinks and notice that it only partially blanks. > There is a vertical artifact. > The jVi application uses a block caret (rather than a vertical line) and the > problem is more more pronounced. -- 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-4940) Caret drawing problems over a TAB
Ernie Rael created NETBEANS-4940: Summary: Caret drawing problems over a TAB Key: NETBEANS-4940 URL: https://issues.apache.org/jira/browse/NETBEANS-4940 Project: NetBeans Issue Type: Bug Components: editor - Other Affects Versions: 12.1 Reporter: Ernie Rael To recreate. # Open a file in the editor (emptyfile, java file,...) # Insert a tab into the file # Place the caret over the tab Observe the caret as it blinks and notice that it only partially blanks. There is a vertical artifact. The jVi application uses a block caret (rather than a vertical line) and the problem is more more pronounced. -- 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-4832) fxml code completion fails with modular java
[
https://issues.apache.org/jira/browse/NETBEANS-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17202472#comment-17202472
]
Ernie Rael commented on NETBEANS-4832:
--
Here's the stacktraces associated with the NPE. The assert stack is in the
messages log. To recreate, cursor after "" (not in a UI element) then
hit Ctrl-Space.
{code}
INFO [org.netbeans.api.java.source.ElementHandle]: Resolved type is null for
kind = CLASS
INFO [org.netbeans.api.java.source.ElementHandle]: Cannot resolve:
ElementHandle[kind=CLASS; sigs=javafx.scene.Node ]
SEVERE [org.openide.util.Exceptions]
java.lang.NullPointerException
at
jdk.compiler/com.sun.tools.javac.model.JavacTypes.validateTypeNotIn(JavacTypes.java:311)
at
jdk.compiler/com.sun.tools.javac.model.JavacTypes.isAssignable(JavacTypes.java:104)
at
org.netbeans.modules.javafx2.editor.completion.impl.FxIncludeCompleter.createCompleter(FxIncludeCompleter.java:73)
at
org.netbeans.modules.javafx2.editor.FXMLCompletion2$Q$Task.run(FXMLCompletion2.java:187)
at
org.netbeans.modules.parsing.impl.TaskProcessor.callUserTask(TaskProcessor.java:586)
at
org.netbeans.modules.parsing.api.ParserManager$MimeTaskAction.run(ParserManager.java:357)
at
org.netbeans.modules.parsing.api.ParserManager$MimeTaskAction.run(ParserManager.java:340)
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)
Caused: org.netbeans.modules.parsing.spi.ParseException
at
org.netbeans.modules.parsing.impl.TaskProcessor.runUserTask(TaskProcessor.java:186)
at
org.netbeans.modules.parsing.api.ParserManager.parse(ParserManager.java:311)
at
org.netbeans.modules.javafx2.editor.FXMLCompletion2$Q$Task.run(FXMLCompletion2.java:159)
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)
Caused: org.netbeans.modules.parsing.spi.ParseException
at
org.netbeans.modules.parsing.impl.TaskProcessor.runUserTask(TaskProcessor.java:186)
at
org.netbeans.modules.parsing.api.ParserManager.parse(ParserManager.java:81)
[catch] at
org.netbeans.modules.javafx2.editor.FXMLCompletion2$Q.query(FXMLCompletion2.java:106)
at
org.netbeans.spi.editor.completion.support.AsyncCompletionTask.run(AsyncCompletionTask.java:198)
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)
{code}
> fxml code completion fails with modular java
>
>
> Key: NETBEANS-4832
> URL: https://issues.apache.org/jira/browse/NETBEANS-4832
> Project: NetBeans
> Issue Type: Bug
> Components: javafx - Editor
> Environment: NB-12.1, jdk-14, no nb-javac, Win7, no userdir/cachedir,
> startup do not import settings
>Reporter: Ernie Rael
>Priority: Major
> Labels: modularization, pull-request-available,
> pull-requests-available
> Attachments: AllModulesAssert-messages-2.log
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> To reproduce (create/open fxml f
[jira] [Updated] (NETBEANS-4832) fxml code completion fails with modular java
[
https://issues.apache.org/jira/browse/NETBEANS-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ernie Rael updated NETBEANS-4832:
-
Labels: modularization pull-requests-available (was: modularization
pull-request-available)
> fxml code completion fails with modular java
>
>
> Key: NETBEANS-4832
> URL: https://issues.apache.org/jira/browse/NETBEANS-4832
> Project: NetBeans
> Issue Type: Bug
> Components: javafx - Editor
> Environment: NB-12.1, jdk-14, no nb-javac, Win7, no userdir/cachedir,
> startup do not import settings
>Reporter: Ernie Rael
>Priority: Major
> Labels: modularization, pull-requests-available
> Attachments: AllModulesAssert-messages-2.log
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> To reproduce (create/open fxml file)
> # NewProject > JavaWithMaven > FXML JavaFX Maven Archetype (Gluon)
> # Open primary.fxml, in "other sources" "source/main/resources"
> # put cursor within xml, for example after ""
> # Enter Ctrl-Space to bring up code completion
> Observe:
> * Typically have to go through a couple web certification dialogs
> * Typically repeat Ctrl-Space and there's a "downloading..." that never
> finishes
> Note: Works OK when running on and using jdk1.8 with nb-javac.
> Fails with JDK assertion: Assert.checkNonNull(allModules)
> (full message log attached)
> {code}
> java.lang.AssertionError at
> jdk.compiler/com.sun.tools.javac.util.Assert.error(Assert.java:155) at
> jdk.compiler/com.sun.tools.javac.util.Assert.checkNonNull(Assert.java:62) at
> jdk.compiler/com.sun.tools.javac.comp.Modules.allModules(Modules.java:1205)
> at
> jdk.compiler/com.sun.tools.javac.model.JavacElements.getAllModuleElements(JavacElements.java:126)
> at
> org.netbeans.modules.java.source.ElementUtils.getTypeElementByBinaryName(ElementUtils.java:49)
> at
> org.netbeans.api.java.source.ElementHandle.getTypeElementByBinaryName(ElementHandle.java:666)
> at
> org.netbeans.api.java.source.ElementHandle.resolveImpl(ElementHandle.java:163)
> at
> org.netbeans.api.java.source.ElementHandle.resolve(ElementHandle.java:132) at
> org.netbeans.modules.javafx2.editor.completion.impl.InstanceCompleter.(InstanceCompleter.java:54)
> {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-4832) fxml code completion fails with modular java
[
https://issues.apache.org/jira/browse/NETBEANS-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17201840#comment-17201840
]
Ernie Rael commented on NETBEANS-4832:
--
Got a fix for the assertion. Then there was the NPE and a fix.
Not sure if this gets fxml up to jdk8 standard.
> fxml code completion fails with modular java
>
>
> Key: NETBEANS-4832
> URL: https://issues.apache.org/jira/browse/NETBEANS-4832
> Project: NetBeans
> Issue Type: Bug
> Components: javafx - Editor
> Environment: NB-12.1, jdk-14, no nb-javac, Win7, no userdir/cachedir,
> startup do not import settings
>Reporter: Ernie Rael
>Priority: Major
> Labels: modularization
> Attachments: AllModulesAssert-messages-2.log
>
>
> To reproduce (create/open fxml file)
> # NewProject > JavaWithMaven > FXML JavaFX Maven Archetype (Gluon)
> # Open primary.fxml, in "other sources" "source/main/resources"
> # put cursor within xml, for example after ""
> # Enter Ctrl-Space to bring up code completion
> Observe:
> * Typically have to go through a couple web certification dialogs
> * Typically repeat Ctrl-Space and there's a "downloading..." that never
> finishes
> Note: Works OK when running on and using jdk1.8 with nb-javac.
> Fails with JDK assertion: Assert.checkNonNull(allModules)
> (full message log attached)
> {code}
> java.lang.AssertionError at
> jdk.compiler/com.sun.tools.javac.util.Assert.error(Assert.java:155) at
> jdk.compiler/com.sun.tools.javac.util.Assert.checkNonNull(Assert.java:62) at
> jdk.compiler/com.sun.tools.javac.comp.Modules.allModules(Modules.java:1205)
> at
> jdk.compiler/com.sun.tools.javac.model.JavacElements.getAllModuleElements(JavacElements.java:126)
> at
> org.netbeans.modules.java.source.ElementUtils.getTypeElementByBinaryName(ElementUtils.java:49)
> at
> org.netbeans.api.java.source.ElementHandle.getTypeElementByBinaryName(ElementHandle.java:666)
> at
> org.netbeans.api.java.source.ElementHandle.resolveImpl(ElementHandle.java:163)
> at
> org.netbeans.api.java.source.ElementHandle.resolve(ElementHandle.java:132) at
> org.netbeans.modules.javafx2.editor.completion.impl.InstanceCompleter.(InstanceCompleter.java:54)
> {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] [Updated] (NETBEANS-4832) fxml code completion fails with modular java
[
https://issues.apache.org/jira/browse/NETBEANS-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ernie Rael updated NETBEANS-4832:
-
Attachment: AllModulesAssert-messages-2.log
> fxml code completion fails with modular java
>
>
> Key: NETBEANS-4832
> URL: https://issues.apache.org/jira/browse/NETBEANS-4832
> Project: NetBeans
> Issue Type: Bug
> Components: javafx - Editor
> Environment: NB-12.1, jdk-14, no nb-javac, Win7, no userdir/cachedir,
> startup do not import settings
>Reporter: Ernie Rael
>Priority: Major
> Labels: modularization
> Attachments: AllModulesAssert-messages-2.log
>
>
> To reproduce (create/open fxml file)
> # NewProject > JavaWithMaven > FXML JavaFX Maven Archetype (Gluon)
> # Open primary.fxml, in "other sources" "source/main/resources"
> # put cursor within xml, for example after ""
> # Enter Ctrl-Space to bring up code completion
> Observe:
> * Typically have to go through a couple web certification dialogs
> * Typically repeat Ctrl-Space and there's a "downloading..." that never
> finishes
> Note: Works OK when running on and using jdk1.8 with nb-javac.
> Fails with JDK assertion: Assert.checkNonNull(allModules)
> (full message log attached)
> {code}
> java.lang.AssertionError at
> jdk.compiler/com.sun.tools.javac.util.Assert.error(Assert.java:155) at
> jdk.compiler/com.sun.tools.javac.util.Assert.checkNonNull(Assert.java:62) at
> jdk.compiler/com.sun.tools.javac.comp.Modules.allModules(Modules.java:1205)
> at
> jdk.compiler/com.sun.tools.javac.model.JavacElements.getAllModuleElements(JavacElements.java:126)
> at
> org.netbeans.modules.java.source.ElementUtils.getTypeElementByBinaryName(ElementUtils.java:49)
> at
> org.netbeans.api.java.source.ElementHandle.getTypeElementByBinaryName(ElementHandle.java:666)
> at
> org.netbeans.api.java.source.ElementHandle.resolveImpl(ElementHandle.java:163)
> at
> org.netbeans.api.java.source.ElementHandle.resolve(ElementHandle.java:132) at
> org.netbeans.modules.javafx2.editor.completion.impl.InstanceCompleter.(InstanceCompleter.java:54)
> {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] [Issue Comment Deleted] (NETBEANS-4745) fxml editor shows errors for Insets (immutable objects in general?)
[
https://issues.apache.org/jira/browse/NETBEANS-4745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ernie Rael updated NETBEANS-4745:
-
Comment: was deleted
(was: [~sdedic] I can't even propose a fix for this one... If a fix is not
obvious, I can gather info, if you'd like. If you can outline a fix, I can try
to put together a PR.
For the error annotator parser (which works ok and has a list of modules)
{code}
ParserManager.MimeTaskAction.run
userTask: FxmlParser$1UT
{code}
For the completion parser, after Ctrl-Space
{code}
ParserManager.UserTaskAction.run
userTask: FXMLCompletion2$Q$Task@4ccbdf93
{code}
The compiler info for the completion parser does not have the list of modules.
)
> fxml editor shows errors for Insets (immutable objects in general?)
> ---
>
> Key: NETBEANS-4745
> URL: https://issues.apache.org/jira/browse/NETBEANS-4745
> Project: NetBeans
> Issue Type: Bug
> Components: javafx - Editor
>Reporter: Ernie Rael
>Priority: Major
> Labels: pull-request-available
> Time Spent: 2h
> Remaining Estimate: 0h
>
> To recreate:
> NewProject > JavaWithMaven > FXML JavaFX Maven Archetype (Gluon)
> Open primary.fxml, in "other sources" "source/main/resources"
> Observe that the lines like:
> {code}
>
> {code}
> show errors, in particular
> {code}
> Instances of javafx.geometry.Insets cannot be created by FXML loader
> Class 'javafx.geometry.Insets' does not support property 'bottom'
> {code}
> examining the code in NetBeans "JavaFX 2 Support" module
> {code:java}
> package org.netbeans.modules.javafx2.editor.completion.beans;
> public final class BeanModelBuilder
> {code}
> The problem seems to start with Insets not having a no argument constructor;
> and the properties are not recognized because they have no setters. So it
> looks like immutable objects are not handled.
> Look near the begginning of BeanModelBuilder.process() around
> {code}
> if (c.getParameters().isEmpty() &&
> {code}
> and then BeanModelBuilder.inspectMembers(), addProperty(), findPropertyName
> {code}
> if (!name.startsWith(SET_NAME_PREFIX) || name.length() ==
> SET_NAME_PREFIX_LEN ||
> {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-4832) fxml code completion fails with modular java
[
https://issues.apache.org/jira/browse/NETBEANS-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17199727#comment-17199727
]
Ernie Rael commented on NETBEANS-4832:
--
[~sdedic] I can't even propose a fix for this one... If a fix is not obvious, I
can gather info, if you'd like. If you can outline a fix, I can try to put
together a PR.
For the error annotator parser (which works ok and has a list of modules)
{code}
ParserManager.MimeTaskAction.run
userTask: FxmlParser$1UT
{code}
For the completion parser, after Ctrl-Space
{code}
ParserManager.UserTaskAction.run
userTask: FXMLCompletion2$Q$Task@4ccbdf93
{code}
The compiler info for the completion parser does not have the list of modules.
> fxml code completion fails with modular java
>
>
> Key: NETBEANS-4832
> URL: https://issues.apache.org/jira/browse/NETBEANS-4832
> Project: NetBeans
> Issue Type: Bug
> Components: javafx - Editor
> Environment: NB-12.1, jdk-14, no nb-javac, Win7, no userdir/cachedir,
> startup do not import settings
>Reporter: Ernie Rael
>Priority: Major
> Labels: modularization
>
> To reproduce (create/open fxml file)
> # NewProject > JavaWithMaven > FXML JavaFX Maven Archetype (Gluon)
> # Open primary.fxml, in "other sources" "source/main/resources"
> # put cursor within xml, for example after ""
> # Enter Ctrl-Space to bring up code completion
> Observe:
> * Typically have to go through a couple web certification dialogs
> * Typically repeat Ctrl-Space and there's a "downloading..." that never
> finishes
> Note: Works OK when running on and using jdk1.8 with nb-javac.
> Fails with JDK assertion: Assert.checkNonNull(allModules)
> (full message log attached)
> {code}
> java.lang.AssertionError at
> jdk.compiler/com.sun.tools.javac.util.Assert.error(Assert.java:155) at
> jdk.compiler/com.sun.tools.javac.util.Assert.checkNonNull(Assert.java:62) at
> jdk.compiler/com.sun.tools.javac.comp.Modules.allModules(Modules.java:1205)
> at
> jdk.compiler/com.sun.tools.javac.model.JavacElements.getAllModuleElements(JavacElements.java:126)
> at
> org.netbeans.modules.java.source.ElementUtils.getTypeElementByBinaryName(ElementUtils.java:49)
> at
> org.netbeans.api.java.source.ElementHandle.getTypeElementByBinaryName(ElementHandle.java:666)
> at
> org.netbeans.api.java.source.ElementHandle.resolveImpl(ElementHandle.java:163)
> at
> org.netbeans.api.java.source.ElementHandle.resolve(ElementHandle.java:132) at
> org.netbeans.modules.javafx2.editor.completion.impl.InstanceCompleter.(InstanceCompleter.java:54)
> {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] [Updated] (NETBEANS-4745) fxml editor shows errors for Insets (immutable objects in general?)
[
https://issues.apache.org/jira/browse/NETBEANS-4745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ernie Rael updated NETBEANS-4745:
-
Attachment: (was: AllModulesAssert-messages-2.log)
> fxml editor shows errors for Insets (immutable objects in general?)
> ---
>
> Key: NETBEANS-4745
> URL: https://issues.apache.org/jira/browse/NETBEANS-4745
> Project: NetBeans
> Issue Type: Bug
> Components: javafx - Editor
>Reporter: Ernie Rael
>Priority: Major
> Labels: pull-request-available
> Time Spent: 2h
> Remaining Estimate: 0h
>
> To recreate:
> NewProject > JavaWithMaven > FXML JavaFX Maven Archetype (Gluon)
> Open primary.fxml, in "other sources" "source/main/resources"
> Observe that the lines like:
> {code}
>
> {code}
> show errors, in particular
> {code}
> Instances of javafx.geometry.Insets cannot be created by FXML loader
> Class 'javafx.geometry.Insets' does not support property 'bottom'
> {code}
> examining the code in NetBeans "JavaFX 2 Support" module
> {code:java}
> package org.netbeans.modules.javafx2.editor.completion.beans;
> public final class BeanModelBuilder
> {code}
> The problem seems to start with Insets not having a no argument constructor;
> and the properties are not recognized because they have no setters. So it
> looks like immutable objects are not handled.
> Look near the begginning of BeanModelBuilder.process() around
> {code}
> if (c.getParameters().isEmpty() &&
> {code}
> and then BeanModelBuilder.inspectMembers(), addProperty(), findPropertyName
> {code}
> if (!name.startsWith(SET_NAME_PREFIX) || name.length() ==
> SET_NAME_PREFIX_LEN ||
> {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-4745) fxml editor shows errors for Insets (immutable objects in general?)
[
https://issues.apache.org/jira/browse/NETBEANS-4745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17199725#comment-17199725
]
Ernie Rael commented on NETBEANS-4745:
--
[~sdedic] I can't even propose a fix for this one... If a fix is not obvious, I
can gather info, if you'd like. If you can outline a fix, I can try to put
together a PR.
For the error annotator parser (which works ok and has a list of modules)
{code}
ParserManager.MimeTaskAction.run
userTask: FxmlParser$1UT
{code}
For the completion parser, after Ctrl-Space
{code}
ParserManager.UserTaskAction.run
userTask: FXMLCompletion2$Q$Task@4ccbdf93
{code}
The compiler info for the completion parser does not have the list of modules.
> fxml editor shows errors for Insets (immutable objects in general?)
> ---
>
> Key: NETBEANS-4745
> URL: https://issues.apache.org/jira/browse/NETBEANS-4745
> Project: NetBeans
> Issue Type: Bug
> Components: javafx - Editor
>Reporter: Ernie Rael
>Priority: Major
> Labels: pull-request-available
> Attachments: AllModulesAssert-messages-2.log
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> To recreate:
> NewProject > JavaWithMaven > FXML JavaFX Maven Archetype (Gluon)
> Open primary.fxml, in "other sources" "source/main/resources"
> Observe that the lines like:
> {code}
>
> {code}
> show errors, in particular
> {code}
> Instances of javafx.geometry.Insets cannot be created by FXML loader
> Class 'javafx.geometry.Insets' does not support property 'bottom'
> {code}
> examining the code in NetBeans "JavaFX 2 Support" module
> {code:java}
> package org.netbeans.modules.javafx2.editor.completion.beans;
> public final class BeanModelBuilder
> {code}
> The problem seems to start with Insets not having a no argument constructor;
> and the properties are not recognized because they have no setters. So it
> looks like immutable objects are not handled.
> Look near the begginning of BeanModelBuilder.process() around
> {code}
> if (c.getParameters().isEmpty() &&
> {code}
> and then BeanModelBuilder.inspectMembers(), addProperty(), findPropertyName
> {code}
> if (!name.startsWith(SET_NAME_PREFIX) || name.length() ==
> SET_NAME_PREFIX_LEN ||
> {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] [Updated] (NETBEANS-4745) fxml editor shows errors for Insets (immutable objects in general?)
[
https://issues.apache.org/jira/browse/NETBEANS-4745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ernie Rael updated NETBEANS-4745:
-
Attachment: AllModulesAssert-messages-2.log
> fxml editor shows errors for Insets (immutable objects in general?)
> ---
>
> Key: NETBEANS-4745
> URL: https://issues.apache.org/jira/browse/NETBEANS-4745
> Project: NetBeans
> Issue Type: Bug
> Components: javafx - Editor
>Reporter: Ernie Rael
>Priority: Major
> Labels: pull-request-available
> Attachments: AllModulesAssert-messages-2.log
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> To recreate:
> NewProject > JavaWithMaven > FXML JavaFX Maven Archetype (Gluon)
> Open primary.fxml, in "other sources" "source/main/resources"
> Observe that the lines like:
> {code}
>
> {code}
> show errors, in particular
> {code}
> Instances of javafx.geometry.Insets cannot be created by FXML loader
> Class 'javafx.geometry.Insets' does not support property 'bottom'
> {code}
> examining the code in NetBeans "JavaFX 2 Support" module
> {code:java}
> package org.netbeans.modules.javafx2.editor.completion.beans;
> public final class BeanModelBuilder
> {code}
> The problem seems to start with Insets not having a no argument constructor;
> and the properties are not recognized because they have no setters. So it
> looks like immutable objects are not handled.
> Look near the begginning of BeanModelBuilder.process() around
> {code}
> if (c.getParameters().isEmpty() &&
> {code}
> and then BeanModelBuilder.inspectMembers(), addProperty(), findPropertyName
> {code}
> if (!name.startsWith(SET_NAME_PREFIX) || name.length() ==
> SET_NAME_PREFIX_LEN ||
> {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-4832) fxml code completion fails with modular java
Ernie Rael created NETBEANS-4832:
Summary: fxml code completion fails with modular java
Key: NETBEANS-4832
URL: https://issues.apache.org/jira/browse/NETBEANS-4832
Project: NetBeans
Issue Type: Bug
Components: javafx - Editor
Environment: NB-12.1, jdk-14, no nb-javac, Win7, no userdir/cachedir,
startup do not import settings
Reporter: Ernie Rael
To reproduce (create/open fxml file)
# NewProject > JavaWithMaven > FXML JavaFX Maven Archetype (Gluon)
# Open primary.fxml, in "other sources" "source/main/resources"
# put cursor within xml, for example after ""
# Enter Ctrl-Space to bring up code completion
Observe:
* Typically have to go through a couple web certification dialogs
* Typically repeat Ctrl-Space and there's a "downloading..." that never
finishes
Note: Works OK when running on and using jdk1.8 with nb-javac.
Fails with JDK assertion: Assert.checkNonNull(allModules)
(full message log attached)
{code}
java.lang.AssertionError at
jdk.compiler/com.sun.tools.javac.util.Assert.error(Assert.java:155) at
jdk.compiler/com.sun.tools.javac.util.Assert.checkNonNull(Assert.java:62) at
jdk.compiler/com.sun.tools.javac.comp.Modules.allModules(Modules.java:1205) at
jdk.compiler/com.sun.tools.javac.model.JavacElements.getAllModuleElements(JavacElements.java:126)
at
org.netbeans.modules.java.source.ElementUtils.getTypeElementByBinaryName(ElementUtils.java:49)
at
org.netbeans.api.java.source.ElementHandle.getTypeElementByBinaryName(ElementHandle.java:666)
at
org.netbeans.api.java.source.ElementHandle.resolveImpl(ElementHandle.java:163)
at org.netbeans.api.java.source.ElementHandle.resolve(ElementHandle.java:132)
at
org.netbeans.modules.javafx2.editor.completion.impl.InstanceCompleter.(InstanceCompleter.java:54)
{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] [Updated] (NETBEANS-4764) EmptyFXML wizard does not fixup module-info as needed
[
https://issues.apache.org/jira/browse/NETBEANS-4764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ernie Rael updated NETBEANS-4764:
-
Labels: modularization (was: )
> EmptyFXML wizard does not fixup module-info as needed
> -
>
> Key: NETBEANS-4764
> URL: https://issues.apache.org/jira/browse/NETBEANS-4764
> Project: NetBeans
> Issue Type: Bug
> Components: javafx - Project
>Reporter: Ernie Rael
>Priority: Major
> Labels: modularization
>
> To reproduce:
> (note insure JavaFX 2 plugin is active otherwise JavaFX>EmptyFXML is not
> available)
> # File >New Project >Java with Maven >FXML JavaFx Maven Archetype (Gluon)
> >
> # File >New File > other > JavaFX > Empty FXML
> # Next
> # Checkbox Use Java Controllers
> # Put the controller in package "newpackage"
> # Finish
> Notice that the file FXML.java in the editor shows an error
> {code:java}
> Class does not exist: newpackage.FXMLController
> {code}
> Things compile but if you try to use the new controller/fxml there is a
> runtime error.
> The problem is fixed by adding these lines to moduleinfo
> {code:java}
> opens newpackage to javafx.fxml;
> exports newpackage;
> {code}
> This should be done automatically by the wizard.
> Notice that after adding these lines, the editor error indication in the fxml
> file goes away.
--
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-4765) module-info utilities for common usage
[
https://issues.apache.org/jira/browse/NETBEANS-4765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ernie Rael updated NETBEANS-4765:
-
Labels: modularization (was: )
> module-info utilities for common usage
> --
>
> Key: NETBEANS-4765
> URL: https://issues.apache.org/jira/browse/NETBEANS-4765
> Project: NetBeans
> Issue Type: Improvement
> Components: java - Platform
>Reporter: Ernie Rael
>Priority: Major
> Labels: modularization
>
> The only common api I've seen for working with module-info is
> {code:java}
> org.netbeans.api.java.source.SourceUtils{.parseModuleName,.getModuleName*}
> {code}
> There are several other things that need to be done with module-info. For
> example, adding a package for fxml access, or for refactoring when moving an
> exported java class to a different package.
> There are module-info utilities scattered throughout the netbeans codebase.
> For example
> {code:java}
> ./maven/src/org/netbeans/modules/maven/api/ModuleInfoUtils.java
> ./maven/src/org/netbeans/modules/maven/ModuleInfoSupport.java
> {code}
> and there's a pending fix for NETBEANS-4718 which adds a local
> "hasModuleInfo".
> And notice sitting in .../netbeans/java there are 64 files given by
> {code}
> srcgrep -l module-info | grep -E -v '/test/|/build/'
> {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-4696) NetBeans 12.1-beta1 sometimes hangs on open
[ https://issues.apache.org/jira/browse/NETBEANS-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17195481#comment-17195481 ] Ernie Rael commented on NETBEANS-4696: -- The PRs to fix this were merged into master on Sep 9. So the daily builds should have these fixes. It's possible there are observable differences. If there are issues, the sooner the better... The as yet undocumented location of the build artifacts is [https://ci-builds.apache.org/job/Netbeans/job/netbeans-linux] With that starting point # Click "Last Successful Artifacts" or something in the "Build History" list on the left # Then traverse "nbbuild > NetBeans-dev-Netbeans # download netbeans-linux-...-release.zip This should run on windows as well as linux, AFAICT. > NetBeans 12.1-beta1 sometimes hangs on open > --- > > Key: NETBEANS-4696 > URL: https://issues.apache.org/jira/browse/NETBEANS-4696 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance >Affects Versions: 12.1 > Environment: Linux (Debian "Buster") > OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.7+10) >Reporter: Glenn Holmer >Priority: Blocker > Labels: deadlock, pull-requests-available > Attachments: 12.1-vc1-thread-dump-orac.txt, > nb12.1-beta1-thread-dump.png, nb12.1-beta1-thread-dump.txt, > netbeans-12.1-thread-dump.txt > > Time Spent: 1h 10m > Remaining Estimate: 0h > > > NetBeans sometimes hangs on startup; the symptom is a stalled "Opening > Projects" progress bar. I haven't been able to find a repro case, but I'm > attaching a thread dump (from VisualVM) and screen shot. -- 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-4765) module-info utilities for common usage
[
https://issues.apache.org/jira/browse/NETBEANS-4765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17194363#comment-17194363
]
Ernie Rael commented on NETBEANS-4765:
--
I see at least two goals
# Provide common API for new development
# Refactor code to use common API
I guess I was thinking of 1, but since probably the best way to do 1, is first
do 2. As "eliminate the duplicities" points out.
> module-info utilities for common usage
> --
>
> Key: NETBEANS-4765
> URL: https://issues.apache.org/jira/browse/NETBEANS-4765
> Project: NetBeans
> Issue Type: Improvement
> Components: java - Platform
>Reporter: Ernie Rael
>Priority: Major
>
> The only common api I've seen for working with module-info is
> {code:java}
> org.netbeans.api.java.source.SourceUtils{.parseModuleName,.getModuleName*}
> {code}
> There are several other things that need to be done with module-info. For
> example, adding a package for fxml access, or for refactoring when moving an
> exported java class to a different package.
> There are module-info utilities scattered throughout the netbeans codebase.
> For example
> {code:java}
> ./maven/src/org/netbeans/modules/maven/api/ModuleInfoUtils.java
> ./maven/src/org/netbeans/modules/maven/ModuleInfoSupport.java
> {code}
> and there's a pending fix for NETBEANS-4718 which adds a local
> "hasModuleInfo".
> And notice sitting in .../netbeans/java there are 64 files given by
> {code}
> srcgrep -l module-info | grep -E -v '/test/|/build/'
> {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-4792) Opening a javafx project does not enable "JavaFX 2" plugin/feature.
Ernie Rael created NETBEANS-4792: Summary: Opening a javafx project does not enable "JavaFX 2" plugin/feature. Key: NETBEANS-4792 URL: https://issues.apache.org/jira/browse/NETBEANS-4792 Project: NetBeans Issue Type: Bug Components: javafx - Project Reporter: Ernie Rael Some javafx project related menu items, for example "NewFile>JavaFX>..." are not available unless the NetBeans standard "JavaFX 2" plugin is enabled. Shouldn't this be done automatically? Ergonomics? -- 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-4790) refactor move class to new package doesn't update module-info.java
[ https://issues.apache.org/jira/browse/NETBEANS-4790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernie Rael updated NETBEANS-4790: - Description: This requires a java version supporting java modules. This is *not* a javafx only problem, but javafx provides a convenient example. Note that controllers in javafx that are referenced from xxx.fxml files must be export for reflection To recreate * NewProject > JavaWithMaven > FXML JavaFX Maven Archetype (Gluon) * Open module-info.java Observe the package containing the controller is exported to javafx.fxml * PrimaryController.java Refactor>Move to another package (May make App.java's setRoot public) Observe no warning that PrimaryController is no longer acessible and/or that module-info.java has not been updated * Before the move, PrimaryController was available for reflection from javafx.fxml, after the move it is not. A warning and/or checkbox to update module-info.java so the class may still be accessed through reflection seems appropriate [NETBEANS-4765] is loosly related. was: This requires a java version supporting java modules. This is *not* a javafx only problem, but javafx provides a convenient example. Note that controllers in javafx that are referenced from xxx.fxml files must be export for reflection To recreate * NewProject > JavaWithMaven > FXML JavaFX Maven Archetype (Gluon) * Open module-info.java Observe the package containing the controller is exported to javafx.fxml * PrimaryController.java Refactor>Move to another package (May make App.java's setRoot public) Observe no warning that PrimaryController is no longer acessible and/or that module-info.java has not been updated *Before the move, PrimaryController was available for reflection from javafx.fxml, after the move it is not. A warning and/or checkbox to update module-info.java so the class may still be accessed through reflection seems appropriate [NETBEANS-4765] is loosly related. > refactor move class to new package doesn't update module-info.java > -- > > Key: NETBEANS-4790 > URL: https://issues.apache.org/jira/browse/NETBEANS-4790 > Project: NetBeans > Issue Type: Bug > Components: java - Refactoring >Reporter: Ernie Rael >Priority: Major > Labels: modularization > > This requires a java version supporting java modules. This is *not* a javafx > only problem, but javafx provides a convenient example. Note that controllers > in javafx that are referenced from xxx.fxml files must be export for > reflection > To recreate > * NewProject > JavaWithMaven > FXML JavaFX Maven Archetype (Gluon) > * Open module-info.java > Observe the package containing the controller is exported to javafx.fxml > * PrimaryController.java Refactor>Move to another package > (May make App.java's setRoot public) > Observe no warning that PrimaryController is no longer acessible and/or that > module-info.java has not been updated > * Before the move, PrimaryController was available for reflection from > javafx.fxml, after the move it is not. > A warning and/or checkbox to update module-info.java so the class may still > be accessed through reflection seems appropriate > [NETBEANS-4765] is loosly related. -- 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-4791) error badges for xxx.fxml file do not propogate to tabs or project window
Ernie Rael created NETBEANS-4791: Summary: error badges for xxx.fxml file do not propogate to tabs or project window Key: NETBEANS-4791 URL: https://issues.apache.org/jira/browse/NETBEANS-4791 Project: NetBeans Issue Type: Bug Components: javafx - Editor Reporter: Ernie Rael To recreate * NewProject > JavaWithMaven > FXML JavaFX Maven Archetype (Gluon) * Edit primary.fxml (If there are no error badges, create an error. For example change the controller name) * Observe the editor shows an error, neither the tab nor the file in project window shows an error This can be particularly important for finding errors that will show up at runtime, since flaws elsewhere in NetBeans can cause errors in this file when doing seemingly unrelated actions. See NETBEANS-4789, NETBEANS-4790. -- 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-4765) module-info utilities for common usage
[
https://issues.apache.org/jira/browse/NETBEANS-4765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17193904#comment-17193904
]
Ernie Rael commented on NETBEANS-4765:
--
[~jtulach] I guess this is an API issue.
> module-info utilities for common usage
> --
>
> Key: NETBEANS-4765
> URL: https://issues.apache.org/jira/browse/NETBEANS-4765
> Project: NetBeans
> Issue Type: Improvement
> Components: java - Platform
>Reporter: Ernie Rael
>Priority: Major
>
> The only common api I've seen for working with module-info is
> {code:java}
> org.netbeans.api.java.source.SourceUtils{.parseModuleName,.getModuleName*}
> {code}
> There are several other things that need to be done with module-info. For
> example, adding a package for fxml access, or for refactoring when moving an
> exported java class to a different package.
> There are module-info utilities scattered throughout the netbeans codebase.
> For example
> {code:java}
> ./maven/src/org/netbeans/modules/maven/api/ModuleInfoUtils.java
> ./maven/src/org/netbeans/modules/maven/ModuleInfoSupport.java
> {code}
> and there's a pending fix for NETBEANS-4718 which adds a local
> "hasModuleInfo".
> And notice sitting in .../netbeans/java there are 64 files given by
> {code}
> srcgrep -l module-info | grep -E -v '/test/|/build/'
> {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-4790) refactor move class to new package doesn't update module-info.java
[ https://issues.apache.org/jira/browse/NETBEANS-4790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17193903#comment-17193903 ] Ernie Rael commented on NETBEANS-4790: -- This issue only addresses refactor>move. Are there other refactoring issues related to maintaining module-info.java? > refactor move class to new package doesn't update module-info.java > -- > > Key: NETBEANS-4790 > URL: https://issues.apache.org/jira/browse/NETBEANS-4790 > Project: NetBeans > Issue Type: Bug > Components: java - Refactoring >Reporter: Ernie Rael >Priority: Major > Labels: modularization > > This requires a java version supporting java modules. This is *not* a javafx > only problem, but javafx provides a convenient example. Note that controllers > in javafx that are referenced from xxx.fxml files must be export for > reflection > To recreate > * NewProject > JavaWithMaven > FXML JavaFX Maven Archetype (Gluon) > * Open module-info.java > Observe the package containing the controller is exported to javafx.fxml > * PrimaryController.java Refactor>Move to another package > (May make App.java's setRoot public) > Observe no warning that PrimaryController is no longer acessible and/or that > module-info.java has not been updated > *Before the move, PrimaryController was available for reflection from > javafx.fxml, after the move it is not. > A warning and/or checkbox to update module-info.java so the class may still > be accessed through reflection seems appropriate > [NETBEANS-4765] is loosly related. -- 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-4790) refactor move class to new package doesn't update module-info.java
[ https://issues.apache.org/jira/browse/NETBEANS-4790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17193901#comment-17193901 ] Ernie Rael commented on NETBEANS-4790: -- [~jlahoda] any thoughts on how this might be addressed? > refactor move class to new package doesn't update module-info.java > -- > > Key: NETBEANS-4790 > URL: https://issues.apache.org/jira/browse/NETBEANS-4790 > Project: NetBeans > Issue Type: Bug > Components: java - Refactoring >Reporter: Ernie Rael >Priority: Major > Labels: modularization > > This requires a java version supporting java modules. This is *not* a javafx > only problem, but javafx provides a convenient example. Note that controllers > in javafx that are referenced from xxx.fxml files must be export for > reflection > To recreate > * NewProject > JavaWithMaven > FXML JavaFX Maven Archetype (Gluon) > * Open module-info.java > Observe the package containing the controller is exported to javafx.fxml > * PrimaryController.java Refactor>Move to another package > (May make App.java's setRoot public) > Observe no warning that PrimaryController is no longer acessible and/or that > module-info.java has not been updated > *Before the move, PrimaryController was available for reflection from > javafx.fxml, after the move it is not. > A warning and/or checkbox to update module-info.java so the class may still > be accessed through reflection seems appropriate > [NETBEANS-4765] is loosly related. -- 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-4790) refactor move class to new package doesn't update module-info.java
[ https://issues.apache.org/jira/browse/NETBEANS-4790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernie Rael updated NETBEANS-4790: - Description: This requires a java version supporting java modules. This is *not* a javafx only problem, but javafx provides a convenient example. Note that controllers in javafx that are referenced from xxx.fxml files must be export for reflection To recreate * NewProject > JavaWithMaven > FXML JavaFX Maven Archetype (Gluon) * Open module-info.java Observe the package containing the controller is exported to javafx.fxml * PrimaryController.java Refactor>Move to another package (May make App.java's setRoot public) Observe no warning that PrimaryController is no longer acessible and/or that module-info.java has not been updated *Before the move, PrimaryController was available for reflection from javafx.fxml, after the move it is not. A warning and/or checkbox to update module-info.java so the class may still be accessed through reflection seems appropriate [NETBEANS-4765] is loosly related. was: This requires a java version supporting java modules. This is *not* a javafx only problem, but javafx provides a convenient example. Note that controllers in javafx that are referenced from xxx.fxml files must be export for reflection To recreate * NewProject > JavaWithMaven > FXML JavaFX Maven Archetype (Gluon) * Open module-info.java Observe the package containing the controller is exported to javafx.fxml * PrimaryController.java Refactor>Move to another package (May make App.java's setRoot public) Observe no warning that PrimaryController is no longer acessible and/or that module-info.java has not been updated *Before the move, PrimaryController was available for reflection from javafx.fxml, after the move it is not. A warning and/or checkbox to update module-info.java so the class may still be accessed through reflection seems appropriate > refactor move class to new package doesn't update module-info.java > -- > > Key: NETBEANS-4790 > URL: https://issues.apache.org/jira/browse/NETBEANS-4790 > Project: NetBeans > Issue Type: Bug > Components: java - Refactoring >Reporter: Ernie Rael >Priority: Major > Labels: modularization > > This requires a java version supporting java modules. This is *not* a javafx > only problem, but javafx provides a convenient example. Note that controllers > in javafx that are referenced from xxx.fxml files must be export for > reflection > To recreate > * NewProject > JavaWithMaven > FXML JavaFX Maven Archetype (Gluon) > * Open module-info.java > Observe the package containing the controller is exported to javafx.fxml > * PrimaryController.java Refactor>Move to another package > (May make App.java's setRoot public) > Observe no warning that PrimaryController is no longer acessible and/or that > module-info.java has not been updated > *Before the move, PrimaryController was available for reflection from > javafx.fxml, after the move it is not. > A warning and/or checkbox to update module-info.java so the class may still > be accessed through reflection seems appropriate > [NETBEANS-4765] is loosly related. -- 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-4790) refactor move class to new package doesn't update module-info.java
[ https://issues.apache.org/jira/browse/NETBEANS-4790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernie Rael updated NETBEANS-4790: - Description: This requires a java version supporting java modules. This is *not* a javafx only problem, but javafx provides a convenient example. Note that controllers in javafx that are referenced from xxx.fxml files must be export for reflection To recreate * NewProject > JavaWithMaven > FXML JavaFX Maven Archetype (Gluon) * Open module-info.java Observe the package containing the controller is exported to javafx.fxml * PrimaryController.java Refactor>Move to another package (May make App.java's setRoot public) Observe no warning that PrimaryController is no longer acessible and/or that module-info.java has not been updated *Before the move, PrimaryController was available for reflection from javafx.fxml, after the move it is not. A warning and/or checkbox to update module-info.java so the class may still be accessed through reflection seems appropriate was: This requires a java version supporting java modules. This is *not* a javafx only problem, but javafx provides a convenient example. Note that controllers in javafx that are referenced from xxx.fxml files must be export for reflection To recreate * NewProject > JavaWithMaven > FXML JavaFX Maven Archetype (Gluon) * Open module-info.java Observe the package containing the controller is exported to javafx.fxml * PrimaryController.java Refactor>Move to another package (May make App.java's setRoot public) Observe no warning that PrimaryController is no longer acessible and/or that module-info.java has not been updated *Before the move, PrimaryController was available for reflection from javafx.fxml, after the move it is not. A warning and/or checkbox to update module-info.java so the class may still be accessed through reflection seems appropriate > refactor move class to new package doesn't update module-info.java > -- > > Key: NETBEANS-4790 > URL: https://issues.apache.org/jira/browse/NETBEANS-4790 > Project: NetBeans > Issue Type: Bug > Components: java - Refactoring >Reporter: Ernie Rael >Priority: Major > Labels: modularization > > This requires a java version supporting java modules. This is *not* a javafx > only problem, but javafx provides a convenient example. Note that controllers > in javafx that are referenced from xxx.fxml files must be export for > reflection > To recreate > * NewProject > JavaWithMaven > FXML JavaFX Maven Archetype (Gluon) > * Open module-info.java > Observe the package containing the controller is exported to javafx.fxml > * PrimaryController.java Refactor>Move to another package > (May make App.java's setRoot public) > Observe no warning that PrimaryController is no longer acessible and/or that > module-info.java has not been updated > *Before the move, PrimaryController was available for reflection from > javafx.fxml, after the move it is not. > A warning and/or checkbox to update module-info.java so the class may still > be accessed through reflection seems appropriate -- 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-4790) refactor move class to new package doesn't update module-info.java
Ernie Rael created NETBEANS-4790: Summary: refactor move class to new package doesn't update module-info.java Key: NETBEANS-4790 URL: https://issues.apache.org/jira/browse/NETBEANS-4790 Project: NetBeans Issue Type: Bug Components: java - Refactoring Reporter: Ernie Rael This requires a java version supporting java modules. This is *not* a javafx only problem, but javafx provides a convenient example. Note that controllers in javafx that are referenced from xxx.fxml files must be export for reflection To recreate * NewProject > JavaWithMaven > FXML JavaFX Maven Archetype (Gluon) * Open module-info.java Observe the package containing the controller is exported to javafx.fxml * PrimaryController.java Refactor>Move to another package (May make App.java's setRoot public) Observe no warning that PrimaryController is no longer acessible and/or that module-info.java has not been updated *Before the move, PrimaryController was available for reflection from javafx.fxml, after the move it is not. A warning and/or checkbox to update module-info.java so the class may still be accessed through reflection seems appropriate -- 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-4789) fxml controller rename does not update reference in xxx.fxml
[
https://issues.apache.org/jira/browse/NETBEANS-4789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ernie Rael updated NETBEANS-4789:
-
Labels: (was: modular)
> fxml controller rename does not update reference in xxx.fxml
>
>
> Key: NETBEANS-4789
> URL: https://issues.apache.org/jira/browse/NETBEANS-4789
> Project: NetBeans
> Issue Type: Bug
> Components: java - Refactoring, javafx - Project
>Reporter: Ernie Rael
>Priority: Major
>
> To recreate
> * NewProject > JavaWithMaven > FXML JavaFX Maven Archetype (Gluon)
> * Open PrimaryController.java and primary.fxml
> Observe in primary.fxml the reference, note that line is without error
> {code}fx:controller="com.raelity.play.jfx.fxml1.PrimaryController"{code}
> * In PrimaryController.java, Refactor>Rename the class (stay in same package)
> Observe in primary.fxml that the reference is not updated
> (Also notice that the editor now flags that line as an error)
--
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-4789) fxml controller rename does not update reference in xxx.fxml
[
https://issues.apache.org/jira/browse/NETBEANS-4789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ernie Rael updated NETBEANS-4789:
-
Labels: modular (was: )
> fxml controller rename does not update reference in xxx.fxml
>
>
> Key: NETBEANS-4789
> URL: https://issues.apache.org/jira/browse/NETBEANS-4789
> Project: NetBeans
> Issue Type: Bug
> Components: java - Refactoring, javafx - Project
>Reporter: Ernie Rael
>Priority: Major
> Labels: modular
>
> To recreate
> * NewProject > JavaWithMaven > FXML JavaFX Maven Archetype (Gluon)
> * Open PrimaryController.java and primary.fxml
> Observe in primary.fxml the reference, note that line is without error
> {code}fx:controller="com.raelity.play.jfx.fxml1.PrimaryController"{code}
> * In PrimaryController.java, Refactor>Rename the class (stay in same package)
> Observe in primary.fxml that the reference is not updated
> (Also notice that the editor now flags that line as an error)
--
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-4789) fxml controller rename does not update reference in xxx.fxml
[
https://issues.apache.org/jira/browse/NETBEANS-4789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17193881#comment-17193881
]
Ernie Rael commented on NETBEANS-4789:
--
[~jlahoda] Perhaps you have some idea on how this might be addressed?
> fxml controller rename does not update reference in xxx.fxml
>
>
> Key: NETBEANS-4789
> URL: https://issues.apache.org/jira/browse/NETBEANS-4789
> Project: NetBeans
> Issue Type: Bug
> Components: java - Refactoring, javafx - Project
>Reporter: Ernie Rael
>Priority: Major
>
> To recreate
> * NewProject > JavaWithMaven > FXML JavaFX Maven Archetype (Gluon)
> * Open PrimaryController.java and primary.fxml
> Observe in primary.fxml the reference, note that line is without error
> {code}fx:controller="com.raelity.play.jfx.fxml1.PrimaryController"{code}
> * In PrimaryController.java, Refactor>Rename the class (stay in same package)
> Observe in primary.fxml that the reference is not updated
> (Also notice that the editor now flags that line as an error)
--
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-4789) fxml controller rename does not update reference in xxx.fxml
Ernie Rael created NETBEANS-4789:
Summary: fxml controller rename does not update reference in
xxx.fxml
Key: NETBEANS-4789
URL: https://issues.apache.org/jira/browse/NETBEANS-4789
Project: NetBeans
Issue Type: Bug
Components: java - Refactoring, javafx - Project
Reporter: Ernie Rael
To recreate
* NewProject > JavaWithMaven > FXML JavaFX Maven Archetype (Gluon)
* Open PrimaryController.java and primary.fxml
Observe in primary.fxml the reference, note that line is without error
{code}fx:controller="com.raelity.play.jfx.fxml1.PrimaryController"{code}
* In PrimaryController.java, Refactor>Rename the class (stay in same package)
Observe in primary.fxml that the reference is not updated
(Also notice that the editor now flags that line as an error)
--
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-4696) NetBeans 12.1-beta1 sometimes hangs on open
[
https://issues.apache.org/jira/browse/NETBEANS-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17190415#comment-17190415
]
Ernie Rael commented on NETBEANS-4696:
--
I went back and looked at removing the dependency from javascript2.knockout to
projectuiapi.base. I had left in
{code:java}
if (!OpenProjects.getDefault().openProjects().isDone()) {
return null;
}
{code}
I took that out (it was before QuerySupport stuff) and it made no difference.
The code is now
{code:java}
KnockoutIndex index = INDEXES.get(project);
if (index == null) {
Collection sourceRoots = QuerySupport.findRoots(project,
null /* all source roots */,
Collections.emptyList(),
Collections.emptyList());
QuerySupport querrySupport = QuerySupport.forRoots(
KnockoutIndexer.Factory.NAME,
KnockoutIndexer.Factory.VERSION,
sourceRoots.toArray(new FileObject[]{}));
index = new KnockoutIndex(querrySupport);
if (sourceRoots.size() > 0) {
INDEXES.put(project, index);
}
}
return index;
{code}
With the early return left out, until the project is open, sourceRoots.size()
is 0 until the open completes. Updating the PR to remove the dependency.
> NetBeans 12.1-beta1 sometimes hangs on open
> ---
>
> Key: NETBEANS-4696
> URL: https://issues.apache.org/jira/browse/NETBEANS-4696
> Project: NetBeans
> Issue Type: Bug
> Components: ide - Performance
>Affects Versions: 12.1
> Environment: Linux (Debian "Buster")
> OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.7+10)
>Reporter: Glenn Holmer
>Priority: Blocker
> Labels: deadlock, pull-requests-available
> Attachments: 12.1-vc1-thread-dump-orac.txt,
> nb12.1-beta1-thread-dump.png, nb12.1-beta1-thread-dump.txt,
> netbeans-12.1-thread-dump.txt
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
>
> NetBeans sometimes hangs on startup; the symptom is a stalled "Opening
> Projects" progress bar. I haven't been able to find a repro case, but I'm
> attaching a thread dump (from VisualVM) and screen shot.
--
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-4696) NetBeans 12.1-beta1 sometimes hangs on open
[ https://issues.apache.org/jira/browse/NETBEANS-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17190368#comment-17190368 ] Ernie Rael commented on NETBEANS-4696: -- There are two pull requests available. # One seems very safe, don't block to get module name. # The other has the html parser's indexer returning null if project opening is not complete. Simple preliminary tests don't show a problem. But the 2nd PR should be carefully considered by someone who has some sense of the html parsing code. Note that either change avoids the deadlock (at least that's the idea). > NetBeans 12.1-beta1 sometimes hangs on open > --- > > Key: NETBEANS-4696 > URL: https://issues.apache.org/jira/browse/NETBEANS-4696 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance >Affects Versions: 12.1 > Environment: Linux (Debian "Buster") > OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.7+10) >Reporter: Glenn Holmer >Priority: Blocker > Labels: deadlock, pull-requests-available > Attachments: 12.1-vc1-thread-dump-orac.txt, > nb12.1-beta1-thread-dump.png, nb12.1-beta1-thread-dump.txt, > netbeans-12.1-thread-dump.txt > > Time Spent: 20m > Remaining Estimate: 0h > > > NetBeans sometimes hangs on startup; the symptom is a stalled "Opening > Projects" progress bar. I haven't been able to find a repro case, but I'm > attaching a thread dump (from VisualVM) and screen shot. -- 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-4696) NetBeans 12.1-beta1 sometimes hangs on open
[ https://issues.apache.org/jira/browse/NETBEANS-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernie Rael updated NETBEANS-4696: - Labels: deadlock pull-requests-available (was: deadlock) > NetBeans 12.1-beta1 sometimes hangs on open > --- > > Key: NETBEANS-4696 > URL: https://issues.apache.org/jira/browse/NETBEANS-4696 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance >Affects Versions: 12.1 > Environment: Linux (Debian "Buster") > OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.7+10) >Reporter: Glenn Holmer >Priority: Blocker > Labels: deadlock, pull-requests-available > Attachments: 12.1-vc1-thread-dump-orac.txt, > nb12.1-beta1-thread-dump.png, nb12.1-beta1-thread-dump.txt, > netbeans-12.1-thread-dump.txt > > Time Spent: 20m > Remaining Estimate: 0h > > > NetBeans sometimes hangs on startup; the symptom is a stalled "Opening > Projects" progress bar. I haven't been able to find a repro case, but I'm > attaching a thread dump (from VisualVM) and screen shot. -- 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-4696) NetBeans 12.1-beta1 sometimes hangs on open
[ https://issues.apache.org/jira/browse/NETBEANS-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17190267#comment-17190267 ] Ernie Rael commented on NETBEANS-4696: -- [~geertjan] From what I can tell from various comments, the code that is in the knockout area has become integral to Netbeans' html infrastructure. (isn't evolution wonderful?). > NetBeans 12.1-beta1 sometimes hangs on open > --- > > Key: NETBEANS-4696 > URL: https://issues.apache.org/jira/browse/NETBEANS-4696 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance >Affects Versions: 12.1 > Environment: Linux (Debian "Buster") > OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.7+10) >Reporter: Glenn Holmer >Priority: Blocker > Labels: deadlock > Attachments: 12.1-vc1-thread-dump-orac.txt, > nb12.1-beta1-thread-dump.png, nb12.1-beta1-thread-dump.txt, > netbeans-12.1-thread-dump.txt > > > > NetBeans sometimes hangs on startup; the symptom is a stalled "Opening > Projects" progress bar. I haven't been able to find a repro case, but I'm > attaching a thread dump (from VisualVM) and screen shot. -- 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-4696) NetBeans 12.1-beta1 sometimes hangs on open
[ https://issues.apache.org/jira/browse/NETBEANS-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17190241#comment-17190241 ] Ernie Rael commented on NETBEANS-4696: -- Actually, I don't need to reproduce the deadlock. Given the changes I'm proposing, there won't be a deadlock (famous last words, but in defense the changes remove *both* contributors to the deadlock). I'm just trying to insure that I haven't broken anything (or at least not too much :-) ). I need to do some things in a project that exercise these indexes. I'm guessing that they are used for navigation, like goto definition, findusages, ... as they would be in a normal java project. But I have no experience in the dynamic html area, so I don't know what behavior is expected. > NetBeans 12.1-beta1 sometimes hangs on open > --- > > Key: NETBEANS-4696 > URL: https://issues.apache.org/jira/browse/NETBEANS-4696 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance >Affects Versions: 12.1 > Environment: Linux (Debian "Buster") > OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.7+10) >Reporter: Glenn Holmer >Priority: Blocker > Labels: deadlock > Attachments: 12.1-vc1-thread-dump-orac.txt, > nb12.1-beta1-thread-dump.png, nb12.1-beta1-thread-dump.txt, > netbeans-12.1-thread-dump.txt > > > > NetBeans sometimes hangs on startup; the symptom is a stalled "Opening > Projects" progress bar. I haven't been able to find a repro case, but I'm > attaching a thread dump (from VisualVM) and screen shot. -- 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-4696) NetBeans 12.1-beta1 sometimes hangs on open
[ https://issues.apache.org/jira/browse/NETBEANS-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17190212#comment-17190212 ] Ernie Rael commented on NETBEANS-4696: -- I need a project xhtml/javascript (I don't know what) that makes use of the "knockout indexes". Does this type of project have the regular navigation stuff like goto definition? Do anyone have, or can someone tell me how to build, a project I can use to verify the fixes for deadlock? > NetBeans 12.1-beta1 sometimes hangs on open > --- > > Key: NETBEANS-4696 > URL: https://issues.apache.org/jira/browse/NETBEANS-4696 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance >Affects Versions: 12.1 > Environment: Linux (Debian "Buster") > OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.7+10) >Reporter: Glenn Holmer >Priority: Blocker > Labels: deadlock > Attachments: 12.1-vc1-thread-dump-orac.txt, > nb12.1-beta1-thread-dump.png, nb12.1-beta1-thread-dump.txt, > netbeans-12.1-thread-dump.txt > > > > NetBeans sometimes hangs on startup; the symptom is a stalled "Opening > Projects" progress bar. I haven't been able to find a repro case, but I'm > attaching a thread dump (from VisualVM) and screen shot. -- 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-4696) NetBeans 12.1-beta1 sometimes hangs on open
[ https://issues.apache.org/jira/browse/NETBEANS-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17189793#comment-17189793 ] Ernie Rael commented on NETBEANS-4696: -- Added a bunch of project that need to be opened and got a breakpoint at "return null", so the above seems to detect open not complete. But I never got any other breakpoint in this method. I suspect/hope that my nearly empty boilerplate xhtml file doesn't have enough stuff in it; so this method never got called again. I don't know what the indexes are used with/for. Can someone suggest a way to test that things are working OK with this change. > NetBeans 12.1-beta1 sometimes hangs on open > --- > > Key: NETBEANS-4696 > URL: https://issues.apache.org/jira/browse/NETBEANS-4696 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance >Affects Versions: 12.1 > Environment: Linux (Debian "Buster") > OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.7+10) >Reporter: Glenn Holmer >Priority: Blocker > Labels: deadlock > Attachments: 12.1-vc1-thread-dump-orac.txt, > nb12.1-beta1-thread-dump.png, nb12.1-beta1-thread-dump.txt, > netbeans-12.1-thread-dump.txt > > > > NetBeans sometimes hangs on startup; the symptom is a stalled "Opening > Projects" progress bar. I haven't been able to find a repro case, but I'm > attaching a thread dump (from VisualVM) and screen shot. -- 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-4696) NetBeans 12.1-beta1 sometimes hangs on open
[
https://issues.apache.org/jira/browse/NETBEANS-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17189716#comment-17189716
]
Ernie Rael commented on NETBEANS-4696:
--
For the knockout side I've got
{code}
$ hg diff
diff --git
a/webcommon/javascript2.knockout/src/org/netbeans/modules/javascript2/knockout/index/KnockoutIndex.java
b/webcommon/javascript2.knockout/src/org/netbeans/modules/javascript2/knockout/index/KnockoutIndex.java
---
a/webcommon/javascript2.knockout/src/org/netbeans/modules/javascript2/knockout/index/KnockoutIndex.java
+++
b/webcommon/javascript2.knockout/src/org/netbeans/modules/javascript2/knockout/index/KnockoutIndex.java
@@ -45,7 +45,6 @@
private static final Map INDEXES = new
WeakHashMap<>();
private final QuerySupport querySupport;
-private static boolean areProjectsOpen = false;
public static KnockoutIndex get(Project project) throws IOException {
if (project == null) {
@@ -54,16 +53,8 @@
synchronized (INDEXES) {
KnockoutIndex index = INDEXES.get(project);
if (index == null) {
-if (!areProjectsOpen) {
-try {
-// just be sure that the projects are open
-OpenProjects.getDefault().openProjects().get();
-} catch (InterruptedException | ExecutionException ex) {
-Exceptions.printStackTrace(ex);
-} finally {
-areProjectsOpen = true;
-}
-}
+if(!OpenProjects.getDefault().openProjects().isDone())
+return null;
Collection sourceRoots =
QuerySupport.findRoots(project,
null /* all source roots */,
Collections.emptyList(),
{code}
FindUsage shows that all callers of "...get(project)" check for a null return.
Looking at the call sites, it doesn't seem like anything is cached; it seems
like it should come back next time it wants info. But I couldn't get a
breakpoint at the "return null", so who knows.
Comments? Just try it?
> NetBeans 12.1-beta1 sometimes hangs on open
> ---
>
> Key: NETBEANS-4696
> URL: https://issues.apache.org/jira/browse/NETBEANS-4696
> Project: NetBeans
> Issue Type: Bug
> Components: ide - Performance
>Affects Versions: 12.1
> Environment: Linux (Debian "Buster")
> OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.7+10)
>Reporter: Glenn Holmer
>Priority: Blocker
> Labels: deadlock
> Attachments: 12.1-vc1-thread-dump-orac.txt,
> nb12.1-beta1-thread-dump.png, nb12.1-beta1-thread-dump.txt,
> netbeans-12.1-thread-dump.txt
>
>
>
> NetBeans sometimes hangs on startup; the symptom is a stalled "Opening
> Projects" progress bar. I haven't been able to find a repro case, but I'm
> attaching a thread dump (from VisualVM) and screen shot.
--
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-4696) NetBeans 12.1-beta1 sometimes hangs on open
[
https://issues.apache.org/jira/browse/NETBEANS-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17189673#comment-17189673
]
Ernie Rael commented on NETBEANS-4696:
--
For the problematic
{code:java}
private static String getModuleName(@NonNull final FileObject moduleInfo)
{code}
in UnitTestsCompilerOptionsQueryImpl.java, replaced the rather expensive method
with the single line
{code:java}
return SourceUtils.parseModuleName(moduleInfo);
{code}
and the debugger shows the same result (in the case I tried)
I couldn't get
{code:java}
SourceUtils.getModuleName(moduleInfo.getParent().toURL())
{code}
to work. Then I noticed that the javadoc asks for a binary root; not sure what
that means.
Unless there's an objection, I'll file a pull request with this change tomorrow.
I'll take a look at KOHtmlExtension and try to come up with something.
[~gholmer], [~hink084] I couldn't get a failure, to verify the fix. I added an
xhtml file and a maven test to get a breakpoint in the troubling method. But no
hang. If this gets pulled into master, maybe you can check a daily build...
> NetBeans 12.1-beta1 sometimes hangs on open
> ---
>
> Key: NETBEANS-4696
> URL: https://issues.apache.org/jira/browse/NETBEANS-4696
> Project: NetBeans
> Issue Type: Bug
> Components: ide - Performance
>Affects Versions: 12.1
> Environment: Linux (Debian "Buster")
> OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.7+10)
>Reporter: Glenn Holmer
>Priority: Blocker
> Labels: deadlock
> Attachments: 12.1-vc1-thread-dump-orac.txt,
> nb12.1-beta1-thread-dump.png, nb12.1-beta1-thread-dump.txt,
> netbeans-12.1-thread-dump.txt
>
>
>
> NetBeans sometimes hangs on startup; the symptom is a stalled "Opening
> Projects" progress bar. I haven't been able to find a repro case, but I'm
> attaching a thread dump (from VisualVM) and screen shot.
--
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-4696) NetBeans 12.1-beta1 sometimes hangs on open
[ https://issues.apache.org/jira/browse/NETBEANS-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17189570#comment-17189570 ] Ernie Rael commented on NETBEANS-4696: -- Just a note. I've recently ran into some issues requiring module-info manipulation. I've filed NETBEANS-4765 which ask for a common public api for working with module-info and mentions some areas where a common api for module-info stuff could be used. > NetBeans 12.1-beta1 sometimes hangs on open > --- > > Key: NETBEANS-4696 > URL: https://issues.apache.org/jira/browse/NETBEANS-4696 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance >Affects Versions: 12.1 > Environment: Linux (Debian "Buster") > OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.7+10) >Reporter: Glenn Holmer >Priority: Blocker > Labels: deadlock > Attachments: 12.1-vc1-thread-dump-orac.txt, > nb12.1-beta1-thread-dump.png, nb12.1-beta1-thread-dump.txt, > netbeans-12.1-thread-dump.txt > > > > NetBeans sometimes hangs on startup; the symptom is a stalled "Opening > Projects" progress bar. I haven't been able to find a repro case, but I'm > attaching a thread dump (from VisualVM) and screen shot. -- 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-4765) module-info utilities for common usage
[
https://issues.apache.org/jira/browse/NETBEANS-4765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17189566#comment-17189566
]
Ernie Rael commented on NETBEANS-4765:
--
As well as NETBEANS-4718, NETBEANS-4764 which can use such a proposed api.
> module-info utilities for common usage
> --
>
> Key: NETBEANS-4765
> URL: https://issues.apache.org/jira/browse/NETBEANS-4765
> Project: NetBeans
> Issue Type: Improvement
> Components: java - Platform
>Reporter: Ernie Rael
>Priority: Major
>
> The only common api I've seen for working with module-info is
> {code:java}
> org.netbeans.api.java.source.SourceUtils{.parseModuleName,.getModuleName*}
> {code}
> There are several other things that need to be done with module-info. For
> example, adding a package for fxml access, or for refactoring when moving an
> exported java class to a different package.
> There are module-info utilities scattered throughout the netbeans codebase.
> For example
> {code:java}
> ./maven/src/org/netbeans/modules/maven/api/ModuleInfoUtils.java
> ./maven/src/org/netbeans/modules/maven/ModuleInfoSupport.java
> {code}
> and there's a pending fix for NETBEANS-4718 which adds a local
> "hasModuleInfo".
> And notice sitting in .../netbeans/java there are 64 files given by
> {code}
> srcgrep -l module-info | grep -E -v '/test/|/build/'
> {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] [Updated] (NETBEANS-4765) module-info utilities for common usage
[
https://issues.apache.org/jira/browse/NETBEANS-4765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ernie Rael updated NETBEANS-4765:
-
Description:
The only common api I've seen for working with module-info is
{code:java}
org.netbeans.api.java.source.SourceUtils{.parseModuleName,.getModuleName*}
{code}
There are several other things that need to be done with module-info. For
example, adding a package for fxml access, or for refactoring when moving an
exported java class to a different package.
There are module-info utilities scattered throughout the netbeans codebase. For
example
{code:java}
./maven/src/org/netbeans/modules/maven/api/ModuleInfoUtils.java
./maven/src/org/netbeans/modules/maven/ModuleInfoSupport.java
{code}
and there's a pending fix for NETBEANS-4718 which adds a local "hasModuleInfo".
And notice sitting in .../netbeans/java there are 64 files given by
{code}
srcgrep -l module-info | grep -E -v '/test/|/build/'
{code}
was:
The only common api I've seen for working with module-info is
{code:java}
org.netbeans.api.java.source.SourceUtils{.parseModuleName,.getModuleName*}
{code}
There are several other things that need to be done with module-info. For
example, adding a package for fxml access, or for refactoring when moving an
exported java class to a different package.
There are module-info utilities scattered throughout the netbeans codebase. For
example
{code:java}
./maven/src/org/netbeans/modules/maven/api/ModuleInfoUtils.java
./maven/src/org/netbeans/modules/maven/ModuleInfoSupport.java
{code}
and there's a pending fix for NETBEANS-4591 which adds a local "hasModuleInfo".
And notice sitting in .../netbeans/java there are 64 files given by
{code}
srcgrep -l module-info | grep -E -v '/test/|/build/'
{code}
> module-info utilities for common usage
> --
>
> Key: NETBEANS-4765
> URL: https://issues.apache.org/jira/browse/NETBEANS-4765
> Project: NetBeans
> Issue Type: Improvement
> Components: java - Platform
>Reporter: Ernie Rael
>Priority: Major
>
> The only common api I've seen for working with module-info is
> {code:java}
> org.netbeans.api.java.source.SourceUtils{.parseModuleName,.getModuleName*}
> {code}
> There are several other things that need to be done with module-info. For
> example, adding a package for fxml access, or for refactoring when moving an
> exported java class to a different package.
> There are module-info utilities scattered throughout the netbeans codebase.
> For example
> {code:java}
> ./maven/src/org/netbeans/modules/maven/api/ModuleInfoUtils.java
> ./maven/src/org/netbeans/modules/maven/ModuleInfoSupport.java
> {code}
> and there's a pending fix for NETBEANS-4718 which adds a local
> "hasModuleInfo".
> And notice sitting in .../netbeans/java there are 64 files given by
> {code}
> srcgrep -l module-info | grep -E -v '/test/|/build/'
> {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-4765) module-info utilities for common usage
Ernie Rael created NETBEANS-4765:
Summary: module-info utilities for common usage
Key: NETBEANS-4765
URL: https://issues.apache.org/jira/browse/NETBEANS-4765
Project: NetBeans
Issue Type: Improvement
Components: java - Platform
Reporter: Ernie Rael
The only common api I've seen for working with module-info is
{code:java}
org.netbeans.api.java.source.SourceUtils{.parseModuleName,.getModuleName*}
{code}
There are several other things that need to be done with module-info. For
example, adding a package for fxml access, or for refactoring when moving an
exported java class to a different package.
There are module-info utilities scattered throughout the netbeans codebase. For
example
{code:java}
./maven/src/org/netbeans/modules/maven/api/ModuleInfoUtils.java
./maven/src/org/netbeans/modules/maven/ModuleInfoSupport.java
{code}
and there's a pending fix for NETBEANS-4591 which adds a local "hasModuleInfo".
And notice sitting in .../netbeans/java there are 64 files given by
{code}
srcgrep -l module-info | grep -E -v '/test/|/build/'
{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-4764) EmptyFXML wizard does not fixup module-info as needed
[
https://issues.apache.org/jira/browse/NETBEANS-4764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17189368#comment-17189368
]
Ernie Rael commented on NETBEANS-4764:
--
FYI, this issue came up when dealing with NETBEANS-4718
That issue was also related to module-info in that you can not put java files
in the default package.
> EmptyFXML wizard does not fixup module-info as needed
> -
>
> Key: NETBEANS-4764
> URL: https://issues.apache.org/jira/browse/NETBEANS-4764
> Project: NetBeans
> Issue Type: Bug
> Components: javafx - Project
>Reporter: Ernie Rael
>Priority: Major
>
> To reproduce:
> (note insure JavaFX 2 plugin is active otherwise JavaFX>EmptyFXML is not
> available)
> # File >New Project >Java with Maven >FXML JavaFx Maven Archetype (Gluon)
> >
> # File >New File > other > JavaFX > Empty FXML
> # Next
> # Checkbox Use Java Controllers
> # Put the controller in package "newpackage"
> # Finish
> Notice that the file FXML.java in the editor shows an error
> {code:java}
> Class does not exist: newpackage.FXMLController
> {code}
> Things compile but if you try to use the new controller/fxml there is a
> runtime error.
> The problem is fixed by adding these lines to moduleinfo
> {code:java}
> opens newpackage to javafx.fxml;
> exports newpackage;
> {code}
> This should be done automatically by the wizard.
> Notice that after adding these lines, the editor error indication in the fxml
> file goes away.
--
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-4764) EmptyFXML wizard does not fixup module-info as needed
Ernie Rael created NETBEANS-4764:
Summary: EmptyFXML wizard does not fixup module-info as needed
Key: NETBEANS-4764
URL: https://issues.apache.org/jira/browse/NETBEANS-4764
Project: NetBeans
Issue Type: Bug
Components: javafx - Project
Reporter: Ernie Rael
To reproduce:
(note insure JavaFX 2 plugin is active otherwise JavaFX>EmptyFXML is not
available)
# File >New Project >Java with Maven >FXML JavaFx Maven Archetype (Gluon) >
# File >New File > other > JavaFX > Empty FXML
# Next
# Checkbox Use Java Controllers
# Put the controller in package "newpackage"
# Finish
Notice that the file FXML.java in the editor shows an error
{code:java}
Class does not exist: newpackage.FXMLController
{code}
Things compile but if you try to use the new controller/fxml there is a runtime
error.
The problem is fixed by adding these lines to moduleinfo
{code:java}
opens newpackage to javafx.fxml;
exports newpackage;
{code}
This should be done automatically by the wizard.
Notice that after adding these lines, the editor error indication in the fxml
file goes away.
--
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-4696) NetBeans 12.1-beta1 sometimes hangs on open
[ https://issues.apache.org/jira/browse/NETBEANS-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernie Rael updated NETBEANS-4696: - Labels: deadlock (was: ) > NetBeans 12.1-beta1 sometimes hangs on open > --- > > Key: NETBEANS-4696 > URL: https://issues.apache.org/jira/browse/NETBEANS-4696 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance >Affects Versions: 12.1 > Environment: Linux (Debian "Buster") > OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.7+10) >Reporter: Glenn Holmer >Priority: Major > Labels: deadlock > Attachments: 12.1-vc1-thread-dump-orac.txt, > nb12.1-beta1-thread-dump.png, nb12.1-beta1-thread-dump.txt, > netbeans-12.1-thread-dump.txt > > > > NetBeans sometimes hangs on startup; the symptom is a stalled "Opening > Projects" progress bar. I haven't been able to find a repro case, but I'm > attaching a thread dump (from VisualVM) and screen shot. -- 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-4696) NetBeans 12.1-beta1 sometimes hangs on open
[ https://issues.apache.org/jira/browse/NETBEANS-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernie Rael updated NETBEANS-4696: - Priority: Blocker (was: Major) > NetBeans 12.1-beta1 sometimes hangs on open > --- > > Key: NETBEANS-4696 > URL: https://issues.apache.org/jira/browse/NETBEANS-4696 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance >Affects Versions: 12.1 > Environment: Linux (Debian "Buster") > OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.7+10) >Reporter: Glenn Holmer >Priority: Blocker > Labels: deadlock > Attachments: 12.1-vc1-thread-dump-orac.txt, > nb12.1-beta1-thread-dump.png, nb12.1-beta1-thread-dump.txt, > netbeans-12.1-thread-dump.txt > > > > NetBeans sometimes hangs on startup; the symptom is a stalled "Opening > Projects" progress bar. I haven't been able to find a repro case, but I'm > attaching a thread dump (from VisualVM) and screen shot. -- 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-4696) NetBeans 12.1-beta1 sometimes hangs on open
[
https://issues.apache.org/jira/browse/NETBEANS-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17189113#comment-17189113
]
Ernie Rael commented on NETBEANS-4696:
--
[~tzezula] I came across
{code:java}
org.netbeans.api.java.source.SourceUtils{.parseModuleName,.getModuleName*}
{code}
I guess these are the module name parsing utilities to which you are referring?
> NetBeans 12.1-beta1 sometimes hangs on open
> ---
>
> Key: NETBEANS-4696
> URL: https://issues.apache.org/jira/browse/NETBEANS-4696
> Project: NetBeans
> Issue Type: Bug
> Components: ide - Performance
>Affects Versions: 12.1
> Environment: Linux (Debian "Buster")
> OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.7+10)
>Reporter: Glenn Holmer
>Priority: Major
> Attachments: 12.1-vc1-thread-dump-orac.txt,
> nb12.1-beta1-thread-dump.png, nb12.1-beta1-thread-dump.txt,
> netbeans-12.1-thread-dump.txt
>
>
>
> NetBeans sometimes hangs on startup; the symptom is a stalled "Opening
> Projects" progress bar. I haven't been able to find a repro case, but I'm
> attaching a thread dump (from VisualVM) and screen shot.
--
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-4696) NetBeans 12.1-beta1 sometimes hangs on open
[
https://issues.apache.org/jira/browse/NETBEANS-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17188841#comment-17188841
]
Ernie Rael commented on NETBEANS-4696:
--
Here's the deadlock, note that parsing.api.ParserManager.parse is one at a time
A task that's parsing is waiting for projects to finish opening.
Project opener is waiting to parse.
The maven stuff from ProjectOpener looks pretty suspicious, but IDK?
If it only happens with the html stuff, then maybe the rule is that
a parser isn't supposed to wait for the ProjectOpener.
=== a parsing task
{code}
Some Random Task does parsing, invokes
at org.netbeans.modules.parsing.api.ParserManager.parse
(ParserManager.java:81)
and then does
at org.netbeans.modules.html.editor.api.gsf.HtmlParserResult.root
(HtmlParserResult.java:119)
which ends up doing
at org.netbeans.modules.project.ui.OpenProjectList$LoadOpenProjects.get
(OpenProjectList.java:576)
and this OpenProjectList$LoadOpenProjects.get() wait for opening to complete
{code}
=== "Load Open Projects"
{code}
at org.netbeans.spi.java.project.support.CompilerOptionsQueryMerger
$CompilerOptionsQueryImpl$ResultImpl.lambda$checkProviders$4
(CompilerOptionsQueryMerger.java:184)
goes into some maven specific code
at org.netbeans.modules.maven.queries.UnitTestsCompilerOptionsQueryImpl
$ResultImpl.getArguments
(UnitTestsCompilerOptionsQueryImpl.java:155)
which ends up at
at org.netbeans.modules.maven.queries.UnitTestsCompilerOptionsQueryImpl
$ResultImpl.getModuleName
(UnitTestsCompilerOptionsQueryImpl.java:289)
and then
at org.netbeans.modules.parsing.api.ParserManager.parse
(ParserManager.java:81)
{code}
> NetBeans 12.1-beta1 sometimes hangs on open
> ---
>
> Key: NETBEANS-4696
> URL: https://issues.apache.org/jira/browse/NETBEANS-4696
> Project: NetBeans
> Issue Type: Bug
> Components: ide - Performance
>Affects Versions: 12.1
> Environment: Linux (Debian "Buster")
> OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.7+10)
>Reporter: Glenn Holmer
>Priority: Major
> Attachments: 12.1-vc1-thread-dump-orac.txt,
> nb12.1-beta1-thread-dump.png, nb12.1-beta1-thread-dump.txt,
> netbeans-12.1-thread-dump.txt
>
>
>
> NetBeans sometimes hangs on startup; the symptom is a stalled "Opening
> Projects" progress bar. I haven't been able to find a repro case, but I'm
> attaching a thread dump (from VisualVM) and screen shot.
--
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-4696) NetBeans 12.1-beta1 sometimes hangs on open
[ https://issues.apache.org/jira/browse/NETBEANS-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernie Rael updated NETBEANS-4696: - Description: NetBeans sometimes hangs on startup; the symptom is a stalled "Opening Projects" progress bar. I haven't been able to find a repro case, but I'm attaching a thread dump (from VisualVM) and screen shot. was:NetBeans sometimes hangs on startup; the symptom is a stalled "Opening Projects" progress bar. I haven't been able to find a repro case, but I'm attaching a thread dump (from VisualVM) and screen shot. > NetBeans 12.1-beta1 sometimes hangs on open > --- > > Key: NETBEANS-4696 > URL: https://issues.apache.org/jira/browse/NETBEANS-4696 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance >Affects Versions: 12.1 > Environment: Linux (Debian "Buster") > OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.7+10) >Reporter: Glenn Holmer >Priority: Major > Attachments: 12.1-vc1-thread-dump-orac.txt, > nb12.1-beta1-thread-dump.png, nb12.1-beta1-thread-dump.txt, > netbeans-12.1-thread-dump.txt > > > > NetBeans sometimes hangs on startup; the symptom is a stalled "Opening > Projects" progress bar. I haven't been able to find a repro case, but I'm > attaching a thread dump (from VisualVM) and screen shot. -- 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-4696) NetBeans 12.1-beta1 sometimes hangs on open
[ https://issues.apache.org/jira/browse/NETBEANS-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17187411#comment-17187411 ] Ernie Rael edited comment on NETBEANS-4696 at 8/31/20, 3:44 AM: My guess is wrong. The syncronizer is part of get(). I wonder if ...OpenProjects.get() should use the timeout method. It might not be a fix, but it could be a workaround. I don't know any of this code at all. Now that it/something can be pinpointed in the html code, maybe another ping of dev? was (Author: errael): My guess is wrong. The syncronizer is part of get(). I wonder if ...OpenProjects.get() should use the timeout method. It might not be a fix, but it could be a workaround. > NetBeans 12.1-beta1 sometimes hangs on open > --- > > Key: NETBEANS-4696 > URL: https://issues.apache.org/jira/browse/NETBEANS-4696 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance >Affects Versions: 12.1 > Environment: Linux (Debian "Buster") > OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.7+10) >Reporter: Glenn Holmer >Priority: Major > Attachments: 12.1-vc1-thread-dump-orac.txt, > nb12.1-beta1-thread-dump.png, nb12.1-beta1-thread-dump.txt, > netbeans-12.1-thread-dump.txt > > > NetBeans sometimes hangs on startup; the symptom is a stalled "Opening > Projects" progress bar. I haven't been able to find a repro case, but I'm > attaching a thread dump (from VisualVM) and screen shot. -- 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-4696) NetBeans 12.1-beta1 sometimes hangs on open
[ https://issues.apache.org/jira/browse/NETBEANS-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17187411#comment-17187411 ] Ernie Rael edited comment on NETBEANS-4696 at 8/31/20, 3:40 AM: My guess is wrong. The syncronizer is part of get(). I wonder if ...OpenProjects.get() should use the timeout method. It might not be a fix, but it could be a workaround. was (Author: errael): My guess is wrong. The syncronizer is part of get(). > NetBeans 12.1-beta1 sometimes hangs on open > --- > > Key: NETBEANS-4696 > URL: https://issues.apache.org/jira/browse/NETBEANS-4696 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance >Affects Versions: 12.1 > Environment: Linux (Debian "Buster") > OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.7+10) >Reporter: Glenn Holmer >Priority: Major > Attachments: 12.1-vc1-thread-dump-orac.txt, > nb12.1-beta1-thread-dump.png, nb12.1-beta1-thread-dump.txt, > netbeans-12.1-thread-dump.txt > > > NetBeans sometimes hangs on startup; the symptom is a stalled "Opening > Projects" progress bar. I haven't been able to find a repro case, but I'm > attaching a thread dump (from VisualVM) and screen shot. -- 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-4696) NetBeans 12.1-beta1 sometimes hangs on open
[ https://issues.apache.org/jira/browse/NETBEANS-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17187411#comment-17187411 ] Ernie Rael commented on NETBEANS-4696: -- My guess is wrong. The syncronizer is part of get(). > NetBeans 12.1-beta1 sometimes hangs on open > --- > > Key: NETBEANS-4696 > URL: https://issues.apache.org/jira/browse/NETBEANS-4696 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance >Affects Versions: 12.1 > Environment: Linux (Debian "Buster") > OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.7+10) >Reporter: Glenn Holmer >Priority: Major > Attachments: 12.1-vc1-thread-dump-orac.txt, > nb12.1-beta1-thread-dump.png, nb12.1-beta1-thread-dump.txt, > netbeans-12.1-thread-dump.txt > > > NetBeans sometimes hangs on startup; the symptom is a stalled "Opening > Projects" progress bar. I haven't been able to find a repro case, but I'm > attaching a thread dump (from VisualVM) and screen shot. -- 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-4696) NetBeans 12.1-beta1 sometimes hangs on open
[ https://issues.apache.org/jira/browse/NETBEANS-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17187406#comment-17187406 ] Ernie Rael commented on NETBEANS-4696: -- BTW, this matches Jeremy's finding that html files are needed to bring about the failure condition. > NetBeans 12.1-beta1 sometimes hangs on open > --- > > Key: NETBEANS-4696 > URL: https://issues.apache.org/jira/browse/NETBEANS-4696 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance >Affects Versions: 12.1 > Environment: Linux (Debian "Buster") > OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.7+10) >Reporter: Glenn Holmer >Priority: Major > Attachments: 12.1-vc1-thread-dump-orac.txt, > nb12.1-beta1-thread-dump.png, nb12.1-beta1-thread-dump.txt, > netbeans-12.1-thread-dump.txt > > > NetBeans sometimes hangs on startup; the symptom is a stalled "Opening > Projects" progress bar. I haven't been able to find a repro case, but I'm > attaching a thread dump (from VisualVM) and screen shot. -- 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-4696) NetBeans 12.1-beta1 sometimes hangs on open
[
https://issues.apache.org/jira/browse/NETBEANS-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17187404#comment-17187404
]
Ernie Rael commented on NETBEANS-4696:
--
All three thread dumps have this signature.
"Load Open Projects" is parking waiting for "XXX". And some other task is
trying to get html results and in trying to get these results does
"OpenProjectList$LoadOpenProjects.get()".
Some possibilities are that
* your not suppose to get the open projects while there being opened, your
supposed to wait
* your not supposed to hold the synchronizer when you call into
openProjects.get()
My guess is the second
{code}
"Load Open Projects" #59 daemon prio=1 os_prio=0 cpu=684.74ms elapsed=136.09s
tid=0x7f833c932000 nid=0x5831 waiting on condition [0x7f82c1bf4000]
java.lang.Thread.State: WAITING (parking)
at jdk.internal.misc.Unsafe.park(java.base@11.0.8/Native Method)
- parking to wait for <0x00070ab1db30> (a
java.util.concurrent.locks.ReentrantLock$FairSync)
{code}
And some other task (the specific task varies) is getting parsing results of an
html file. The stack of this task always ends with
{code}
"Editor Parsing Loop (12.1-cade25887c5450e4595fa59e616daee4d2520ee0)" #16
daemon prio=1 os_prio=0 cpu=504.56ms elapsed=145.75s tid=0x7f83d87a8000
nid=0x57f3 in Object.wait() [0x7f838991d000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(java.base@11.0.8/Native Method)
- waiting on
at java.lang.Object.wait(java.base@11.0.8/Object.java:328)
at org.openide.util.Task.waitFinished(Task.java:110)
- waiting to re-lock in wait() <0x0007072bf790> (a
org.openide.util.RequestProcessor$Task)
at
org.openide.util.RequestProcessor$Task.waitFinished(RequestProcessor.java:1672)
at
org.netbeans.modules.project.ui.OpenProjectList$LoadOpenProjects.get(OpenProjectList.java:576)
at
org.netbeans.modules.project.ui.OpenProjectList$LoadOpenProjects.get(OpenProjectList.java:320)
at
org.netbeans.modules.javascript2.knockout.index.KnockoutIndex.get(KnockoutIndex.java:60)
- locked <0x000714b0> (a java.util.WeakHashMap)
at
org.netbeans.modules.html.knockout.KOHtmlExtension.isTagCustomKnockoutElement(KOHtmlExtension.java:395)
at
org.netbeans.modules.html.knockout.KOHtmlExtension.isCustomTag(KOHtmlExtension.java:302)
at
org.netbeans.modules.html.editor.gsf.HtmlGSFParser$1.isCustomTag(HtmlGSFParser.java:109)
at
org.netbeans.modules.html.editor.gsf.HtmlGSFParser$AggregatedUndeclaredContentResolver.isCustomTag(HtmlGSFParser.java:153)
at
org.netbeans.modules.html.editor.lib.api.SyntaxAnalyzerResult$ElementContentFilter.shouldBeFiltered(SyntaxAnalyzerResult.java:752)
at
org.netbeans.modules.html.editor.lib.api.SyntaxAnalyzerResult$ElementContentFilter.getMasks(SyntaxAnalyzerResult.java:720)
at
org.netbeans.modules.html.editor.lib.api.SyntaxAnalyzerResult.getMaskedAreas(SyntaxAnalyzerResult.java:492)
- locked <0x000714b00350> (a
org.netbeans.modules.html.editor.lib.api.SyntaxAnalyzerResult)
at
org.netbeans.modules.html.editor.lib.api.SyntaxAnalyzerResult.doParseHtml(SyntaxAnalyzerResult.java:259)
at
org.netbeans.modules.html.editor.lib.api.SyntaxAnalyzerResult.parseHtml(SyntaxAnalyzerResult.java:185)
- locked <0x000714b00350> (a
org.netbeans.modules.html.editor.lib.api.SyntaxAnalyzerResult)
at
org.netbeans.modules.html.editor.api.gsf.HtmlParserResult.root(HtmlParserResult.java:119)
{code}
and this task always has
{code}
Locked ownable synchronizers:
- <0x00070ab1db30> (a
java.util.concurrent.locks.ReentrantLock$FairSync)
{code}
where this "Locked ownable" thing is the same as what the "Load Open Projects"
task is waiting for.
> NetBeans 12.1-beta1 sometimes hangs on open
> ---
>
> Key: NETBEANS-4696
> URL: https://issues.apache.org/jira/browse/NETBEANS-4696
> Project: NetBeans
> Issue Type: Bug
> Components: ide - Performance
>Affects Versions: 12.1
> Environment: Linux (Debian "Buster")
> OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.7+10)
>Reporter: Glenn Holmer
>Priority: Major
> Attachments: 12.1-vc1-thread-dump-orac.txt,
> nb12.1-beta1-thread-dump.png, nb12.1-beta1-thread-dump.txt,
> netbeans-12.1-thread-dump.txt
>
>
> NetBeans sometimes hangs on startup; the symptom is a stalled "Opening
> Projects" progress bar. I haven't been able to find a repro case, but I'm
> attaching a thread dump (from VisualVM) and screen shot.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-
[jira] [Updated] (NETBEANS-4745) fxml editor shows errors for Insets (immutable objects in general?)
[
https://issues.apache.org/jira/browse/NETBEANS-4745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ernie Rael updated NETBEANS-4745:
-
Labels: pull-request-available (was: )
> fxml editor shows errors for Insets (immutable objects in general?)
> ---
>
> Key: NETBEANS-4745
> URL: https://issues.apache.org/jira/browse/NETBEANS-4745
> Project: NetBeans
> Issue Type: Bug
> Components: javafx - Editor
>Reporter: Ernie Rael
>Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> To recreate:
> NewProject > JavaWithMaven > FXML JavaFX Maven Archetype (Gluon)
> Open primary.fxml, in "other sources" "source/main/resources"
> Observe that the lines like:
> {code}
>
> {code}
> show errors, in particular
> {code}
> Instances of javafx.geometry.Insets cannot be created by FXML loader
> Class 'javafx.geometry.Insets' does not support property 'bottom'
> {code}
> examining the code in NetBeans "JavaFX 2 Support" module
> {code:java}
> package org.netbeans.modules.javafx2.editor.completion.beans;
> public final class BeanModelBuilder
> {code}
> The problem seems to start with Insets not having a no argument constructor;
> and the properties are not recognized because they have no setters. So it
> looks like immutable objects are not handled.
> Look near the begginning of BeanModelBuilder.process() around
> {code}
> if (c.getParameters().isEmpty() &&
> {code}
> and then BeanModelBuilder.inspectMembers(), addProperty(), findPropertyName
> {code}
> if (!name.startsWith(SET_NAME_PREFIX) || name.length() ==
> SET_NAME_PREFIX_LEN ||
> {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-4745) fxml editor shows errors for Insets (immutable objects in general?)
[
https://issues.apache.org/jira/browse/NETBEANS-4745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17186012#comment-17186012
]
Ernie Rael commented on NETBEANS-4745:
--
This was reported against NB-8.1
https://bz.apache.org/netbeans/show_bug.cgi?id=254824
> fxml editor shows errors for Insets (immutable objects in general?)
> ---
>
> Key: NETBEANS-4745
> URL: https://issues.apache.org/jira/browse/NETBEANS-4745
> Project: NetBeans
> Issue Type: Bug
> Components: javafx - Editor
>Reporter: Ernie Rael
>Priority: Major
>
> To recreate:
> NewProject > JavaWithMaven > FXML JavaFX Maven Archetype (Gluon)
> Open primary.fxml, in "other sources" "source/main/resources"
> Observe that the lines like:
> {code}
>
> {code}
> show errors, in particular
> {code}
> Instances of javafx.geometry.Insets cannot be created by FXML loader
> Class 'javafx.geometry.Insets' does not support property 'bottom'
> {code}
> examining the code in NetBeans "JavaFX 2 Support" module
> {code:java}
> package org.netbeans.modules.javafx2.editor.completion.beans;
> public final class BeanModelBuilder
> {code}
> The problem seems to start with Insets not having a no argument constructor;
> and the properties are not recognized because they have no setters. So it
> looks like immutable objects are not handled.
> Look near the begginning of BeanModelBuilder.process() around
> {code}
> if (c.getParameters().isEmpty() &&
> {code}
> and then BeanModelBuilder.inspectMembers(), addProperty(), findPropertyName
> {code}
> if (!name.startsWith(SET_NAME_PREFIX) || name.length() ==
> SET_NAME_PREFIX_LEN ||
> {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-4745) fxml editor shows errors for Insets (immutable objects in general?)
Ernie Rael created NETBEANS-4745:
Summary: fxml editor shows errors for Insets (immutable objects in
general?)
Key: NETBEANS-4745
URL: https://issues.apache.org/jira/browse/NETBEANS-4745
Project: NetBeans
Issue Type: Bug
Components: javafx - Editor
Reporter: Ernie Rael
To recreate:
NewProject > JavaWithMaven > FXML JavaFX Maven Archetype (Gluon)
Open primary.fxml, in "other sources" "source/main/resources"
Observe that the lines like:
{code}
{code}
show errors, in particular
{code}
Instances of javafx.geometry.Insets cannot be created by FXML loader
Class 'javafx.geometry.Insets' does not support property 'bottom'
{code}
examining the code in NetBeans "JavaFX 2 Support" module
{code:java}
package org.netbeans.modules.javafx2.editor.completion.beans;
public final class BeanModelBuilder
{code}
The problem seems to start with Insets not having a no argument constructor;
and the properties are not recognized because they have no setters. So it looks
like immutable objects are not handled.
Look near the begginning of BeanModelBuilder.process() around
{code}
if (c.getParameters().isEmpty() &&
{code}
and then BeanModelBuilder.inspectMembers(), addProperty(), findPropertyName
{code}
if (!name.startsWith(SET_NAME_PREFIX) || name.length() ==
SET_NAME_PREFIX_LEN ||
{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-1746) Error while parsing form a java source file
[ https://issues.apache.org/jira/browse/NETBEANS-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17185576#comment-17185576 ] Ernie Rael commented on NETBEANS-1746: -- [~Michal_cat] do you still see this? I don't see design option with NB-12 > Error while parsing form a java source file > --- > > Key: NETBEANS-1746 > URL: https://issues.apache.org/jira/browse/NETBEANS-1746 > Project: NetBeans > Issue Type: Bug > Components: javafx - Editor >Affects Versions: 10.0 > Environment: Windows 10, Incubator NetBeans Linux 927, Java 12 > Early-Access 20 >Reporter: Michal Rama >Priority: Major > Labels: editor, javafx > Attachments: picture1.png > > > For an existing JavaFX project (JDK 10), I have the option to switch to > design (for class with the main method). > But if I do, it will be displayed. > !picture1.png! > It is quite logical. This is an editor for JFrame (Swing). For such JavaFX > editing, you need to install the JavaFX Scene Builder. > So why is that option here? And why, at the new JavaFX project, the design > tab is not. > Please help > Thank you -- 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-1823) JavaFX Scene Builder Integration is still broken (Since Java SE 8u40)
[ https://issues.apache.org/jira/browse/NETBEANS-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17185574#comment-17185574 ] Ernie Rael commented on NETBEANS-1823: -- Gluon's Scene Builder works on Windows 7, NetBeans-12.0 > JavaFX Scene Builder Integration is still broken (Since Java SE 8u40) > - > > Key: NETBEANS-1823 > URL: https://issues.apache.org/jira/browse/NETBEANS-1823 > Project: NetBeans > Issue Type: Bug > Components: javafx - Editor >Affects Versions: 10.0 > Environment: MacOS High Sierra; NetBeans 10.vc5 running on JDK 10.0.1 > >Reporter: r-go >Priority: Major > Labels: 10.0-vc5, clos > > NetBeans -> Preferences (Options) -> Java ->JavaFX > The only path supported is one that refers to long abandoned (since Java SE > 8u40) Oracle's Scene Builder. JavaFX Scene Builder provided by Gluon can not > be registered and used in NetBeans - which is kind of nonsense as its in fact > the only maintained version of JavaFX scene builder, recommended even by > oracle. > As JavaFX scene builder is effectively "just" an external .fxml file editor - > the integration with NB is trivial (but for some strange reasons it is > missing from NB for years now) - please fix it if possible. -- 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-1823) JavaFX Scene Builder Integration is still broken (Since Java SE 8u40)
[ https://issues.apache.org/jira/browse/NETBEANS-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17185573#comment-17185573 ] Ernie Rael commented on NETBEANS-1823: -- [~johnsgp] when you say "replicated", this means you see the problem on MAC? > JavaFX Scene Builder Integration is still broken (Since Java SE 8u40) > - > > Key: NETBEANS-1823 > URL: https://issues.apache.org/jira/browse/NETBEANS-1823 > Project: NetBeans > Issue Type: Bug > Components: javafx - Editor >Affects Versions: 10.0 > Environment: MacOS High Sierra; NetBeans 10.vc5 running on JDK 10.0.1 > >Reporter: r-go >Priority: Major > Labels: 10.0-vc5, clos > > NetBeans -> Preferences (Options) -> Java ->JavaFX > The only path supported is one that refers to long abandoned (since Java SE > 8u40) Oracle's Scene Builder. JavaFX Scene Builder provided by Gluon can not > be registered and used in NetBeans - which is kind of nonsense as its in fact > the only maintained version of JavaFX scene builder, recommended even by > oracle. > As JavaFX scene builder is effectively "just" an external .fxml file editor - > the integration with NB is trivial (but for some strange reasons it is > missing from NB for years now) - please fix it if possible. -- 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-1823) JavaFX Scene Builder Integration is still broken (Since Java SE 8u40)
[ https://issues.apache.org/jira/browse/NETBEANS-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernie Rael updated NETBEANS-1823: - Labels: 10.0-vc5 clos (was: 10.0-vc5) > JavaFX Scene Builder Integration is still broken (Since Java SE 8u40) > - > > Key: NETBEANS-1823 > URL: https://issues.apache.org/jira/browse/NETBEANS-1823 > Project: NetBeans > Issue Type: Bug > Components: javafx - Editor >Affects Versions: 10.0 > Environment: MacOS High Sierra; NetBeans 10.vc5 running on JDK 10.0.1 > >Reporter: r-go >Priority: Major > Labels: 10.0-vc5, clos > > NetBeans -> Preferences (Options) -> Java ->JavaFX > The only path supported is one that refers to long abandoned (since Java SE > 8u40) Oracle's Scene Builder. JavaFX Scene Builder provided by Gluon can not > be registered and used in NetBeans - which is kind of nonsense as its in fact > the only maintained version of JavaFX scene builder, recommended even by > oracle. > As JavaFX scene builder is effectively "just" an external .fxml file editor - > the integration with NB is trivial (but for some strange reasons it is > missing from NB for years now) - please fix it if possible. -- 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-4718) NewFile>JavaFX2>EmptyFXML default controller placement causes runtime error
[
https://issues.apache.org/jira/browse/NETBEANS-4718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ernie Rael updated NETBEANS-4718:
-
Labels: pull-request-available (was: )
> NewFile>JavaFX2>EmptyFXML default controller placement causes runtime error
> ---
>
> Key: NETBEANS-4718
> URL: https://issues.apache.org/jira/browse/NETBEANS-4718
> Project: NetBeans
> Issue Type: Bug
> Components: apisupport - Maven, javafx - Project
>Affects Versions: 12.0
> Environment: Windows 10
>Reporter: Anthony Romano
>Priority: Major
> Labels: pull-request-available
> Fix For: Next
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The original description, from the "heat of battle", does not describe a bug
> and without knowing the error, the problem that OP ran into is unknown. The
> first comment does describe an error generated by using default values from
> the wizard. Proceeding with fix for that.
> Please file another issue how to reproduce, if there is still a problem.
> {quote}
> In the Maven-based JavaFx project in Netbeans 12.0, the system generated FXML
> file in the default package of ${Project}\src\main\resources\fxml is not
> detected and leads to a Runtime exception when the app tries to load the FXML
> file using the FXMLLoad.load() API. As a workaround the developer needs to
> copy the FXML file from the aforementioned default directory to the
> src\main\resources\org\openjfx\${Project} folder so the build process can
> process this file.
> {quote}
--
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-4718) NewFile>JavaFX2>EmptyFXML default controller placement causes runtime error
[
https://issues.apache.org/jira/browse/NETBEANS-4718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ernie Rael updated NETBEANS-4718:
-
Description:
The original description, from the "heat of battle", does not describe a bug
and without knowing the error, the problem that OP ran into is unknown. The
first comment does describe an error generated by using default values from the
wizard. Proceeding with fix for that.
Please file another issue how to reproduce, if there is still a problem.
{quote}
In the Maven-based JavaFx project in Netbeans 12.0, the system generated FXML
file in the default package of ${Project}\src\main\resources\fxml is not
detected and leads to a Runtime exception when the app tries to load the FXML
file using the FXMLLoad.load() API. As a workaround the developer needs to copy
the FXML file from the aforementioned default directory to the
src\main\resources\org\openjfx\${Project} folder so the build process can
process this file.
{quote}
was:
The original description, from the "heat of battle", does not describe a bug
and without knowing the error, the problem that OP ran into is unknown. The
first comment does describe an error generated by using default values from the
wizard. Proceeding with fix for that.
Please file another issue how to reproduce, if there is still a problem.
In the Maven-based JavaFx project in Netbeans 12.0, the system generated FXML
file in the default package of ${Project}\src\main\resources\fxml is not
detected and leads to a Runtime exception when the app tries to load the FXML
file using the FXMLLoad.load() API. As a workaround the developer needs to copy
the FXML file from the aforementioned default directory to the
src\main\resources\org\openjfx\${Project} folder so the build process can
process this file.
> NewFile>JavaFX2>EmptyFXML default controller placement causes runtime error
> ---
>
> Key: NETBEANS-4718
> URL: https://issues.apache.org/jira/browse/NETBEANS-4718
> Project: NetBeans
> Issue Type: Bug
> Components: apisupport - Maven, javafx - Project
>Affects Versions: 12.0
> Environment: Windows 10
>Reporter: Anthony Romano
>Priority: Major
> Fix For: Next
>
>
> The original description, from the "heat of battle", does not describe a bug
> and without knowing the error, the problem that OP ran into is unknown. The
> first comment does describe an error generated by using default values from
> the wizard. Proceeding with fix for that.
> Please file another issue how to reproduce, if there is still a problem.
> {quote}
> In the Maven-based JavaFx project in Netbeans 12.0, the system generated FXML
> file in the default package of ${Project}\src\main\resources\fxml is not
> detected and leads to a Runtime exception when the app tries to load the FXML
> file using the FXMLLoad.load() API. As a workaround the developer needs to
> copy the FXML file from the aforementioned default directory to the
> src\main\resources\org\openjfx\${Project} folder so the build process can
> process this file.
> {quote}
--
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-4718) NewFile>JavaFX2>EmptyFXML default controller placement causes runtime error
[
https://issues.apache.org/jira/browse/NETBEANS-4718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ernie Rael updated NETBEANS-4718:
-
Description:
The original description, from the "heat of battle", does not describe a bug
and without knowing the error, the problem that OP ran into is unknown. The
first comment does describe an error generated by using default values from the
wizard. Proceeding with fix for that.
Please file another issue how to reproduce, if there is still a problem.
In the Maven-based JavaFx project in Netbeans 12.0, the system generated FXML
file in the default package of ${Project}\src\main\resources\fxml is not
detected and leads to a Runtime exception when the app tries to load the FXML
file using the FXMLLoad.load() API. As a workaround the developer needs to copy
the FXML file from the aforementioned default directory to the
src\main\resources\org\openjfx\${Project} folder so the build process can
process this file.
was:
The original description, from the "heat of battle", does not describe a bug
and without knowing the error, the problem that OP ran into is unknown. The
first comment does describe an error generated by using default values from the
wizard.
In the Maven-based JavaFx project in Netbeans 12.0, the system generated FXML
file in the default package of ${Project}\src\main\resources\fxml is not
detected and leads to a Runtime exception when the app tries to load the FXML
file using the FXMLLoad.load() API. As a workaround the developer needs to copy
the FXML file from the aforementioned default directory to the
src\main\resources\org\openjfx\${Project} folder so the build process can
process this file.
> NewFile>JavaFX2>EmptyFXML default controller placement causes runtime error
> ---
>
> Key: NETBEANS-4718
> URL: https://issues.apache.org/jira/browse/NETBEANS-4718
> Project: NetBeans
> Issue Type: Bug
> Components: apisupport - Maven, javafx - Project
>Affects Versions: 12.0
> Environment: Windows 10
>Reporter: Anthony Romano
>Priority: Major
> Fix For: Next
>
>
> The original description, from the "heat of battle", does not describe a bug
> and without knowing the error, the problem that OP ran into is unknown. The
> first comment does describe an error generated by using default values from
> the wizard. Proceeding with fix for that.
> Please file another issue how to reproduce, if there is still a problem.
> In the Maven-based JavaFx project in Netbeans 12.0, the system generated FXML
> file in the default package of ${Project}\src\main\resources\fxml is not
> detected and leads to a Runtime exception when the app tries to load the FXML
> file using the FXMLLoad.load() API. As a workaround the developer needs to
> copy the FXML file from the aforementioned default directory to the
> src\main\resources\org\openjfx\${Project} folder so the build process can
> process this file.
--
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-4718) NewFile>JavaFX2>EmptyFXML default controller placement causes runtime error
[
https://issues.apache.org/jira/browse/NETBEANS-4718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ernie Rael updated NETBEANS-4718:
-
Description:
The original description, from the "heat of battle", does not describe a bug
and without knowing the error, the problem that OP ran into is unknown. The
first comment does describe an error generated by using default values from the
wizard.
In the Maven-based JavaFx project in Netbeans 12.0, the system generated FXML
file in the default package of ${Project}\src\main\resources\fxml is not
detected and leads to a Runtime exception when the app tries to load the FXML
file using the FXMLLoad.load() API. As a workaround the developer needs to copy
the FXML file from the aforementioned default directory to the
src\main\resources\org\openjfx\${Project} folder so the build process can
process this file.
was:
The original description, from the "heat of battle", does not describe a bug
and without knowing the error, the problem that OP ran into is unknow. The
first comment
In the Maven-based JavaFx project in Netbeans 12.0, the system generated FXML
file in the default package of ${Project}\src\main\resources\fxml is not
detected and leads to a Runtime exception when the app tries to load the FXML
file using the FXMLLoad.load() API. As a workaround the developer needs to copy
the FXML file from the aforementioned default directory to the
src\main\resources\org\openjfx\${Project} folder so the build process can
process this file.
> NewFile>JavaFX2>EmptyFXML default controller placement causes runtime error
> ---
>
> Key: NETBEANS-4718
> URL: https://issues.apache.org/jira/browse/NETBEANS-4718
> Project: NetBeans
> Issue Type: Bug
> Components: apisupport - Maven, javafx - Project
>Affects Versions: 12.0
> Environment: Windows 10
>Reporter: Anthony Romano
>Priority: Major
> Fix For: Next
>
>
> The original description, from the "heat of battle", does not describe a bug
> and without knowing the error, the problem that OP ran into is unknown. The
> first comment does describe an error generated by using default values from
> the wizard.
> In the Maven-based JavaFx project in Netbeans 12.0, the system generated FXML
> file in the default package of ${Project}\src\main\resources\fxml is not
> detected and leads to a Runtime exception when the app tries to load the FXML
> file using the FXMLLoad.load() API. As a workaround the developer needs to
> copy the FXML file from the aforementioned default directory to the
> src\main\resources\org\openjfx\${Project} folder so the build process can
> process this file.
--
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-4718) NewFile>JavaFX2>EmptyFXML default controller placement causes runtime error
[
https://issues.apache.org/jira/browse/NETBEANS-4718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ernie Rael updated NETBEANS-4718:
-
Description:
The original description, from the "heat of battle", does not describe a bug
and without knowing the error, the problem that OP ran into is unknow. The
first comment
In the Maven-based JavaFx project in Netbeans 12.0, the system generated FXML
file in the default package of ${Project}\src\main\resources\fxml is not
detected and leads to a Runtime exception when the app tries to load the FXML
file using the FXMLLoad.load() API. As a workaround the developer needs to copy
the FXML file from the aforementioned default directory to the
src\main\resources\org\openjfx\${Project} folder so the build process can
process this file.
was:In the Maven-based JavaFx project in Netbeans 12.0, the system generated
FXML file in the default package of ${Project}\src\main\resources\fxml is not
detected and leads to a Runtime exception when the app tries to load the FXML
file using the FXMLLoad.load() API. As a workaround the developer needs to copy
the FXML file from the aforementioned default directory to the
src\main\resources\org\openjfx\${Project} folder so the build process can
process this file.
> NewFile>JavaFX2>EmptyFXML default controller placement causes runtime error
> ---
>
> Key: NETBEANS-4718
> URL: https://issues.apache.org/jira/browse/NETBEANS-4718
> Project: NetBeans
> Issue Type: Bug
> Components: apisupport - Maven, javafx - Project
>Affects Versions: 12.0
> Environment: Windows 10
>Reporter: Anthony Romano
>Priority: Major
> Fix For: Next
>
>
> The original description, from the "heat of battle", does not describe a bug
> and without knowing the error, the problem that OP ran into is unknow. The
> first comment
> In the Maven-based JavaFx project in Netbeans 12.0, the system generated FXML
> file in the default package of ${Project}\src\main\resources\fxml is not
> detected and leads to a Runtime exception when the app tries to load the FXML
> file using the FXMLLoad.load() API. As a workaround the developer needs to
> copy the FXML file from the aforementioned default directory to the
> src\main\resources\org\openjfx\${Project} folder so the build process can
> process this file.
--
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-4718) NewFile>JavaFX2>EmptyFXML default controller placement causes runtime error
[
https://issues.apache.org/jira/browse/NETBEANS-4718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ernie Rael updated NETBEANS-4718:
-
Summary: NewFile>JavaFX2>EmptyFXML default controller placement causes
runtime error (was: The default package for generated FXML file in maven based
JavaFx application is not detected)
> NewFile>JavaFX2>EmptyFXML default controller placement causes runtime error
> ---
>
> Key: NETBEANS-4718
> URL: https://issues.apache.org/jira/browse/NETBEANS-4718
> Project: NetBeans
> Issue Type: Bug
> Components: apisupport - Maven, javafx - Project
>Affects Versions: 12.0
> Environment: Windows 10
>Reporter: Anthony Romano
>Priority: Major
> Fix For: Next
>
>
> In the Maven-based JavaFx project in Netbeans 12.0, the system generated FXML
> file in the default package of ${Project}\src\main\resources\fxml is not
> detected and leads to a Runtime exception when the app tries to load the FXML
> file using the FXMLLoad.load() API. As a workaround the developer needs to
> copy the FXML file from the aforementioned default directory to the
> src\main\resources\org\openjfx\${Project} folder so the build process can
> process this file.
--
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-4718) The default package for generated FXML file in maven based JavaFx application is not detected
[
https://issues.apache.org/jira/browse/NETBEANS-4718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17184190#comment-17184190
]
Ernie Rael edited comment on NETBEANS-4718 at 8/25/20, 4:55 PM:
After some analysis, changing the bug title. The original title
{quote}The default package for generated FXML file in maven based JavaFx
application is not detected
{quote}
is about the location of the generated empty fxml file. The location chosen
does not cause errors. A feature request for picking a better spot could be
filed. There is no concept of "default package" for fxml files.
Since OP did not include the error, hard to say exactly what he was running
into.
was (Author: errael):
After some analysis, changing the bug title. The original title
{quote}The default package for generated FXML file in maven based JavaFx
application is not detected
{quote}
is about the location of the generated empty fxml file. The location chosen
does not cause errors. A feature request for picking a better spot could be
filed. There is no concept of "default package" for fxml files.
> The default package for generated FXML file in maven based JavaFx application
> is not detected
> -
>
> Key: NETBEANS-4718
> URL: https://issues.apache.org/jira/browse/NETBEANS-4718
> Project: NetBeans
> Issue Type: Bug
> Components: apisupport - Maven, javafx - Project
>Affects Versions: 12.0
> Environment: Windows 10
>Reporter: Anthony Romano
>Priority: Major
> Fix For: Next
>
>
> In the Maven-based JavaFx project in Netbeans 12.0, the system generated FXML
> file in the default package of ${Project}\src\main\resources\fxml is not
> detected and leads to a Runtime exception when the app tries to load the FXML
> file using the FXMLLoad.load() API. As a workaround the developer needs to
> copy the FXML file from the aforementioned default directory to the
> src\main\resources\org\openjfx\${Project} folder so the build process can
> process this file.
--
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-4718) The default package for generated FXML file in maven based JavaFx application is not detected
[
https://issues.apache.org/jira/browse/NETBEANS-4718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17184190#comment-17184190
]
Ernie Rael commented on NETBEANS-4718:
--
After some analysis, changing the bug title. The original title
{quote}The default package for generated FXML file in maven based JavaFx
application is not detected
{quote}
is about the location of the generated empty fxml file. The location chosen
does not cause errors. A feature request for picking a better spot could be
filed. There is no concept of "default package" for fxml files.
> The default package for generated FXML file in maven based JavaFx application
> is not detected
> -
>
> Key: NETBEANS-4718
> URL: https://issues.apache.org/jira/browse/NETBEANS-4718
> Project: NetBeans
> Issue Type: Bug
> Components: apisupport - Maven, javafx - Project
>Affects Versions: 12.0
> Environment: Windows 10
>Reporter: Anthony Romano
>Priority: Major
> Fix For: Next
>
>
> In the Maven-based JavaFx project in Netbeans 12.0, the system generated FXML
> file in the default package of ${Project}\src\main\resources\fxml is not
> detected and leads to a Runtime exception when the app tries to load the FXML
> file using the FXMLLoad.load() API. As a workaround the developer needs to
> copy the FXML file from the aforementioned default directory to the
> src\main\resources\org\openjfx\${Project} folder so the build process can
> process this file.
--
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-4718) The default package for generated FXML file in maven based JavaFx application is not detected
[
https://issues.apache.org/jira/browse/NETBEANS-4718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17179971#comment-17179971
]
Ernie Rael edited comment on NETBEANS-4718 at 8/18/20, 5:50 PM:
My tests running current repo (about 12.1beta2) on jdk-14.
This issue first turned up in thread
[http://mail-archives.apache.org/mod_mbox/netbeans-users/202008.mbox/%3C1732072939.1651138.1597416076300%40mail.yahoo.com%3E]
Use NB to create an fxml project, and then add an empty fxml file, in
particular:
# File->New Project->Java with Maven->FXML JavaFx Maven Archetype (Gluon)->
# File ->New File -> JavaFX->Empty FXML->->Use Java
Controller->...->Finish
Using the dialog defaults; the default package for FXML.fxml file is "fxml",
default for controller is "". This results in
{code:java}
In /src/main
./resources/fxml/FXML.fxml
./java/FXMLController.java
{code}
and in FXML.fxml there is
{code:java}
fx:controller=".FXMLController
{code}
which is higlighted with the error :Class does not exist: .FXMLController". And
the execution fails with
{code:java}
--- javafx-maven-plugin:0.0.4:run (default-cli) @ fxml-bug ---
Error occurred during initialization of boot layer
java.lang.module.FindException: Error reading module:
C:\f\tmp\fxml-bug\target\classes
Caused by: java.lang.module.InvalidModuleDescriptorException:
FXMLController.class found in top-level directory (unnamed package not allowed
in module)
Command execution failed.
{code}
With the cursor over the package, play.fxml.bug in my case, the dialog still
has "fxml","" as defaults.
Selecting the package in the two places in the dialog, play.fxml.bug, gives
{code:java}
./java/play/fxml/bug/FXMLController.java
./resources/play/fxml/bug/FXML.fxml
{code}
The execution succeeds
was (Author: errael):
This issue first turned up in thread
[http://mail-archives.apache.org/mod_mbox/netbeans-users/202008.mbox/%3C1732072939.1651138.1597416076300%40mail.yahoo.com%3E]
Use NB to create an fxml project, and then add an empty fxml file, in
particular:
# File->New Project->Java with Maven->FXML JavaFx Maven Archetype (Gluon)->
# File ->New File -> JavaFX->Empty FXML->->Use Java
Controller->...->Finish
Using the dialog defaults; the default package for FXML.fxml file is "fxml",
default for controller is "". This results in
{code:java}
In /src/main
./resources/fxml/FXML.fxml
./java/FXMLController.java
{code}
and in FXML.fxml there is
{code:java}
fx:controller=".FXMLController
{code}
which is higlighted with the error :Class does not exist: .FXMLController". And
the execution fails with
{code}
--- javafx-maven-plugin:0.0.4:run (default-cli) @ fxml-bug ---
Error occurred during initialization of boot layer
java.lang.module.FindException: Error reading module:
C:\f\tmp\fxml-bug\target\classes
Caused by: java.lang.module.InvalidModuleDescriptorException:
FXMLController.class found in top-level directory (unnamed package not allowed
in module)
Command execution failed.
{code}
With the cursor over the package, play.fxml.bug in my case, the dialog still
has "fxml","" as defaults.
Selecting the package in the two places in the dialog, play.fxml.bug, gives
{code}
./java/play/fxml/bug/FXMLController.java
./resources/play/fxml/bug/FXML.fxml
{code}
The execution succeeds
> The default package for generated FXML file in maven based JavaFx application
> is not detected
> -
>
> Key: NETBEANS-4718
> URL: https://issues.apache.org/jira/browse/NETBEANS-4718
> Project: NetBeans
> Issue Type: Bug
> Components: apisupport - Maven, javafx - Project
>Affects Versions: 12.0
> Environment: Windows 10
>Reporter: Anthony Romano
>Priority: Major
> Fix For: Next
>
>
> In the Maven-based JavaFx project in Netbeans 12.0, the system generated FXML
> file in the default package of ${Project}\src\main\resources\fxml is not
> detected and leads to a Runtime exception when the app tries to load the FXML
> file using the FXMLLoad.load() API. As a workaround the developer needs to
> copy the FXML file from the aforementioned default directory to the
> src\main\resources\org\openjfx\${Project} folder so the build process can
> process this file.
--
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-4718) The default package for generated FXML file in maven based JavaFx application is not detected
[
https://issues.apache.org/jira/browse/NETBEANS-4718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17179971#comment-17179971
]
Ernie Rael commented on NETBEANS-4718:
--
This issue first turned up in thread
[http://mail-archives.apache.org/mod_mbox/netbeans-users/202008.mbox/%3C1732072939.1651138.1597416076300%40mail.yahoo.com%3E]
Use NB to create an fxml project, and then add an empty fxml file, in
particular:
# File->New Project->Java with Maven->FXML JavaFx Maven Archetype (Gluon)->
# File ->New File -> JavaFX->Empty FXML->->Use Java
Controller->...->Finish
Using the dialog defaults; the default package for FXML.fxml file is "fxml",
default for controller is "". This results in
{code:java}
In /src/main
./resources/fxml/FXML.fxml
./java/FXMLController.java
{code}
and in FXML.fxml there is
{code:java}
fx:controller=".FXMLController
{code}
which is higlighted with the error :Class does not exist: .FXMLController". And
the execution fails with
{code}
--- javafx-maven-plugin:0.0.4:run (default-cli) @ fxml-bug ---
Error occurred during initialization of boot layer
java.lang.module.FindException: Error reading module:
C:\f\tmp\fxml-bug\target\classes
Caused by: java.lang.module.InvalidModuleDescriptorException:
FXMLController.class found in top-level directory (unnamed package not allowed
in module)
Command execution failed.
{code}
With the cursor over the package, play.fxml.bug in my case, the dialog still
has "fxml","" as defaults.
Selecting the package in the two places in the dialog, play.fxml.bug, gives
{code}
./java/play/fxml/bug/FXMLController.java
./resources/play/fxml/bug/FXML.fxml
{code}
The execution succeeds
> The default package for generated FXML file in maven based JavaFx application
> is not detected
> -
>
> Key: NETBEANS-4718
> URL: https://issues.apache.org/jira/browse/NETBEANS-4718
> Project: NetBeans
> Issue Type: Bug
> Components: apisupport - Maven, javafx - Project
>Affects Versions: 12.0
> Environment: Windows 10
>Reporter: Anthony Romano
>Priority: Major
> Fix For: Next
>
>
> In the Maven-based JavaFx project in Netbeans 12.0, the system generated FXML
> file in the default package of ${Project}\src\main\resources\fxml is not
> detected and leads to a Runtime exception when the app tries to load the FXML
> file using the FXMLLoad.load() API. As a workaround the developer needs to
> copy the FXML file from the aforementioned default directory to the
> src\main\resources\org\openjfx\${Project} folder so the build process can
> process this file.
--
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-4718) The default package for generated FXML file in maven based JavaFx application is not detected
[
https://issues.apache.org/jira/browse/NETBEANS-4718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17178494#comment-17178494
]
Ernie Rael commented on NETBEANS-4718:
--
Made myself a watcher rather than assignee. I might have a chance to
investigate, but not soon.
> The default package for generated FXML file in maven based JavaFx application
> is not detected
> -
>
> Key: NETBEANS-4718
> URL: https://issues.apache.org/jira/browse/NETBEANS-4718
> Project: NetBeans
> Issue Type: Bug
> Components: apisupport - Maven, javafx - Project
>Affects Versions: 12.0
> Environment: Windows 10
>Reporter: Anthony Romano
>Priority: Major
> Fix For: Next
>
>
> In the Maven-based JavaFx project in Netbeans 12.0, the system generated FXML
> file in the default package of ${Project}\src\main\resources\fxml is not
> detected and leads to a Runtime exception when the app tries to load the FXML
> file using the FXMLLoad.load() API. As a workaround the developer needs to
> copy the FXML file from the aforementioned default directory to the
> src\main\resources\org\openjfx\${Project} folder so the build process can
> process this file.
--
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-4718) The default package for generated FXML file in maven based JavaFx application is not detected
[
https://issues.apache.org/jira/browse/NETBEANS-4718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ernie Rael reassigned NETBEANS-4718:
Assignee: (was: Ernie Rael)
> The default package for generated FXML file in maven based JavaFx application
> is not detected
> -
>
> Key: NETBEANS-4718
> URL: https://issues.apache.org/jira/browse/NETBEANS-4718
> Project: NetBeans
> Issue Type: Bug
> Components: apisupport - Maven, javafx - Project
>Affects Versions: 12.0
> Environment: Windows 10
>Reporter: Anthony Romano
>Priority: Major
> Fix For: Next
>
>
> In the Maven-based JavaFx project in Netbeans 12.0, the system generated FXML
> file in the default package of ${Project}\src\main\resources\fxml is not
> detected and leads to a Runtime exception when the app tries to load the FXML
> file using the FXMLLoad.load() API. As a workaround the developer needs to
> copy the FXML file from the aforementioned default directory to the
> src\main\resources\org\openjfx\${Project} folder so the build process can
> process this file.
--
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-4711) maven "add existing module" doesn't hook up child
[ https://issues.apache.org/jira/browse/NETBEANS-4711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17177441#comment-17177441 ] Ernie Rael commented on NETBEANS-4711: -- Added watcher who turned me on to maven parent modules > maven "add existing module" doesn't hook up child > - > > Key: NETBEANS-4711 > URL: https://issues.apache.org/jira/browse/NETBEANS-4711 > Project: NetBeans > Issue Type: Bug > Components: projects - Maven >Reporter: Ernie Rael >Priority: Major > > On a maven pom project, if I do "create new module" then the module is added > to the parent and the child has a "" defined. With "add existing > module" the child does not get a "". > If there are some cases where a child shouldn't get a parent, then there > should be a checkbox for that case. -- 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-4711) maven "add existing module" doesn't hook up child
Ernie Rael created NETBEANS-4711: Summary: maven "add existing module" doesn't hook up child Key: NETBEANS-4711 URL: https://issues.apache.org/jira/browse/NETBEANS-4711 Project: NetBeans Issue Type: Bug Components: projects - Maven Reporter: Ernie Rael On a maven pom project, if I do "create new module" then the module is added to the parent and the child has a "" defined. With "add existing module" the child does not get a "". If there are some cases where a child shouldn't get a parent, then there should be a checkbox for that case. -- 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-4679) Website welcome page references wrong php learning pages
Ernie Rael created NETBEANS-4679:
Summary: Website welcome page references wrong php learning pages
Key: NETBEANS-4679
URL: https://issues.apache.org/jira/browse/NETBEANS-4679
Project: NetBeans
Issue Type: Bug
Components: website
Reporter: Ernie Rael
(This came up in mailing lists, I lost track of it...)
That is a bug!
El 10/07/2020 a las 3:56, Ernie Rael escribió:
{quote}Perfect, many thanks. (and lots to go through)
It's probably worth noting that the main page,
[https://netbeans.apache.org|https://netbeans.apache.org/], has a pointer for
PHP that goes to [https://netbeans.apache.org/kb/docs/php/index.html] where
there is far less information. I don't know if this is intentional, or still in
progress or ...
-ernie
On 7/8/2020 12:05 PM, antonio wrote:
{quote}I don't think we have NB-12 specific documents yet.
Maybe you want to take a look to the NetBeans PHP Learning Trail here:
[https://netbeans.apache.org/kb/docs/php.html]{quote}{quote}
--
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-4560) plugin portal, PP3, does not publish GroupId of plugin
Ernie Rael created NETBEANS-4560: Summary: plugin portal, PP3, does not publish GroupId of plugin Key: NETBEANS-4560 URL: https://issues.apache.org/jira/browse/NETBEANS-4560 Project: NetBeans Issue Type: Bug Components: updatecenters - Pluginportal Reporter: Ernie Rael The plugins have ArtifactId, but not GroupId, shown. I have seen several artifacts ( in general, not necessarily plugins) where the same ArtifactId is used but with different GroupId. If someone wanted to take a look at the source code, the missing GroupId is a problem. Is it a security violation? ;) -- 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-2331) Make signing of plugins mandatory or remove it completely
[
https://issues.apache.org/jira/browse/NETBEANS-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17146700#comment-17146700
]
Ernie Rael commented on NETBEANS-2331:
--
{quote}... sign his plugin. Neither the plugin portal, nor the IDE enforce it
{quote}
Just to note that this is a change from PP2. PP2 required a signed nbm in order
to get it verified and thus included in the catalog for the plugin manager.
> Make signing of plugins mandatory or remove it completely
> -
>
> Key: NETBEANS-2331
> URL: https://issues.apache.org/jira/browse/NETBEANS-2331
> Project: NetBeans
> Issue Type: Improvement
> Components: platform - Module System, updatecenters - Pluginportal
>Affects Versions: Next
>Reporter: Christian Lenz
>Priority: Major
>
> Atm the moment, the process is you can create and upload a plugin on the
> plugin page. Everything is fine and you need to go to that page if you want
> to download this plugin which is not signed. So you will not find it on the
> plugin manager of NetBeans.
> If you want to see it inside of the plugin manager inside NetBeans, you need
> to sign the plugin or you can add the catalg for unsigned plugins.
> The thing is, some or maybe most of plugin developers doesn't know to
> generate the keystore file or it is to complicated and often a pain in the
> ass.
> So my proposal is either we make it mandatory for Ant and Maven (Maybe Gradle
> too) to sign the plugin inside of the project settings where you can fill in
> the stuff, that is needed or we remove the signing stuff completely. Afaik VS
> Code or IntelliJ doesn't have such process. But only guessing.
> When I had a look into the docu of IntelliJ to create a plugin, I couldn't
> find an info for sigining a plugin.
> Another proposal, if we still want to have the sigining, should add the not
> signed plugins as default to NetBeans and show the user which plugins are
> signed and which not. That everyone can find the plugin inside of the
> NetBeans plugin manager and not on both, the page and manager. That is a pain
> in the ass.
--
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-1136) Cannot activate some installed plugins
[ https://issues.apache.org/jira/browse/NETBEANS-1136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17133756#comment-17133756 ] Ernie Rael commented on NETBEANS-1136: -- moved to plugin manager instead of plugin portal > Cannot activate some installed plugins > -- > > Key: NETBEANS-1136 > URL: https://issues.apache.org/jira/browse/NETBEANS-1136 > Project: NetBeans > Issue Type: Bug > Components: platform - Plugin Manager >Affects Versions: 8.2 > Environment: Windows 10 PRO Creators Edition >Reporter: PETER BORREGGINE >Priority: Major > Labels: patch > Fix For: 8.2 > > Attachments: netbeans install plugin problem 1.png, netbeans install > plugin problem 2.png, netbeans install plugin problem 3.PNG, netbeans install > plugin problem 4.PNG, netbeans install plugin problem 5.PNG, > netbeans-fails-to-activate-plugins.PNG > > > Upon trying to activate installed plugins, I get this: > > Activation failed: Not all requested modules can be enabled: > [StandardModule:org.netbeans.modules.php.zend jarFile: C:\Program > Files\NetBeans 8.2\php\modules\org-netbeans-modules-php-zend.jar, > StandardModule:org.netbeans.modules.websvc.restkit jarFile: C:\Program > Files\NetBeans > 8.2\enterprise\modules\org-netbeans-modules-websvc-restkit.jar, > StandardModule:org.netbeans.modules.ant.kit jarFile: C:\Program > Files\NetBeans 8.2\java\modules\org-netbeans-modules-ant-kit.jar, > StandardModule:org.netbeans.modules.web.jsf.kit jarFile: C:\Program > Files\NetBeans 8.2\enterprise\modules\org-netbeans-modules-web-jsf-kit.jar, > StandardModule:org.netbeans.modules.debugger.jpda.kit jarFile: C:\Program > Files\NetBeans 8.2\java\modules\org-netbeans-modules-debugger-jpda-kit.jar, > StandardModule:org.netbeans.modules.spring.webmvc jarFile: C:\Program > Files\NetBeans 8.2\enterprise\modules\org-netbeans-modules-spring-webmvc.jar, > StandardModule:org.netbeans.modules.apisupport.kit jarFile: C:\Program > Files\NetBeans > 8.2\apisupport\modules\org-netbeans-modules-apisupport-kit.jar, > StandardModule:org.netbeans.modules.websvc.saas.kit jarFile: C:\Program > Files\NetBeans > 8.2\websvccommon\modules\org-netbeans-modules-websvc-saas-kit.jar, > StandardModule:org.netbeans.modules.php.latte jarFile: C:\Program > Files\NetBeans 8.2\php\modules\org-netbeans-modules-php-latte.jar, > StandardModule:org.netbeans.modules.java.kit jarFile: C:\Program > Files\NetBeans 8.2\java\modules\org-netbeans-modules-java-kit.jar, > StandardModule:org.netbeans.modules.hibernate jarFile: C:\Program > Files\NetBeans 8.2\java\modules\org-netbeans-modules-hibernate.jar, > StandardModule:org.netbeans.modules.php.phpdoc jarFile: C:\Program > Files\NetBeans 8.2\php\modules\org-netbeans-modules-php-phpdoc.jar, > StandardModule:org.netbeans.modules.maven.kit jarFile: C:\Program > Files\NetBeans 8.2\java\modules\org-netbeans-modules-maven-kit.jar, > StandardModule:org.netbeans.modules.ide.kit jarFile: C:\Program > Files\NetBeans 8.2\ide\modules\org-netbeans-modules-ide-kit.jar, > StandardModule:org.netbeans.modules.php.smarty jarFile: C:\Program > Files\NetBeans 8.2\php\modules\org-netbeans-modules-php-smarty.jar, > StandardModule:org.netbeans.modules.php.symfony2 jarFile: C:\Program > Files\NetBeans 8.2\php\modules\org-netbeans-modules-php-symfony2.jar, > StandardModule:org.netbeans.modules.web.kit jarFile: C:\Program > Files\NetBeans 8.2\enterprise\modules\org-netbeans-modules-web-kit.jar, > StandardModule:org.netbeans.modules.php.twig jarFile: C:\Program > Files\NetBeans 8.2\php\modules\org-netbeans-modules-php-twig.jar, > StandardModule:org.netbeans.modules.web.primefaces jarFile: C:\Program > Files\NetBeans > 8.2\enterprise\modules\org-netbeans-modules-web-primefaces.jar, > StandardModule:org.netbeans.modules.php.composer jarFile: C:\Program > Files\NetBeans 8.2\php\modules\org-netbeans-modules-php-composer.jar, > StandardModule:org.netbeans.modules.spring.beans jarFile: C:\Program > Files\NetBeans 8.2\java\modules\org-netbeans-modules-spring-beans.jar, > StandardModule:org.netbeans.modules.j2ee.kit jarFile: C:\Program > Files\NetBeans 8.2\enterprise\modules\org-netbeans-modules-j2ee-kit.jar, > StandardModule:org.netbeans.modules.php.zend2 jarFile: C:\Program > Files\NetBeans 8.2\php\modules\org-netbeans-modules-php-zend2.jar, > StandardModule:org.netbeans.modules.php.kit jarFile: C:\Program > Files\NetBeans 8.2\php\modules\org-netbeans-modules-php-kit.jar, > StandardModule:org.netbeans.modules.php.apigen jarFile: C:\Program > Files\NetBeans 8.2\php\modules\org-netbeans-modules-php-apigen.jar, > StandardModule:org.netbeans.modules.web.struts jarFile: C:\Program > Files\NetBeans 8.2\enterprise\modules\org-netbeans-modules-web-struts.jar, > StandardMod
[jira] [Updated] (NETBEANS-1136) Cannot activate some installed plugins
[ https://issues.apache.org/jira/browse/NETBEANS-1136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernie Rael updated NETBEANS-1136: - Component/s: (was: updatecenters - Pluginportal) platform - Plugin Manager > Cannot activate some installed plugins > -- > > Key: NETBEANS-1136 > URL: https://issues.apache.org/jira/browse/NETBEANS-1136 > Project: NetBeans > Issue Type: Bug > Components: platform - Plugin Manager >Affects Versions: 8.2 > Environment: Windows 10 PRO Creators Edition >Reporter: PETER BORREGGINE >Priority: Major > Labels: patch > Fix For: 8.2 > > Attachments: netbeans install plugin problem 1.png, netbeans install > plugin problem 2.png, netbeans install plugin problem 3.PNG, netbeans install > plugin problem 4.PNG, netbeans install plugin problem 5.PNG, > netbeans-fails-to-activate-plugins.PNG > > > Upon trying to activate installed plugins, I get this: > > Activation failed: Not all requested modules can be enabled: > [StandardModule:org.netbeans.modules.php.zend jarFile: C:\Program > Files\NetBeans 8.2\php\modules\org-netbeans-modules-php-zend.jar, > StandardModule:org.netbeans.modules.websvc.restkit jarFile: C:\Program > Files\NetBeans > 8.2\enterprise\modules\org-netbeans-modules-websvc-restkit.jar, > StandardModule:org.netbeans.modules.ant.kit jarFile: C:\Program > Files\NetBeans 8.2\java\modules\org-netbeans-modules-ant-kit.jar, > StandardModule:org.netbeans.modules.web.jsf.kit jarFile: C:\Program > Files\NetBeans 8.2\enterprise\modules\org-netbeans-modules-web-jsf-kit.jar, > StandardModule:org.netbeans.modules.debugger.jpda.kit jarFile: C:\Program > Files\NetBeans 8.2\java\modules\org-netbeans-modules-debugger-jpda-kit.jar, > StandardModule:org.netbeans.modules.spring.webmvc jarFile: C:\Program > Files\NetBeans 8.2\enterprise\modules\org-netbeans-modules-spring-webmvc.jar, > StandardModule:org.netbeans.modules.apisupport.kit jarFile: C:\Program > Files\NetBeans > 8.2\apisupport\modules\org-netbeans-modules-apisupport-kit.jar, > StandardModule:org.netbeans.modules.websvc.saas.kit jarFile: C:\Program > Files\NetBeans > 8.2\websvccommon\modules\org-netbeans-modules-websvc-saas-kit.jar, > StandardModule:org.netbeans.modules.php.latte jarFile: C:\Program > Files\NetBeans 8.2\php\modules\org-netbeans-modules-php-latte.jar, > StandardModule:org.netbeans.modules.java.kit jarFile: C:\Program > Files\NetBeans 8.2\java\modules\org-netbeans-modules-java-kit.jar, > StandardModule:org.netbeans.modules.hibernate jarFile: C:\Program > Files\NetBeans 8.2\java\modules\org-netbeans-modules-hibernate.jar, > StandardModule:org.netbeans.modules.php.phpdoc jarFile: C:\Program > Files\NetBeans 8.2\php\modules\org-netbeans-modules-php-phpdoc.jar, > StandardModule:org.netbeans.modules.maven.kit jarFile: C:\Program > Files\NetBeans 8.2\java\modules\org-netbeans-modules-maven-kit.jar, > StandardModule:org.netbeans.modules.ide.kit jarFile: C:\Program > Files\NetBeans 8.2\ide\modules\org-netbeans-modules-ide-kit.jar, > StandardModule:org.netbeans.modules.php.smarty jarFile: C:\Program > Files\NetBeans 8.2\php\modules\org-netbeans-modules-php-smarty.jar, > StandardModule:org.netbeans.modules.php.symfony2 jarFile: C:\Program > Files\NetBeans 8.2\php\modules\org-netbeans-modules-php-symfony2.jar, > StandardModule:org.netbeans.modules.web.kit jarFile: C:\Program > Files\NetBeans 8.2\enterprise\modules\org-netbeans-modules-web-kit.jar, > StandardModule:org.netbeans.modules.php.twig jarFile: C:\Program > Files\NetBeans 8.2\php\modules\org-netbeans-modules-php-twig.jar, > StandardModule:org.netbeans.modules.web.primefaces jarFile: C:\Program > Files\NetBeans > 8.2\enterprise\modules\org-netbeans-modules-web-primefaces.jar, > StandardModule:org.netbeans.modules.php.composer jarFile: C:\Program > Files\NetBeans 8.2\php\modules\org-netbeans-modules-php-composer.jar, > StandardModule:org.netbeans.modules.spring.beans jarFile: C:\Program > Files\NetBeans 8.2\java\modules\org-netbeans-modules-spring-beans.jar, > StandardModule:org.netbeans.modules.j2ee.kit jarFile: C:\Program > Files\NetBeans 8.2\enterprise\modules\org-netbeans-modules-j2ee-kit.jar, > StandardModule:org.netbeans.modules.php.zend2 jarFile: C:\Program > Files\NetBeans 8.2\php\modules\org-netbeans-modules-php-zend2.jar, > StandardModule:org.netbeans.modules.php.kit jarFile: C:\Program > Files\NetBeans 8.2\php\modules\org-netbeans-modules-php-kit.jar, > StandardModule:org.netbeans.modules.php.apigen jarFile: C:\Program > Files\NetBeans 8.2\php\modules\org-netbeans-modules-php-apigen.jar, > StandardModule:org.netbeans.modules.web.struts jarFile: C:\Program > Files\NetBeans 8.2\enterprise\modules\org-netbeans-modules-web-struts.jar, > StandardModule:org
[jira] [Commented] (NETBEANS-1633) Installing nb-javac library leads to an exception
[ https://issues.apache.org/jira/browse/NETBEANS-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17133754#comment-17133754 ] Ernie Rael commented on NETBEANS-1633: -- moved to plugin manager instead of plugin portal > Installing nb-javac library leads to an exception > - > > Key: NETBEANS-1633 > URL: https://issues.apache.org/jira/browse/NETBEANS-1633 > Project: NetBeans > Issue Type: Bug > Components: platform - Plugin Manager >Affects Versions: 10.0 > Environment: windows 7 >Reporter: Baerbel Lindner >Priority: Minor > Attachments: messages.log > > > I have downloaded and installed > Apache NetBeans IDE Dev (Build incubator-netbeans-release-365-on-20181105) > (10-vc3). > > I got a notification to install the nb-javac library. This leads to an > exception (added at the end of the text). > Maybe there was a little java version confusion: > I started NetBeans with configuring jdk1.8.0_191 in netbeans.conf. Some > functions like "navigate -> go to declaration did not work" and code > completation did not work. Therefore I decided to switch to java 10 and > restarted NetBeans. Code complemtation and navigate worked. The notifaction > appeared after working with the IDE for some time. > Additionally I have configured a 8.2 update center. > > > -- 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-1633) Installing nb-javac library leads to an exception
[ https://issues.apache.org/jira/browse/NETBEANS-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernie Rael updated NETBEANS-1633: - Component/s: (was: updatecenters - Pluginportal) platform - Plugin Manager > Installing nb-javac library leads to an exception > - > > Key: NETBEANS-1633 > URL: https://issues.apache.org/jira/browse/NETBEANS-1633 > Project: NetBeans > Issue Type: Bug > Components: platform - Plugin Manager >Affects Versions: 10.0 > Environment: windows 7 >Reporter: Baerbel Lindner >Priority: Minor > Attachments: messages.log > > > I have downloaded and installed > Apache NetBeans IDE Dev (Build incubator-netbeans-release-365-on-20181105) > (10-vc3). > > I got a notification to install the nb-javac library. This leads to an > exception (added at the end of the text). > Maybe there was a little java version confusion: > I started NetBeans with configuring jdk1.8.0_191 in netbeans.conf. Some > functions like "navigate -> go to declaration did not work" and code > completation did not work. Therefore I decided to switch to java 10 and > restarted NetBeans. Code complemtation and navigate worked. The notifaction > appeared after working with the IDE for some time. > Additionally I have configured a 8.2 update center. > > > -- 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] [Closed] (NETBEANS-2301) Unable to access plugin portal from browser or IDE
[ https://issues.apache.org/jira/browse/NETBEANS-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernie Rael closed NETBEANS-2301. Resolution: Fixed Should be auto closed or somesuch > Unable to access plugin portal from browser or IDE > -- > > Key: NETBEANS-2301 > URL: https://issues.apache.org/jira/browse/NETBEANS-2301 > Project: NetBeans > Issue Type: Bug > Components: platform - Plugin Manager, updatecenters - Pluginportal >Affects Versions: 10.0 >Reporter: Fernando Montenegro >Priority: Major > > In Netbeans IDE 10, trying to check for new plugins via > Tools/Plugins/Available Plugins Check for Newest, gives an error saying that > there was a 502 error from the server. > I checked the URL via Firefox and Chrome and was unable to connect to > http[s]://plugins.netbeans.org/PluginPortal. It says connection was reset. > Also tried via mobile, using mobile data (not my ISP) and got the same result. -- 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-2478) SQL DAL Maker plugin does not recognize its own data nodes after reactivation
[ https://issues.apache.org/jira/browse/NETBEANS-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernie Rael updated NETBEANS-2478: - Component/s: (was: updatecenters - Pluginportal) platform - Plugin Manager > SQL DAL Maker plugin does not recognize its own data nodes after reactivation > - > > Key: NETBEANS-2478 > URL: https://issues.apache.org/jira/browse/NETBEANS-2478 > Project: NetBeans > Issue Type: Bug > Components: platform - Plugin Manager >Affects Versions: 11.0 >Reporter: Jiří Kovalský >Assignee: Andrey M >Priority: Minor > > SQL DAL Maker plugin ([http://plugins.netbeans.org/plugin/73614]) for some > reason does recognize *.dal files when activated after being deactive and > perhaps same issue occurs when re-installed. > *Steps to reproduce:* > # Download 1556400791_com-sqldalmaker-netbeans.nbm file [1] > # Go to *Tools > Plugins > Download*, click *Add Plugins...* button and > instal it. > # Create new Java sample project and then new empty _java.dal_ file via > *Ctrl+N*. > # It is opened in Editor with DTO, DAO and Admin tabs. > # Go to *Tools > Plugins > Installed*, uncheck Show details option, select > SQL DAL Maker plugin and deactivate it. > # After restart reactivate the plugin in a similar way. > [1] [http://plugins.netbeans.org/download/plugin/10010] > *Expected result:* The _java.dal_ file is recognized and DTO, DAO and Admin > tabs in Editor are displayed when opening java.dal file. > *Actual result:* NetBeans treats _java.dal_ file as a plain text file and > shows only empty editor without any additional tabs. Workaround is to restart > the IDE. -- 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
