[jira] [Resolved] (NETBEANS-5398) Exceptions thrown when attempting to set Gradle options
[ https://issues.apache.org/jira/browse/NETBEANS-5398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laszlo Kishalmi resolved NETBEANS-5398. --- Fix Version/s: 12.4 Resolution: Fixed > Exceptions thrown when attempting to set Gradle options > --- > > Key: NETBEANS-5398 > URL: https://issues.apache.org/jira/browse/NETBEANS-5398 > Project: NetBeans > Issue Type: Bug > Components: projects - Gradle >Affects Versions: 12.2, 12.3 >Reporter: Albert Flex >Assignee: Laszlo Kishalmi >Priority: Major > Labels: fix-by-workaround, pull-request-available > Fix For: 12.4 > > Attachments: 截图_2021-03-03_00-49-10.png, 截图_2021-03-03_00-50-53.png > > Time Spent: 1h > Remaining Estimate: 0h > > There is an exception when setting the distribution address of gradle. > Although the interface display has been changed, it is still not set > successfully after restart. An exception was reported in the log. > > java.lang.NullPointerException > at > org.netbeans.modules.gradle.options.SettingsPanel.applyValues(SettingsPanel.java:768) > at > org.netbeans.modules.gradle.options.GradleOptionsController.applyChanges(GradleOptionsController.java:53) > at > org.netbeans.modules.options.TabbedController.applyChanges(TabbedController.java:111) > at > org.netbeans.modules.options.CategoryModel$Category.applyChanges(CategoryModel.java:379) > at > org.netbeans.modules.options.CategoryModel$Category.access$1100(CategoryModel.java:302) > at org.netbeans.modules.options.CategoryModel.save(CategoryModel.java:198) > at org.netbeans.modules.options.OptionsPanel.save(OptionsPanel.java:294) > at org.netbeans.modules.options.OptionsPanel.save(OptionsPanel.java:278) > at > org.netbeans.modules.options.OptionsDisplayerImpl$OptionsPanelListener$3.run(OptionsDisplayerImpl.java:514) > at > org.netbeans.modules.progress.ui.RunOffEDTImpl$3.run(RunOffEDTImpl.java:252) > at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1418) > at > org.netbeans.modules.openide.util.GlobalLookup.execute(GlobalLookup.java:45) > at org.openide.util.lookup.Lookups.executeWith(Lookups.java:278) > [catch] at > org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2033) > > -- 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-5629) Gradle project Lookups ordering not defined well
[
https://issues.apache.org/jira/browse/NETBEANS-5629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17337941#comment-17337941
]
Jaroslav Tulach commented on NETBEANS-5629:
---
{quote}[~jtulach] - what do you think: shouldn't we use the MimeLookup-like
composition for plugin-implied services ?
{quote}
Sure, if existing implementation works for your case, then use it! MimeLookup
implementation is in the platform already. It is no longer tight to editor and
it doesn't have to be tight to MIME types.
You can also enhance {{ProxyLookup}} to honor {{position}} value of the
{{Lookup.Item }} instances it delegates to, if you think it would fix your
problem.
> Gradle project Lookups ordering not defined well
>
>
> Key: NETBEANS-5629
> URL: https://issues.apache.org/jira/browse/NETBEANS-5629
> Project: NetBeans
> Issue Type: Bug
>Reporter: Svatopluk Dedic
>Priority: Major
>
> Individual Plugins can contribute to project Lookup. In my testcase, which
> uses java/java-base plugins, the Lookups loaded from
> *Projects/org-netbeans-modules-gradle/*** were loaded in the following order:
> {code:java}
> [java, , root, java-base, base]
> {code}
> When Groovy was also present, the order was
> {code:java}
> [java, groovy, , root, groovy-base, java-base, base]
> {code}
> (note - groovy after java, groovy-base before java-base). But with scala, the
> order is:
> {code:java}
> [java, scala, , root, java-base, scala-base, base]
> {code}
> (note - scala-base AFTER java-base).
> When opening a project with
> {code:java}
> apply plugin: 'groovy'
> {code}
> the order is yet different:
> {code:java}
> [groovy, java, , root, groovy-base, java-base, base]{code}
> The order is unreliable and I guess under some circumstances even the
> , xxx-base and xxx could be reordered as plugin names go through
> series of hashmaps.
--
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-5649) "Open in Finder" not working in Big Sur
Dave D created NETBEANS-5649: Summary: "Open in Finder" not working in Big Sur Key: NETBEANS-5649 URL: https://issues.apache.org/jira/browse/NETBEANS-5649 Project: NetBeans Issue Type: Bug Reporter: Dave D -- 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-5648) Unable to generate JSF pages from Entity classes
[ https://issues.apache.org/jira/browse/NETBEANS-5648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17337879#comment-17337879 ] Muneeb Gulzar Ditta Gulzar commented on NETBEANS-5648: -- Hi, I cant open my projects. I attach the screenshot. Regards. > Unable to generate JSF pages from Entity classes > > > Key: NETBEANS-5648 > URL: https://issues.apache.org/jira/browse/NETBEANS-5648 > Project: NetBeans > Issue Type: Bug >Affects Versions: 12.3 > Environment: OS: Windows 10/ 64 bit > JDK version: 1.8.31 > NB version: 12.3 >Reporter: Chalapathi Ravi >Priority: Blocker > Attachments: image-2021-05-01-22-36-17-786.png, messages.log, > screenshot-1.png, screenshot-2.png > > > The "JSF pages from Entity classes" is generating empty facade class for the > selected entity. It is not generating the facelets for CRUD operations. We > are running on Java 1.8.31. The var log has the following stack trace which > may hep you in identifying the issue. Please provide a resolution. Thanks in > Advance > > -- 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-5648) Unable to generate JSF pages from Entity classes
[ https://issues.apache.org/jira/browse/NETBEANS-5648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Muneeb Gulzar Ditta Gulzar updated NETBEANS-5648: - Attachment: screenshot-2.png > Unable to generate JSF pages from Entity classes > > > Key: NETBEANS-5648 > URL: https://issues.apache.org/jira/browse/NETBEANS-5648 > Project: NetBeans > Issue Type: Bug >Affects Versions: 12.3 > Environment: OS: Windows 10/ 64 bit > JDK version: 1.8.31 > NB version: 12.3 >Reporter: Chalapathi Ravi >Priority: Blocker > Attachments: image-2021-05-01-22-36-17-786.png, messages.log, > screenshot-1.png, screenshot-2.png > > > The "JSF pages from Entity classes" is generating empty facade class for the > selected entity. It is not generating the facelets for CRUD operations. We > are running on Java 1.8.31. The var log has the following stack trace which > may hep you in identifying the issue. Please provide a resolution. Thanks in > Advance > > -- 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-5648) Unable to generate JSF pages from Entity classes
[ https://issues.apache.org/jira/browse/NETBEANS-5648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Muneeb Gulzar Ditta Gulzar updated NETBEANS-5648: - Attachment: image-2021-05-01-22-36-17-786.png > Unable to generate JSF pages from Entity classes > > > Key: NETBEANS-5648 > URL: https://issues.apache.org/jira/browse/NETBEANS-5648 > Project: NetBeans > Issue Type: Bug >Affects Versions: 12.3 > Environment: OS: Windows 10/ 64 bit > JDK version: 1.8.31 > NB version: 12.3 >Reporter: Chalapathi Ravi >Priority: Blocker > Attachments: image-2021-05-01-22-36-17-786.png, messages.log, > screenshot-1.png > > > The "JSF pages from Entity classes" is generating empty facade class for the > selected entity. It is not generating the facelets for CRUD operations. We > are running on Java 1.8.31. The var log has the following stack trace which > may hep you in identifying the issue. Please provide a resolution. Thanks in > Advance > > -- 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-5648) Unable to generate JSF pages from Entity classes
[ https://issues.apache.org/jira/browse/NETBEANS-5648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Muneeb Gulzar Ditta Gulzar updated NETBEANS-5648: - Attachment: screenshot-1.png > Unable to generate JSF pages from Entity classes > > > Key: NETBEANS-5648 > URL: https://issues.apache.org/jira/browse/NETBEANS-5648 > Project: NetBeans > Issue Type: Bug >Affects Versions: 12.3 > Environment: OS: Windows 10/ 64 bit > JDK version: 1.8.31 > NB version: 12.3 >Reporter: Chalapathi Ravi >Priority: Blocker > Attachments: image-2021-05-01-22-36-17-786.png, messages.log, > screenshot-1.png > > > The "JSF pages from Entity classes" is generating empty facade class for the > selected entity. It is not generating the facelets for CRUD operations. We > are running on Java 1.8.31. The var log has the following stack trace which > may hep you in identifying the issue. Please provide a resolution. Thanks in > Advance > > -- 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-5648) Unable to generate JSF pages from Entity classes
[ https://issues.apache.org/jira/browse/NETBEANS-5648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lorenzo updated NETBEANS-5648: --- External issue ID: method print doesn't work Hi guys just inform you that the method System.out.print ( ) doesn't work like should be If you use for any program give problem to print the message on the screen; It seems that doesn't work , because doesn't print anything in the screen I hope you can solve this problem. Kind regards > Unable to generate JSF pages from Entity classes > > > Key: NETBEANS-5648 > URL: https://issues.apache.org/jira/browse/NETBEANS-5648 > Project: NetBeans > Issue Type: Bug >Affects Versions: 12.3 > Environment: OS: Windows 10/ 64 bit > JDK version: 1.8.31 > NB version: 12.3 >Reporter: Chalapathi Ravi >Priority: Blocker > Attachments: messages.log > > > The "JSF pages from Entity classes" is generating empty facade class for the > selected entity. It is not generating the facelets for CRUD operations. We > are running on Java 1.8.31. The var log has the following stack trace which > may hep you in identifying the issue. Please provide a resolution. Thanks in > Advance > > -- 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-5648) Unable to generate JSF pages from Entity classes
Chalapathi Ravi created NETBEANS-5648: - Summary: Unable to generate JSF pages from Entity classes Key: NETBEANS-5648 URL: https://issues.apache.org/jira/browse/NETBEANS-5648 Project: NetBeans Issue Type: Bug Affects Versions: 12.3 Environment: OS: Windows 10/ 64 bit JDK version: 1.8.31 NB version: 12.3 Reporter: Chalapathi Ravi Attachments: messages.log The "JSF pages from Entity classes" is generating empty facade class for the selected entity. It is not generating the facelets for CRUD operations. We are running on Java 1.8.31. The var log has the following stack trace which may hep you in identifying the issue. Please provide a resolution. Thanks in Advance -- 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-5629) Gradle project Lookups ordering not defined well
[
https://issues.apache.org/jira/browse/NETBEANS-5629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17337820#comment-17337820
]
Laszlo Kishalmi commented on NETBEANS-5629:
---
Hmm. That's interesting. Seems to be a bug in the Project API, at least for me.
Though while I was checking its implementation, I'd find difficult to fix that.
Probably the ordering has disappeared with:
[https://github.com/apache/netbeans/pull/2553] when I removed the
ProjectServiceProvider registrations.
I see three options to fix this:
# Fix the project api to handle ProjectServiceProvider well
# Use a LinkedHasSet to keep the order of the plugins, the plugin detection is
happening in NbProjectInfoBuilder, upon a pre-defined list of plugins, so the
order can be set there.
# Maybe it is enough to to put a position attribute to the
LookupProvider.Registration on the LookupProviders
This issue was not really a problem earlier since compared to Gradle, Ant and
Maven projects are relatively static.
> Gradle project Lookups ordering not defined well
>
>
> Key: NETBEANS-5629
> URL: https://issues.apache.org/jira/browse/NETBEANS-5629
> Project: NetBeans
> Issue Type: Bug
>Reporter: Svatopluk Dedic
>Priority: Major
>
> Individual Plugins can contribute to project Lookup. In my testcase, which
> uses java/java-base plugins, the Lookups loaded from
> *Projects/org-netbeans-modules-gradle/*** were loaded in the following order:
> {code:java}
> [java, , root, java-base, base]
> {code}
> When Groovy was also present, the order was
> {code:java}
> [java, groovy, , root, groovy-base, java-base, base]
> {code}
> (note - groovy after java, groovy-base before java-base). But with scala, the
> order is:
> {code:java}
> [java, scala, , root, java-base, scala-base, base]
> {code}
> (note - scala-base AFTER java-base).
> When opening a project with
> {code:java}
> apply plugin: 'groovy'
> {code}
> the order is yet different:
> {code:java}
> [groovy, java, , root, groovy-base, java-base, base]{code}
> The order is unreliable and I guess under some circumstances even the
> , xxx-base and xxx could be reordered as plugin names go through
> series of hashmaps.
--
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-5540) package x.y.z does not exist for Gradle project
[
https://issues.apache.org/jira/browse/NETBEANS-5540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laszlo Kishalmi resolved NETBEANS-5540.
---
Resolution: Fixed
> package x.y.z does not exist for Gradle project
> ---
>
> Key: NETBEANS-5540
> URL: https://issues.apache.org/jira/browse/NETBEANS-5540
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Gradle
>Affects Versions: 12.4
> Environment: NB 12.4 Beta1, macOS, Java(TM) SE Runtime Environment
> 18.9 (build 11.0.10+8-LTS-162)
> git clone https://github.com/micronaut-projects/micronaut-test.git
>Reporter: Martin Balin
>Assignee: Svatopluk Dedic
>Priority: Major
> Labels: VSNetBeans, pull-request-available
> Fix For: 12.4
>
> Attachments: Screenshot 2021-04-04 at 10.42.30.png, demogradle.zip,
> messages.log.1, without_nbjavac.png
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Unpacked NB 12.4 beta1. Started fresh no user dir, no import of settings.
> Run NB, install nb-javac when requested.
> Open micronaut-test, previously cloned from
> [https://github.com/micronaut-projects/micronaut-test|https://github.com/micronaut-projects/micronaut-test.]
> I did not check the check box, trust the project in Project open dlg.
> When top level project is open NB asks for Resolve problems, click Resolve,
> then open test-junit5, Resolve Problems step is done, subproject is open.
> It looks like attached screenshot.
> Performing Clean & Build on project in NB does not fix this.
> Close NB, run {{./gradlew build}} on top level project in terminal, same JDK
> used, it builds the project successfully.
> Open the multi project in NB again, still same errors displayed. See attached
> screenshot and log file from this session.
> In the next step I delete .gradle folder in micronaut-test, removed NB user
> dir, start from scratch. In Open Project dlg I checked Trust the project.
> Resolve Problems dlg appears for top level project with two problems: Priming
> build and Trust the project. Click Resolve button, it gets green.
> Then open test-junit5, Resolve Problems project appears and it is empty.
> Source files are open with with same errors as previously in attachment.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-5629) Gradle project Lookups ordering not defined well
[
https://issues.apache.org/jira/browse/NETBEANS-5629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17337808#comment-17337808
]
Svatopluk Dedic commented on NETBEANS-5629:
---
It does :) experienced on my own in Maven projects, which work in a similar
way, but for packaging only (sidenote: packaging (distribution type) can be an
interesting additional 'axis' in the gradle plugin system, too as it ultimately
combines with technology plugins).
It does matter since individual plugin-folders are merged in ProxyLookup, which
enumerates the contents (= list of ProjectServiceProviders) in the order of the
ProxyLookup components, and only then (2nd level) ordered by position attribute
of ProjectserviceProviders). I would like to take the opportunity that Gradle
APIs do not define (at the moment) the order at all, to work out a system that
works consistently for Ant, Maven, Gradle projects.
> Gradle project Lookups ordering not defined well
>
>
> Key: NETBEANS-5629
> URL: https://issues.apache.org/jira/browse/NETBEANS-5629
> Project: NetBeans
> Issue Type: Bug
>Reporter: Svatopluk Dedic
>Priority: Major
>
> Individual Plugins can contribute to project Lookup. In my testcase, which
> uses java/java-base plugins, the Lookups loaded from
> *Projects/org-netbeans-modules-gradle/*** were loaded in the following order:
> {code:java}
> [java, , root, java-base, base]
> {code}
> When Groovy was also present, the order was
> {code:java}
> [java, groovy, , root, groovy-base, java-base, base]
> {code}
> (note - groovy after java, groovy-base before java-base). But with scala, the
> order is:
> {code:java}
> [java, scala, , root, java-base, scala-base, base]
> {code}
> (note - scala-base AFTER java-base).
> When opening a project with
> {code:java}
> apply plugin: 'groovy'
> {code}
> the order is yet different:
> {code:java}
> [groovy, java, , root, groovy-base, java-base, base]{code}
> The order is unreliable and I guess under some circumstances even the
> , xxx-base and xxx could be reordered as plugin names go through
> series of hashmaps.
--
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-5587) Gradle project does not show -SNAPSHOT in Configurations
[
https://issues.apache.org/jira/browse/NETBEANS-5587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laszlo Kishalmi resolved NETBEANS-5587.
---
Resolution: Fixed
> Gradle project does not show -SNAPSHOT in Configurations
>
>
> Key: NETBEANS-5587
> URL: https://issues.apache.org/jira/browse/NETBEANS-5587
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Gradle
>Affects Versions: 12.3
> Environment: Ubuntu Linux 19.04; Oracle JDK 8.
>Reporter: Svatopluk Dedic
>Assignee: Svatopluk Dedic
>Priority: Major
> Labels: VSNetBeans, pull-request-available
> Fix For: 12.4
>
> Attachments: nb-compile-classpath.jpg
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> I am working (for example) with project
>
> [g...@github.com:micronaut-projects/micronaut-starter.git|mailto:g...@github.com:micronaut-projects/micronaut-starter.git]
>
>
> I open the root one, and the 'starter-core' project. The explorer shows
> something like this (see nb-compile-classpath.jpg). But the compileClasspath
> from gradle dependencies seems a little richer:
>
> {code:java}
> +--- io.micronaut:micronaut-http -> 2.3.4-SNAPSHOT
> +--- io.micronaut:micronaut-http-client -> 2.3.4-SNAPSHOT
> | | +--- io.micronaut:micronaut-http:2.3.4-SNAPSHOT (*)
> | +--- io.micronaut:micronaut-http-client-core:2.3.4-SNAPSHOT
> | | +--- io.micronaut:micronaut-http:2.3.4-SNAPSHOT (*)
> | +--- io.micronaut:micronaut-http-netty:2.3.4-SNAPSHOT
> | | +--- io.micronaut:micronaut-http:2.3.4-SNAPSHOT (*)
> | +--- io.micronaut:micronaut-http:2.3.4-SNAPSHOT (c)
> | +--- io.micronaut:micronaut-http-client:2.3.4-SNAPSHOT (c)
> | +--- io.micronaut:micronaut-http-client-core:2.3.4-SNAPSHOT (c)
> | +--- io.micronaut:micronaut-http-netty:2.3.4-SNAPSHOT (c) {code}
> None of the 'snapshot' dependencies are displayed in the explorer tree (but
> they are repored in COMPILE ClassPath as roots).I tried to use
> ModuleDependency from GradleConfiguration to map back JARs to
> group:artifact:version coordinates, but in this case, the relevant
> ModuleDependency lists no artifacts.
>
--
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-4945) Newly applying java plugin on an open Gradle Project doe not propagate the Java SourceGroups
[ https://issues.apache.org/jira/browse/NETBEANS-4945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laszlo Kishalmi resolved NETBEANS-4945. --- Fix Version/s: 12.3 Resolution: Fixed > Newly applying java plugin on an open Gradle Project doe not propagate the > Java SourceGroups > - > > Key: NETBEANS-4945 > URL: https://issues.apache.org/jira/browse/NETBEANS-4945 > Project: NetBeans > Issue Type: Bug > Components: projects - Gradle >Reporter: Laszlo Kishalmi >Assignee: Jaroslav Tulach >Priority: Major > Fix For: 12.3 > > > Let the issue 1 identified in NETBEANS-4938 live here. > > Issue number 1 is much harder and requires a good knowledge on how the Lookup > system works. > So the Lookup of NBGradleProjectImpl consists of a basic lookup created at: > [https://github.com/apache/netbeans/blob/3a2cad159a2a60665653ce83a67547f679ec/extide/gradle/src/org/netbeans/modules/gradle/NbGradleProjectImpl.java#L161] > and a plugin dependent ProxyLookup at > [https://github.com/apache/netbeans/blob/3a2cad159a2a60665653ce83a67547f679ec/extide/gradle/src/org/netbeans/modules/gradle/NbGradleProjectImpl.java#L330] > > The issue is the following: > # Project loads with no plugins, the base set of lookups registers a > SourcesMerger > # Initially the only Sources implementation is for GENERIC_SOURCE_TYPE for > the project folder. > # On reload through the PluginDependentLookup a new Sources implementation > become available org.netbeans.modules.gradle.java.classpath.GradleSourcesImpl > from the Gradle Java project > # Unfortunately the SourceMerger is not pick up the new Sources > implementations -- 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-5629) Gradle project Lookups ordering not defined well
[
https://issues.apache.org/jira/browse/NETBEANS-5629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17337801#comment-17337801
]
Laszlo Kishalmi commented on NETBEANS-5629:
---
Telling the truth, I never considered that the order of these Lookups count.
BTW does this really count? Not just the orders on the ProjectServiceProviders?
> Gradle project Lookups ordering not defined well
>
>
> Key: NETBEANS-5629
> URL: https://issues.apache.org/jira/browse/NETBEANS-5629
> Project: NetBeans
> Issue Type: Bug
>Reporter: Svatopluk Dedic
>Priority: Major
>
> Individual Plugins can contribute to project Lookup. In my testcase, which
> uses java/java-base plugins, the Lookups loaded from
> *Projects/org-netbeans-modules-gradle/*** were loaded in the following order:
> {code:java}
> [java, , root, java-base, base]
> {code}
> When Groovy was also present, the order was
> {code:java}
> [java, groovy, , root, groovy-base, java-base, base]
> {code}
> (note - groovy after java, groovy-base before java-base). But with scala, the
> order is:
> {code:java}
> [java, scala, , root, java-base, scala-base, base]
> {code}
> (note - scala-base AFTER java-base).
> When opening a project with
> {code:java}
> apply plugin: 'groovy'
> {code}
> the order is yet different:
> {code:java}
> [groovy, java, , root, groovy-base, java-base, base]{code}
> The order is unreliable and I guess under some circumstances even the
> , xxx-base and xxx could be reordered as plugin names go through
> series of hashmaps.
--
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-5621) illegal state error
[ https://issues.apache.org/jira/browse/NETBEANS-5621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laszlo Kishalmi resolved NETBEANS-5621. --- Resolution: Incomplete Please reopen if you could provide more information. > illegal state error > --- > > Key: NETBEANS-5621 > URL: https://issues.apache.org/jira/browse/NETBEANS-5621 > Project: NetBeans > Issue Type: Bug > Components: java - Compiler, serverplugins - Tomcat >Affects Versions: 12.3 >Reporter: SHARON XAVIER >Priority: Major > > [^neterror] -- 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-5627) Gradle project Lookup inconsistent until OpenProjects.open()
[
https://issues.apache.org/jira/browse/NETBEANS-5627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laszlo Kishalmi reassigned NETBEANS-5627:
-
Assignee: Svatopluk Dedic (was: Laszlo Kishalmi)
> Gradle project Lookup inconsistent until OpenProjects.open()
>
>
> Key: NETBEANS-5627
> URL: https://issues.apache.org/jira/browse/NETBEANS-5627
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Gradle
>Reporter: Svatopluk Dedic
>Assignee: Svatopluk Dedic
>Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> Gradle fallback support recognizes several plugins from the directory
> structure (without reading the {{build.gradle}} file): groovy, java, scala,
> war.
> However project Lookup does not contain services for those Plugins, until
> OpenProjects.open() is called. The Project, however still untrusted, and
> unevaluated, starts to serve java-related services.
> This is inconsistent with project API's philosophy:
> [https://bits.netbeans.org/dev/javadoc/org-netbeans-modules-projectuiapi-base/org/netbeans/api/project/ui/OpenProjects.html]
> {quote}*Only certain operations should actually be aware of which projects
> are "open"; by default, all project functionality should be available whether
> it is open or not.*
> {quote}
> In this particular situation, ClassPath.getClassPath(sourceFile, SOURCE) does
> not return ClassPath even though Gradle fallback support recognizes 'java'
> and 'java-base' plugins until the project opens in the UI. For the rest of
> the IDE, the project appears as not having any sources in it - the returned
> ClassPath is not marked as incomplete, but simply does not exist.
--
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
