[jira] [Resolved] (NETBEANS-6519) Maven dependency query produces incorrect results
[
https://issues.apache.org/jira/browse/NETBEANS-6519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Svatopluk Dedic resolved NETBEANS-6519.
---
Fix Version/s: 17
(was: 16)
Resolution: Fixed
> Maven dependency query produces incorrect results
> -
>
> Key: NETBEANS-6519
> URL: https://issues.apache.org/jira/browse/NETBEANS-6519
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Maven
>Affects Versions: 15
>Reporter: Svatopluk Dedic
>Priority: Major
> Fix For: 17
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Maven dependency tree factory produces a dependency tree where duplicates and
> conflicts are omitted - or present, marked, but with no children. These
> duplicates (conflicts) are reported through the results of the query - but
> there's no indication that the artifact is actually incomplete (no subtree)
> or where the complete subtree should be found.
> An exhaustive dependency traversal is affected by that behaviour. The desired
> state would be to:
> * for a duplicated artifact, report also a copy of the subtree: exhaustive
> dependency traversal will process it
> * if a back reference appears, to an artifact reported higher in the branch,
> make a separate node instead of back reference, and leave the children empty.
> This prevent infinite loops during (simple) traversals.
> For graph algorithms an additional API ({*}project.dependency{*}) should be
> introduced, that
> * reports that a tree node is a duplicate, providing a reference to the
> 'master' copy of the subtree. The client may opt to skip it, process the
> master instead or just use the master's identification.
> * report that a tree node had a conflict (which has been resolved), and what
> the original (conflicting) artifact is. This will usually indicate a version
> clash between library dependencies, but it will be useful to see it in the
> data.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: 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-6519) Maven dependency query produces incorrect results
Svatopluk Dedic created NETBEANS-6519:
-
Summary: Maven dependency query produces incorrect results
Key: NETBEANS-6519
URL: https://issues.apache.org/jira/browse/NETBEANS-6519
Project: NetBeans
Issue Type: Bug
Components: projects - Maven
Affects Versions: 15
Reporter: Svatopluk Dedic
Fix For: 16
Maven dependency tree factory produces a dependency tree where duplicates and
conflicts are omitted - or present, marked, but with no children. These
duplicates (conflicts) are reported through the results of the query - but
there's no indication that the artifact is actually incomplete (no subtree) or
where the complete subtree should be found.
An exhaustive dependency traversal is affected by that behaviour. The desired
state would be to:
* for a duplicated artifact, report also a copy of the subtree: exhaustive
dependency traversal will process it
* if a back reference appears, to an artifact reported higher in the branch,
make a separate node instead of back reference, and leave the children empty.
This prevent infinite loops during (simple) traversals.
For graph algorithms an additional API ({*}project.dependency{*}) should be
introduced, that
* reports that a tree node is a duplicate, providing a reference to the
'master' copy of the subtree. The client may opt to skip it, process the master
instead or just use the master's identification.
* report that a tree node had a conflict (which has been resolved), and what
the original (conflicting) artifact is. This will usually indicate a version
clash between library dependencies, but it will be useful to see it in the data.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: 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-6518) Provide CommandProvider LSP SPI
[ https://issues.apache.org/jira/browse/NETBEANS-6518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Svatopluk Dedic updated NETBEANS-6518: -- Affects Version/s: 15 > Provide CommandProvider LSP SPI > --- > > Key: NETBEANS-6518 > URL: https://issues.apache.org/jira/browse/NETBEANS-6518 > Project: NetBeans > Issue Type: Bug > Components: lsp >Affects Versions: 15 >Reporter: Svatopluk Dedic >Priority: Major > > There are already other modules that depend on LSP APIs, but they cannot > contribute commmands to LSP clients, some weird hacks (see > https://github.com/apache/netbeans/pull/4461#discussion_r936310039) must be > done in integration code. Some SPI should be introduced so that the modules > can expose their functions not only to the IDE, but also to lsp clients. > IMHO trivial deserialization of command parameters and serialization of the > command results should be handled by the LSP server module. > Question: should be the LSP commands, served to external LSP clients, served > also to the INTERNAL LSP client, if used ? > // cc: [~dbalek] [~jlahoda] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: 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-6518) Provide CommandProvider LSP SPI
[ https://issues.apache.org/jira/browse/NETBEANS-6518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Svatopluk Dedic updated NETBEANS-6518: -- Description: There are already other modules that depend on LSP APIs, but they cannot contribute commmands to LSP clients, some weird hacks (see https://github.com/apache/netbeans/pull/4461#discussion_r936310039) must be done in integration code. Some SPI should be introduced so that the modules can expose their functions not only to the IDE, but also to lsp clients. IMHO trivial deserialization of command parameters and serialization of the command results should be handled by the LSP server module. Question: should be the LSP commands, served to external LSP clients, served also to the INTERNAL LSP client, if used ? // cc: [~dbalek] [~jlahoda] was: There are already other modules that depend on LSP APIs, but they cannot contribute commmands to LSP clients, some weird hacks (see ) must be done in integration code. Some SPI should be introduced so that the modules can expose their functions not only to the IDE, but also to lsp clients. IMHO trivial deserialization of command parameters and serialization of the command results should be handled by the LSP server module. Question: should be the LSP commands, served to external LSP clients, served also to the INTERNAL LSP client, if used ? // cc: [~dbalek] [~jlahoda] > Provide CommandProvider LSP SPI > --- > > Key: NETBEANS-6518 > URL: https://issues.apache.org/jira/browse/NETBEANS-6518 > Project: NetBeans > Issue Type: Bug > Components: lsp >Reporter: Svatopluk Dedic >Priority: Major > > There are already other modules that depend on LSP APIs, but they cannot > contribute commmands to LSP clients, some weird hacks (see > https://github.com/apache/netbeans/pull/4461#discussion_r936310039) must be > done in integration code. Some SPI should be introduced so that the modules > can expose their functions not only to the IDE, but also to lsp clients. > IMHO trivial deserialization of command parameters and serialization of the > command results should be handled by the LSP server module. > Question: should be the LSP commands, served to external LSP clients, served > also to the INTERNAL LSP client, if used ? > // cc: [~dbalek] [~jlahoda] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: 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-6518) Provide CommandProvider LSP SPI
Svatopluk Dedic created NETBEANS-6518: - Summary: Provide CommandProvider LSP SPI Key: NETBEANS-6518 URL: https://issues.apache.org/jira/browse/NETBEANS-6518 Project: NetBeans Issue Type: Bug Components: lsp Reporter: Svatopluk Dedic There are already other modules that depend on LSP APIs, but they cannot contribute commmands to LSP clients, some weird hacks (see ) must be done in integration code. Some SPI should be introduced so that the modules can expose their functions not only to the IDE, but also to lsp clients. IMHO trivial deserialization of command parameters and serialization of the command results should be handled by the LSP server module. Question: should be the LSP commands, served to external LSP clients, served also to the INTERNAL LSP client, if used ? // cc: [~dbalek] [~jlahoda] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: 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-6517) Gradle project reports generated sources among regular ones
Svatopluk Dedic created NETBEANS-6517:
-
Summary: Gradle project reports generated sources among regular
ones
Key: NETBEANS-6517
URL: https://issues.apache.org/jira/browse/NETBEANS-6517
Project: NetBeans
Issue Type: Bug
Components: projects - Gradle
Affects Versions: 14
Reporter: Svatopluk Dedic
Assignee: Laszlo Kishalmi
Attachments: micronaut-core.png
I worked with Micronaut Starter
(g...@github.com:micronaut-projects/micronaut-starter.git
) project. It apparently generates some Java sources using rocker templates,
which are placed in {*}build/generated-src{*}.
But the presentation in the project view is as on the following screenshot:
!micronaut-core.png!
The highlighted (second from the top) [java][main] source directory is actually
*build/generated-src/rocker/main* directory. The same applies to tests, the 2nd
[java][test] is *build/generated-src/rocker/test*
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: 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-6516) --modules --disable commandline option does not work
Svatopluk Dedic created NETBEANS-6516:
-
Summary: --modules --disable commandline option does not work
Key: NETBEANS-6516
URL: https://issues.apache.org/jira/browse/NETBEANS-6516
Project: NetBeans
Issue Type: Bug
Components: platform - Autoupdate
Affects Versions: NB13
Reporter: Svatopluk Dedic
The *--disable* option should disable the mentioned modules, perhaps (because
of possible issues with {*}un{*}loading code from the memory) during the next
IDE run.
However the implementation does not actually generate post-restart files that
would be read by the Updater and does not even force the restart, so in effect
it does nothing.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: 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-6494) Gradle projects reload into memory on project close
[
https://issues.apache.org/jira/browse/NETBEANS-6494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Svatopluk Dedic updated NETBEANS-6494:
--
Component/s: projects - Gradle
Fix Version/s: 14
Affects Version/s: 13
Priority: Critical (was: Major)
> Gradle projects reload into memory on project close
> ---
>
> Key: NETBEANS-6494
> URL: https://issues.apache.org/jira/browse/NETBEANS-6494
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Gradle
>Affects Versions: 13
>Reporter: Svatopluk Dedic
>Assignee: Svatopluk Dedic
>Priority: Critical
> Fix For: 14
>
>
> When / after a gradle project is closed (I used File | Close All Projects)
> various UI-based refreshes cause the project(s) to be reloaded back into the
> memory.
> I've capture two stacktraces:
>
> {code:java}
> java.lang.Exception
> at
> org.netbeans.modules.project.ui.problems.BrokenProjectAnnotator.propertyChange(BrokenProjectAnnotator.java:183)
> at
> java.desktop/java.beans.PropertyChangeSupport.fire(PropertyChangeSupport.java:343)
> at
> java.desktop/java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:335)
> at
> java.desktop/java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:268)
> at
> org.netbeans.spi.project.ui.support.UILookupMergerSupport$ProjectProblemsProviderImpl.propertyChange(UILookupMergerSupport.java:283)
> at
> org.openide.util.WeakListenerImpl$PropertyChange.propertyChange(WeakListenerImpl.java:190)
> at
> java.desktop/java.beans.PropertyChangeSupport.fire(PropertyChangeSupport.java:343)
> at
> java.desktop/java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:335)
> at
> java.desktop/java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:268)
> at
> org.netbeans.modules.gradle.java.GradleJavaProjectProblemProvider.lambda$new$0(GradleJavaProjectProblemProvider.java:47)
> at
> java.desktop/java.beans.PropertyChangeSupport.fire(PropertyChangeSupport.java:343)
> at
> java.desktop/java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:335)
> at
> java.desktop/java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:268)
> at
> org.netbeans.modules.gradle.api.NbGradleProject.doFireReload(NbGradleProject.java:256)
> at
> org.netbeans.modules.gradle.api.NbGradleProject.access$100(NbGradleProject.java:57)
> at
> org.netbeans.modules.gradle.api.NbGradleProject$AccessorImpl.doFireReload(NbGradleProject.java:166)
> at
> org.netbeans.modules.gradle.NbGradleProjectImpl.loadOwnProject0(NbGradleProjectImpl.java:481)
> at
> org.netbeans.modules.gradle.NbGradleProjectImpl.projectWithQuality(NbGradleProjectImpl.java:277)
> at
> org.netbeans.modules.gradle.NbGradleProjectImpl.getGradleProject(NbGradleProjectImpl.java:193)
> at
> org.netbeans.modules.gradle.api.NbGradleProject.projectLookup(NbGradleProject.java:186)
> at
> org.netbeans.modules.gradle.java.api.GradleJavaProject.get(GradleJavaProject.java:125)
> at
> org.netbeans.modules.gradle.java.queries.GradleSourceForBinary$Res.getRoots(GradleSourceForBinary.java:146)
> at
> org.netbeans.api.java.queries.SourceForBinaryQuery$Result2.getRoots(SourceForBinaryQuery.java:173)
> at
> org.netbeans.modules.java.api.common.classpath.ModuleClassPaths$ModuleInfoClassPathImplementation.lambda$collectProjectSourceRoots$25(ModuleClassPaths.java:1158)
> at
> java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183)
> at
> java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:197)
> at
> java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1625)
> at
> java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:509)
> at
> java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:499)
> at
> java.base/java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:150)
> at
> java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:173)
> at
> java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at
> java.base/java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:596)
> at
> org.netbeans.modules.java.api.common.classpath.ModuleClassPaths$ModuleInfoClassPathImplementation.collectProjectSourceRoots(ModuleClassPaths.java:1155)
> at
> org.netbeans.modules.java.api.common.classpath.ModuleClassPaths$ModuleInfoClassPathImplementation.getResources(ModuleClassPaths.java:682)
> at
>
[jira] [Created] (NETBEANS-6494) Gradle projects reload into memory on project close
Svatopluk Dedic created NETBEANS-6494:
-
Summary: Gradle projects reload into memory on project close
Key: NETBEANS-6494
URL: https://issues.apache.org/jira/browse/NETBEANS-6494
Project: NetBeans
Issue Type: Bug
Reporter: Svatopluk Dedic
Assignee: Svatopluk Dedic
When / after a gradle project is closed (I used File | Close All Projects)
various UI-based refreshes cause the project(s) to be reloaded back into the
memory.
I've capture two stacktraces:
{code:java}
java.lang.Exception
at
org.netbeans.modules.project.ui.problems.BrokenProjectAnnotator.propertyChange(BrokenProjectAnnotator.java:183)
at
java.desktop/java.beans.PropertyChangeSupport.fire(PropertyChangeSupport.java:343)
at
java.desktop/java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:335)
at
java.desktop/java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:268)
at
org.netbeans.spi.project.ui.support.UILookupMergerSupport$ProjectProblemsProviderImpl.propertyChange(UILookupMergerSupport.java:283)
at
org.openide.util.WeakListenerImpl$PropertyChange.propertyChange(WeakListenerImpl.java:190)
at
java.desktop/java.beans.PropertyChangeSupport.fire(PropertyChangeSupport.java:343)
at
java.desktop/java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:335)
at
java.desktop/java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:268)
at
org.netbeans.modules.gradle.java.GradleJavaProjectProblemProvider.lambda$new$0(GradleJavaProjectProblemProvider.java:47)
at
java.desktop/java.beans.PropertyChangeSupport.fire(PropertyChangeSupport.java:343)
at
java.desktop/java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:335)
at
java.desktop/java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:268)
at
org.netbeans.modules.gradle.api.NbGradleProject.doFireReload(NbGradleProject.java:256)
at
org.netbeans.modules.gradle.api.NbGradleProject.access$100(NbGradleProject.java:57)
at
org.netbeans.modules.gradle.api.NbGradleProject$AccessorImpl.doFireReload(NbGradleProject.java:166)
at
org.netbeans.modules.gradle.NbGradleProjectImpl.loadOwnProject0(NbGradleProjectImpl.java:481)
at
org.netbeans.modules.gradle.NbGradleProjectImpl.projectWithQuality(NbGradleProjectImpl.java:277)
at
org.netbeans.modules.gradle.NbGradleProjectImpl.getGradleProject(NbGradleProjectImpl.java:193)
at
org.netbeans.modules.gradle.api.NbGradleProject.projectLookup(NbGradleProject.java:186)
at
org.netbeans.modules.gradle.java.api.GradleJavaProject.get(GradleJavaProject.java:125)
at
org.netbeans.modules.gradle.java.queries.GradleSourceForBinary$Res.getRoots(GradleSourceForBinary.java:146)
at
org.netbeans.api.java.queries.SourceForBinaryQuery$Result2.getRoots(SourceForBinaryQuery.java:173)
at
org.netbeans.modules.java.api.common.classpath.ModuleClassPaths$ModuleInfoClassPathImplementation.lambda$collectProjectSourceRoots$25(ModuleClassPaths.java:1158)
at
java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183)
at
java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:197)
at
java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1625)
at
java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:509)
at
java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:499)
at
java.base/java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:150)
at
java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:173)
at
java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at
java.base/java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:596)
at
org.netbeans.modules.java.api.common.classpath.ModuleClassPaths$ModuleInfoClassPathImplementation.collectProjectSourceRoots(ModuleClassPaths.java:1155)
at
org.netbeans.modules.java.api.common.classpath.ModuleClassPaths$ModuleInfoClassPathImplementation.getResources(ModuleClassPaths.java:682)
at
org.netbeans.api.java.classpath.ClassPath$SPIListener.propertyChange(ClassPath.java:1343)
at
org.openide.util.WeakListenerImpl$PropertyChange.propertyChange(WeakListenerImpl.java:190)
at
java.desktop/java.beans.PropertyChangeSupport.fire(PropertyChangeSupport.java:343)
at
java.desktop/java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:335)
at
java.desktop/java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:268)
at
org.netbeans.modules.java.api.common.classpath.ModuleClassPaths$BaseClassPathImplementation.fire(ModuleClassPaths.java:1378)
at
[jira] [Created] (NETBEANS-6492) Maven should warn, if settings.xml proxy does not match the runtime
Svatopluk Dedic created NETBEANS-6492: - Summary: Maven should warn, if settings.xml proxy does not match the runtime Key: NETBEANS-6492 URL: https://issues.apache.org/jira/browse/NETBEANS-6492 Project: NetBeans Issue Type: Improvement Components: projects - Maven Affects Versions: 13 Reporter: Svatopluk Dedic Maven launched from NetBeans does not respect proxies of the IDE - loads its own settings from the .m2/settings.xml The IDE should: * override this for the maven invocation, passing the proxy that has been configured and/or autodetected by the IDE, or * if that's not possible *warn the user* to correct the settings.xml -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: 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-6491) New NB platform application w/ maven does not offer NB's own release
Svatopluk Dedic created NETBEANS-6491: - Summary: New NB platform application w/ maven does not offer NB's own release Key: NETBEANS-6491 URL: https://issues.apache.org/jira/browse/NETBEANS-6491 Project: NetBeans Issue Type: Bug Components: apisupport - Maven Affects Versions: NB13 Reporter: Svatopluk Dedic I've tried to create NB platform application right after installation and with a fresh userdir. Only *RELEASE90* and *dev-* versions were offered in the New from Template wizard. All releases became available only *after whole central index was downloaded* and indexed. * NetBeans own version should be offered - RELEASE130 in this case as I was using the release binaries downloaded from Apache * Maven project infra should support version queries for a specific g:a even though the central repo is not indexed yet - one can do that using HTTP queries. Would be also useful for completion, too -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: 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-6477) UpToDateStatusProvider is broken for Java, Groovy, Maven hint-related tasks
Svatopluk Dedic created NETBEANS-6477: - Summary: UpToDateStatusProvider is broken for Java, Groovy, Maven hint-related tasks Key: NETBEANS-6477 URL: https://issues.apache.org/jira/browse/NETBEANS-6477 Project: NetBeans Issue Type: Improvement Components: editor - Hints Annotations, groovy - Editor, java - Hints, php - Editor, projects - Maven Reporter: Svatopluk Dedic There is *UpToDateStatusProvider* that ought to report when annotations / decorations for an opened editor are being compujed. But Java hints and CSL hints (= groovy, php, ...) do not implement this interface properly: it contains a stub, which reports "DONE" always. Maven implementation was partially broken and I broke it completely transitioning to Parsing API, so it became the same as Java+CSL. The general idea how to fix that is to provide some SPI / event source from Parsing API that would inform about source(s) being parsed and task(s) being applied on it. Then the Hint infrastructure could convert that to UpToDateStatusProvider that fires PENDING if there are some 'marked' tasks (i.e. by a mixin interface) before the tasks are run and fires DONE after all the tasks finish. // cc: [~jlahoda] -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: 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-6476) ActionItem indexer does not work for project root files
[ https://issues.apache.org/jira/browse/NETBEANS-6476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Svatopluk Dedic updated NETBEANS-6476: -- Issue Type: Bug (was: Improvement) > ActionItem indexer does not work for project root files > --- > > Key: NETBEANS-6476 > URL: https://issues.apache.org/jira/browse/NETBEANS-6476 > Project: NetBeans > Issue Type: Bug > Components: editor - Parsing Indexing, projects - Maven >Reporter: Svatopluk Dedic >Priority: Major > > Tasklist infrastructure was rewritten to use Parsing API in the past, the > [FileScanningWorker|https://github.com/apache/netbeans/blob/master/ide/tasklist.ui/src/org/netbeans/modules/tasklist/impl/FileScanningWorker.java] > is not called from anywhere. But the TaskIndexer is only called for > registered GPR roots, which includes all sources, resources ... but not the > project root itself. > That means that Tasks are not collected from the project buildscript or > definition files, for example. All other folders, not reported through GPR > are ignored as well. > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: 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-6476) ActionItem indexer does not work for project root files
Svatopluk Dedic created NETBEANS-6476: - Summary: ActionItem indexer does not work for project root files Key: NETBEANS-6476 URL: https://issues.apache.org/jira/browse/NETBEANS-6476 Project: NetBeans Issue Type: Improvement Components: editor - Parsing Indexing, projects - Maven Reporter: Svatopluk Dedic Tasklist infrastructure was rewritten to use Parsing API in the past, the [FileScanningWorker|https://github.com/apache/netbeans/blob/master/ide/tasklist.ui/src/org/netbeans/modules/tasklist/impl/FileScanningWorker.java] is not called from anywhere. But the TaskIndexer is only called for registered GPR roots, which includes all sources, resources ... but not the project root itself. That means that Tasks are not collected from the project buildscript or definition files, for example. All other folders, not reported through GPR are ignored as well. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: 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-6347) Adding Global Goal Definitions for Maven is broken for 12.5 + 12.6.
[ https://issues.apache.org/jira/browse/NETBEANS-6347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17476092#comment-17476092 ] Svatopluk Dedic commented on NETBEANS-6347: --- Re. the vacant place - this is reserved for inline help / description of the focused text entry - see the picture: !dialog-hint.jpg! So I would not prefer to remove the area entirely. I made it smaller + gave it less resize weight so when you expand the dialog, other controls will gain more space than this one. > Adding Global Goal Definitions for Maven is broken for 12.5 + 12.6. > --- > > Key: NETBEANS-6347 > URL: https://issues.apache.org/jira/browse/NETBEANS-6347 > Project: NetBeans > Issue Type: Bug > Components: apisupport - Maven >Affects Versions: 12.5, 12.6 >Reporter: Thomas Schapitz >Assignee: Svatopluk Dedic >Priority: Critical > Labels: pull-request-available > Fix For: NB13 > > Attachments: dialog-hint.jpg, image-2021-12-31-10-27-08-275.png, > image-2021-12-31-10-30-58-143.png, image-2022-01-13-19-09-32-623.png, > image-2022-01-13-19-27-19-230.png > > Time Spent: 1h > Remaining Estimate: 0h > > The following hardcopy illustrates the problem. > It *is* possible, to add a new definition, but afterwards, it is no longer > possible to maintain values for the goals & profiles, as has been the case up > to version 12.3 > And it isn't possible to activate the definition, it get's created in > disabled state. (Prior to 12.4, it wasn't possible to disable a definition) > Furthermore, at least on Windows 10 / JDK 17, one may observe, that the > alignment of the buttons with the list is botched, as the last one, "Disable" > gets clipped, because the listbox default hight dictates the length. > !image-2021-12-31-10-30-58-143.png! > > This is how it looked like up to 12.3: > !image-2021-12-31-10-27-08-275.png! > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: 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-6347) Adding Global Goal Definitions for Maven is broken for 12.5 + 12.6.
[ https://issues.apache.org/jira/browse/NETBEANS-6347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Svatopluk Dedic updated NETBEANS-6347: -- Attachment: dialog-hint.jpg > Adding Global Goal Definitions for Maven is broken for 12.5 + 12.6. > --- > > Key: NETBEANS-6347 > URL: https://issues.apache.org/jira/browse/NETBEANS-6347 > Project: NetBeans > Issue Type: Bug > Components: apisupport - Maven >Affects Versions: 12.5, 12.6 >Reporter: Thomas Schapitz >Assignee: Svatopluk Dedic >Priority: Critical > Labels: pull-request-available > Fix For: NB13 > > Attachments: dialog-hint.jpg, image-2021-12-31-10-27-08-275.png, > image-2021-12-31-10-30-58-143.png, image-2022-01-13-19-09-32-623.png, > image-2022-01-13-19-27-19-230.png > > Time Spent: 1h > Remaining Estimate: 0h > > The following hardcopy illustrates the problem. > It *is* possible, to add a new definition, but afterwards, it is no longer > possible to maintain values for the goals & profiles, as has been the case up > to version 12.3 > And it isn't possible to activate the definition, it get's created in > disabled state. (Prior to 12.4, it wasn't possible to disable a definition) > Furthermore, at least on Windows 10 / JDK 17, one may observe, that the > alignment of the buttons with the list is botched, as the last one, "Disable" > gets clipped, because the listbox default hight dictates the length. > !image-2021-12-31-10-30-58-143.png! > > This is how it looked like up to 12.3: > !image-2021-12-31-10-27-08-275.png! > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: 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-6347) Adding Global Goal Definitions for Maven is broken for 12.5 + 12.6.
[ https://issues.apache.org/jira/browse/NETBEANS-6347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17475678#comment-17475678 ] Svatopluk Dedic commented on NETBEANS-6347: --- I just wanted to have reproduction steps and/or the buggy state so I can verify the supposed fix before PR gets merged. Thanks for that and for pointing out the layout issues - I'll look at it. Re. the behaviour - in the first round, it is fixable by enabling 'disable' button just for builtin actions; this was added more or less just override contributed defaults (some plugins may disable some actions which user may not like). I filed the other issue to provide better experience / consistency overall - but that requires to slightly change the APIs and serialization, which I don't want to do just before the branching - so filed an issue to remind me. > Adding Global Goal Definitions for Maven is broken for 12.5 + 12.6. > --- > > Key: NETBEANS-6347 > URL: https://issues.apache.org/jira/browse/NETBEANS-6347 > Project: NetBeans > Issue Type: Bug > Components: apisupport - Maven >Affects Versions: 12.5, 12.6 >Reporter: Thomas Schapitz >Assignee: Svatopluk Dedic >Priority: Critical > Labels: pull-request-available > Fix For: NB13 > > Attachments: image-2021-12-31-10-27-08-275.png, > image-2021-12-31-10-30-58-143.png, image-2022-01-13-19-09-32-623.png, > image-2022-01-13-19-27-19-230.png > > Time Spent: 50m > Remaining Estimate: 0h > > The following hardcopy illustrates the problem. > It *is* possible, to add a new definition, but afterwards, it is no longer > possible to maintain values for the goals & profiles, as has been the case up > to version 12.3 > And it isn't possible to activate the definition, it get's created in > disabled state. (Prior to 12.4, it wasn't possible to disable a definition) > Furthermore, at least on Windows 10 / JDK 17, one may observe, that the > alignment of the buttons with the list is botched, as the last one, "Disable" > gets clipped, because the listbox default hight dictates the length. > !image-2021-12-31-10-30-58-143.png! > > This is how it looked like up to 12.3: > !image-2021-12-31-10-27-08-275.png! > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: 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-6347) Adding Global Goal Definitions for Maven is broken for 12.5 + 12.6.
[
https://issues.apache.org/jira/browse/NETBEANS-6347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17475330#comment-17475330
]
Svatopluk Dedic commented on NETBEANS-6347:
---
Could you please supply a sample of your global action defs ? They are located
in {*}userdir{*}/config/Projects/org-netbeans-modules-maven/nbactions.xml.
The reason for the bug is that *disabled* condition for an action is
represented as *absence* of any goal, which is the default state of any new
action. A proper fix is more complicated - filed NETBEANS-6387 to track the
progress.
The fast fix before NB13 branch point is simply to assume user-defined actions
as always enabled + necessary adjustments in UI.
> Adding Global Goal Definitions for Maven is broken for 12.5 + 12.6.
> ---
>
> Key: NETBEANS-6347
> URL: https://issues.apache.org/jira/browse/NETBEANS-6347
> Project: NetBeans
> Issue Type: Bug
> Components: apisupport - Maven
>Affects Versions: 12.5, 12.6
>Reporter: Thomas Schapitz
>Assignee: Neil C Smith
>Priority: Critical
> Labels: pull-request-available
> Fix For: NB13
>
> Attachments: image-2021-12-31-10-27-08-275.png,
> image-2021-12-31-10-30-58-143.png
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The following hardcopy illustrates the problem.
> It *is* possible, to add a new definition, but afterwards, it is no longer
> possible to maintain values for the goals & profiles, as has been the case up
> to version 12.3
> And it isn't possible to activate the definition, it get's created in
> disabled state. (Prior to 12.4, it wasn't possible to disable a definition)
> Furthermore, at least on Windows 10 / JDK 17, one may observe, that the
> alignment of the buttons with the list is botched, as the last one, "Disable"
> gets clipped, because the listbox default hight dictates the length.
> !image-2021-12-31-10-30-58-143.png!
>
> This is how it looked like up to 12.3:
> !image-2021-12-31-10-27-08-275.png!
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: 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-6347) Adding Global Goal Definitions for Maven is broken for 12.5 + 12.6.
[ https://issues.apache.org/jira/browse/NETBEANS-6347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Svatopluk Dedic reassigned NETBEANS-6347: - Assignee: Svatopluk Dedic (was: Neil C Smith) > Adding Global Goal Definitions for Maven is broken for 12.5 + 12.6. > --- > > Key: NETBEANS-6347 > URL: https://issues.apache.org/jira/browse/NETBEANS-6347 > Project: NetBeans > Issue Type: Bug > Components: apisupport - Maven >Affects Versions: 12.5, 12.6 >Reporter: Thomas Schapitz >Assignee: Svatopluk Dedic >Priority: Critical > Labels: pull-request-available > Fix For: NB13 > > Attachments: image-2021-12-31-10-27-08-275.png, > image-2021-12-31-10-30-58-143.png > > Time Spent: 40m > Remaining Estimate: 0h > > The following hardcopy illustrates the problem. > It *is* possible, to add a new definition, but afterwards, it is no longer > possible to maintain values for the goals & profiles, as has been the case up > to version 12.3 > And it isn't possible to activate the definition, it get's created in > disabled state. (Prior to 12.4, it wasn't possible to disable a definition) > Furthermore, at least on Windows 10 / JDK 17, one may observe, that the > alignment of the buttons with the list is botched, as the last one, "Disable" > gets clipped, because the listbox default hight dictates the length. > !image-2021-12-31-10-30-58-143.png! > > This is how it looked like up to 12.3: > !image-2021-12-31-10-27-08-275.png! > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: 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-6387) Explicit representation of disabled actions, Maven-Gradle consistency
Svatopluk Dedic created NETBEANS-6387: - Summary: Explicit representation of disabled actions, Maven-Gradle consistency Key: NETBEANS-6387 URL: https://issues.apache.org/jira/browse/NETBEANS-6387 Project: NetBeans Issue Type: Improvement Components: projects - Gradle, projects - Maven Affects Versions: 12.5, 12.6 Reporter: Svatopluk Dedic Assignee: Svatopluk Dedic Concept of *disabled* *actions* was introduced primarily as a way how a plugin in a specific *provided* configuration could disable certain predefined actions, bcs they do not make sense in that configuration. The examples are Development mode (continuous build) provided natively by Gradle, and a Development mode that Micronaut plugin provides for Maven: In both cases, *Debug* makes only a little sense, as a change in the source will result in VM restart - this is inconvenient in debug mode to the degree that I/we decided to disable the action by default. As the feature was implemented at the end of the release cycle, the disabled actions are identified by existing action mapping poperties. For gradle it is no task + reload_never, for maven no goals. This is not optimal, as it prevents user from half-defining the actions, complicates new action creation and also mangles action definition so if a (builtin) action is customized, then disabled, and re-enabled, the customizations are gone (or may be gone, if the customized properties are the ones used to indicate disabled status). * The property should be explicit * both Maven | Gradle should allow to disable actions in any (not just non-default) configurations, if possible. * User actions should be allowed to be disabled as well * *Disabled* actions should not be presented in popup goals/tasks submenu on a project // cc: [~lkishalmi] for feature comments -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: 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-6307) Gradle project fails to identify artifact, if loaded by different NB instance
[ https://issues.apache.org/jira/browse/NETBEANS-6307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Svatopluk Dedic updated NETBEANS-6307: -- Labels: VSNetBeans (was: pull-request-available) > Gradle project fails to identify artifact, if loaded by different NB instance > - > > Key: NETBEANS-6307 > URL: https://issues.apache.org/jira/browse/NETBEANS-6307 > Project: NetBeans > Issue Type: Bug > Components: projects - Gradle >Affects Versions: 12.6 >Reporter: Svatopluk Dedic >Assignee: Svatopluk Dedic >Priority: Critical > Labels: VSNetBeans > Time Spent: 10m > Remaining Estimate: 0h > > Gradle projects have two caches. One stored in project, in *.gradle/nbcache* > directory. This cache stores project information and artifact coordinates. > The other cache is in *var/cache/gradle* and stores artfiact paths and for a > binary artifact it registers javadocs and sources. > When a project is primed for the first time, it is fully loaded and those two > caches are populated. Now imagine that the user *deletes* var/cache for some > reason, or starts a new instance of NetBeans. > Since the project already contains cached data and project is not trusted, > it's loaded from the cache to prevent gradle execution in an untrusted source > tree. But - the var/cache/gradle/* global cache *in this instance* of > NetBeans is not populated. > As a result, ModuleDependency objects from GradleConfiguration have proper > coordinates, but list no .jar artifact - even though the artifact is already > downloaded, and gradle daemon/compiler can work with it. > // cc: [~lkishalmi] -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: 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-6305) ProjectManager.find() return null for project dir - race between Git and Projects
[
https://issues.apache.org/jira/browse/NETBEANS-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Svatopluk Dedic updated NETBEANS-6305:
--
Labels: VSNetBeans (was: )
> ProjectManager.find() return null for project dir - race between Git and
> Projects
> -
>
> Key: NETBEANS-6305
> URL: https://issues.apache.org/jira/browse/NETBEANS-6305
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Generic Infrastructure, versioncontrol - Git
>Reporter: Svatopluk Dedic
>Assignee: Jaroslav Tulach
>Priority: Major
> Labels: VSNetBeans
> Attachments: git-project-race-strack.png, git-project-race1.png,
> git-project-race2.png
>
>
> I was trying to write some gradle projects tests using NbModuleSuite – the
> plan was to create a simpel gradle project (just buildscript), then open it
> as a project and inspect.
> To my surprise, calls like FileObject.createAndOpen or
> FileObject.getOuputStream() write (inside FS Atomic Action) resulted in the
> project directory not being recognized at all ! When I tried to debug the
> situation, a stop in the debugger (just a single thread) caused the project
> to be found magically.
> It turned to be a race between Git module (the workdir is created inside the
> source tree managed by git) and the Project system: Git module runs as
> extension to filesystems even inside FS Atomic Action (shown on a pictured
> stacktrace from debugger) and executes {*}FileOwnerQuery{*}{*}.findOwner{*}
> on the to-be-project directory before the buildscript is even created. The
> result of *not being a project* is then cached - and the cache is reset
> asynchronously when/after the project file is created.
> But the test manages to call ProjectManager.findProject sooner, while the
> cache still holds the negative result.
> One of the screenshots shows a debugger that stopped in a situation when the
> script file has been already created (a message in the output window), but
> project manager call invoked *after* the creation does not find a project.
> Uncommenting the m.invoke() line in HACK section will fix the situation -
> caches must be reset.
> The other screenshot is a debugger stopping when the to-be-project directory
> is first inspected, showing that the directory's is yet empty.
> // cc: [~entlicher]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: 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-6308) Spurious exceptions logged in the ide log file
Svatopluk Dedic created NETBEANS-6308:
-
Summary: Spurious exceptions logged in the ide log file
Key: NETBEANS-6308
URL: https://issues.apache.org/jira/browse/NETBEANS-6308
Project: NetBeans
Issue Type: Bug
Components: projects - Gradle
Affects Versions: 12.6
Reporter: Svatopluk Dedic
Assignee: Laszlo Kishalmi
When the IDE is configured to prefer gradle wrapper, it checks whether the
wrapper configuration is present; if not, it logs the following into the log
file:
{code:java}
INFO [org.netbeans.modules.gradle.execute.GradleDistributionProviderImpl]:
Cannot evaulate Gradle Wrapper
java.io.FileNotFoundException: Gradle Wrapper properties not found at:
/space/src/vscode/netbeans/extide/gradle/build/test/unit/work/o.n.m.g.l.D/testInitialLoadProject/projectA/gradle/wrapper/gradle-wrapper.properties
at
org.netbeans.modules.gradle.api.execute.GradleDistributionManager.getWrapperDistributionURI(GradleDistributionManager.java:257)
at
org.netbeans.modules.gradle.api.execute.GradleDistributionManager.distributionFromWrapper(GradleDistributionManager.java:215)
[catch] at
org.netbeans.modules.gradle.execute.GradleDistributionProviderImpl.getGradleDistribution(GradleDistributionProviderImpl.java:106)
at
org.netbeans.modules.gradle.GradleProjectConnection.getConnection(GradleProjectConnection.java:125)
at
org.netbeans.modules.gradle.GradleProjectConnection.action(GradleProjectConnection.java:89)
at
org.netbeans.modules.gradle.loaders.LegacyProjectLoader.createInfoAction(LegacyProjectLoader.java:202)
at
org.netbeans.modules.gradle.loaders.LegacyProjectLoader.retrieveProjectInfo(LegacyProjectLoader.java:250)
at
org.netbeans.modules.gradle.loaders.LegacyProjectLoader.loadGradleProject(LegacyProjectLoader.java:145)
at
org.netbeans.modules.gradle.loaders.LegacyProjectLoader.access$100(LegacyProjectLoader.java:68)
at
org.netbeans.modules.gradle.loaders.LegacyProjectLoader$ProjectLoaderTask.call(LegacyProjectLoader.java:294)
at
org.netbeans.modules.gradle.loaders.LegacyProjectLoader$ProjectLoaderTask.call(LegacyProjectLoader.java:263)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
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)
INFO [org.netbeans.modules.gradle.execute.GradleDistributionProviderImpl]:
Gradle Distribution for Gradle: projectA[FALLBACK] is
GradleDistribution{gradleUserHome=/home/sdedic/.gradle,
distributionDir=/home/sdedic/.gradle/wrapper/dists/gradle-7.3-bin/ddwl0k7mt9g6ak16i1m905vyv/gradle-7.3,
distributionURI=https://services.gradle.org/distributions/gradle-7.3-bin.zip,
version=Gradle 7.3}692331943
{code}
The message should not be probably logged at the INFO level, as it is quite
normal situation and project configuration style (not using wrapper at all).
If the user should be informed (as using wrapper is more reliable, after all),
then a status message or a bubble would be more appropriate.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: 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-6307) Gradle project fails to identify artifact, if loaded by different NB instance
Svatopluk Dedic created NETBEANS-6307: - Summary: Gradle project fails to identify artifact, if loaded by different NB instance Key: NETBEANS-6307 URL: https://issues.apache.org/jira/browse/NETBEANS-6307 Project: NetBeans Issue Type: Bug Components: projects - Gradle Affects Versions: 12.6 Reporter: Svatopluk Dedic Assignee: Svatopluk Dedic Gradle projects have two caches. One stored in project, in *.gradle/nbcache* directory. This cache stores project information and artifact coordinates. The other cache is in *var/cache/gradle* and stores artfiact paths and for a binary artifact it registers javadocs and sources. When a project is primed for the first time, it is fully loaded and those two caches are populated. Now imagine that the user *deletes* var/cache for some reason, or starts a new instance of NetBeans. Since the project already contains cached data and project is not trusted, it's loaded from the cache to prevent gradle execution in an untrusted source tree. But - the var/cache/gradle/* global cache *in this instance* of NetBeans is not populated. As a result, ModuleDependency objects from GradleConfiguration have proper coordinates, but list no .jar artifact - even though the artifact is already downloaded, and gradle daemon/compiler can work with it. // cc: [~lkishalmi] -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: 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-6305) ProjectManager.find() return null for project dir - race between Git and Projects
[
https://issues.apache.org/jira/browse/NETBEANS-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Svatopluk Dedic updated NETBEANS-6305:
--
Attachment: git-project-race-strack.png
> ProjectManager.find() return null for project dir - race between Git and
> Projects
> -
>
> Key: NETBEANS-6305
> URL: https://issues.apache.org/jira/browse/NETBEANS-6305
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Generic Infrastructure, versioncontrol - Git
>Reporter: Svatopluk Dedic
>Assignee: Jaroslav Tulach
>Priority: Major
> Attachments: git-project-race-strack.png, git-project-race1.png,
> git-project-race2.png
>
>
> I was trying to write some gradle projects tests using NbModuleSuite – the
> plan was to create a simpel gradle project (just buildscript), then open it
> as a project and inspect.
> To my surprise, calls like FileObject.createAndOpen or
> FileObject.getOuputStream() write (inside FS Atomic Action) resulted in the
> project directory not being recognized at all ! When I tried to debug the
> situation, a stop in the debugger (just a single thread) caused the project
> to be found magically.
> It turned to be a race between Git module (the workdir is created inside the
> source tree managed by git) and the Project system: Git module runs as
> extension to filesystems even inside FS Atomic Action (shown on a pictured
> stacktrace from debugger) and executes {*}FileOwnerQuery{*}{*}.findOwner{*}
> on the to-be-project directory before the buildscript is even created. The
> result of *not being a project* is then cached - and the cache is reset
> asynchronously when/after the project file is created.
> But the test manages to call ProjectManager.findProject sooner, while the
> cache still holds the negative result.
> One of the screenshots shows a debugger that stopped in a situation when the
> script file has been already created (a message in the output window), but
> project manager call invoked *after* the creation does not find a project.
> Uncommenting the m.invoke() line in HACK section will fix the situation -
> caches must be reset.
> The other screenshot is a debugger stopping when the to-be-project directory
> is first inspected, showing that the directory's is yet empty.
> // cc: [~entlicher]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: 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-6305) ProjectManager.find() return null for project dir - race between Git and Projects
[
https://issues.apache.org/jira/browse/NETBEANS-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Svatopluk Dedic updated NETBEANS-6305:
--
Attachment: git-project-race2.png
> ProjectManager.find() return null for project dir - race between Git and
> Projects
> -
>
> Key: NETBEANS-6305
> URL: https://issues.apache.org/jira/browse/NETBEANS-6305
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Generic Infrastructure, versioncontrol - Git
>Reporter: Svatopluk Dedic
>Assignee: Jaroslav Tulach
>Priority: Major
> Attachments: git-project-race-strack.png, git-project-race1.png,
> git-project-race2.png
>
>
> I was trying to write some gradle projects tests using NbModuleSuite – the
> plan was to create a simpel gradle project (just buildscript), then open it
> as a project and inspect.
> To my surprise, calls like FileObject.createAndOpen or
> FileObject.getOuputStream() write (inside FS Atomic Action) resulted in the
> project directory not being recognized at all ! When I tried to debug the
> situation, a stop in the debugger (just a single thread) caused the project
> to be found magically.
> It turned to be a race between Git module (the workdir is created inside the
> source tree managed by git) and the Project system: Git module runs as
> extension to filesystems even inside FS Atomic Action (shown on a pictured
> stacktrace from debugger) and executes {*}FileOwnerQuery{*}{*}.findOwner{*}
> on the to-be-project directory before the buildscript is even created. The
> result of *not being a project* is then cached - and the cache is reset
> asynchronously when/after the project file is created.
> But the test manages to call ProjectManager.findProject sooner, while the
> cache still holds the negative result.
> One of the screenshots shows a debugger that stopped in a situation when the
> script file has been already created (a message in the output window), but
> project manager call invoked *after* the creation does not find a project.
> Uncommenting the m.invoke() line in HACK section will fix the situation -
> caches must be reset.
> The other screenshot is a debugger stopping when the to-be-project directory
> is first inspected, showing that the directory's is yet empty.
> // cc: [~entlicher]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: 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-6305) ProjectManager.find() return null for project dir - race between Git and Projects
[
https://issues.apache.org/jira/browse/NETBEANS-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17460498#comment-17460498
]
Svatopluk Dedic commented on NETBEANS-6305:
---
I'll add references to the test file here once it is pushed in a PR so the
situation can be inspected, stay tuned.
> ProjectManager.find() return null for project dir - race between Git and
> Projects
> -
>
> Key: NETBEANS-6305
> URL: https://issues.apache.org/jira/browse/NETBEANS-6305
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Generic Infrastructure, versioncontrol - Git
>Reporter: Svatopluk Dedic
>Assignee: Jaroslav Tulach
>Priority: Major
> Attachments: git-project-race1.png
>
>
> I was trying to write some gradle projects tests using NbModuleSuite – the
> plan was to create a simpel gradle project (just buildscript), then open it
> as a project and inspect.
> To my surprise, calls like FileObject.createAndOpen or
> FileObject.getOuputStream() write (inside FS Atomic Action) resulted in the
> project directory not being recognized at all ! When I tried to debug the
> situation, a stop in the debugger (just a single thread) caused the project
> to be found magically.
> It turned to be a race between Git module (the workdir is created inside the
> source tree managed by git) and the Project system: Git module runs as
> extension to filesystems even inside FS Atomic Action (shown on a pictured
> stacktrace from debugger) and executes {*}FileOwnerQuery{*}{*}.findOwner{*}
> on the to-be-project directory before the buildscript is even created. The
> result of *not being a project* is then cached - and the cache is reset
> asynchronously when/after the project file is created.
> But the test manages to call ProjectManager.findProject sooner, while the
> cache still holds the negative result.
> One of the screenshots shows a debugger that stopped in a situation when the
> script file has been already created (a message in the output window), but
> project manager call invoked *after* the creation does not find a project.
> Uncommenting the m.invoke() line in HACK section will fix the situation -
> caches must be reset.
> The other screenshot is a debugger stopping when the to-be-project directory
> is first inspected, showing that the directory's is yet empty.
> // cc: [~entlicher]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: 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-6305) ProjectManager.find() return null for project dir - race between Git and Projects
Svatopluk Dedic created NETBEANS-6305:
-
Summary: ProjectManager.find() return null for project dir - race
between Git and Projects
Key: NETBEANS-6305
URL: https://issues.apache.org/jira/browse/NETBEANS-6305
Project: NetBeans
Issue Type: Bug
Components: projects - Generic Infrastructure, versioncontrol - Git
Reporter: Svatopluk Dedic
Assignee: Jaroslav Tulach
Attachments: git-project-race1.png
I was trying to write some gradle projects tests using NbModuleSuite – the plan
was to create a simpel gradle project (just buildscript), then open it as a
project and inspect.
To my surprise, calls like FileObject.createAndOpen or
FileObject.getOuputStream() write (inside FS Atomic Action) resulted in the
project directory not being recognized at all ! When I tried to debug the
situation, a stop in the debugger (just a single thread) caused the project to
be found magically.
It turned to be a race between Git module (the workdir is created inside the
source tree managed by git) and the Project system: Git module runs as
extension to filesystems even inside FS Atomic Action (shown on a pictured
stacktrace from debugger) and executes {*}FileOwnerQuery{*}{*}.findOwner{*} on
the to-be-project directory before the buildscript is even created. The result
of *not being a project* is then cached - and the cache is reset asynchronously
when/after the project file is created.
But the test manages to call ProjectManager.findProject sooner, while the cache
still holds the negative result.
One of the screenshots shows a debugger that stopped in a situation when the
script file has been already created (a message in the output window), but
project manager call invoked *after* the creation does not find a project.
Uncommenting the m.invoke() line in HACK section will fix the situation -
caches must be reset.
The other screenshot is a debugger stopping when the to-be-project directory is
first inspected, showing that the directory's is yet empty.
// cc: [~entlicher]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: 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-6295) Split j2ee.persistence module into .base and ui / ide part
[ https://issues.apache.org/jira/browse/NETBEANS-6295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Svatopluk Dedic updated NETBEANS-6295: -- Issue Type: Task (was: Bug) > Split j2ee.persistence module into .base and ui / ide part > -- > > Key: NETBEANS-6295 > URL: https://issues.apache.org/jira/browse/NETBEANS-6295 > Project: NetBeans > Issue Type: Task > Components: javaee - Persistence >Affects Versions: 12.5 >Reporter: Svatopluk Dedic >Priority: Major > Labels: VSNetBeans > > The LSP module suffers from huge dependency tree of j2ee.persistence, which > is +- unnecessary for headless operation. > Splitting the module will require a considerable time given the API > compatibility should be preserved at almost all costs. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: 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-6296) Allow to split LSP server module into several cooperating ones
[ https://issues.apache.org/jira/browse/NETBEANS-6296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Svatopluk Dedic updated NETBEANS-6296: -- Issue Type: Task (was: Bug) > Allow to split LSP server module into several cooperating ones > -- > > Key: NETBEANS-6296 > URL: https://issues.apache.org/jira/browse/NETBEANS-6296 > Project: NetBeans > Issue Type: Task > Components: lsp >Affects Versions: 12.5 >Reporter: Svatopluk Dedic >Priority: Major > Labels: VSNetBeans > > The LSP server module is getting bloated and mix even unrelated technologies > in a single module. For example, the Node visualization is rather independent > of projects, building, ...test discovery. Refactoring has only little common > with project action management. Database features are also mostly unrelated > to everything other. Former work on dialogs or progress indication also does > not relate to refactoring | db. > It would be great, if those features would just integrate with the LSP server > and form their own satelite modules that the LSP server distribution would > combine. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: 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-6296) Allow to split LSP server module into several cooperating ones
Svatopluk Dedic created NETBEANS-6296: - Summary: Allow to split LSP server module into several cooperating ones Key: NETBEANS-6296 URL: https://issues.apache.org/jira/browse/NETBEANS-6296 Project: NetBeans Issue Type: Bug Components: lsp Affects Versions: 12.5 Reporter: Svatopluk Dedic The LSP server module is getting bloated and mix even unrelated technologies in a single module. For example, the Node visualization is rather independent of projects, building, ...test discovery. Refactoring has only little common with project action management. Database features are also mostly unrelated to everything other. Former work on dialogs or progress indication also does not relate to refactoring | db. It would be great, if those features would just integrate with the LSP server and form their own satelite modules that the LSP server distribution would combine. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: 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-6295) Split j2ee.persistence module into .base and ui / ide part
Svatopluk Dedic created NETBEANS-6295: - Summary: Split j2ee.persistence module into .base and ui / ide part Key: NETBEANS-6295 URL: https://issues.apache.org/jira/browse/NETBEANS-6295 Project: NetBeans Issue Type: Bug Components: javaee - Persistence Affects Versions: 12.5 Reporter: Svatopluk Dedic The LSP module suffers from huge dependency tree of j2ee.persistence, which is +- unnecessary for headless operation. Splitting the module will require a considerable time given the API compatibility should be preserved at almost all costs. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: 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-6294) FileObject for folder has no presentation Node in its lookup
Svatopluk Dedic created NETBEANS-6294: - Summary: FileObject for folder has no presentation Node in its lookup Key: NETBEANS-6294 URL: https://issues.apache.org/jira/browse/NETBEANS-6294 Project: NetBeans Issue Type: Bug Components: platform - Data Systems Affects Versions: 12.5 Reporter: Svatopluk Dedic ... and DataFolder (and its Node) does not provide FileObject from its Lookup. For details see PR [https://github.com/apache/netbeans/pull/3363] and hacked code in [https://github.com/apache/netbeans/pull/3363/files#diff-8e1f3f0485b58ff61a67f45673d37af218d3bcbb7501d0754b09edb8c5e4fd27R120] The bug is there probably from ancient ages, and need to be fixed carefully so it does not break *subclasses* of DataFolder or *delegates* to folder node that could eventually list the FileObject twice. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: 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-6288) Provide lang-independent API to set per-project preferred connection
Svatopluk Dedic created NETBEANS-6288: - Summary: Provide lang-independent API to set per-project preferred connection Key: NETBEANS-6288 URL: https://issues.apache.org/jira/browse/NETBEANS-6288 Project: NetBeans Issue Type: Improvement Components: db - Code, lsp, php - Editor Reporter: Svatopluk Dedic Assignee: Svatopluk Dedic PHP editor already uses concept of per-project DB connection, LSP could use that as well for Java projects. The "per-project preferred DB connection" should probably move to the core DB module + SPI should be implemented by PHP + Java (maven, gradle ?) to persist the setting within project's metadata somehow. An API should be made for clients to find a DB connection "suitable" for a file (from its project). -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: 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-6283) Create CommandProvider as a supertype of CodeActionsProvider
Svatopluk Dedic created NETBEANS-6283: - Summary: Create CommandProvider as a supertype of CodeActionsProvider Key: NETBEANS-6283 URL: https://issues.apache.org/jira/browse/NETBEANS-6283 Project: NetBeans Issue Type: Improvement Components: lsp Reporter: Svatopluk Dedic The WorkspaceServiceImpl is becoming bloated - I've already implemented some of the commands related to DB separately, but with projects, project actions may become valid commands for LSP and the WorkspaceService would be bloated even more. In addition, different projects may offer different actions, so the interface could possibly support change notification that would cause the client to emit *registerCapability* if the set of commands change. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: 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-6274) Build and Clean Workspace run builds in parallel
Svatopluk Dedic created NETBEANS-6274: - Summary: Build and Clean Workspace run builds in parallel Key: NETBEANS-6274 URL: https://issues.apache.org/jira/browse/NETBEANS-6274 Project: NetBeans Issue Type: Bug Components: lsp Reporter: Svatopluk Dedic When there are more projects in the workspace the build / clean commands are executed in parallel for all projects. The projects are typically either dependent on each other or (worse) in a parent - child relationship. When the build (clean) process happens simultaneously, the independent build process may interfere like create/delete files for each other. This is a real issue for maven, I do not know whether Gradle (running through gradle daemon) is also affected. With parent-child relationship, the parent should be probably processed either alone, or pnly after the child (all children) have been processed. // cc: [~dbalek] -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: 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-6266) Stabilize commit-validation / VerifySimpleTemplatesTest in travis build
Svatopluk Dedic created NETBEANS-6266: - Summary: Stabilize commit-validation / VerifySimpleTemplatesTest in travis build Key: NETBEANS-6266 URL: https://issues.apache.org/jira/browse/NETBEANS-6266 Project: NetBeans Issue Type: Bug Components: ide - Code Reporter: Svatopluk Dedic The *VerifySimpleTemplatesTest* is failing on CI, but typically succeeds when running locally. Should be fixed soon as Travis *commit-validation* job fails. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: 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-6262) IDE shoulld print a warning if it chooses different Gradle distribution than configured
[
https://issues.apache.org/jira/browse/NETBEANS-6262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Svatopluk Dedic reassigned NETBEANS-6262:
-
Assignee: Svatopluk Dedic (was: Laszlo Kishalmi)
> IDE shoulld print a warning if it chooses different Gradle distribution than
> configured
> ---
>
> Key: NETBEANS-6262
> URL: https://issues.apache.org/jira/browse/NETBEANS-6262
> Project: NetBeans
> Issue Type: Improvement
> Components: projects - Gradle
>Reporter: Svatopluk Dedic
>Assignee: Svatopluk Dedic
>Priority: Major
>
> The gradle implementation may choose a different Gradle than configure in the
> project's *gradle-wrapper.properties* in case the distribution is not
> compatible with the runtime JDK that should run the gradle daemon.
> This may lead to unexpected situations, like version conflict between a
> gradle plugin and gradle core, such as this:
> {code:java}
> FINE [org.netbeans.modules.gradle.loaders.LegacyProjectLoader]: Failed to
> retrieve project information for:
> /space/src/vscode/scratch/micronaut-jdbc-repository
> org.gradle.api.ProjectConfigurationException: A problem occurred configuring
> root project 'micronautguide'.
> at
> org.gradle.configuration.project.LifecycleProjectEvaluator.wrapException(LifecycleProjectEvaluator.java:75)
> at
> org.gradle.configuration.project.LifecycleProjectEvaluator.addConfigurationFailure(LifecycleProjectEvaluator.java:68)
> at
> org.gradle.configuration.project.LifecycleProjectEvaluator.access$400(LifecycleProjectEvaluator.java:51)
> ...
> Caused by: java.lang.IllegalStateException: The value for task ':test'
> property 'testFrameworkProperty' is final and cannot be changed any further.
> at
> org.gradle.api.internal.provider.AbstractProperty$FinalizedValue.beforeMutate(AbstractProperty.java:489)
> at
> org.gradle.api.internal.provider.AbstractProperty.assertCanMutate(AbstractProperty.java:263)
> at
> org.gradle.api.internal.provider.AbstractProperty.setSupplier(AbstractProperty.java:212)
> at
> org.gradle.api.internal.provider.DefaultProperty.set(DefaultProperty.java:71)
> at org.gradle.api.tasks.testing.Test.useTestFramework(Test.java:979)
> at org.gradle.api.tasks.testing.Test.useJUnitPlatform(Test.java:1049)
> at org.gradle.api.tasks.testing.Test.useJUnitPlatform(Test.java:1032)
> at
> io.micronaut.gradle.MicronautLibraryPlugin.lambda$null$1(MicronautLibraryPlugin.java:103)
> {code}
> Apparently the plugin works OK with gradle 7.2 that the project uses, but
> fails with gradle 7.3 because of some incompatible change in gradle.
> The IDE should *at least* print a warning message. I would even recommend to
> provide a setting that would {*}fail the build{*}, if such incompatibility is
> found.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: 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-6262) IDE shoulld print a warning if it chooses different Gradle distribution than configured
[
https://issues.apache.org/jira/browse/NETBEANS-6262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17453150#comment-17453150
]
Svatopluk Dedic commented on NETBEANS-6262:
---
Great - then assigning to myself :) to properly report over LSP again.
> IDE shoulld print a warning if it chooses different Gradle distribution than
> configured
> ---
>
> Key: NETBEANS-6262
> URL: https://issues.apache.org/jira/browse/NETBEANS-6262
> Project: NetBeans
> Issue Type: Improvement
> Components: projects - Gradle
>Reporter: Svatopluk Dedic
>Assignee: Laszlo Kishalmi
>Priority: Major
>
> The gradle implementation may choose a different Gradle than configure in the
> project's *gradle-wrapper.properties* in case the distribution is not
> compatible with the runtime JDK that should run the gradle daemon.
> This may lead to unexpected situations, like version conflict between a
> gradle plugin and gradle core, such as this:
> {code:java}
> FINE [org.netbeans.modules.gradle.loaders.LegacyProjectLoader]: Failed to
> retrieve project information for:
> /space/src/vscode/scratch/micronaut-jdbc-repository
> org.gradle.api.ProjectConfigurationException: A problem occurred configuring
> root project 'micronautguide'.
> at
> org.gradle.configuration.project.LifecycleProjectEvaluator.wrapException(LifecycleProjectEvaluator.java:75)
> at
> org.gradle.configuration.project.LifecycleProjectEvaluator.addConfigurationFailure(LifecycleProjectEvaluator.java:68)
> at
> org.gradle.configuration.project.LifecycleProjectEvaluator.access$400(LifecycleProjectEvaluator.java:51)
> ...
> Caused by: java.lang.IllegalStateException: The value for task ':test'
> property 'testFrameworkProperty' is final and cannot be changed any further.
> at
> org.gradle.api.internal.provider.AbstractProperty$FinalizedValue.beforeMutate(AbstractProperty.java:489)
> at
> org.gradle.api.internal.provider.AbstractProperty.assertCanMutate(AbstractProperty.java:263)
> at
> org.gradle.api.internal.provider.AbstractProperty.setSupplier(AbstractProperty.java:212)
> at
> org.gradle.api.internal.provider.DefaultProperty.set(DefaultProperty.java:71)
> at org.gradle.api.tasks.testing.Test.useTestFramework(Test.java:979)
> at org.gradle.api.tasks.testing.Test.useJUnitPlatform(Test.java:1049)
> at org.gradle.api.tasks.testing.Test.useJUnitPlatform(Test.java:1032)
> at
> io.micronaut.gradle.MicronautLibraryPlugin.lambda$null$1(MicronautLibraryPlugin.java:103)
> {code}
> Apparently the plugin works OK with gradle 7.2 that the project uses, but
> fails with gradle 7.3 because of some incompatible change in gradle.
> The IDE should *at least* print a warning message. I would even recommend to
> provide a setting that would {*}fail the build{*}, if such incompatibility is
> found.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: 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-6262) IDE shoulld print a warning if it chooses different Gradle distribution than configured
Svatopluk Dedic created NETBEANS-6262:
-
Summary: IDE shoulld print a warning if it chooses different
Gradle distribution than configured
Key: NETBEANS-6262
URL: https://issues.apache.org/jira/browse/NETBEANS-6262
Project: NetBeans
Issue Type: Improvement
Components: projects - Gradle
Reporter: Svatopluk Dedic
Assignee: Laszlo Kishalmi
The gradle implementation may choose a different Gradle than configure in the
project's *gradle-wrapper.properties* in case the distribution is not
compatible with the runtime JDK that should run the gradle daemon.
This may lead to unexpected situations, like version conflict between a gradle
plugin and gradle core, such as this:
{code:java}
FINE [org.netbeans.modules.gradle.loaders.LegacyProjectLoader]: Failed to
retrieve project information for:
/space/src/vscode/scratch/micronaut-jdbc-repository
org.gradle.api.ProjectConfigurationException: A problem occurred configuring
root project 'micronautguide'.
at
org.gradle.configuration.project.LifecycleProjectEvaluator.wrapException(LifecycleProjectEvaluator.java:75)
at
org.gradle.configuration.project.LifecycleProjectEvaluator.addConfigurationFailure(LifecycleProjectEvaluator.java:68)
at
org.gradle.configuration.project.LifecycleProjectEvaluator.access$400(LifecycleProjectEvaluator.java:51)
...
Caused by: java.lang.IllegalStateException: The value for task ':test' property
'testFrameworkProperty' is final and cannot be changed any further.
at
org.gradle.api.internal.provider.AbstractProperty$FinalizedValue.beforeMutate(AbstractProperty.java:489)
at
org.gradle.api.internal.provider.AbstractProperty.assertCanMutate(AbstractProperty.java:263)
at
org.gradle.api.internal.provider.AbstractProperty.setSupplier(AbstractProperty.java:212)
at
org.gradle.api.internal.provider.DefaultProperty.set(DefaultProperty.java:71)
at org.gradle.api.tasks.testing.Test.useTestFramework(Test.java:979)
at org.gradle.api.tasks.testing.Test.useJUnitPlatform(Test.java:1049)
at org.gradle.api.tasks.testing.Test.useJUnitPlatform(Test.java:1032)
at
io.micronaut.gradle.MicronautLibraryPlugin.lambda$null$1(MicronautLibraryPlugin.java:103)
{code}
Apparently the plugin works OK with gradle 7.2 that the project uses, but fails
with gradle 7.3 because of some incompatible change in gradle.
The IDE should *at least* print a warning message. I would even recommend to
provide a setting that would {*}fail the build{*}, if such incompatibility is
found.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: 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-6261) Project load errors should be transmitted to LSP clients
Svatopluk Dedic created NETBEANS-6261:
-
Summary: Project load errors should be transmitted to LSP clients
Key: NETBEANS-6261
URL: https://issues.apache.org/jira/browse/NETBEANS-6261
Project: NetBeans
Issue Type: Improvement
Components: lsp, projects - Gradle
Affects Versions: 12.5
Reporter: Svatopluk Dedic
Assignee: Svatopluk Dedic
java/LSP server attempts to 'prime' the gradle project so NB can construct a
classpath and can answer LSP client questions. If the project loading fails for
some reason - e.g. misconfiguration or build plugin error, only a generic
message ("project has problems") will appear in LSP client and the remedy
action is - run priming build (which fails again).
An appropriate action is to report the problem to the user.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: 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-6260) Implement detailed login for gradle daemon / tools API interaction
Svatopluk Dedic created NETBEANS-6260: - Summary: Implement detailed login for gradle daemon / tools API interaction Key: NETBEANS-6260 URL: https://issues.apache.org/jira/browse/NETBEANS-6260 Project: NetBeans Issue Type: Task Components: projects - Gradle Affects Versions: 12.5 Reporter: Svatopluk Dedic Assignee: Svatopluk Dedic We have occasional reports that the project classpaths cannot be set up properly, but the issue could not be usually reproduced on dev machines - some environment influence is suspected, but never confirmed. The interaction between gradle pluign, gradle tooling and gradle daemon is not logged with enough details - there should be a way how to inspect real runtime values of environment, paths, whatever affects the selection of a specific Gradle version or the gradle builder startup. Also logging from the tooling plugin, when it inspects gradle's data structures would be helpful. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: 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-6245) MySQL driver does not work out of the box
[
https://issues.apache.org/jira/browse/NETBEANS-6245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Svatopluk Dedic closed NETBEANS-6245.
-
Resolution: Won't Fix
Does not work, but we cannot distribute GPLv2 binary either. Closing.
> MySQL driver does not work out of the box
> -
>
> Key: NETBEANS-6245
> URL: https://issues.apache.org/jira/browse/NETBEANS-6245
> Project: NetBeans
> Issue Type: Bug
> Components: db - MySQL
>Affects Versions: 12.6
>Reporter: Svatopluk Dedic
>Assignee: Svatopluk Dedic
>Priority: Critical
> Labels: pull-request-available
> Attachments: connect-error.png
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> The db.mysql module provides an entry for MySQL driver, but an attempt to
> connect to a database will result an error (see the attached screenshot).
> The JDBC driver is not shipped with the module (although it IS specified in
> `external/binaries-list`) and the driver's URL is not supplied in mysql
> regitration. In fact, the mysql.xml is provided by a generic DB drivers
> module, but not the MySQL specific one.
> The error printed to the log is
> {code:java}
> java.lang.ClassNotFoundException: com.mysql.cj.jdbc.Driver
> at java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:471)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:588)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
> at java.base/java.lang.Class.forName0(Native Method)
> at java.base/java.lang.Class.forName(Class.java:398)
> at
> org.netbeans.modules.db.explorer.DbDriverManager.getDriver(DbDriverManager.java:205)
> Caused: java.sql.SQLException: Unable to find a suitable driver
> at
> org.netbeans.modules.db.explorer.DbDriverManager.createDriverNotFoundException(DbDriverManager.java:279)
> at
> org.netbeans.modules.db.explorer.DbDriverManager.getDriver(DbDriverManager.java:207)
> at
> org.netbeans.modules.db.explorer.DbDriverManager.getDriverInternal(DbDriverManager.java:241)
> at
> org.netbeans.modules.db.explorer.DbDriverManager.getConnection(DbDriverManager.java:98)
> at
> org.netbeans.modules.db.explorer.DatabaseConnection.doConnect(DatabaseConnection.java:898)
> at
> org.netbeans.modules.db.explorer.DatabaseConnection.access$200(DatabaseConnection.java:78)
> [catch] at
> org.netbeans.modules.db.explorer.DatabaseConnection$3.run(DatabaseConnection.java:963)
> 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)
> INFO [org.netbeans.modules.db.mysql.impl.ConnectManager]:
> org.netbeans.api.db.explorer.DatabaseException: Unable to load JDBC
> Drivercom.mysql.cj.jdbc.Driver
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: 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-6245) MySQL driver does not work out of the box
[
https://issues.apache.org/jira/browse/NETBEANS-6245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Svatopluk Dedic updated NETBEANS-6245:
--
Attachment: connect-error.png
> MySQL driver does not work out of the box
> -
>
> Key: NETBEANS-6245
> URL: https://issues.apache.org/jira/browse/NETBEANS-6245
> Project: NetBeans
> Issue Type: Bug
> Components: db - MySQL
>Affects Versions: 12.6
>Reporter: Svatopluk Dedic
>Assignee: Svatopluk Dedic
>Priority: Critical
> Attachments: connect-error.png
>
>
> The db.mysql module provides an entry for MySQL driver, but an attempt to
> connect to a database will result an error (see the attached screenshot).
> The JDBC driver is not shipped with the module (although it IS specified in
> `external/binaries-list`) and the driver's URL is not supplied in mysql
> regitration. In fact, the mysql.xml is provided by a generic DB drivers
> module, but not the MySQL specific one.
> The error printed to the log is
> {code:java}
> java.lang.ClassNotFoundException: com.mysql.cj.jdbc.Driver
> at java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:471)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:588)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
> at java.base/java.lang.Class.forName0(Native Method)
> at java.base/java.lang.Class.forName(Class.java:398)
> at
> org.netbeans.modules.db.explorer.DbDriverManager.getDriver(DbDriverManager.java:205)
> Caused: java.sql.SQLException: Unable to find a suitable driver
> at
> org.netbeans.modules.db.explorer.DbDriverManager.createDriverNotFoundException(DbDriverManager.java:279)
> at
> org.netbeans.modules.db.explorer.DbDriverManager.getDriver(DbDriverManager.java:207)
> at
> org.netbeans.modules.db.explorer.DbDriverManager.getDriverInternal(DbDriverManager.java:241)
> at
> org.netbeans.modules.db.explorer.DbDriverManager.getConnection(DbDriverManager.java:98)
> at
> org.netbeans.modules.db.explorer.DatabaseConnection.doConnect(DatabaseConnection.java:898)
> at
> org.netbeans.modules.db.explorer.DatabaseConnection.access$200(DatabaseConnection.java:78)
> [catch] at
> org.netbeans.modules.db.explorer.DatabaseConnection$3.run(DatabaseConnection.java:963)
> 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)
> INFO [org.netbeans.modules.db.mysql.impl.ConnectManager]:
> org.netbeans.api.db.explorer.DatabaseException: Unable to load JDBC
> Drivercom.mysql.cj.jdbc.Driver
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: 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-6245) MySQL driver does not work out of the box
Svatopluk Dedic created NETBEANS-6245:
-
Summary: MySQL driver does not work out of the box
Key: NETBEANS-6245
URL: https://issues.apache.org/jira/browse/NETBEANS-6245
Project: NetBeans
Issue Type: Bug
Components: db - MySQL
Affects Versions: 12.6
Reporter: Svatopluk Dedic
Assignee: Svatopluk Dedic
The db.mysql module provides an entry for MySQL driver, but an attempt to
connect to a database will result an error (see the attached screenshot).
The JDBC driver is not shipped with the module (although it IS specified in
`external/binaries-list`) and the driver's URL is not supplied in mysql
regitration. In fact, the mysql.xml is provided by a generic DB drivers module,
but not the MySQL specific one.
The error printed to the log is
{code:java}
java.lang.ClassNotFoundException: com.mysql.cj.jdbc.Driver
at java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:471)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:588)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
at java.base/java.lang.Class.forName0(Native Method)
at java.base/java.lang.Class.forName(Class.java:398)
at
org.netbeans.modules.db.explorer.DbDriverManager.getDriver(DbDriverManager.java:205)
Caused: java.sql.SQLException: Unable to find a suitable driver
at
org.netbeans.modules.db.explorer.DbDriverManager.createDriverNotFoundException(DbDriverManager.java:279)
at
org.netbeans.modules.db.explorer.DbDriverManager.getDriver(DbDriverManager.java:207)
at
org.netbeans.modules.db.explorer.DbDriverManager.getDriverInternal(DbDriverManager.java:241)
at
org.netbeans.modules.db.explorer.DbDriverManager.getConnection(DbDriverManager.java:98)
at
org.netbeans.modules.db.explorer.DatabaseConnection.doConnect(DatabaseConnection.java:898)
at
org.netbeans.modules.db.explorer.DatabaseConnection.access$200(DatabaseConnection.java:78)
[catch] at
org.netbeans.modules.db.explorer.DatabaseConnection$3.run(DatabaseConnection.java:963)
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)
INFO [org.netbeans.modules.db.mysql.impl.ConnectManager]:
org.netbeans.api.db.explorer.DatabaseException: Unable to load JDBC
Drivercom.mysql.cj.jdbc.Driver
{code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: 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-6244) StackOverflowError while indexing project
[
https://issues.apache.org/jira/browse/NETBEANS-6244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Svatopluk Dedic reassigned NETBEANS-6244:
-
Assignee: Jan Lahoda
> StackOverflowError while indexing project
> -
>
> Key: NETBEANS-6244
> URL: https://issues.apache.org/jira/browse/NETBEANS-6244
> Project: NetBeans
> Issue Type: Bug
> Components: java - Source
>Affects Versions: 12.6
>Reporter: Svatopluk Dedic
>Assignee: Jan Lahoda
>Priority: Major
>
> During indexing of projects I've noticed a StackTraceError printed to the
> log. I don't know what file causes that.
> The relevant stacktrace part is:
>
> {code:java}
> at
> com.sun.tools.javac.api.JavacTrees$Copier.visitVariable(JavacTrees.java:1177)
> at
> org.netbeans.lib.nbjavac.services.NBJavacTrees$2.visitVariable(NBJavacTrees.java:75)
> at
> com.sun.tools.javac.api.JavacTrees$Copier.visitVariable(JavacTrees.java:1177)
> at
> org.netbeans.lib.nbjavac.services.NBJavacTrees$2.visitVariable(NBJavacTrees.java:75)
> at
> com.sun.tools.javac.api.JavacTrees$Copier.visitVariable(JavacTrees.java:1177)
> at
> org.netbeans.lib.nbjavac.services.NBJavacTrees$2.visitVariable(NBJavacTrees.java:75)
> at
> com.sun.tools.javac.api.JavacTrees$Copier.visitVariable(JavacTrees.java:1177)
> [catch] at
> org.netbeans.lib.nbjavac.services.NBJavacTrees$2.visitVariable(NBJavacTrees.java:75)
> Caused: java.lang.reflect.InvocationTargetException
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> [catch] at
> org.netbeans.modules.java.hints.providers.code.CodeHintProviderImpl$WorkerImpl.createErrors(CodeHintProviderImpl.java:315)
> at
> org.netbeans.modules.java.hints.spiimpl.hints.HintsInvoker.runHint(HintsInvoker.java:794)
> at
> org.netbeans.modules.java.hints.spiimpl.hints.HintsInvoker.doComputeHints(HintsInvoker.java:562)
> at
> org.netbeans.modules.java.hints.spiimpl.hints.HintsInvoker.computeHintsImpl(HintsInvoker.java:282)
> at
> org.netbeans.modules.java.hints.spiimpl.hints.HintsInvoker.computeHints(HintsInvoker.java:227)
> at
> org.netbeans.modules.java.hints.spiimpl.hints.HintsInvoker.computeHints(HintsInvoker.java:192)
> at
> org.netbeans.modules.java.hints.spiimpl.hints.HintsInvoker.computeHints(HintsInvoker.java:165)
> at
> org.netbeans.modules.java.hints.spiimpl.hints.HintsInvoker.computeHints(HintsInvoker.java:127)
> at
> org.netbeans.modules.java.hints.spiimpl.hints.HintsTask.run(HintsTask.java:113)
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: 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-6244) StackOverflowError while indexing project
Svatopluk Dedic created NETBEANS-6244:
-
Summary: StackOverflowError while indexing project
Key: NETBEANS-6244
URL: https://issues.apache.org/jira/browse/NETBEANS-6244
Project: NetBeans
Issue Type: Bug
Components: java - Source
Affects Versions: 12.6
Reporter: Svatopluk Dedic
During indexing of projects I've noticed a StackTraceError printed to the log.
I don't know what file causes that.
The relevant stacktrace part is:
{code:java}
at
com.sun.tools.javac.api.JavacTrees$Copier.visitVariable(JavacTrees.java:1177)
at
org.netbeans.lib.nbjavac.services.NBJavacTrees$2.visitVariable(NBJavacTrees.java:75)
at
com.sun.tools.javac.api.JavacTrees$Copier.visitVariable(JavacTrees.java:1177)
at
org.netbeans.lib.nbjavac.services.NBJavacTrees$2.visitVariable(NBJavacTrees.java:75)
at
com.sun.tools.javac.api.JavacTrees$Copier.visitVariable(JavacTrees.java:1177)
at
org.netbeans.lib.nbjavac.services.NBJavacTrees$2.visitVariable(NBJavacTrees.java:75)
at
com.sun.tools.javac.api.JavacTrees$Copier.visitVariable(JavacTrees.java:1177)
[catch] at
org.netbeans.lib.nbjavac.services.NBJavacTrees$2.visitVariable(NBJavacTrees.java:75)
Caused: java.lang.reflect.InvocationTargetException
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
[catch] at
org.netbeans.modules.java.hints.providers.code.CodeHintProviderImpl$WorkerImpl.createErrors(CodeHintProviderImpl.java:315)
at
org.netbeans.modules.java.hints.spiimpl.hints.HintsInvoker.runHint(HintsInvoker.java:794)
at
org.netbeans.modules.java.hints.spiimpl.hints.HintsInvoker.doComputeHints(HintsInvoker.java:562)
at
org.netbeans.modules.java.hints.spiimpl.hints.HintsInvoker.computeHintsImpl(HintsInvoker.java:282)
at
org.netbeans.modules.java.hints.spiimpl.hints.HintsInvoker.computeHints(HintsInvoker.java:227)
at
org.netbeans.modules.java.hints.spiimpl.hints.HintsInvoker.computeHints(HintsInvoker.java:192)
at
org.netbeans.modules.java.hints.spiimpl.hints.HintsInvoker.computeHints(HintsInvoker.java:165)
at
org.netbeans.modules.java.hints.spiimpl.hints.HintsInvoker.computeHints(HintsInvoker.java:127)
at
org.netbeans.modules.java.hints.spiimpl.hints.HintsTask.run(HintsTask.java:113)
{code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: 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-6117) StackOverflowError when creating Gradle Java EE Web Application.
[ https://issues.apache.org/jira/browse/NETBEANS-6117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Svatopluk Dedic updated NETBEANS-6117: -- Component/s: projects - Gradle > StackOverflowError when creating Gradle Java EE Web Application. > > > Key: NETBEANS-6117 > URL: https://issues.apache.org/jira/browse/NETBEANS-6117 > Project: NetBeans > Issue Type: Bug > Components: projects - Gradle, projects - Gradle Java EE >Affects Versions: 12.5 > Environment: Microsoft Windows 10 Enterprise LTSC 2019 (1809) > OpenJDK Runtime Environment 11.0.12+7 >Reporter: Fox MCCLOUD >Assignee: Laszlo Kishalmi >Priority: Major > Labels: ee, gradle > Attachments: ide-log.log > > > When creating a new Gradle Web Application project with GlassFish 6.1.0, a > background error happens after clicking the 'Finish' button (after server > selection). > Selected server is GlassFish 6.1.0 with Jakarta EE 9. > The exception log is attached. > Tested on both Eclipse Temurin (OpenJDK) 11 and IBM Semeru Runtime (OpenJ9) > 11. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Resolved] (NETBEANS-5330) java.lang.StackOverflowErrorjava.lang.StackOverflowError
[ https://issues.apache.org/jira/browse/NETBEANS-5330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Svatopluk Dedic resolved NETBEANS-5330. --- Resolution: Duplicate > java.lang.StackOverflowErrorjava.lang.StackOverflowError > > > Key: NETBEANS-5330 > URL: https://issues.apache.org/jira/browse/NETBEANS-5330 > Project: NetBeans > Issue Type: Bug >Affects Versions: 12.0, 12.2 >Reporter: Pavel Pagurets >Priority: Major > > java.lang.StackOverflowErrorjava.lang.StackOverflowError at > java.io.UnixFileSystem.getBooleanAttributes0(Native Method) at > java.io.UnixFileSystem.getBooleanAttributes(UnixFileSystem.java:242) at > java.io.File.exists(File.java:819) at > org.apache.lucene.store.FSDirectory.listAll(FSDirectory.java:217) at > org.apache.lucene.store.FSDirectory.listAll(FSDirectory.java:241) at > org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:602) > at > org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:554) > at org.apache.lucene.index.SegmentInfos.read(SegmentInfos.java:359) at > org.apache.lucene.index.IndexReader.indexExists(IndexReader.java:1099) at > org.netbeans.modules.parsing.lucene.LuceneIndex$DirCache.exists(LuceneIndex.java:783) > at > org.netbeans.modules.parsing.lucene.LuceneIndex._doStore(LuceneIndex.java:411) > at > org.netbeans.modules.parsing.lucene.LuceneIndex.txStore(LuceneIndex.java:386) > at > org.netbeans.modules.parsing.lucene.DocumentIndexImpl.storeImpl(DocumentIndexImpl.java:196) > at > org.netbeans.modules.parsing.lucene.DocumentIndexImpl.store(DocumentIndexImpl.java:171) > at > org.netbeans.modules.parsing.lucene.DocumentIndexImpl.addDocument(DocumentIndexImpl.java:108) > at > org.netbeans.modules.parsing.impl.indexing.lucene.LayeredDocumentIndex.addDocument(LayeredDocumentIndex.java:71) > at > org.netbeans.modules.parsing.spi.indexing.support.IndexingSupport.addDocument(IndexingSupport.java:136) > at > org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:222) > at > org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229) > at > org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229) > at > org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229) > at > org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229) > at > org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229) > at > org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229) > at > org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229) > at > org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229) > at > org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229) > at > org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229) > at > org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229) > at > org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229) > at > org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229) > at > org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229) > at > org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229) > at > org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229) > at > org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229) > at > org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229) > at > org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229) > at > org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229) > at > org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229) > at > org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229) > at > org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229) > at > org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229) > at > org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229) > at > org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229) > at > org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229) > at > org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229) > at >
[jira] [Resolved] (NETBEANS-2312) Stackoverflow crash while indexing project
[
https://issues.apache.org/jira/browse/NETBEANS-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Svatopluk Dedic resolved NETBEANS-2312.
---
Resolution: Duplicate
> Stackoverflow crash while indexing project
> --
>
> Key: NETBEANS-2312
> URL: https://issues.apache.org/jira/browse/NETBEANS-2312
> Project: NetBeans
> Issue Type: Bug
>Affects Versions: 10.0
>Reporter: Stefan
>Priority: Major
>
>
> {code:java}
> WARNING [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]
> java.lang.StackOverflowError
> at java.base/java.util.WeakHashMap.getTable(WeakHashMap.java:350)
> at java.base/java.util.WeakHashMap.get(WeakHashMap.java:398)
> at
> org.openide.util.lookup.MetaInfServicesLookup.beforeLookup(MetaInfServicesLookup.java:121)
> at org.openide.util.lookup.AbstractLookup.lookupItem(AbstractLookup.java:402)
> at org.openide.util.lookup.AbstractLookup.lookup(AbstractLookup.java:396)
> at org.openide.util.lookup.ProxyLookup.lookup(ProxyLookup.java:197)
> at
> org.netbeans.modules.javascript2.model.JsElementImpl.isInternalFile(JsElementImpl.java:194)
> at
> org.netbeans.modules.javascript2.model.JsElementImpl.isPlatform(JsElementImpl.java:188)
> at
> org.netbeans.modules.javascript2.model.api.IndexedElement$Flag.getFlag(IndexedElement.java:387)
> at
> org.netbeans.modules.javascript2.editor.index.JsIndexer.createDocument(JsIndexer.java:121)
> at
> org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:221)
> at
> org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229)
> // ...
> at
> org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229)
> at
> org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229)
> [catch] at
> org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229)
> {code}
> I received this right after importing a new project, together with a
> NullPointerException when trying to update the repository:
> {code:java}
> WARNING [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]
> java.lang.NullPointerException
> at
> org.netbeans.modules.javascript2.model.JsObjectImpl.addAssignment(JsObjectImpl.java:272)
> at
> org.netbeans.modules.javascript2.nodejs.editor.model.NodeJsObjectInterceptor.interceptGlobal(NodeJsObjectInterceptor.java:73)
> at
> org.netbeans.modules.javascript2.model.api.Model.getModelVisitor(Model.java:179)
> at
> org.netbeans.modules.javascript2.model.api.Model.getGlobalObject(Model.java:468)
> at
> org.netbeans.modules.javascript2.editor.index.JsIndexer.index(JsIndexer.java:96)
> at
> org.netbeans.modules.parsing.spi.indexing.Indexable$MyAccessor$3.run(Indexable.java:225)
> at
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.runIndexer(RepositoryUpdater.java:275)
> at
> org.netbeans.modules.parsing.spi.indexing.Indexable$MyAccessor.index(Indexable.java:223)
> [catch] at
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work$2.run(RepositoryUpdater.java:3209)
> at
> org.netbeans.modules.parsing.impl.TaskProcessor.callUserTask(TaskProcessor.java:586)
> at
> org.netbeans.modules.parsing.api.ParserManager$UserTaskAction.run(ParserManager.java:130)
> at
> org.netbeans.modules.parsing.api.ParserManager$UserTaskAction.run(ParserManager.java:114)
> at
> org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:181)
> at
> org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:178)
> at
> org.netbeans.modules.masterfs.filebasedfs.utils.FileChangedManager.priorityIO(FileChangedManager.java:153)
> at
> org.netbeans.modules.masterfs.providers.ProvidedExtensions.priorityIO(ProvidedExtensions.java:335)
> at
> org.netbeans.modules.parsing.nb.DataObjectEnvFactory.runPriorityIO(DataObjectEnvFactory.java:118)
> at
> org.netbeans.modules.parsing.impl.Utilities.runPriorityIO(Utilities.java:67)
> at
> org.netbeans.modules.parsing.impl.TaskProcessor.runUserTask(TaskProcessor.java:178)
> at org.netbeans.modules.parsing.api.ParserManager.parse(ParserManager.java:81)
> at
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work.indexEmbedding(RepositoryUpdater.java:3143)
> at
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work.doIndex(RepositoryUpdater.java:2862)
> at
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work.access$800(RepositoryUpdater.java:2154)
> at
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work$1.run(RepositoryUpdater.java:2636)
> at
> org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater$Work$1.run(RepositoryUpdater.java:2634)
> at
> org.netbeans.modules.parsing.impl.indexing.errors.TaskCache.refreshTransaction(TaskCache.java:540)
> at
>
[jira] [Resolved] (NETBEANS-4186) Stackoverflow error during scanning of projects
[
https://issues.apache.org/jira/browse/NETBEANS-4186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Svatopluk Dedic resolved NETBEANS-4186.
---
Resolution: Duplicate
> Stackoverflow error during scanning of projects
> ---
>
> Key: NETBEANS-4186
> URL: https://issues.apache.org/jira/browse/NETBEANS-4186
> Project: NetBeans
> Issue Type: Bug
>Affects Versions: 12.0
> Environment: Windows 10, OpenJDK 13, NetBeans 12.0-beta3
>Reporter: Thomas Kellerer
>Priority: Minor
>
> I have cleared the "cache" subdirectory of my userdir, to force reindexing.
> The background scanning completed and it seems to have worked. However the
> problem reported showed the following exception
> {noformat}
> java.lang.StackOverflowError
> at java.base/java.util.WeakHashMap.getTable(WeakHashMap.java:350)
> at java.base/java.util.WeakHashMap.get(WeakHashMap.java:398)
> at
> org.openide.util.lookup.MetaInfServicesLookup.beforeLookup(MetaInfServicesLookup.java:121)
> at
> org.openide.util.lookup.AbstractLookup.lookupItem(AbstractLookup.java:402)
> at
> org.openide.util.lookup.AbstractLookup.lookup(AbstractLookup.java:396)
> at org.openide.util.lookup.ProxyLookup.lookup(ProxyLookup.java:197)
> at
> org.netbeans.modules.javascript2.model.JsElementImpl.isInternalFile(JsElementImpl.java:194)
> at
> org.netbeans.modules.javascript2.model.JsElementImpl.isPlatform(JsElementImpl.java:188)
> at
> org.netbeans.modules.javascript2.model.api.IndexedElement$Flag.getFlag(IndexedElement.java:387)
> at
> org.netbeans.modules.javascript2.editor.index.JsIndexer.createDocument(JsIndexer.java:121)
> at
> org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:221)
> at
> org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229)
> at
> org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229)
> at
> org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229)
> at
> org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229)
> at
> org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229)
> at
> org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229)
> at
> org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229)
> at
> org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229)
> at
> org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229)
> at
> org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229)
> at
> org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229)
> at
> org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229)
> at
> org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229)
> at
> org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229)
> at
> org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229)
> at
> org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229)
> at
> org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229)
> at
> org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229)
> at
> org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229)
> at
> org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229)
> at
> org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229)
> at
> org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229)
> at
> org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229)
> at
> org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229)
> at
> org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229)
> at
> org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229)
> at
> org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229)
> at
> org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229)
> at
> org.netbeans.modules.javascript2.editor.index.JsIndexer.storeObject(JsIndexer.java:229)
> at
>
[jira] [Created] (NETBEANS-6232) Line number and folding Sidebars may detach from the text view after expand-all
Svatopluk Dedic created NETBEANS-6232: - Summary: Line number and folding Sidebars may detach from the text view after expand-all Key: NETBEANS-6232 URL: https://issues.apache.org/jira/browse/NETBEANS-6232 Project: NetBeans Issue Type: Bug Components: editor - Code folding, editor - Painting Printing Affects Versions: 11.3 Reporter: Svatopluk Dedic Attachments: detach_bug.png This is a long-standing peculiar bug that possibly affects *all versions* of NetBeans platform. It is not reproducible on NetBeans IDE as such (detals later). Consider a structured document, such as XML or JSON, that supports folding. Let's configure autofolding, or have a FoldManager that autofolds all possible lines. When user is viewing such file with autofolded everything, he expands all - and when scrolling down, the sidebars in the editor detach from the text content, stop moving, but the text view is freely scrolled up to the end of the file. See the attached screenshot. The right part is a scrolled contents - line numbers are the same (remain at their positions), but the text content is shifted. The cause of this bug is timing: the sidebars (Glyph gutter, code folding, ...) gets an appropriate *ViewHierarchyChangeEvent* marked as Y-change, and each of them will post an update into EDT. The text component's *preferredSize* property is already computed at the time the hierarchy event is delivered, but the size did not yet materialize in text view's *bounds* or *size.* This will happen after revalidation of the component tree, which has a low priority. At the time the update proceeds, the text the revalidation *still did not occur* sometimes - so these sidebars compute their effective height from *old getSize()* value of the text editor. Only after that the text editor revalidates, and has correct *size* property set from the layout manager. The funny reason why this works in *NetBeans* is that there's an AnnotationSideBar, that what god-knows-why reason multiplies the current size of the editor * 2, so it computes always the preferredSize higher than the screen slot, therefore forcing all other sidebars to be at least that high. Our NB platform-based application has no such mathematician, so the bug surfaced there. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: 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-5638) NbTestCase.assertGC fails with SecurityException
[
https://issues.apache.org/jira/browse/NETBEANS-5638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Svatopluk Dedic updated NETBEANS-5638:
--
Fix Version/s: (was: 12.6)
12.5
> NbTestCase.assertGC fails with SecurityException
>
>
> Key: NETBEANS-5638
> URL: https://issues.apache.org/jira/browse/NETBEANS-5638
> Project: NetBeans
> Issue Type: Bug
> Components: apisupport - Harness
>Affects Versions: 12.4
>Reporter: Svatopluk Dedic
>Assignee: Svatopluk Dedic
>Priority: Major
> Labels: Testing, pull-request-available
> Fix For: 12.5
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> During testing, I've found out that *assertGC* paths to root analysis fails
> with *SecurityException* and does not provide any reasonable results:
> {code:java}
> java.lang.SecurityException: Prohibited package name: java.lang
> at java.lang.ClassLoader.preDefineClass(ClassLoader.java:655)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:754)
> at
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:468)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:74)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:369)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:363)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:362)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:355)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
> at java.lang.Class.getDeclaredMethods0(Native Method)
> at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
> at java.lang.Class.getDeclaredMethods(Class.java:1975)
> at
> org.netbeans.insane.impl.InsaneEngine.recognizeClass(InsaneEngine.java:123)
> {code}
> The exception was thrown, because Insane library queries
> *getDeclaredMethods()* on *org.netbeans.NbInstrumentation* - the whole heap
> traversal then fails, since on JDK8 Module is not loaded from runtime, and an
> attempt to load it from boot.jar fails.
>
--
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-6107) Gradle support does not work when NB/project is JDK17
[ https://issues.apache.org/jira/browse/NETBEANS-6107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17438694#comment-17438694 ] Svatopluk Dedic edited comment on NETBEANS-6107 at 11/4/21, 12:42 PM: -- [~lkishalmi] Initially I throught it could be closed, but we still don't have 7.3 GA, so I'll rather keep it open ... Would you like to upgrade to [https://mvnrepository.com/artifact/org.gradle/gradle-tooling-api/7.3-rc-3] for 12.6 NB release ? was (Author: sdedic): [~lkishalmi] I guess this issue can be closed – or would you like to upgrade to [https://mvnrepository.com/artifact/org.gradle/gradle-tooling-api/7.3-rc-3] for 12.6 NB release ? > Gradle support does not work when NB/project is JDK17 > - > > Key: NETBEANS-6107 > URL: https://issues.apache.org/jira/browse/NETBEANS-6107 > Project: NetBeans > Issue Type: Bug > Components: projects - Gradle >Affects Versions: 12.5 > Environment: macOS, GraalVM JDK17, using Micronaut Gradle project, > generated by wizard. >Reporter: Martin Balin >Assignee: Svata Dedic >Priority: Major > Labels: pull-request-available > Fix For: 12.6 > > Attachments: Screenshot 2021-10-05 at 10.57.02.png > > Time Spent: 2h > Remaining Estimate: 0h > > Opening Gradle based project which uses JDK17 and running NB on JDK17 does > not Resolve Problems when project is open. > It is stuck in this with attached screenshot error. Running Build as command > completes as it uses Gradle 7.2 along with JDK17. > I don't know why JDK16 is referenced, it does not exist on the system and I > also removed all NB user dirs. -- 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-6107) Gradle support does not work when NB/project is JDK17
[ https://issues.apache.org/jira/browse/NETBEANS-6107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17438694#comment-17438694 ] Svatopluk Dedic commented on NETBEANS-6107: --- I guess this issue can be closed – or would you like to upgrade to [https://mvnrepository.com/artifact/org.gradle/gradle-tooling-api/7.3-rc-3] for 12.6 NB release ? > Gradle support does not work when NB/project is JDK17 > - > > Key: NETBEANS-6107 > URL: https://issues.apache.org/jira/browse/NETBEANS-6107 > Project: NetBeans > Issue Type: Bug > Components: projects - Gradle >Affects Versions: 12.5 > Environment: macOS, GraalVM JDK17, using Micronaut Gradle project, > generated by wizard. >Reporter: Martin Balin >Assignee: Svata Dedic >Priority: Major > Labels: pull-request-available > Fix For: 12.6 > > Attachments: Screenshot 2021-10-05 at 10.57.02.png > > Time Spent: 2h > Remaining Estimate: 0h > > Opening Gradle based project which uses JDK17 and running NB on JDK17 does > not Resolve Problems when project is open. > It is stuck in this with attached screenshot error. Running Build as command > completes as it uses Gradle 7.2 along with JDK17. > I don't know why JDK16 is referenced, it does not exist on the system and I > also removed all NB user dirs. -- 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-6107) Gradle support does not work when NB/project is JDK17
[ https://issues.apache.org/jira/browse/NETBEANS-6107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17438694#comment-17438694 ] Svatopluk Dedic edited comment on NETBEANS-6107 at 11/4/21, 12:41 PM: -- [~lkishalmi] I guess this issue can be closed – or would you like to upgrade to [https://mvnrepository.com/artifact/org.gradle/gradle-tooling-api/7.3-rc-3] for 12.6 NB release ? was (Author: sdedic): I guess this issue can be closed – or would you like to upgrade to [https://mvnrepository.com/artifact/org.gradle/gradle-tooling-api/7.3-rc-3] for 12.6 NB release ? > Gradle support does not work when NB/project is JDK17 > - > > Key: NETBEANS-6107 > URL: https://issues.apache.org/jira/browse/NETBEANS-6107 > Project: NetBeans > Issue Type: Bug > Components: projects - Gradle >Affects Versions: 12.5 > Environment: macOS, GraalVM JDK17, using Micronaut Gradle project, > generated by wizard. >Reporter: Martin Balin >Assignee: Svata Dedic >Priority: Major > Labels: pull-request-available > Fix For: 12.6 > > Attachments: Screenshot 2021-10-05 at 10.57.02.png > > Time Spent: 2h > Remaining Estimate: 0h > > Opening Gradle based project which uses JDK17 and running NB on JDK17 does > not Resolve Problems when project is open. > It is stuck in this with attached screenshot error. Running Build as command > completes as it uses Gradle 7.2 along with JDK17. > I don't know why JDK16 is referenced, it does not exist on the system and I > also removed all NB user dirs. -- 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-6171) GraalSDK ScriptEngine throws ClassCast instead of returning null
[
https://issues.apache.org/jira/browse/NETBEANS-6171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Svatopluk Dedic reassigned NETBEANS-6171:
-
Assignee: Svatopluk Dedic
> GraalSDK ScriptEngine throws ClassCast instead of returning null
>
>
> Key: NETBEANS-6171
> URL: https://issues.apache.org/jira/browse/NETBEANS-6171
> Project: NetBeans
> Issue Type: Bug
> Components: ide - Code
>Affects Versions: 12.5
>Reporter: Svatopluk Dedic
>Assignee: Svatopluk Dedic
>Priority: Major
> Labels: pull-request-available
> Fix For: 12.6
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> My code calls
> ScriptEngine eng = ...
> ((Invocable)eng).getInterface(aValue, SomeInterface.class);
> In case of an incompatible 'aValue', the ScriptEngine throws a
> ClassCastException, although it should return just null (" null if the
> requested interface is unavailable").
> This behaviour changed after NB 11.3, and is present in NB 12.5 - should be
> fixed.
--
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-6171) GraalSDK ScriptEngine throws ClassCast instead of returning null
Svatopluk Dedic created NETBEANS-6171:
-
Summary: GraalSDK ScriptEngine throws ClassCast instead of
returning null
Key: NETBEANS-6171
URL: https://issues.apache.org/jira/browse/NETBEANS-6171
Project: NetBeans
Issue Type: Bug
Components: ide - Code
Affects Versions: 12.5
Reporter: Svatopluk Dedic
Fix For: 12.6
My code calls
ScriptEngine eng = ...
((Invocable)eng).getInterface(aValue, SomeInterface.class);
In case of an incompatible 'aValue', the ScriptEngine throws a
ClassCastException, although it should return just null (" null if the
requested interface is unavailable").
This behaviour changed after NB 11.3, and is present in NB 12.5 - should be
fixed.
--
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-6131) Maven cleans up the project although it should delete the contents.
Svatopluk Dedic created NETBEANS-6131: - Summary: Maven cleans up the project although it should delete the contents. Key: NETBEANS-6131 URL: https://issues.apache.org/jira/browse/NETBEANS-6131 Project: NetBeans Issue Type: Bug Components: projects - Maven Affects Versions: 12.5 Reporter: Svatopluk Dedic Assignee: Svatopluk Dedic When the user invokes Project > Delete, the IDE asks if it should just delete the project from the workspace, or delete contents. Even though 'delete contents' checkbox is set, the IDE first calls *mvn clean*, which is IMHO unnecessary. Clean action is questionable even in case of deleting from workspace: why should be the project files cleaned ? -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Resolved] (NETBEANS-5672) Plugin-based service registrations
[ https://issues.apache.org/jira/browse/NETBEANS-5672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Svatopluk Dedic resolved NETBEANS-5672. --- Resolution: Fixed Accidentally implemented as part of [https://github.com/apache/netbeans/pull/2948] for 12.5 > Plugin-based service registrations > -- > > Key: NETBEANS-5672 > URL: https://issues.apache.org/jira/browse/NETBEANS-5672 > Project: NetBeans > Issue Type: Improvement > Components: projects - Maven >Reporter: Svatopluk Dedic >Assignee: Svatopluk Dedic >Priority: Major > Fix For: 12.5 > > > Maven projects should support registrations of services / providers per > plugin, similar to Gradle. While it is possible to register a > *ProjectServiceProvider*, then query the maven project for a list of plugins, > each such provider must monitor the list of plugins and adjust the behaviour > appropriately. > Still the plugins used in the project are known and the maven core model > level, so this filter can be implemented centraly, by the maven core module. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Resolved] (NETBEANS-5732) Profiler not working with Maven Project when installed in path-with-spaces
[
https://issues.apache.org/jira/browse/NETBEANS-5732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Svatopluk Dedic resolved NETBEANS-5732.
---
Resolution: Fixed
Was fixed for 12.5 by https://github.com/apache/netbeans/pull/3099
> Profiler not working with Maven Project when installed in path-with-spaces
> --
>
> Key: NETBEANS-5732
> URL: https://issues.apache.org/jira/browse/NETBEANS-5732
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Maven
>Affects Versions: 12.4
>Reporter: Peter Hull
>Assignee: Svatopluk Dedic
>Priority: Major
> Fix For: 12.5
>
> Attachments: IDE_log.txt, nbactions.xml
>
>
> Profiler does not start when attempting to profile a Swing app using a maven
> project on MacOS.
> Expected: profiler does start
> Actual: Shows an error in the output tab, given below:
> {{cd /Users/peterhull/Projects/mavenproject2;
> JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk-11.jdk/Contents/Home
> "/Applications/NetBeans/Apache NetBeans
> 12.4.app/Contents/Resources/NetBeans/netbeans/java/maven/bin/mvn"
> "-Dexec.vmArgs='-agentpath:}}
> {{'/Applications/NetBeans/Apache NetBeans
> 12.4.app/Contents/Resources/NetBeans/netbeans/profiler/lib/deployed/jdk16/mac/libprofilerinterface.jnilib\\'=}}
> {{'/Applications/NetBeans/Apache NetBeans
> 12.4.app/Contents/Resources/NetBeans/netbeans/profiler/lib}}
> {{',5140,10' -XX:+HeapDumpOnOutOfMemoryError
> '-XX:HeapDumpPath=/Users/peterhull/Library/Caches/NetBeans/12.4/mavencachedirs/1004131909/org-netbeans-modules-profiler
> '" "-Dexec.args=${exec.vmArgs} -classpath %classpath ${exec.mainClass}
> ${exec.appArgs}" -Dexec.mainClass=com.nowhere.mavenproject2.NewJFrame
> -Dexec.executable=/Library/Java/JavaVirtualMachines/jdk-11.jdk/Contents/Home/bin/java
> "-Dprofiler.jvmargs.all= -XX:+HeapDumpOnOutOfMemoryError
> -XX:HeapDumpPath=/Users/peterhull/Library/Caches/NetBeans/12.4/mavencachedirs/1004131909/org-netbeans-modules-profiler
> -agentpath:'/Applications/NetBeans/Apache NetBeans
> 12.4.app/Contents/Resources/NetBeans/netbeans/profiler/lib/deployed/jdk16/mac/libprofilerinterface.jnilib'='/Applications/NetBeans/Apache
> NetBeans
> 12.4.app/Contents/Resources/NetBeans/netbeans/profiler/lib',5140,10"
> "-Dprofiler.jvmargs.arg1=-agentpath:'/Applications/NetBeans/Apache NetBeans
> 12.4.app/Contents/Resources/NetBeans/netbeans/profiler/lib/deployed/jdk16/mac/libprofilerinterface.jnilib'='/Applications/NetBeans/Apache
> NetBeans
> 12.4.app/Contents/Resources/NetBeans/netbeans/profiler/lib',5140,10"
> -Dprofiler.jvmargs.arg2=-XX:HeapDumpPath=/Users/peterhull/Library/Caches/NetBeans/12.4/mavencachedirs/1004131909/org-netbeans-modules-profiler
> -Dprofiler.jvmargs.arg3=-XX:+HeapDumpOnOutOfMemoryError -Dexec.appArgs=
> org.codehaus.mojo:exec-maven-plugin:3.0.0:exec}}
> {{ Running NetBeans Compile On Save execution. Phase execution is skipped and
> output directories of dependency projects (with Compile on Save turned on)
> will be used instead of their jar artifacts.}}
> {{ Scanning for projects...}}{{-<
> com.nowhere:mavenproject2 >--}}
> {{ Building mavenproject2 1.0-SNAPSHOT}}
> {{ [ jar
> ]-}}{{— exec-maven-plugin:3.0.0:exec
> (default-cli) @ mavenproject2 —}}
> {{ Error occurred during initialization of VM}}
> {{ Could not find agent library \/Applications/NetBeans/Apache in absolute
> path, with error: dlopen(\/Applications/NetBeans/Apache, 1): image not found}}
> {{ Command execution failed.}}
> {{ org.apache.commons.exec.ExecuteException: Process exited with an error: 1
> (Exit value: 1)}}
> {{ at org.apache.commons.exec.DefaultExecutor.executeInternal
> (DefaultExecutor.java:404)}}
> {{ at org.apache.commons.exec.DefaultExecutor.execute
> (DefaultExecutor.java:166)}}
> {{ at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:982)}}
> {{ at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:929)}}
> {{ at org.codehaus.mojo.exec.ExecMojo.execute (ExecMojo.java:457)}}
> {{ at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)}}
> {{ at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:210)}}
> {{ at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)}}
> {{ at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)}}
> {{ at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)}}
> {{ at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)}}
> {{ at
>
[jira] [Resolved] (NETBEANS-6106) Stabilize java.gradle unit tests
[ https://issues.apache.org/jira/browse/NETBEANS-6106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Svatopluk Dedic resolved NETBEANS-6106. --- Resolution: Fixed Fixed test code. > Stabilize java.gradle unit tests > > > Key: NETBEANS-6106 > URL: https://issues.apache.org/jira/browse/NETBEANS-6106 > Project: NetBeans > Issue Type: Task > Components: projects - Gradle >Reporter: Svatopluk Dedic >Assignee: Svatopluk Dedic >Priority: Major > Labels: pull-request-available > Fix For: 12.6 > > Time Spent: 10m > Remaining Estimate: 0h > > Java Gradle unit test is constantly failing on CI: > [junit] Test > org.netbeans.modules.gradle.java.execute.JavaExecTokenProviderTest FAILED > See for example https://api.travis-ci.com/v3/job/541430369/log.txt -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Resolved] (NETBEANS-6102) Category Actions can not be opend in project properties for certain Maven Projects
[
https://issues.apache.org/jira/browse/NETBEANS-6102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Svatopluk Dedic resolved NETBEANS-6102.
---
Resolution: Fixed
> Category Actions can not be opend in project properties for certain Maven
> Projects
> --
>
> Key: NETBEANS-6102
> URL: https://issues.apache.org/jira/browse/NETBEANS-6102
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Maven
>Affects Versions: 12.5
> Environment: Windows
> Java 11 and 17
>Reporter: Ronny Perinke
>Assignee: Svatopluk Dedic
>Priority: Critical
> Labels: Regression, maven, pull-request-available
> Fix For: 12.6
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> For Maven Projects of packaging type "pom" (_e.g. the parent in a
> multi-module project_) or "hpi" (_Jenkins plugin_), the menu item "Actions"
> in the project settings can not be opened. A {{NullPointerException}} is
> logged instead.
> This is likely a regression of [commit
> c282a25d5071c1b44de7026a4ceb9d200e161e14|https://github.com/apache/netbeans/commit/c282a25d5071c1b44de7026a4ceb9d200e161e14#diff-a0789b6ea44b9deffb46bc59c2da95e1ab44302f648e02703d521d0ea042398dR201]
> and [PR #3016|https://github.com/apache/netbeans/pull/3016].
> {code:title=NPE in messages.log}
> java.lang.NullPointerException: Cannot invoke
> "org.netbeans.modules.maven.execute.model.NetbeansActionMapping.getGoals()"
> because "am" is null
> at
> org.netbeans.modules.maven.execute.ActionToGoalUtils.isDisabledMapping(ActionToGoalUtils.java:201)
> at
> org.netbeans.modules.maven.customizer.ActionMappings$Renderer.getListCellRendererComponent(ActionMappings.java:1082)
> at
> java.desktop/javax.swing.plaf.basic.BasicListUI.updateLayoutState(BasicListUI.java:1444)
> at
> java.desktop/javax.swing.plaf.basic.BasicListUI.maybeUpdateLayoutState(BasicListUI.java:1394)
> at
> java.desktop/javax.swing.plaf.basic.BasicListUI.getPreferredSize(BasicListUI.java:653)
> at
> java.desktop/javax.swing.JComponent.getPreferredSize(JComponent.java:1725)
> at
> java.desktop/javax.swing.ScrollPaneLayout.layoutContainer(ScrollPaneLayout.java:799)
> at java.desktop/java.awt.Container.layout(Container.java:1541)
> at java.desktop/java.awt.Container.doLayout(Container.java:1530)
> at java.desktop/java.awt.Container.validateTree(Container.java:1725)
> at java.desktop/java.awt.Container.validateTree(Container.java:1734)
> at java.desktop/java.awt.Container.validateTree(Container.java:1734)
> at java.desktop/java.awt.Container.validateTree(Container.java:1734)
> at java.desktop/java.awt.Container.validateTree(Container.java:1734)
> at java.desktop/java.awt.Container.validateTree(Container.java:1734)
> at java.desktop/java.awt.Container.validateTree(Container.java:1734)
> at java.desktop/java.awt.Container.validate(Container.java:1660)
> at
> java.desktop/javax.swing.RepaintManager$3.run(RepaintManager.java:757)
> at
> java.desktop/javax.swing.RepaintManager$3.run(RepaintManager.java:755)
> at
> java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
> at
> java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:86)
> at
> java.desktop/javax.swing.RepaintManager.validateInvalidComponents(RepaintManager.java:754)
> at
> java.desktop/javax.swing.RepaintManager$ProcessingRunnable.run(RepaintManager.java:1897)
> at
> java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:318)
> at
> java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:771)
> at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:722)
> at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:716)
> at
> java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
> at
> java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:86)
> at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:741)
> at
> org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:136)
> [catch] at
> java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
> at
> java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
> at
> java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:117)
> at
> java.desktop/java.awt.WaitDispatchSupport$2.run(WaitDispatchSupport.java:191)
> at
>
[jira] [Resolved] (NETBEANS-5670) MavenActionProviders should contribute configurations
[ https://issues.apache.org/jira/browse/NETBEANS-5670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Svatopluk Dedic resolved NETBEANS-5670. --- Resolution: Fixed Has been implemented by [https://github.com/apache/netbeans/pull/2948] and https://github.com/apache/netbeans/pull/3016 > MavenActionProviders should contribute configurations > - > > Key: NETBEANS-5670 > URL: https://issues.apache.org/jira/browse/NETBEANS-5670 > Project: NetBeans > Issue Type: Improvement > Components: javaee - Micronaut, projects - Maven >Reporter: Svatopluk Dedic >Assignee: Svatopluk Dedic >Priority: Major > Labels: VSNetBeans > Fix For: 12.5 > > > Currently *MavenActionProviders* can only contribute action replacements or > new actions. They can not contribute *configurations*. This could be useful > for plugins like Micronaut, that supports *mn:run* which is a suitable > alternative to *regular* run. It *may* be preferred by some developers, but > should not *replace* and disallow access to the traditional application > launch mode. > -- 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-6068) Groovy broken in 12.5
[ https://issues.apache.org/jira/browse/NETBEANS-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17426193#comment-17426193 ] Svatopluk Dedic commented on NETBEANS-6068: --- Please provide the logiles and the zipped projects. Maven works for me as shown on the pictures, so there must be something in your env and/or project. Also note that Groovy 3.0.8 (used in NB 12.5) does not fully support JDK17 (can't read VM9+ extension attributes in class files), so I'd suggest to keep with some older JDK. Should not have impact on this issue, however. > Groovy broken in 12.5 > - > > Key: NETBEANS-6068 > URL: https://issues.apache.org/jira/browse/NETBEANS-6068 > Project: NetBeans > Issue Type: Bug > Components: groovy - Editor >Affects Versions: 12.5 > Environment: Windows 10 > JDK 17 > >Reporter: Mike >Assignee: Svatopluk Dedic >Priority: Major > Attachments: groovyclassescreated.jpg, > image-2021-10-08-12-57-24-831.png, image-2021-10-08-12-58-24-619.png, > image-2021-10-08-12-59-50-283.png, image-2021-10-08-13-00-25-440.png, > image-2021-10-08-13-01-27-408.png, image-2021-10-08-13-02-31-076.png, > image-2021-10-08-13-03-45-465.png, image-2021-10-08-13-04-54-754.png, > image-2021-10-08-13-05-56-717.png, image-2021-10-08-13-08-23-947.png, > image-2021-10-08-14-13-26-696.png, image-2021-10-08-14-14-41-061.png, > image-2021-10-08-14-16-57-710.png, mavenproject.jpg, sourcecretaed.jpg > > > Easy to replicate. > On a clean install of NB 12.5 using numerous JDK versions. > Install JDK > Install NB 12.5 > Enable Groovy plugin > Create new project > Create 'demo' package space in project > Create new template groovy script in package. > * Fails to create file * > encoding="UTF-8"?> settings 1.0//EN" > "http://www.netbeans.org/dtds/sessionsettings-1_0.dtd;> version="1.0"> class="org.netbeans.modules.jshell.editor.ConsoleEditor"/>ALL > [null]: Class: class org.netbeans.modules.jshell.editor.ConsoleEditorALL > [null]: Source: > MultiFileObject@634c9c14[Windows2Local/Components/JShellEditor.settings]INFO > [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Resolving > dependencies took: 4 msINFO > [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Complete > indexing of 31 binary roots took: 3,452 msINFO > [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Indexing of: > C:\Temp\g4\test took: 2 ms (New or modified files: 0, Deleted files: 0) > [Adding listeners took: 0 ms]INFO > [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Indexing of: > C:\Temp\g4\src took: 215 ms (New or modified files: 0, Deleted files: 0) > [Adding listeners took: 0 ms]INFO > [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Complete > indexing of 2 source roots took: 217 ms (New or modified files: 0, Deleted > files: 0) [Adding listeners took: 0 ms]SEVERE > [global]java.lang.IllegalArgumentException: No folders selected at > org.netbeans.spi.java.project.support.ui.templates.JavaTemplates.createPackageChooser(JavaTemplates.java:95) > at > org.netbeans.spi.java.project.support.ui.templates.JavaTemplates.createPackageChooser(JavaTemplates.java:74) > at > org.netbeans.spi.java.project.support.ui.templates.JavaTemplates.createPackageChooser(JavaTemplates.java:49) > at > org.netbeans.modules.groovy.support.wizard.AbstractFileWizard.createPanels(AbstractFileWizard.java:99) > at > org.netbeans.modules.groovy.support.wizard.AbstractFileWizard.initialize(AbstractFileWizard.java:71) > at > org.netbeans.modules.groovy.support.wizard.AbstractGroovyWizard.initialize(AbstractGroovyWizard.java:61) > > If you click through the error if creates the template script. However, > trying to run the file give this error; > > ant -f C:\\Temp\\g4 -Djavac.includes=demo/newGroovyScript.groovy > -Drun.class=demo.newGroovyScript run-single > init: > Deleting: C:\Temp\g4\build\built-jar.properties > deps-jar: > Updating property file: C:\Temp\g4\build\built-jar.properties > compile-single: > run-single: > Error: Could not find or load main class demo.newGroovyScript > Caused by: java.lang.ClassNotFoundException: demo.newGroovyScript > C:\Temp\g4\nbproject\build-impl.xml:1341: The following error occurred while > executing this line: > C:\Temp\g4\nbproject\build-impl.xml:936: Java returned: 1 > BUILD FAILED (total time: 0 seconds) > > > > -- 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-6068) Groovy broken in 12.5
[
https://issues.apache.org/jira/browse/NETBEANS-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17426175#comment-17426175
]
Svatopluk Dedic commented on NETBEANS-6068:
---
Can you also try with Maven ?
{quote}Java Application, both Ant & Maven
{quote}
> Groovy broken in 12.5
> -
>
> Key: NETBEANS-6068
> URL: https://issues.apache.org/jira/browse/NETBEANS-6068
> Project: NetBeans
> Issue Type: Bug
> Components: groovy - Editor
>Affects Versions: 12.5
> Environment: Windows 10
> JDK 17
>
>Reporter: Mike
>Assignee: Svatopluk Dedic
>Priority: Major
> Attachments: groovyclassescreated.jpg,
> image-2021-10-08-12-57-24-831.png, image-2021-10-08-12-58-24-619.png,
> image-2021-10-08-12-59-50-283.png, image-2021-10-08-13-00-25-440.png,
> image-2021-10-08-13-01-27-408.png, image-2021-10-08-13-02-31-076.png,
> image-2021-10-08-13-03-45-465.png, image-2021-10-08-13-04-54-754.png,
> image-2021-10-08-13-05-56-717.png, image-2021-10-08-13-08-23-947.png,
> mavenproject.jpg, sourcecretaed.jpg
>
>
> Easy to replicate.
> On a clean install of NB 12.5 using numerous JDK versions.
> Install JDK
> Install NB 12.5
> Enable Groovy plugin
> Create new project
> Create 'demo' package space in project
> Create new template groovy script in package.
> * Fails to create file *
> encoding="UTF-8"?> settings 1.0//EN"
> "http://www.netbeans.org/dtds/sessionsettings-1_0.dtd;> version="1.0"> class="org.netbeans.modules.jshell.editor.ConsoleEditor"/>ALL
> [null]: Class: class org.netbeans.modules.jshell.editor.ConsoleEditorALL
> [null]: Source:
> MultiFileObject@634c9c14[Windows2Local/Components/JShellEditor.settings]INFO
> [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Resolving
> dependencies took: 4 msINFO
> [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Complete
> indexing of 31 binary roots took: 3,452 msINFO
> [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Indexing of:
> C:\Temp\g4\test took: 2 ms (New or modified files: 0, Deleted files: 0)
> [Adding listeners took: 0 ms]INFO
> [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Indexing of:
> C:\Temp\g4\src took: 215 ms (New or modified files: 0, Deleted files: 0)
> [Adding listeners took: 0 ms]INFO
> [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Complete
> indexing of 2 source roots took: 217 ms (New or modified files: 0, Deleted
> files: 0) [Adding listeners took: 0 ms]SEVERE
> [global]java.lang.IllegalArgumentException: No folders selected at
> org.netbeans.spi.java.project.support.ui.templates.JavaTemplates.createPackageChooser(JavaTemplates.java:95)
> at
> org.netbeans.spi.java.project.support.ui.templates.JavaTemplates.createPackageChooser(JavaTemplates.java:74)
> at
> org.netbeans.spi.java.project.support.ui.templates.JavaTemplates.createPackageChooser(JavaTemplates.java:49)
> at
> org.netbeans.modules.groovy.support.wizard.AbstractFileWizard.createPanels(AbstractFileWizard.java:99)
> at
> org.netbeans.modules.groovy.support.wizard.AbstractFileWizard.initialize(AbstractFileWizard.java:71)
> at
> org.netbeans.modules.groovy.support.wizard.AbstractGroovyWizard.initialize(AbstractGroovyWizard.java:61)
>
> If you click through the error if creates the template script. However,
> trying to run the file give this error;
>
> ant -f C:\\Temp\\g4 -Djavac.includes=demo/newGroovyScript.groovy
> -Drun.class=demo.newGroovyScript run-single
> init:
> Deleting: C:\Temp\g4\build\built-jar.properties
> deps-jar:
> Updating property file: C:\Temp\g4\build\built-jar.properties
> compile-single:
> run-single:
> Error: Could not find or load main class demo.newGroovyScript
> Caused by: java.lang.ClassNotFoundException: demo.newGroovyScript
> C:\Temp\g4\nbproject\build-impl.xml:1341: The following error occurred while
> executing this line:
> C:\Temp\g4\nbproject\build-impl.xml:936: Java returned: 1
> BUILD FAILED (total time: 0 seconds)
>
>
>
>
--
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-6068) Groovy broken in 12.5
[
https://issues.apache.org/jira/browse/NETBEANS-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17426130#comment-17426130
]
Svatopluk Dedic edited comment on NETBEANS-6068 at 10/8/21, 11:51 AM:
--
What is
{quote}Create 'demo' package space in project
{quote}
?
Please help me to reproduce the defect, as I cannot reproduce it with either
master or the pristine 12.5 release.
* Start NetBeans on the project that does not work, verify the creation still
does not work
* Note the *exact steps* taken from the start of the IDE. If using context
(right-click) actions, note the node / place where it was invoked
* After veryfing the defect exists:
** ZIP the project folder, attach here.
** attach *var/log/messages.log* from your userdir - mainly the startup part,
so I can see what modules were enabled and the runtime config
This is what is happening on my machine:
* maven project created
* demo package created
* wizard started creating Groovy Class (the groovy sources is created during
the wizard)
* source created
No exceptions.
!mavenproject.jpg! !groovyclassescreated.jpg!!sourcecretaed.jpg!
{noformat}
---
>Log Session: Friday, October 8, 2021 1:35:09 PM CEST
>System Info:
Product Version = Apache NetBeans IDE 12.5
Operating System= Linux version 5.0.0-38-generic running on amd64
Java; VM; Vendor= 1.8.0_241; Java HotSpot(TM) 64-Bit Server VM
25.241-b07; Oracle Corporation
Runtime = Java(TM) SE Runtime Environment 1.8.0_241-b07
Java Home = /space/java/jdk1.8.0_241/jre
System Locale; Encoding = en_US (nb); ISO-8859-1
Home Directory = /home/sdedic
Current Directory = /space/apps/nb125
User Directory = /space/tmp/nb125-user
Cache Directory = /space/tmp/nb125-user/var/cache
Installation= /space/apps/nb125/nb{noformat}
was (Author: sdedic):
What is
{quote}Create 'demo' package space in project
{quote}
?
Please help me to reproduce the defect, as I cannot reproduce it with either
master or the pristine 12.5 release.
* Start NetBeans on the project that does not work, verify the creation still
does not work
* Note the *exact steps* taken from the start of the IDE. If using context
(right-click) actions, note the node / place where it was invoked
* After veryfing the defect exists:
** ZIP the project folder, attach here.
** attach *var/log/messages.log* from your userdir - mainly the startup part,
so I can see what modules were enabled and the runtime config
This is what is happening on my machine:
* maven project created
* demo package created
* wizard started creating Groovy Class (the groovy sources is created during
the wizard)
* source created
No exceptions.
!mavenproject.jpg! !groovyclassescreated.jpg!!sourcecretaed.jpg!
> Groovy broken in 12.5
> -
>
> Key: NETBEANS-6068
> URL: https://issues.apache.org/jira/browse/NETBEANS-6068
> Project: NetBeans
> Issue Type: Bug
> Components: groovy - Editor
>Affects Versions: 12.5
> Environment: Windows 10
> JDK 17
>
>Reporter: Mike
>Assignee: Svatopluk Dedic
>Priority: Major
> Attachments: groovyclassescreated.jpg, mavenproject.jpg,
> sourcecretaed.jpg
>
>
> Easy to replicate.
> On a clean install of NB 12.5 using numerous JDK versions.
> Install JDK
> Install NB 12.5
> Enable Groovy plugin
> Create new project
> Create 'demo' package space in project
> Create new template groovy script in package.
> * Fails to create file *
> encoding="UTF-8"?> settings 1.0//EN"
> "http://www.netbeans.org/dtds/sessionsettings-1_0.dtd;> version="1.0"> class="org.netbeans.modules.jshell.editor.ConsoleEditor"/>ALL
> [null]: Class: class org.netbeans.modules.jshell.editor.ConsoleEditorALL
> [null]: Source:
> MultiFileObject@634c9c14[Windows2Local/Components/JShellEditor.settings]INFO
> [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Resolving
> dependencies took: 4 msINFO
> [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Complete
> indexing of 31 binary roots took: 3,452 msINFO
> [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Indexing of:
> C:\Temp\g4\test took: 2 ms (New or modified files: 0, Deleted files: 0)
> [Adding listeners took: 0 ms]INFO
> [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Indexing of:
> C:\Temp\g4\src took: 215 ms (New or modified files: 0, Deleted files: 0)
> [Adding listeners took: 0 ms]INFO
> [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Complete
> indexing of 2 source roots took: 217 ms (New or modified files: 0, Deleted
> files: 0) [Adding listeners took: 0 ms]SEVERE
>
[jira] [Updated] (NETBEANS-6068) Groovy broken in 12.5
[ https://issues.apache.org/jira/browse/NETBEANS-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Svatopluk Dedic updated NETBEANS-6068: -- Attachment: groovyclassescreated.jpg > Groovy broken in 12.5 > - > > Key: NETBEANS-6068 > URL: https://issues.apache.org/jira/browse/NETBEANS-6068 > Project: NetBeans > Issue Type: Bug > Components: groovy - Editor >Affects Versions: 12.5 > Environment: Windows 10 > JDK 17 > >Reporter: Mike >Assignee: Svatopluk Dedic >Priority: Major > Attachments: groovyclassescreated.jpg, mavenproject.jpg, > sourcecretaed.jpg > > > Easy to replicate. > On a clean install of NB 12.5 using numerous JDK versions. > Install JDK > Install NB 12.5 > Enable Groovy plugin > Create new project > Create 'demo' package space in project > Create new template groovy script in package. > * Fails to create file * > encoding="UTF-8"?> settings 1.0//EN" > "http://www.netbeans.org/dtds/sessionsettings-1_0.dtd;> version="1.0"> class="org.netbeans.modules.jshell.editor.ConsoleEditor"/>ALL > [null]: Class: class org.netbeans.modules.jshell.editor.ConsoleEditorALL > [null]: Source: > MultiFileObject@634c9c14[Windows2Local/Components/JShellEditor.settings]INFO > [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Resolving > dependencies took: 4 msINFO > [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Complete > indexing of 31 binary roots took: 3,452 msINFO > [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Indexing of: > C:\Temp\g4\test took: 2 ms (New or modified files: 0, Deleted files: 0) > [Adding listeners took: 0 ms]INFO > [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Indexing of: > C:\Temp\g4\src took: 215 ms (New or modified files: 0, Deleted files: 0) > [Adding listeners took: 0 ms]INFO > [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Complete > indexing of 2 source roots took: 217 ms (New or modified files: 0, Deleted > files: 0) [Adding listeners took: 0 ms]SEVERE > [global]java.lang.IllegalArgumentException: No folders selected at > org.netbeans.spi.java.project.support.ui.templates.JavaTemplates.createPackageChooser(JavaTemplates.java:95) > at > org.netbeans.spi.java.project.support.ui.templates.JavaTemplates.createPackageChooser(JavaTemplates.java:74) > at > org.netbeans.spi.java.project.support.ui.templates.JavaTemplates.createPackageChooser(JavaTemplates.java:49) > at > org.netbeans.modules.groovy.support.wizard.AbstractFileWizard.createPanels(AbstractFileWizard.java:99) > at > org.netbeans.modules.groovy.support.wizard.AbstractFileWizard.initialize(AbstractFileWizard.java:71) > at > org.netbeans.modules.groovy.support.wizard.AbstractGroovyWizard.initialize(AbstractGroovyWizard.java:61) > > If you click through the error if creates the template script. However, > trying to run the file give this error; > > ant -f C:\\Temp\\g4 -Djavac.includes=demo/newGroovyScript.groovy > -Drun.class=demo.newGroovyScript run-single > init: > Deleting: C:\Temp\g4\build\built-jar.properties > deps-jar: > Updating property file: C:\Temp\g4\build\built-jar.properties > compile-single: > run-single: > Error: Could not find or load main class demo.newGroovyScript > Caused by: java.lang.ClassNotFoundException: demo.newGroovyScript > C:\Temp\g4\nbproject\build-impl.xml:1341: The following error occurred while > executing this line: > C:\Temp\g4\nbproject\build-impl.xml:936: Java returned: 1 > BUILD FAILED (total time: 0 seconds) > > > > -- 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-6068) Groovy broken in 12.5
[ https://issues.apache.org/jira/browse/NETBEANS-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Svatopluk Dedic updated NETBEANS-6068: -- Attachment: sourcecretaed.jpg > Groovy broken in 12.5 > - > > Key: NETBEANS-6068 > URL: https://issues.apache.org/jira/browse/NETBEANS-6068 > Project: NetBeans > Issue Type: Bug > Components: groovy - Editor >Affects Versions: 12.5 > Environment: Windows 10 > JDK 17 > >Reporter: Mike >Assignee: Svatopluk Dedic >Priority: Major > Attachments: groovyclassescreated.jpg, mavenproject.jpg, > sourcecretaed.jpg > > > Easy to replicate. > On a clean install of NB 12.5 using numerous JDK versions. > Install JDK > Install NB 12.5 > Enable Groovy plugin > Create new project > Create 'demo' package space in project > Create new template groovy script in package. > * Fails to create file * > encoding="UTF-8"?> settings 1.0//EN" > "http://www.netbeans.org/dtds/sessionsettings-1_0.dtd;> version="1.0"> class="org.netbeans.modules.jshell.editor.ConsoleEditor"/>ALL > [null]: Class: class org.netbeans.modules.jshell.editor.ConsoleEditorALL > [null]: Source: > MultiFileObject@634c9c14[Windows2Local/Components/JShellEditor.settings]INFO > [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Resolving > dependencies took: 4 msINFO > [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Complete > indexing of 31 binary roots took: 3,452 msINFO > [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Indexing of: > C:\Temp\g4\test took: 2 ms (New or modified files: 0, Deleted files: 0) > [Adding listeners took: 0 ms]INFO > [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Indexing of: > C:\Temp\g4\src took: 215 ms (New or modified files: 0, Deleted files: 0) > [Adding listeners took: 0 ms]INFO > [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Complete > indexing of 2 source roots took: 217 ms (New or modified files: 0, Deleted > files: 0) [Adding listeners took: 0 ms]SEVERE > [global]java.lang.IllegalArgumentException: No folders selected at > org.netbeans.spi.java.project.support.ui.templates.JavaTemplates.createPackageChooser(JavaTemplates.java:95) > at > org.netbeans.spi.java.project.support.ui.templates.JavaTemplates.createPackageChooser(JavaTemplates.java:74) > at > org.netbeans.spi.java.project.support.ui.templates.JavaTemplates.createPackageChooser(JavaTemplates.java:49) > at > org.netbeans.modules.groovy.support.wizard.AbstractFileWizard.createPanels(AbstractFileWizard.java:99) > at > org.netbeans.modules.groovy.support.wizard.AbstractFileWizard.initialize(AbstractFileWizard.java:71) > at > org.netbeans.modules.groovy.support.wizard.AbstractGroovyWizard.initialize(AbstractGroovyWizard.java:61) > > If you click through the error if creates the template script. However, > trying to run the file give this error; > > ant -f C:\\Temp\\g4 -Djavac.includes=demo/newGroovyScript.groovy > -Drun.class=demo.newGroovyScript run-single > init: > Deleting: C:\Temp\g4\build\built-jar.properties > deps-jar: > Updating property file: C:\Temp\g4\build\built-jar.properties > compile-single: > run-single: > Error: Could not find or load main class demo.newGroovyScript > Caused by: java.lang.ClassNotFoundException: demo.newGroovyScript > C:\Temp\g4\nbproject\build-impl.xml:1341: The following error occurred while > executing this line: > C:\Temp\g4\nbproject\build-impl.xml:936: Java returned: 1 > BUILD FAILED (total time: 0 seconds) > > > > -- 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-6068) Groovy broken in 12.5
[
https://issues.apache.org/jira/browse/NETBEANS-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17426130#comment-17426130
]
Svatopluk Dedic commented on NETBEANS-6068:
---
What is
{quote}Create 'demo' package space in project
{quote}
?
Please help me to reproduce the defect, as I cannot reproduce it with either
master or the pristine 12.5 release.
* Start NetBeans on the project that does not work, verify the creation still
does not work
* Note the *exact steps* taken from the start of the IDE. If using context
(right-click) actions, note the node / place where it was invoked
* After veryfing the defect exists:
** ZIP the project folder, attach here.
** attach *var/log/messages.log* from your userdir - mainly the startup part,
so I can see what modules were enabled and the runtime config
This is what is happening on my machine:
* maven project created
* demo package created
* wizard started creating Groovy Class (the groovy sources is created during
the wizard)
* source created
No exceptions.
!mavenproject.jpg! !groovyclassescreated.jpg!!sourcecretaed.jpg!
> Groovy broken in 12.5
> -
>
> Key: NETBEANS-6068
> URL: https://issues.apache.org/jira/browse/NETBEANS-6068
> Project: NetBeans
> Issue Type: Bug
> Components: groovy - Editor
>Affects Versions: 12.5
> Environment: Windows 10
> JDK 17
>
>Reporter: Mike
>Assignee: Svatopluk Dedic
>Priority: Major
> Attachments: groovyclassescreated.jpg, mavenproject.jpg,
> sourcecretaed.jpg
>
>
> Easy to replicate.
> On a clean install of NB 12.5 using numerous JDK versions.
> Install JDK
> Install NB 12.5
> Enable Groovy plugin
> Create new project
> Create 'demo' package space in project
> Create new template groovy script in package.
> * Fails to create file *
> encoding="UTF-8"?> settings 1.0//EN"
> "http://www.netbeans.org/dtds/sessionsettings-1_0.dtd;> version="1.0"> class="org.netbeans.modules.jshell.editor.ConsoleEditor"/>ALL
> [null]: Class: class org.netbeans.modules.jshell.editor.ConsoleEditorALL
> [null]: Source:
> MultiFileObject@634c9c14[Windows2Local/Components/JShellEditor.settings]INFO
> [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Resolving
> dependencies took: 4 msINFO
> [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Complete
> indexing of 31 binary roots took: 3,452 msINFO
> [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Indexing of:
> C:\Temp\g4\test took: 2 ms (New or modified files: 0, Deleted files: 0)
> [Adding listeners took: 0 ms]INFO
> [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Indexing of:
> C:\Temp\g4\src took: 215 ms (New or modified files: 0, Deleted files: 0)
> [Adding listeners took: 0 ms]INFO
> [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Complete
> indexing of 2 source roots took: 217 ms (New or modified files: 0, Deleted
> files: 0) [Adding listeners took: 0 ms]SEVERE
> [global]java.lang.IllegalArgumentException: No folders selected at
> org.netbeans.spi.java.project.support.ui.templates.JavaTemplates.createPackageChooser(JavaTemplates.java:95)
> at
> org.netbeans.spi.java.project.support.ui.templates.JavaTemplates.createPackageChooser(JavaTemplates.java:74)
> at
> org.netbeans.spi.java.project.support.ui.templates.JavaTemplates.createPackageChooser(JavaTemplates.java:49)
> at
> org.netbeans.modules.groovy.support.wizard.AbstractFileWizard.createPanels(AbstractFileWizard.java:99)
> at
> org.netbeans.modules.groovy.support.wizard.AbstractFileWizard.initialize(AbstractFileWizard.java:71)
> at
> org.netbeans.modules.groovy.support.wizard.AbstractGroovyWizard.initialize(AbstractGroovyWizard.java:61)
>
> If you click through the error if creates the template script. However,
> trying to run the file give this error;
>
> ant -f C:\\Temp\\g4 -Djavac.includes=demo/newGroovyScript.groovy
> -Drun.class=demo.newGroovyScript run-single
> init:
> Deleting: C:\Temp\g4\build\built-jar.properties
> deps-jar:
> Updating property file: C:\Temp\g4\build\built-jar.properties
> compile-single:
> run-single:
> Error: Could not find or load main class demo.newGroovyScript
> Caused by: java.lang.ClassNotFoundException: demo.newGroovyScript
> C:\Temp\g4\nbproject\build-impl.xml:1341: The following error occurred while
> executing this line:
> C:\Temp\g4\nbproject\build-impl.xml:936: Java returned: 1
> BUILD FAILED (total time: 0 seconds)
>
>
>
>
--
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:
[jira] [Updated] (NETBEANS-6068) Groovy broken in 12.5
[ https://issues.apache.org/jira/browse/NETBEANS-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Svatopluk Dedic updated NETBEANS-6068: -- Attachment: mavenproject.jpg > Groovy broken in 12.5 > - > > Key: NETBEANS-6068 > URL: https://issues.apache.org/jira/browse/NETBEANS-6068 > Project: NetBeans > Issue Type: Bug > Components: groovy - Editor >Affects Versions: 12.5 > Environment: Windows 10 > JDK 17 > >Reporter: Mike >Assignee: Svatopluk Dedic >Priority: Major > Attachments: mavenproject.jpg > > > Easy to replicate. > On a clean install of NB 12.5 using numerous JDK versions. > Install JDK > Install NB 12.5 > Enable Groovy plugin > Create new project > Create 'demo' package space in project > Create new template groovy script in package. > * Fails to create file * > encoding="UTF-8"?> settings 1.0//EN" > "http://www.netbeans.org/dtds/sessionsettings-1_0.dtd;> version="1.0"> class="org.netbeans.modules.jshell.editor.ConsoleEditor"/>ALL > [null]: Class: class org.netbeans.modules.jshell.editor.ConsoleEditorALL > [null]: Source: > MultiFileObject@634c9c14[Windows2Local/Components/JShellEditor.settings]INFO > [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Resolving > dependencies took: 4 msINFO > [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Complete > indexing of 31 binary roots took: 3,452 msINFO > [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Indexing of: > C:\Temp\g4\test took: 2 ms (New or modified files: 0, Deleted files: 0) > [Adding listeners took: 0 ms]INFO > [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Indexing of: > C:\Temp\g4\src took: 215 ms (New or modified files: 0, Deleted files: 0) > [Adding listeners took: 0 ms]INFO > [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Complete > indexing of 2 source roots took: 217 ms (New or modified files: 0, Deleted > files: 0) [Adding listeners took: 0 ms]SEVERE > [global]java.lang.IllegalArgumentException: No folders selected at > org.netbeans.spi.java.project.support.ui.templates.JavaTemplates.createPackageChooser(JavaTemplates.java:95) > at > org.netbeans.spi.java.project.support.ui.templates.JavaTemplates.createPackageChooser(JavaTemplates.java:74) > at > org.netbeans.spi.java.project.support.ui.templates.JavaTemplates.createPackageChooser(JavaTemplates.java:49) > at > org.netbeans.modules.groovy.support.wizard.AbstractFileWizard.createPanels(AbstractFileWizard.java:99) > at > org.netbeans.modules.groovy.support.wizard.AbstractFileWizard.initialize(AbstractFileWizard.java:71) > at > org.netbeans.modules.groovy.support.wizard.AbstractGroovyWizard.initialize(AbstractGroovyWizard.java:61) > > If you click through the error if creates the template script. However, > trying to run the file give this error; > > ant -f C:\\Temp\\g4 -Djavac.includes=demo/newGroovyScript.groovy > -Drun.class=demo.newGroovyScript run-single > init: > Deleting: C:\Temp\g4\build\built-jar.properties > deps-jar: > Updating property file: C:\Temp\g4\build\built-jar.properties > compile-single: > run-single: > Error: Could not find or load main class demo.newGroovyScript > Caused by: java.lang.ClassNotFoundException: demo.newGroovyScript > C:\Temp\g4\nbproject\build-impl.xml:1341: The following error occurred while > executing this line: > C:\Temp\g4\nbproject\build-impl.xml:936: Java returned: 1 > BUILD FAILED (total time: 0 seconds) > > > > -- 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-6068) Groovy broken in 12.5
[ https://issues.apache.org/jira/browse/NETBEANS-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Svatopluk Dedic reassigned NETBEANS-6068: - Assignee: Svatopluk Dedic > Groovy broken in 12.5 > - > > Key: NETBEANS-6068 > URL: https://issues.apache.org/jira/browse/NETBEANS-6068 > Project: NetBeans > Issue Type: Bug > Components: groovy - Editor >Affects Versions: 12.5 > Environment: Windows 10 > JDK 17 > >Reporter: Mike >Assignee: Svatopluk Dedic >Priority: Major > > Easy to replicate. > On a clean install of NB 12.5 using numerous JDK versions. > Install JDK > Install NB 12.5 > Enable Groovy plugin > Create new project > Create 'demo' package space in project > Create new template groovy script in package. > * Fails to create file * > encoding="UTF-8"?> settings 1.0//EN" > "http://www.netbeans.org/dtds/sessionsettings-1_0.dtd;> version="1.0"> class="org.netbeans.modules.jshell.editor.ConsoleEditor"/>ALL > [null]: Class: class org.netbeans.modules.jshell.editor.ConsoleEditorALL > [null]: Source: > MultiFileObject@634c9c14[Windows2Local/Components/JShellEditor.settings]INFO > [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Resolving > dependencies took: 4 msINFO > [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Complete > indexing of 31 binary roots took: 3,452 msINFO > [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Indexing of: > C:\Temp\g4\test took: 2 ms (New or modified files: 0, Deleted files: 0) > [Adding listeners took: 0 ms]INFO > [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Indexing of: > C:\Temp\g4\src took: 215 ms (New or modified files: 0, Deleted files: 0) > [Adding listeners took: 0 ms]INFO > [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Complete > indexing of 2 source roots took: 217 ms (New or modified files: 0, Deleted > files: 0) [Adding listeners took: 0 ms]SEVERE > [global]java.lang.IllegalArgumentException: No folders selected at > org.netbeans.spi.java.project.support.ui.templates.JavaTemplates.createPackageChooser(JavaTemplates.java:95) > at > org.netbeans.spi.java.project.support.ui.templates.JavaTemplates.createPackageChooser(JavaTemplates.java:74) > at > org.netbeans.spi.java.project.support.ui.templates.JavaTemplates.createPackageChooser(JavaTemplates.java:49) > at > org.netbeans.modules.groovy.support.wizard.AbstractFileWizard.createPanels(AbstractFileWizard.java:99) > at > org.netbeans.modules.groovy.support.wizard.AbstractFileWizard.initialize(AbstractFileWizard.java:71) > at > org.netbeans.modules.groovy.support.wizard.AbstractGroovyWizard.initialize(AbstractGroovyWizard.java:61) > > If you click through the error if creates the template script. However, > trying to run the file give this error; > > ant -f C:\\Temp\\g4 -Djavac.includes=demo/newGroovyScript.groovy > -Drun.class=demo.newGroovyScript run-single > init: > Deleting: C:\Temp\g4\build\built-jar.properties > deps-jar: > Updating property file: C:\Temp\g4\build\built-jar.properties > compile-single: > run-single: > Error: Could not find or load main class demo.newGroovyScript > Caused by: java.lang.ClassNotFoundException: demo.newGroovyScript > C:\Temp\g4\nbproject\build-impl.xml:1341: The following error occurred while > executing this line: > C:\Temp\g4\nbproject\build-impl.xml:936: Java returned: 1 > BUILD FAILED (total time: 0 seconds) > > > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Resolved] (NETBEANS-6077) Groovy loads half of Micronaut library on each completion
[ https://issues.apache.org/jira/browse/NETBEANS-6077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Svatopluk Dedic resolved NETBEANS-6077. --- Fix Version/s: 12.6 Resolution: Fixed > Groovy loads half of Micronaut library on each completion > - > > Key: NETBEANS-6077 > URL: https://issues.apache.org/jira/browse/NETBEANS-6077 > Project: NetBeans > Issue Type: Bug > Components: groovy - Editor, javaee - Micronaut >Affects Versions: 12.5 >Reporter: Svatopluk Dedic >Priority: Critical > Labels: pull-request-available > Fix For: 12.6 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > Transformations / visitors are loaded from user project's libraries to > participate on groovy compilation. It seems that classes of those visitors > are loaded for *each parse operation* anew, which makes the parser startup > longer. > Attaching a report (placed Logger.info() in TransformationLoader.findClass()) > - about 570 classes are loaded after each keystroke + parse. > Mitigation step 1: have the loaded classes cached based on set of library > URLs used by the project (cache the parent classloader). > Mitigation step 2: consider to disable InjectTransform etc. from Micronaut ... -- 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-6107) Gradle support does not work when NB/project is JDK17
[ https://issues.apache.org/jira/browse/NETBEANS-6107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Svatopluk Dedic updated NETBEANS-6107: -- Priority: Major (was: Critical) > Gradle support does not work when NB/project is JDK17 > - > > Key: NETBEANS-6107 > URL: https://issues.apache.org/jira/browse/NETBEANS-6107 > Project: NetBeans > Issue Type: Bug > Components: projects - Gradle >Affects Versions: 12.5 > Environment: macOS, GraalVM JDK17, using Micronaut Gradle project, > generated by wizard. >Reporter: Martin Balin >Assignee: Svata Dedic >Priority: Major > Labels: pull-request-available > Fix For: 12.6 > > Attachments: Screenshot 2021-10-05 at 10.57.02.png > > Time Spent: 1h 50m > Remaining Estimate: 0h > > Opening Gradle based project which uses JDK17 and running NB on JDK17 does > not Resolve Problems when project is open. > It is stuck in this with attached screenshot error. Running Build as command > completes as it uses Gradle 7.2 along with JDK17. > I don't know why JDK16 is referenced, it does not exist on the system and I > also removed all NB user dirs. -- 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-6107) Gradle support does not work when NB/project is JDK17
[ https://issues.apache.org/jira/browse/NETBEANS-6107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17426009#comment-17426009 ] Svatopluk Dedic commented on NETBEANS-6107: --- Semi-fixed: Gradle 7.2 distribution is allowed, which makes the IDE load project structure and somehow work. But that does not guarantee the project will actually build with JDK17, as that is officialy *not supported* by Gradle 7.2. We need to update again when Gradle 7.3 comes out + possibly bundle its API. // cc: [~lkishalmi] Lowering priority, hopefully will fix during 12.6 release. > Gradle support does not work when NB/project is JDK17 > - > > Key: NETBEANS-6107 > URL: https://issues.apache.org/jira/browse/NETBEANS-6107 > Project: NetBeans > Issue Type: Bug > Components: projects - Gradle >Affects Versions: 12.5 > Environment: macOS, GraalVM JDK17, using Micronaut Gradle project, > generated by wizard. >Reporter: Martin Balin >Assignee: Svata Dedic >Priority: Critical > Labels: pull-request-available > Fix For: 12.6 > > Attachments: Screenshot 2021-10-05 at 10.57.02.png > > Time Spent: 1h 50m > Remaining Estimate: 0h > > Opening Gradle based project which uses JDK17 and running NB on JDK17 does > not Resolve Problems when project is open. > It is stuck in this with attached screenshot error. Running Build as command > completes as it uses Gradle 7.2 along with JDK17. > I don't know why JDK16 is referenced, it does not exist on the system and I > also removed all NB user dirs. -- 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-6107) Gradle support does not work when NB/project is JDK17
[ https://issues.apache.org/jira/browse/NETBEANS-6107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Svatopluk Dedic updated NETBEANS-6107: -- Fix Version/s: (was: 12.5) 12.6 > Gradle support does not work when NB/project is JDK17 > - > > Key: NETBEANS-6107 > URL: https://issues.apache.org/jira/browse/NETBEANS-6107 > Project: NetBeans > Issue Type: Bug > Components: projects - Gradle >Affects Versions: 12.5 > Environment: macOS, GraalVM JDK17, using Micronaut Gradle project, > generated by wizard. >Reporter: Martin Balin >Assignee: Svata Dedic >Priority: Critical > Labels: pull-request-available > Fix For: 12.6 > > Attachments: Screenshot 2021-10-05 at 10.57.02.png > > Time Spent: 1h 50m > Remaining Estimate: 0h > > Opening Gradle based project which uses JDK17 and running NB on JDK17 does > not Resolve Problems when project is open. > It is stuck in this with attached screenshot error. Running Build as command > completes as it uses Gradle 7.2 along with JDK17. > I don't know why JDK16 is referenced, it does not exist on the system and I > also removed all NB user dirs. -- 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-6112) AssertionError from javac during project indexing
Svatopluk Dedic created NETBEANS-6112:
-
Summary: AssertionError from javac during project indexing
Key: NETBEANS-6112
URL: https://issues.apache.org/jira/browse/NETBEANS-6112
Project: NetBeans
Issue Type: Bug
Components: java - Compiler
Affects Versions: 12.5
Reporter: Svatopluk Dedic
I've opened project *http-server-netty* from *micronaut-core* github project,
tag *v3.0.2* The following error was printed to the console during project
indexing:
{code:java}
WARNING [org.netbeans.modules.java.source.indexing.JavaIndex]:
SuperOnePassCompileWorker caused an exceptionWARNING
[org.netbeans.modules.java.source.indexing.JavaIndex]:
SuperOnePassCompileWorker caused an exceptionRoot:
/space/src/micronaut-core/http-server-netty/src/main/javaBootpath:
/space/java/8/jre/lib/resources.jar:/space/java/8/jre/lib/rt.jar:/space/java/8/jre/lib/sunrsasign.jar:/space/java/8/jre/lib/jsse.jar:/space/java/8/jre/lib/jce.jar:/space/java/8/jre/lib/charsets.jar:/space/java/8/jre/lib/jfr.jar:/space/java/8/jre/classes:/space/java/8/jre/lib/ext/jaccess.jar:/space/java/8/jre/lib/ext/sunpkcs11.jar:/space/java/8/jre/lib/ext/jfxrt.jar:/space/java/8/jre/lib/ext/nashorn.jar:/space/java/8/jre/lib/ext/sunec.jar:/space/java/8/jre/lib/ext/zipfs.jar:/space/java/8/jre/lib/ext/dnsns.jar:/space/java/8/jre/lib/ext/cldrdata.jar:/space/java/8/jre/lib/ext/localedata.jar:/space/java/8/jre/lib/ext/sunjce_provider.jarClasspath:
[jira] [Created] (NETBEANS-6106) Stabilize java.gradle unit tests
Svatopluk Dedic created NETBEANS-6106: - Summary: Stabilize java.gradle unit tests Key: NETBEANS-6106 URL: https://issues.apache.org/jira/browse/NETBEANS-6106 Project: NetBeans Issue Type: Task Components: projects - Gradle Reporter: Svatopluk Dedic Assignee: Svatopluk Dedic Fix For: 12.6 Java Gradle unit test is constantly failing on CI: [junit] Test org.netbeans.modules.gradle.java.execute.JavaExecTokenProviderTest FAILED See for example https://api.travis-ci.com/v3/job/541430369/log.txt -- 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-6102) Category Actions can not be opend in project properties for certain Maven Projects
[
https://issues.apache.org/jira/browse/NETBEANS-6102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Svatopluk Dedic updated NETBEANS-6102:
--
Fix Version/s: 12.6
> Category Actions can not be opend in project properties for certain Maven
> Projects
> --
>
> Key: NETBEANS-6102
> URL: https://issues.apache.org/jira/browse/NETBEANS-6102
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Maven
>Affects Versions: 12.5
> Environment: Windows
> Java 11 and 17
>Reporter: Ronny Perinke
>Assignee: Svatopluk Dedic
>Priority: Critical
> Labels: Regression, maven
> Fix For: 12.6
>
>
> For Maven Projects of packaging type "pom" (_e.g. the parent in a
> multi-module project_) or "hpi" (_Jenkins plugin_), the menu item "Actions"
> in the project settings can not be opened. A {{NullPointerException}} is
> logged instead.
> This is likely a regression of [commit
> c282a25d5071c1b44de7026a4ceb9d200e161e14|https://github.com/apache/netbeans/commit/c282a25d5071c1b44de7026a4ceb9d200e161e14#diff-a0789b6ea44b9deffb46bc59c2da95e1ab44302f648e02703d521d0ea042398dR201]
> and [PR #3016|https://github.com/apache/netbeans/pull/3016].
> {code:title=NPE in messages.log}
> java.lang.NullPointerException: Cannot invoke
> "org.netbeans.modules.maven.execute.model.NetbeansActionMapping.getGoals()"
> because "am" is null
> at
> org.netbeans.modules.maven.execute.ActionToGoalUtils.isDisabledMapping(ActionToGoalUtils.java:201)
> at
> org.netbeans.modules.maven.customizer.ActionMappings$Renderer.getListCellRendererComponent(ActionMappings.java:1082)
> at
> java.desktop/javax.swing.plaf.basic.BasicListUI.updateLayoutState(BasicListUI.java:1444)
> at
> java.desktop/javax.swing.plaf.basic.BasicListUI.maybeUpdateLayoutState(BasicListUI.java:1394)
> at
> java.desktop/javax.swing.plaf.basic.BasicListUI.getPreferredSize(BasicListUI.java:653)
> at
> java.desktop/javax.swing.JComponent.getPreferredSize(JComponent.java:1725)
> at
> java.desktop/javax.swing.ScrollPaneLayout.layoutContainer(ScrollPaneLayout.java:799)
> at java.desktop/java.awt.Container.layout(Container.java:1541)
> at java.desktop/java.awt.Container.doLayout(Container.java:1530)
> at java.desktop/java.awt.Container.validateTree(Container.java:1725)
> at java.desktop/java.awt.Container.validateTree(Container.java:1734)
> at java.desktop/java.awt.Container.validateTree(Container.java:1734)
> at java.desktop/java.awt.Container.validateTree(Container.java:1734)
> at java.desktop/java.awt.Container.validateTree(Container.java:1734)
> at java.desktop/java.awt.Container.validateTree(Container.java:1734)
> at java.desktop/java.awt.Container.validateTree(Container.java:1734)
> at java.desktop/java.awt.Container.validate(Container.java:1660)
> at
> java.desktop/javax.swing.RepaintManager$3.run(RepaintManager.java:757)
> at
> java.desktop/javax.swing.RepaintManager$3.run(RepaintManager.java:755)
> at
> java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
> at
> java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:86)
> at
> java.desktop/javax.swing.RepaintManager.validateInvalidComponents(RepaintManager.java:754)
> at
> java.desktop/javax.swing.RepaintManager$ProcessingRunnable.run(RepaintManager.java:1897)
> at
> java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:318)
> at
> java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:771)
> at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:722)
> at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:716)
> at
> java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
> at
> java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:86)
> at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:741)
> at
> org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:136)
> [catch] at
> java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
> at
> java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
> at
> java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:117)
> at
> java.desktop/java.awt.WaitDispatchSupport$2.run(WaitDispatchSupport.java:191)
> at
> java.desktop/java.awt.WaitDispatchSupport$4.run(WaitDispatchSupport.java:236)
> at
>
[jira] [Updated] (NETBEANS-6102) Category Actions can not be opend in project properties for certain Maven Projects
[
https://issues.apache.org/jira/browse/NETBEANS-6102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Svatopluk Dedic updated NETBEANS-6102:
--
Priority: Critical (was: Major)
> Category Actions can not be opend in project properties for certain Maven
> Projects
> --
>
> Key: NETBEANS-6102
> URL: https://issues.apache.org/jira/browse/NETBEANS-6102
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Maven
>Affects Versions: 12.5
> Environment: Windows
> Java 11 and 17
>Reporter: Ronny Perinke
>Assignee: Svatopluk Dedic
>Priority: Critical
> Labels: Regression, maven
>
> For Maven Projects of packaging type "pom" (_e.g. the parent in a
> multi-module project_) or "hpi" (_Jenkins plugin_), the menu item "Actions"
> in the project settings can not be opened. A {{NullPointerException}} is
> logged instead.
> This is likely a regression of [commit
> c282a25d5071c1b44de7026a4ceb9d200e161e14|https://github.com/apache/netbeans/commit/c282a25d5071c1b44de7026a4ceb9d200e161e14#diff-a0789b6ea44b9deffb46bc59c2da95e1ab44302f648e02703d521d0ea042398dR201]
> and [PR #3016|https://github.com/apache/netbeans/pull/3016].
> {code:title=NPE in messages.log}
> java.lang.NullPointerException: Cannot invoke
> "org.netbeans.modules.maven.execute.model.NetbeansActionMapping.getGoals()"
> because "am" is null
> at
> org.netbeans.modules.maven.execute.ActionToGoalUtils.isDisabledMapping(ActionToGoalUtils.java:201)
> at
> org.netbeans.modules.maven.customizer.ActionMappings$Renderer.getListCellRendererComponent(ActionMappings.java:1082)
> at
> java.desktop/javax.swing.plaf.basic.BasicListUI.updateLayoutState(BasicListUI.java:1444)
> at
> java.desktop/javax.swing.plaf.basic.BasicListUI.maybeUpdateLayoutState(BasicListUI.java:1394)
> at
> java.desktop/javax.swing.plaf.basic.BasicListUI.getPreferredSize(BasicListUI.java:653)
> at
> java.desktop/javax.swing.JComponent.getPreferredSize(JComponent.java:1725)
> at
> java.desktop/javax.swing.ScrollPaneLayout.layoutContainer(ScrollPaneLayout.java:799)
> at java.desktop/java.awt.Container.layout(Container.java:1541)
> at java.desktop/java.awt.Container.doLayout(Container.java:1530)
> at java.desktop/java.awt.Container.validateTree(Container.java:1725)
> at java.desktop/java.awt.Container.validateTree(Container.java:1734)
> at java.desktop/java.awt.Container.validateTree(Container.java:1734)
> at java.desktop/java.awt.Container.validateTree(Container.java:1734)
> at java.desktop/java.awt.Container.validateTree(Container.java:1734)
> at java.desktop/java.awt.Container.validateTree(Container.java:1734)
> at java.desktop/java.awt.Container.validateTree(Container.java:1734)
> at java.desktop/java.awt.Container.validate(Container.java:1660)
> at
> java.desktop/javax.swing.RepaintManager$3.run(RepaintManager.java:757)
> at
> java.desktop/javax.swing.RepaintManager$3.run(RepaintManager.java:755)
> at
> java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
> at
> java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:86)
> at
> java.desktop/javax.swing.RepaintManager.validateInvalidComponents(RepaintManager.java:754)
> at
> java.desktop/javax.swing.RepaintManager$ProcessingRunnable.run(RepaintManager.java:1897)
> at
> java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:318)
> at
> java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:771)
> at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:722)
> at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:716)
> at
> java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
> at
> java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:86)
> at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:741)
> at
> org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:136)
> [catch] at
> java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
> at
> java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
> at
> java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:117)
> at
> java.desktop/java.awt.WaitDispatchSupport$2.run(WaitDispatchSupport.java:191)
> at
> java.desktop/java.awt.WaitDispatchSupport$4.run(WaitDispatchSupport.java:236)
> at
>
[jira] [Resolved] (NETBEANS-6044) Annotation processors configured for compiler plugin are not used for editor parsing
[ https://issues.apache.org/jira/browse/NETBEANS-6044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Svatopluk Dedic resolved NETBEANS-6044. --- Fix Version/s: 12.6 Resolution: Fixed > Annotation processors configured for compiler plugin are not used for editor > parsing > > > Key: NETBEANS-6044 > URL: https://issues.apache.org/jira/browse/NETBEANS-6044 > Project: NetBeans > Issue Type: Bug > Components: projects - Maven >Affects Versions: 12.5 >Reporter: Svatopluk Dedic >Assignee: Svatopluk Dedic >Priority: Major > Labels: pull-request-available > Fix For: 12.6 > > Time Spent: 2.5h > Remaining Estimate: 0h > > Maven supplies "classpath/compile" ClassPath as the processor classpath. But > the compiler-maven-plugin supports a special processor classpath that can be > set in plugin configuration and should be used for discovery in addition(?) > to regular compile classpath. > This technique is used in e.g. *micronaut* where the *micronaut-parent* POM > inherited into user projects configures annotation processors this way. > Errors that appear at compile time are not reported or underlined in the > IDE's editor. -- 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-6077) Groovy loads half of Micronaut library on each completion
Svatopluk Dedic created NETBEANS-6077: - Summary: Groovy loads half of Micronaut library on each completion Key: NETBEANS-6077 URL: https://issues.apache.org/jira/browse/NETBEANS-6077 Project: NetBeans Issue Type: Bug Components: groovy - Editor, javaee - Micronaut Affects Versions: 12.5 Reporter: Svatopluk Dedic Transformations / visitors are loaded from user project's libraries to participate on groovy compilation. It seems that classes of those visitors are loaded for *each parse operation* anew, which makes the parser startup longer. Attaching a report (placed Logger.info() in TransformationLoader.findClass()) - about 570 classes are loaded after each keystroke + parse. Mitigation step 1: have the loaded classes cached based on set of library URLs used by the project (cache the parent classloader). Mitigation step 2: consider to disable InjectTransform etc. from Micronaut ... -- 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-6075) Groovy loads user classes into JVM on each completion
Svatopluk Dedic created NETBEANS-6075: - Summary: Groovy loads user classes into JVM on each completion Key: NETBEANS-6075 URL: https://issues.apache.org/jira/browse/NETBEANS-6075 Project: NetBeans Issue Type: Bug Components: groovy - Editor Affects Versions: 12.5 Reporter: Svatopluk Dedic Groovy Editor's *MetaElementsProvider* uses *GroovyClassLoader.loadClass*, which in turn *compiles* and loads a .groovy file into JVM. The class is then introspected, which is likely to trigger all JVM lazy-run stuff, as class initializer, potentially executing something in the IDE's JVM. The bad thing is that Groovy's MetaClass registry is a runtime implementation centered around j.l.Class type. There's only a little chance to reuse _anything_ from Groovy's implementation. -- 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-6044) Annotation processors configured for compiler plugin are not used for editor parsing
Svatopluk Dedic created NETBEANS-6044: - Summary: Annotation processors configured for compiler plugin are not used for editor parsing Key: NETBEANS-6044 URL: https://issues.apache.org/jira/browse/NETBEANS-6044 Project: NetBeans Issue Type: Bug Components: projects - Maven Affects Versions: 12.5 Reporter: Svatopluk Dedic Assignee: Svatopluk Dedic Maven supplies "classpath/compile" ClassPath as the processor classpath. But the compiler-maven-plugin supports a special processor classpath that can be set in plugin configuration and should be used for discovery in addition(?) to regular compile classpath. This technique is used in e.g. *micronaut* where the *micronaut-parent* POM inherited into user projects configures annotation processors this way. Errors that appear at compile time are not reported or underlined in the IDE's editor. -- 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-6031) Decision of class name resolved to SourceUnit not cached
Svatopluk Dedic created NETBEANS-6031: - Summary: Decision of class name resolved to SourceUnit not cached Key: NETBEANS-6031 URL: https://issues.apache.org/jira/browse/NETBEANS-6031 Project: NetBeans Issue Type: Bug Components: groovy - Editor Affects Versions: 12.5 Reporter: Svatopluk Dedic A type name is repeatedly resolved through *ClassNodeResolver* (NbClassNodeResolver) to LookupResult with SourceUnit; the decision can be cached, which saves some resource lookups + timestamp checks. The improvement will not be high, but we cache everything else, so we could this as well. -- 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-6028) Javac is unnecessary inited & queried for Groovy class
Svatopluk Dedic created NETBEANS-6028: - Summary: Javac is unnecessary inited & queried for Groovy class Key: NETBEANS-6028 URL: https://issues.apache.org/jira/browse/NETBEANS-6028 Project: NetBeans Issue Type: Bug Components: groovy - Editor Affects Versions: 12.5 Reporter: Svatopluk Dedic If a Groovy class references another Groovy class (not yet compiled). the name is first resolved to LookupResult with sourceUnit (= it's a groovy source), but still our CompileUnit.getClass() gets called and attempts to resolve the name using Javac - completely useless in this case. Each javac invocation gives a small performance penalty and in this case, it is done for each such type, not sure about overall impac though -- 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-6003) Groovy code completion does not offer field constants for enum values
[ https://issues.apache.org/jira/browse/NETBEANS-6003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17415548#comment-17415548 ] Svatopluk Dedic commented on NETBEANS-6003: --- The AST node is replaced rather early, at the start of semanticAnalysis phase. IMHO best fixed directly in Groovy compiler - some trace should be left in node's metadata; the constants may have to be copied - e.g. enum values are returned directly from the field's initialValueExpression. > Groovy code completion does not offer field constants for enum values > - > > Key: NETBEANS-6003 > URL: https://issues.apache.org/jira/browse/NETBEANS-6003 > Project: NetBeans > Issue Type: Bug > Components: groovy - Editor >Reporter: Svatopluk Dedic >Priority: Major > > [https://github.com/micronaut-projects/micronaut-core/blob/3.0.x/http-server-netty/src/test/groovy/io/micronaut/http/server/netty/sse/ServerSentEventSpec.groovy#L94] > The member values of the annotation are evaluated compile-time into > *ConstantExpressions* while the original *PropertyExpression* that would > provide the proper Class context for the code completion is complete gone. > The resulting ConstantExpression even does not contain line/column > information copied fro the original source; so it won't be properly matched > in AST against the source. > -- 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-6003) Groovy code completion does not offer field constants for enum values
[ https://issues.apache.org/jira/browse/NETBEANS-6003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Svatopluk Dedic updated NETBEANS-6003: -- Component/s: groovy - Editor > Groovy code completion does not offer field constants for enum values > - > > Key: NETBEANS-6003 > URL: https://issues.apache.org/jira/browse/NETBEANS-6003 > Project: NetBeans > Issue Type: Bug > Components: groovy - Editor >Reporter: Svatopluk Dedic >Priority: Major > > [https://github.com/micronaut-projects/micronaut-core/blob/3.0.x/http-server-netty/src/test/groovy/io/micronaut/http/server/netty/sse/ServerSentEventSpec.groovy#L94] > The member values of the annotation are evaluated compile-time into > *ConstantExpressions* while the original *PropertyExpression* that would > provide the proper Class context for the code completion is complete gone. > The resulting ConstantExpression even does not contain line/column > information copied fro the original source; so it won't be properly matched > in AST against the source. > -- 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-6003) Groovy code completion does not offer field constants for enum values
Svatopluk Dedic created NETBEANS-6003: - Summary: Groovy code completion does not offer field constants for enum values Key: NETBEANS-6003 URL: https://issues.apache.org/jira/browse/NETBEANS-6003 Project: NetBeans Issue Type: Bug Reporter: Svatopluk Dedic [https://github.com/micronaut-projects/micronaut-core/blob/3.0.x/http-server-netty/src/test/groovy/io/micronaut/http/server/netty/sse/ServerSentEventSpec.groovy#L94] The member values of the annotation are evaluated compile-time into *ConstantExpressions* while the original *PropertyExpression* that would provide the proper Class context for the code completion is complete gone. The resulting ConstantExpression even does not contain line/column information copied fro the original source; so it won't be properly matched in AST against the source. -- 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-5992) Groovy compiler / parser bugs affecting NB code completion
[ https://issues.apache.org/jira/browse/NETBEANS-5992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Svatopluk Dedic reassigned NETBEANS-5992: - Assignee: Svatopluk Dedic Description: Umbrella issue, that could help to collect dependent errors filed in Groovy. Maybe it could be split to an issue tracking possible improvements and an issue that tracks improvment necessary for the next release. Issue Type: Task (was: Bug) > Groovy compiler / parser bugs affecting NB code completion > -- > > Key: NETBEANS-5992 > URL: https://issues.apache.org/jira/browse/NETBEANS-5992 > Project: NetBeans > Issue Type: Task > Components: groovy - Editor >Reporter: Svatopluk Dedic >Assignee: Svatopluk Dedic >Priority: Major > > Umbrella issue, that could help to collect dependent errors filed in Groovy. > Maybe it could be split to an issue tracking possible improvements and an > issue that tracks improvment necessary for the next release. > -- 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-5992) Groovy compiler / parser bugs affecting NB code completion
Svatopluk Dedic created NETBEANS-5992: - Summary: Groovy compiler / parser bugs affecting NB code completion Key: NETBEANS-5992 URL: https://issues.apache.org/jira/browse/NETBEANS-5992 Project: NetBeans Issue Type: Bug Reporter: Svatopluk Dedic -- 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-5992) Groovy compiler / parser bugs affecting NB code completion
[ https://issues.apache.org/jira/browse/NETBEANS-5992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Svatopluk Dedic updated NETBEANS-5992: -- Component/s: groovy - Editor > Groovy compiler / parser bugs affecting NB code completion > -- > > Key: NETBEANS-5992 > URL: https://issues.apache.org/jira/browse/NETBEANS-5992 > Project: NetBeans > Issue Type: Bug > Components: groovy - Editor >Reporter: Svatopluk Dedic >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Created] (NETBEANS-5991) Completion does not substitute type parameters into superclass methods.
Svatopluk Dedic created NETBEANS-5991:
-
Summary: Completion does not substitute type parameters into
superclass methods.
Key: NETBEANS-5991
URL: https://issues.apache.org/jira/browse/NETBEANS-5991
Project: NetBeans
Issue Type: Bug
Components: groovy - Editor
Affects Versions: 12.5
Reporter: Svatopluk Dedic
Consider type like *java.util.Properties* extends Hastable.
When going up, the completion calls *ClassNode.getSuperclass()*.
Internally the ClassNode's superClass fields leads to
{quote}superClass ClassNode #9125 java.util.Hashtable -> java.util.Hashtable
{quote}
But as the getSuperClass() redirects, it will return
{quote}typeNode.getSuperClass() DecompiledClassNode #8988 java.util.Hashtable
{quote}
The redirect target type declares type variables, but the substitutions are in
the ClassNode that redirects to the target.
Completion should probably circumvent that using *getSuperclassUnresolved* or
something like that.
Because of that, *FieldsCCTest.testFields2_javaPropertyReference* displays both
{quote}METHOD getOrDefault(Object, Object) [PUBLIC] Object
METHOD getOrDefault(Object, V) [PUBLIC] V
{quote}
the second method comes from Hashtable, but V := Object is lost.
--
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-5983) Static type analysis does not consider instanceof type hint
[
https://issues.apache.org/jira/browse/NETBEANS-5983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17411945#comment-17411945
]
Svatopluk Dedic commented on NETBEANS-5983:
---
Attached sample groovy script that fails to compile although type should be
inferred according to
http://groovy-lang.org/semantics.html#_instanceof_inference
> Static type analysis does not consider instanceof type hint
> ---
>
> Key: NETBEANS-5983
> URL: https://issues.apache.org/jira/browse/NETBEANS-5983
> Project: NetBeans
> Issue Type: Bug
> Components: groovy - Editor
>Reporter: Svatopluk Dedic
>Priority: Major
> Attachments: T.groovy
>
>
> Consider code like
> {code:java}
> public BindingHolder(BindingHolder parent, Object value) {
>if(value instanceof List) {
> def instance = value[0]; // ERROR
> ...
>}
> }
> {code}
> whent the editor parser uses static type analysis, it will report an error on
> the marker line, as *vlaue* is typed as *java.lang.Object*, which has no
> *get()* method.
> In this specific case, the subtree can be evaluated speculatively, supposing
> that *value* is instance of *List* - requires partial evaluation of
> if-conditions. Similar case when typecast precedes reference to an identifier.
> This must be probably fixed in Groovy; in NetBeans we can block the message
> and try to re-evaluate the AST subtree with a speculative type(s) found on
> path(s) to the 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-5983) Static type analysis does not consider instanceof type hint
[
https://issues.apache.org/jira/browse/NETBEANS-5983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Svatopluk Dedic updated NETBEANS-5983:
--
Attachment: T.groovy
> Static type analysis does not consider instanceof type hint
> ---
>
> Key: NETBEANS-5983
> URL: https://issues.apache.org/jira/browse/NETBEANS-5983
> Project: NetBeans
> Issue Type: Bug
> Components: groovy - Editor
>Reporter: Svatopluk Dedic
>Priority: Major
> Attachments: T.groovy
>
>
> Consider code like
> {code:java}
> public BindingHolder(BindingHolder parent, Object value) {
>if(value instanceof List) {
> def instance = value[0]; // ERROR
> ...
>}
> }
> {code}
> whent the editor parser uses static type analysis, it will report an error on
> the marker line, as *vlaue* is typed as *java.lang.Object*, which has no
> *get()* method.
> In this specific case, the subtree can be evaluated speculatively, supposing
> that *value* is instance of *List* - requires partial evaluation of
> if-conditions. Similar case when typecast precedes reference to an identifier.
> This must be probably fixed in Groovy; in NetBeans we can block the message
> and try to re-evaluate the AST subtree with a speculative type(s) found on
> path(s) to the 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-5984) Spurious 'could not find matching method' in editor
Svatopluk Dedic created NETBEANS-5984:
-
Summary: Spurious 'could not find matching method' in editor
Key: NETBEANS-5984
URL: https://issues.apache.org/jira/browse/NETBEANS-5984
Project: NetBeans
Issue Type: Bug
Components: groovy - Editor
Reporter: Svatopluk Dedic
Consider the following code:
{code:java}
def instance = value[0];
def propertyName = value[1];
observable = Util.getJavaFXProperty(instance, propertyName)
{code}
The *instance* and *propertyName* lack completely type information; static
type analysis reports an error in this case.
It's not wise to completely disable 'method not found' errors, as typed code
would not be hinted either. It could be possible to suppress error if the
method call parameters type-evaluates to j.l.Object or something similarly
generic, in the case there's at least method with the appropriate arity.
--
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-5983) Static type analysis does not consider instanceof type hint
Svatopluk Dedic created NETBEANS-5983:
-
Summary: Static type analysis does not consider instanceof type
hint
Key: NETBEANS-5983
URL: https://issues.apache.org/jira/browse/NETBEANS-5983
Project: NetBeans
Issue Type: Bug
Components: groovy - Editor
Reporter: Svatopluk Dedic
Consider code like
{code:java}
public BindingHolder(BindingHolder parent, Object value) {
if(value instanceof List) {
def instance = value[0]; // ERROR
...
}
}
{code}
whent the editor parser uses static type analysis, it will report an error on
the marker line, as *vlaue* is typed as *java.lang.Object*, which has no
*get()* method.
In this specific case, the subtree can be evaluated speculatively, supposing
that *value* is instance of *List* - requires partial evaluation of
if-conditions. Similar case when typecast precedes reference to an identifier.
This must be probably fixed in Groovy; in NetBeans we can block the message and
try to re-evaluate the AST subtree with a speculative type(s) found on path(s)
to the 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-5982) Groovy parser cannot handle annotations from source
[ https://issues.apache.org/jira/browse/NETBEANS-5982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Svatopluk Dedic updated NETBEANS-5982: -- Description: Symbols resolved for annotations are inspected using *ClassNode.getTypeClass*() called on the annotation's type. This attempts to *load annotation class into JVM*. If the referenced annotation is *in the same project*, the classes may not be generated yet an the j.l.Class cannot be loaded. The compilation immediately terminates with an internal error, bypassing rest of attributing work. References to library annotations are OK - they are loaded from .class files (althoug loading into JVM should be avoided) Note: this is a Groovy bug, not NetBeans. Must be fixed in Groovy, or we need to patch Groovy for our purposes. was: Symbols resolved for annotations are inspected using *ClassNode.getTypeClass*() called on the annotation's type. This attempts to *load annotation class into JVM*. If the referenced annotation is *in the same project*, the classes may not be generated yet an the j.l.Class cannot be loaded. The compilation immediately terminates with an internal error, bypassing rest of attributing work. References to library annotations are OK - they are loaded from .class files (althoug loading into JVM should be avoided) > Groovy parser cannot handle annotations from source > --- > > Key: NETBEANS-5982 > URL: https://issues.apache.org/jira/browse/NETBEANS-5982 > Project: NetBeans > Issue Type: Bug > Components: groovy - Editor >Reporter: Svatopluk Dedic >Priority: Critical > > Symbols resolved for annotations are inspected using > *ClassNode.getTypeClass*() called on the annotation's type. This attempts to > *load annotation class into JVM*. > If the referenced annotation is *in the same project*, the classes may not be > generated yet an the j.l.Class cannot be loaded. The compilation immediately > terminates with an internal error, bypassing rest of attributing work. > References to library annotations are OK - they are loaded from .class files > (althoug loading into JVM should be avoided) > > Note: this is a Groovy bug, not NetBeans. Must be fixed in Groovy, or we need > to patch Groovy for our purposes. -- 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-5982) Groovy parser cannot handle annotations from source
Svatopluk Dedic created NETBEANS-5982: - Summary: Groovy parser cannot handle annotations from source Key: NETBEANS-5982 URL: https://issues.apache.org/jira/browse/NETBEANS-5982 Project: NetBeans Issue Type: Bug Components: groovy - Editor Reporter: Svatopluk Dedic Symbols resolved for annotations are inspected using *ClassNode.getTypeClass*() called on the annotation's type. This attempts to *load annotation class into JVM*. If the referenced annotation is *in the same project*, the classes may not be generated yet an the j.l.Class cannot be loaded. The compilation immediately terminates with an internal error, bypassing rest of attributing work. References to library annotations are OK - they are loaded from .class files (althoug loading into JVM should be avoided) -- 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-5974) Fix Groovy ResolverVisitor for typename.class
Svatopluk Dedic created NETBEANS-5974:
-
Summary: Fix Groovy ResolverVisitor for typename.class
Key: NETBEANS-5974
URL: https://issues.apache.org/jira/browse/NETBEANS-5974
Project: NetBeans
Issue Type: Improvement
Components: groovy - Editor
Reporter: Svatopluk Dedic
ResolveVisitor ~1038: if the property name is {{class}} (a keword!), it cannot
be an inner class - an extra unneeded set of resource lookups is done
--
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
