[jira] [Commented] (NETBEANS-3115) Netbeans (gradle) opens sources from source-jar files instead of (opened) projects
[ https://issues.apache.org/jira/browse/NETBEANS-3115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17338070#comment-17338070 ] Laszlo Kishalmi commented on NETBEANS-3115: --- Unfortunately I cannot reproduce this one any more. Using NetBeans 12.4 rc1 [~BES]please test it again. If it still happens I need probably another sample or a clear description how to reproduce this. > Netbeans (gradle) opens sources from source-jar files instead of (opened) > projects > -- > > Key: NETBEANS-3115 > URL: https://issues.apache.org/jira/browse/NETBEANS-3115 > Project: NetBeans > Issue Type: Bug > Components: projects - Gradle >Affects Versions: 11.1, 11.2, 11.3 >Reporter: Björn Schmidt >Assignee: Laszlo Kishalmi >Priority: Major > Labels: pull-request-available, usability > Fix For: 11.3 > > Attachments: nbtest2.tbz2 > > Time Spent: 2h > Remaining Estimate: 0h > > I'm using many independent gradle (java-library style) projects opened in NB. > They are not part of a big multi module project! > Whenever I want to navigate to a source file from another project relative to > the current one, Netbeans opens the source from > ~/.m2/repository.../project.jar and not from the local file of the referenced > project which is of course also opened in NB. > The same goes for debugging, I have to set breakpoints in .m2 sources (opened > from projects configurations navigator items). Debugging libraries from local > sources is not possible. > I already tried to disable all ~/.m2 Sources under Window->Debugging->Sources. > This doesn't change the behavior though (also not after restarting). > Even if it would change the behavior I then would have to disable all those > automatically added ~/.m2 (which are somehow preferred) references for every > project. > Maybe I'm just to stupid to find the right (global) option but ATM I think > this behavior is a bug. > — > Attached Test Case: > - open both projects in Netbeans > - deploy both project to local maven repo via custom rungradle action (clean > build publishToMavenLocal) > - go to NewClass in justalib > - ctrl click on the new Lib2Class statement > Expectation: Lib2Class gets opened from local filesystem, one can directly > edit the referenced file. > Actual: Lib2Class gets opened from local maven repo, read only. > > > -- 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-3115) Netbeans (gradle) opens sources from source-jar files instead of (opened) projects
[ https://issues.apache.org/jira/browse/NETBEANS-3115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17207894#comment-17207894 ] Björn Schmidt commented on NETBEANS-3115: - Netbeans 12.0 ist still "erratically" resolving source roots. When opening a project group with 20 or so projects, source roots get resolved correctly and point to the local files. But after compiling/building some of them, source roots of those projects get resolved from .m2 or not (can't see a pattern here). After a few iterations Netbeans seems to get completely lost and source roots no longer work at all, dependencies and/or import lines get marked red. This happens mostly if you break things by changing API functions in dependent project, but even after fixing everything NB still canÄt sime to figure out what's what. And then you restart NB and everything is fine again. [~lkishalmi] is this ticket still on the agenda? > Netbeans (gradle) opens sources from source-jar files instead of (opened) > projects > -- > > Key: NETBEANS-3115 > URL: https://issues.apache.org/jira/browse/NETBEANS-3115 > Project: NetBeans > Issue Type: Bug > Components: projects - Gradle >Affects Versions: 11.1, 11.2, 11.3 >Reporter: Björn Schmidt >Assignee: Laszlo Kishalmi >Priority: Major > Labels: pull-request-available, usability > Fix For: 11.3 > > Attachments: nbtest2.tbz2 > > Time Spent: 2h > Remaining Estimate: 0h > > I'm using many independent gradle (java-library style) projects opened in NB. > They are not part of a big multi module project! > Whenever I want to navigate to a source file from another project relative to > the current one, Netbeans opens the source from > ~/.m2/repository.../project.jar and not from the local file of the referenced > project which is of course also opened in NB. > The same goes for debugging, I have to set breakpoints in .m2 sources (opened > from projects configurations navigator items). Debugging libraries from local > sources is not possible. > I already tried to disable all ~/.m2 Sources under Window->Debugging->Sources. > This doesn't change the behavior though (also not after restarting). > Even if it would change the behavior I then would have to disable all those > automatically added ~/.m2 (which are somehow preferred) references for every > project. > Maybe I'm just to stupid to find the right (global) option but ATM I think > this behavior is a bug. > — > Attached Test Case: > - open both projects in Netbeans > - deploy both project to local maven repo via custom rungradle action (clean > build publishToMavenLocal) > - go to NewClass in justalib > - ctrl click on the new Lib2Class statement > Expectation: Lib2Class gets opened from local filesystem, one can directly > edit the referenced file. > Actual: Lib2Class gets opened from local maven repo, read only. > > > -- 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-3115) Netbeans (gradle) opens sources from source-jar files instead of (opened) projects
[ https://issues.apache.org/jira/browse/NETBEANS-3115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17106003#comment-17106003 ] Björn Schmidt commented on NETBEANS-3115: - I don't understand. Is that something changeable in options/prefs? > Netbeans (gradle) opens sources from source-jar files instead of (opened) > projects > -- > > Key: NETBEANS-3115 > URL: https://issues.apache.org/jira/browse/NETBEANS-3115 > Project: NetBeans > Issue Type: Bug > Components: projects - Gradle >Affects Versions: 11.1, 11.2, 11.3 >Reporter: Björn Schmidt >Assignee: Laszlo Kishalmi >Priority: Major > Labels: pull-request-available, usability > Fix For: 11.3 > > Attachments: nbtest2.tbz2 > > Time Spent: 2h > Remaining Estimate: 0h > > I'm using many independent gradle (java-library style) projects opened in NB. > They are not part of a big multi module project! > Whenever I want to navigate to a source file from another project relative to > the current one, Netbeans opens the source from > ~/.m2/repository.../project.jar and not from the local file of the referenced > project which is of course also opened in NB. > The same goes for debugging, I have to set breakpoints in .m2 sources (opened > from projects configurations navigator items). Debugging libraries from local > sources is not possible. > I already tried to disable all ~/.m2 Sources under Window->Debugging->Sources. > This doesn't change the behavior though (also not after restarting). > Even if it would change the behavior I then would have to disable all those > automatically added ~/.m2 (which are somehow preferred) references for every > project. > Maybe I'm just to stupid to find the right (global) option but ATM I think > this behavior is a bug. > — > Attached Test Case: > - open both projects in Netbeans > - deploy both project to local maven repo via custom rungradle action (clean > build publishToMavenLocal) > - go to NewClass in justalib > - ctrl click on the new Lib2Class statement > Expectation: Lib2Class gets opened from local filesystem, one can directly > edit the referenced file. > Actual: Lib2Class gets opened from local maven repo, read only. > > > -- 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-3115) Netbeans (gradle) opens sources from source-jar files instead of (opened) projects
[ https://issues.apache.org/jira/browse/NETBEANS-3115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105564#comment-17105564 ] Laszlo Kishalmi commented on NETBEANS-3115: --- It seems the Gradle Open project defined source resolver has lower priority than the Maven repository resolver. > Netbeans (gradle) opens sources from source-jar files instead of (opened) > projects > -- > > Key: NETBEANS-3115 > URL: https://issues.apache.org/jira/browse/NETBEANS-3115 > Project: NetBeans > Issue Type: Bug > Components: projects - Gradle >Affects Versions: 11.1, 11.2, 11.3 >Reporter: Björn Schmidt >Assignee: Laszlo Kishalmi >Priority: Major > Labels: pull-request-available, usability > Fix For: 11.3 > > Attachments: nbtest2.tbz2 > > Time Spent: 2h > Remaining Estimate: 0h > > I'm using many independent gradle (java-library style) projects opened in NB. > They are not part of a big multi module project! > Whenever I want to navigate to a source file from another project relative to > the current one, Netbeans opens the source from > ~/.m2/repository.../project.jar and not from the local file of the referenced > project which is of course also opened in NB. > The same goes for debugging, I have to set breakpoints in .m2 sources (opened > from projects configurations navigator items). Debugging libraries from local > sources is not possible. > I already tried to disable all ~/.m2 Sources under Window->Debugging->Sources. > This doesn't change the behavior though (also not after restarting). > Even if it would change the behavior I then would have to disable all those > automatically added ~/.m2 (which are somehow preferred) references for every > project. > Maybe I'm just to stupid to find the right (global) option but ATM I think > this behavior is a bug. > — > Attached Test Case: > - open both projects in Netbeans > - deploy both project to local maven repo via custom rungradle action (clean > build publishToMavenLocal) > - go to NewClass in justalib > - ctrl click on the new Lib2Class statement > Expectation: Lib2Class gets opened from local filesystem, one can directly > edit the referenced file. > Actual: Lib2Class gets opened from local maven repo, read only. > > > -- 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-3115) Netbeans (gradle) opens sources from source-jar files instead of (opened) projects
[ https://issues.apache.org/jira/browse/NETBEANS-3115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105401#comment-17105401 ] Björn Schmidt commented on NETBEANS-3115: - Apparently whenever you compile and publish a project, all the other open project that use it change to .m2 sources again. Open Netbeans with lots of independent projects open: References work Compile and deployToMavenLocal one of them: References suddenly get opened from .m2 Links from the Output window always open sources from .m2 @[~lkishalmi] would be very much appreciated if you could take another look at the problem. > Netbeans (gradle) opens sources from source-jar files instead of (opened) > projects > -- > > Key: NETBEANS-3115 > URL: https://issues.apache.org/jira/browse/NETBEANS-3115 > Project: NetBeans > Issue Type: Bug > Components: projects - Gradle >Affects Versions: 11.1, 11.2 >Reporter: Björn Schmidt >Assignee: Laszlo Kishalmi >Priority: Major > Labels: pull-request-available, usability > Fix For: 11.3 > > Attachments: nbtest2.tbz2 > > Time Spent: 2h > Remaining Estimate: 0h > > I'm using many independent gradle (java-library style) projects opened in NB. > They are not part of a big multi module project! > Whenever I want to navigate to a source file from another project relative to > the current one, Netbeans opens the source from > ~/.m2/repository.../project.jar and not from the local file of the referenced > project which is of course also opened in NB. > The same goes for debugging, I have to set breakpoints in .m2 sources (opened > from projects configurations navigator items). Debugging libraries from local > sources is not possible. > I already tried to disable all ~/.m2 Sources under Window->Debugging->Sources. > This doesn't change the behavior though (also not after restarting). > Even if it would change the behavior I then would have to disable all those > automatically added ~/.m2 (which are somehow preferred) references for every > project. > Maybe I'm just to stupid to find the right (global) option but ATM I think > this behavior is a bug. > — > Attached Test Case: > - open both projects in Netbeans > - deploy both project to local maven repo via custom rungradle action (clean > build publishToMavenLocal) > - go to NewClass in justalib > - ctrl click on the new Lib2Class statement > Expectation: Lib2Class gets opened from local filesystem, one can directly > edit the referenced file. > Actual: Lib2Class gets opened from local maven repo, read only. > > > -- 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-3115) Netbeans (gradle) opens sources from source-jar files instead of (opened) projects
[ https://issues.apache.org/jira/browse/NETBEANS-3115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17054852#comment-17054852 ] Björn Schmidt commented on NETBEANS-3115: - Interestingly it is working on "some" references of my real life projects but not on all. Can't see a pattern yet. What's never working though is class links in the Log window (for instance strack traces) those are still always opened from the local Maven cache. > Netbeans (gradle) opens sources from source-jar files instead of (opened) > projects > -- > > Key: NETBEANS-3115 > URL: https://issues.apache.org/jira/browse/NETBEANS-3115 > Project: NetBeans > Issue Type: Bug > Components: projects - Gradle >Affects Versions: 11.1, 11.2 >Reporter: Björn Schmidt >Assignee: Laszlo Kishalmi >Priority: Major > Labels: pull-request-available, usability > Fix For: 11.3 > > Attachments: nbtest2.tbz2 > > Time Spent: 2h > Remaining Estimate: 0h > > I'm using many independent gradle (java-library style) projects opened in NB. > They are not part of a big multi module project! > Whenever I want to navigate to a source file from another project relative to > the current one, Netbeans opens the source from > ~/.m2/repository.../project.jar and not from the local file of the referenced > project which is of course also opened in NB. > The same goes for debugging, I have to set breakpoints in .m2 sources (opened > from projects configurations navigator items). Debugging libraries from local > sources is not possible. > I already tried to disable all ~/.m2 Sources under Window->Debugging->Sources. > This doesn't change the behavior though (also not after restarting). > Even if it would change the behavior I then would have to disable all those > automatically added ~/.m2 (which are somehow preferred) references for every > project. > Maybe I'm just to stupid to find the right (global) option but ATM I think > this behavior is a bug. > — > Attached Test Case: > - open both projects in Netbeans > - deploy both project to local maven repo via custom rungradle action (clean > build publishToMavenLocal) > - go to NewClass in justalib > - ctrl click on the new Lib2Class statement > Expectation: Lib2Class gets opened from local filesystem, one can directly > edit the referenced file. > Actual: Lib2Class gets opened from local maven repo, read only. > > > -- 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-3115) Netbeans (gradle) opens sources from source-jar files instead of (opened) projects
[ https://issues.apache.org/jira/browse/NETBEANS-3115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17047289#comment-17047289 ] Björn Schmidt commented on NETBEANS-3115: - I still can't see any changes in build #1499. Attached test case still opens sources of referenced project (justalib) from the local maven source jar (if previously published with publishToMavenLocal) and not from the also opened project. > Netbeans (gradle) opens sources from source-jar files instead of (opened) > projects > -- > > Key: NETBEANS-3115 > URL: https://issues.apache.org/jira/browse/NETBEANS-3115 > Project: NetBeans > Issue Type: Bug > Components: projects - Gradle >Affects Versions: 11.1 >Reporter: Björn Schmidt >Assignee: Laszlo Kishalmi >Priority: Major > Labels: pull-request-available, usability > Fix For: 11.3 > > Attachments: nbtest2.tbz2 > > Time Spent: 2h > Remaining Estimate: 0h > > I'm using many independent gradle (java-library style) projects opened in NB. > They are not part of a big multi module project! > Whenever I want to navigate to a source file from another project relative to > the current one, Netbeans opens the source from > ~/.m2/repository.../project.jar and not from the local file of the referenced > project which is of course also opened in NB. > The same goes for debugging, I have to set breakpoints in .m2 sources (opened > from projects configurations navigator items). Debugging libraries from local > sources is not possible. > I already tried to disable all ~/.m2 Sources under Window->Debugging->Sources. > This doesn't change the behavior though (also not after restarting). > Even if it would change the behavior I then would have to disable all those > automatically added ~/.m2 (which are somehow preferred) references for every > project. > Maybe I'm just to stupid to find the right (global) option but ATM I think > this behavior is a bug. > — > Attached Test Case: > - open both projects in Netbeans > - deploy both project to local maven repo via custom rungradle action (clean > build publishToMavenLocal) > - go to NewClass in justalib > - ctrl click on the new Lib2Class statement > Expectation: Lib2Class gets opened from local filesystem, one can directly > edit the referenced file. > Actual: Lib2Class gets opened from local maven repo, read only. > > > -- 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-3115) Netbeans (gradle) opens sources from source-jar files instead of (opened) projects
[ https://issues.apache.org/jira/browse/NETBEANS-3115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17017923#comment-17017923 ] Laszlo Kishalmi commented on NETBEANS-3115: --- I've just discovered two bugs in the implementation. One can make it not working in some cases and the other causing an NPE. Fixing soon. > Netbeans (gradle) opens sources from source-jar files instead of (opened) > projects > -- > > Key: NETBEANS-3115 > URL: https://issues.apache.org/jira/browse/NETBEANS-3115 > Project: NetBeans > Issue Type: Bug > Components: projects - Gradle >Affects Versions: 11.1 >Reporter: Björn Schmidt >Assignee: Laszlo Kishalmi >Priority: Major > Labels: pull-request-available, usability > Fix For: 11.3 > > Attachments: nbtest2.tbz2 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > I'm using many independent gradle (java-library style) projects opened in NB. > They are not part of a big multi module project! > Whenever I want to navigate to a source file from another project relative to > the current one, Netbeans opens the source from > ~/.m2/repository.../project.jar and not from the local file of the referenced > project which is of course also opened in NB. > The same goes for debugging, I have to set breakpoints in .m2 sources (opened > from projects configurations navigator items). Debugging libraries from local > sources is not possible. > I already tried to disable all ~/.m2 Sources under Window->Debugging->Sources. > This doesn't change the behavior though (also not after restarting). > Even if it would change the behavior I then would have to disable all those > automatically added ~/.m2 (which are somehow preferred) references for every > project. > Maybe I'm just to stupid to find the right (global) option but ATM I think > this behavior is a bug. > — > Attached Test Case: > - open both projects in Netbeans > - deploy both project to local maven repo via custom rungradle action (clean > build publishToMavenLocal) > - go to NewClass in justalib > - ctrl click on the new Lib2Class statement > Expectation: Lib2Class gets opened from local filesystem, one can directly > edit the referenced file. > Actual: Lib2Class gets opened from local maven repo, read only. > > > -- 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-3115) Netbeans (gradle) opens sources from source-jar files instead of (opened) projects
[ https://issues.apache.org/jira/browse/NETBEANS-3115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17017796#comment-17017796 ] Björn Schmidt commented on NETBEANS-3115: - Do I have to enable this somewhere in options? Just installed Build #1458 but got the same behavior on my attached test case. > Netbeans (gradle) opens sources from source-jar files instead of (opened) > projects > -- > > Key: NETBEANS-3115 > URL: https://issues.apache.org/jira/browse/NETBEANS-3115 > Project: NetBeans > Issue Type: Bug > Components: projects - Gradle >Affects Versions: 11.1 >Reporter: Björn Schmidt >Assignee: Laszlo Kishalmi >Priority: Major > Labels: pull-request-available, usability > Fix For: 11.3 > > Attachments: nbtest2.tbz2 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > I'm using many independent gradle (java-library style) projects opened in NB. > They are not part of a big multi module project! > Whenever I want to navigate to a source file from another project relative to > the current one, Netbeans opens the source from > ~/.m2/repository.../project.jar and not from the local file of the referenced > project which is of course also opened in NB. > The same goes for debugging, I have to set breakpoints in .m2 sources (opened > from projects configurations navigator items). Debugging libraries from local > sources is not possible. > I already tried to disable all ~/.m2 Sources under Window->Debugging->Sources. > This doesn't change the behavior though (also not after restarting). > Even if it would change the behavior I then would have to disable all those > automatically added ~/.m2 (which are somehow preferred) references for every > project. > Maybe I'm just to stupid to find the right (global) option but ATM I think > this behavior is a bug. > — > Attached Test Case: > - open both projects in Netbeans > - deploy both project to local maven repo via custom rungradle action (clean > build publishToMavenLocal) > - go to NewClass in justalib > - ctrl click on the new Lib2Class statement > Expectation: Lib2Class gets opened from local filesystem, one can directly > edit the referenced file. > Actual: Lib2Class gets opened from local maven repo, read only. > > > -- 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-3115) Netbeans (gradle) opens sources from source-jar files instead of (opened) projects
[ https://issues.apache.org/jira/browse/NETBEANS-3115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17008937#comment-17008937 ] Björn Schmidt commented on NETBEANS-3115: - Think of 2 Libraries you're working on. One is an ASF Library, one is from JBOSS. lets say JBOSS is the consumer of the ASF lib. Both are opened in Netbeans. You have to tweak both libraries, implement some API extension in ASF for example. Use it in JBOSS. And you want to Debug what's going on. Would you want to edit the settings.gradle on the JBOSS lib just because in this very use-case to you and only you it is something like a composite build? And without it Netbeans will only want to open ASF files from the local repo? Additionally ASF lib might have some subpackages pulling in non standard maven modules for the build in which case the composite build will probably fail, cause composite builds are still under heavy developement and only work correctly for gradle core library modules. Even mixing war/jar sometimes still causes problems. > Netbeans (gradle) opens sources from source-jar files instead of (opened) > projects > -- > > Key: NETBEANS-3115 > URL: https://issues.apache.org/jira/browse/NETBEANS-3115 > Project: NetBeans > Issue Type: Bug > Components: projects - Gradle >Affects Versions: 11.1 >Reporter: Björn Schmidt >Assignee: Laszlo Kishalmi >Priority: Major > Labels: usability > Attachments: nbtest2.tbz2 > > > I'm using many independent gradle (java-library style) projects opened in NB. > They are not part of a big multi module project! > Whenever I want to navigate to a source file from another project relative to > the current one, Netbeans opens the source from > ~/.m2/repository.../project.jar and not from the local file of the referenced > project which is of course also opened in NB. > The same goes for debugging, I have to set breakpoints in .m2 sources (opened > from projects configurations navigator items). Debugging libraries from local > sources is not possible. > I already tried to disable all ~/.m2 Sources under Window->Debugging->Sources. > This doesn't change the behavior though (also not after restarting). > Even if it would change the behavior I then would have to disable all those > automatically added ~/.m2 (which are somehow preferred) references for every > project. > Maybe I'm just to stupid to find the right (global) option but ATM I think > this behavior is a bug. > — > Attached Test Case: > - open both projects in Netbeans > - deploy both project to local maven repo via custom rungradle action (clean > build publishToMavenLocal) > - go to NewClass in justalib > - ctrl click on the new Lib2Class statement > Expectation: Lib2Class gets opened from local filesystem, one can directly > edit the referenced file. > Actual: Lib2Class gets opened from local maven repo, read only. > > > -- 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-3115) Netbeans (gradle) opens sources from source-jar files instead of (opened) projects
[ https://issues.apache.org/jira/browse/NETBEANS-3115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17008927#comment-17008927 ] Laszlo Kishalmi commented on NETBEANS-3115: --- Hmm. >From Gradle: Composite builds allow you to: * combine builds that are usually developed independently, for instance when trying out a bug fix in a library that your application uses * decompose a large multi-project build into smaller, more isolated chunks that can be worked in independently or together as needed >From the provided example it seems your use case is falling in this cases, if >not, then I'm sorry I might not got it correctly. Composite builds can be used as a temporal command line parameter as well, there is no need to add it. There will be an upcoming feature to add all the Gradle projects opened in the IDE to the build process of the current build as Included Build. > Netbeans (gradle) opens sources from source-jar files instead of (opened) > projects > -- > > Key: NETBEANS-3115 > URL: https://issues.apache.org/jira/browse/NETBEANS-3115 > Project: NetBeans > Issue Type: Bug > Components: projects - Gradle >Affects Versions: 11.1 >Reporter: Björn Schmidt >Assignee: Laszlo Kishalmi >Priority: Major > Labels: usability > Attachments: nbtest2.tbz2 > > > I'm using many independent gradle (java-library style) projects opened in NB. > They are not part of a big multi module project! > Whenever I want to navigate to a source file from another project relative to > the current one, Netbeans opens the source from > ~/.m2/repository.../project.jar and not from the local file of the referenced > project which is of course also opened in NB. > The same goes for debugging, I have to set breakpoints in .m2 sources (opened > from projects configurations navigator items). Debugging libraries from local > sources is not possible. > I already tried to disable all ~/.m2 Sources under Window->Debugging->Sources. > This doesn't change the behavior though (also not after restarting). > Even if it would change the behavior I then would have to disable all those > automatically added ~/.m2 (which are somehow preferred) references for every > project. > Maybe I'm just to stupid to find the right (global) option but ATM I think > this behavior is a bug. > — > Attached Test Case: > - open both projects in Netbeans > - deploy both project to local maven repo via custom rungradle action (clean > build publishToMavenLocal) > - go to NewClass in justalib > - ctrl click on the new Lib2Class statement > Expectation: Lib2Class gets opened from local filesystem, one can directly > edit the referenced file. > Actual: Lib2Class gets opened from local maven repo, read only. > > > -- 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-3115) Netbeans (gradle) opens sources from source-jar files instead of (opened) projects
[ https://issues.apache.org/jira/browse/NETBEANS-3115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17008623#comment-17008623 ] Björn Schmidt commented on NETBEANS-3115: - That's not a solution but a dirty hack. I would try to band aid a missing feature with a completely different functionality. Once I add composite builds, grade starts to do all kinds of magic that I don't intend it to do. Composite builds are not yet stable and will break the build in many cases (non standard modules for instance) That it is a hack becomes very clear when you think about the fact that you'd have to add every (local) dependency of every gradle module to settings.gradle as well. As already written, this is probably not the intention behind composite builds. > Netbeans (gradle) opens sources from source-jar files instead of (opened) > projects > -- > > Key: NETBEANS-3115 > URL: https://issues.apache.org/jira/browse/NETBEANS-3115 > Project: NetBeans > Issue Type: Bug > Components: projects - Gradle >Affects Versions: 11.1 >Reporter: Björn Schmidt >Assignee: Laszlo Kishalmi >Priority: Major > Labels: usability > Attachments: nbtest2.tbz2 > > > I'm using many independent gradle (java-library style) projects opened in NB. > They are not part of a big multi module project! > Whenever I want to navigate to a source file from another project relative to > the current one, Netbeans opens the source from > ~/.m2/repository.../project.jar and not from the local file of the referenced > project which is of course also opened in NB. > The same goes for debugging, I have to set breakpoints in .m2 sources (opened > from projects configurations navigator items). Debugging libraries from local > sources is not possible. > I already tried to disable all ~/.m2 Sources under Window->Debugging->Sources. > This doesn't change the behavior though (also not after restarting). > Even if it would change the behavior I then would have to disable all those > automatically added ~/.m2 (which are somehow preferred) references for every > project. > Maybe I'm just to stupid to find the right (global) option but ATM I think > this behavior is a bug. > — > Attached Test Case: > - open both projects in Netbeans > - deploy both project to local maven repo via custom rungradle action (clean > build publishToMavenLocal) > - go to NewClass in justalib > - ctrl click on the new Lib2Class statement > Expectation: Lib2Class gets opened from local filesystem, one can directly > edit the referenced file. > Actual: Lib2Class gets opened from local maven repo, read only. > > > -- 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-3115) Netbeans (gradle) opens sources from source-jar files instead of (opened) projects
[ https://issues.apache.org/jira/browse/NETBEANS-3115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16981363#comment-16981363 ] Björn Schmidt commented on NETBEANS-3115: - Sorry made a mistake while renaming, uploaded a new reproducer / edited description > Netbeans (gradle) opens sources from source-jar files instead of (opened) > projects > -- > > Key: NETBEANS-3115 > URL: https://issues.apache.org/jira/browse/NETBEANS-3115 > Project: NetBeans > Issue Type: Bug > Components: projects - Gradle >Affects Versions: 11.1 >Reporter: Björn Schmidt >Assignee: Laszlo Kishalmi >Priority: Major > Labels: usability > Attachments: nbtest2.tbz2 > > > I'm using many independent gradle (java-library style) projects opened in NB. > They are not part of a big multi module project! > Whenever I want to navigate to a source file from another project relative to > the current one, Netbeans opens the source from > ~/.m2/repository.../project.jar and not from the local file of the referenced > project which is of course also opened in NB. > I already tried to disable all ~/.m2 Sources under Window->Debugging->Sources > but that doesn't change the behaviour (also not after restarting). > Even if it would change the behavior I then would have to disable all those > automatically added ~/.m2 (which are somehow preferred) references for every > project. > Maybe I'm just to stupid to find the right (global) option but ATM I think > this behavior is a bug. > — > Attached Test Case: > - open both projects in Netbeans > - deploy both project to local maven repo via custom rungradle action (clean > build publishToMavenLocal) > - go to NewClass in justalib > - ctrl click on the new Lib2Class statement > Expectation: Lib2Class gets opened from local filesystem, one can directly > edit the referenced file. > Actual: Lib2Class gets opened from local maven repo, read only. > > > -- 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-3115) Netbeans (gradle) opens sources from source-jar files instead of (opened) projects
[ https://issues.apache.org/jira/browse/NETBEANS-3115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16980882#comment-16980882 ] Laszlo Kishalmi commented on NETBEANS-3115: --- It seems the attached sample project are not dependent each other. The consumer is compilable adn the other is depending on some libtest2 project which is searched in the local maven repository. I obviously do not have that project at hand. > Netbeans (gradle) opens sources from source-jar files instead of (opened) > projects > -- > > Key: NETBEANS-3115 > URL: https://issues.apache.org/jira/browse/NETBEANS-3115 > Project: NetBeans > Issue Type: Bug > Components: projects - Gradle >Affects Versions: 11.1 >Reporter: Björn Schmidt >Assignee: Laszlo Kishalmi >Priority: Major > Labels: usability > Attachments: nbtest.tbz2 > > > I'm using many independent gradle (java-library style) projects opened in NB. > They are not part of a big multi module project! > Whenever I want to navigate to a source file from another project relative to > the current one, Netbeans opens the source from > ~/.m2/repository.../project.jar and not from the local file of the referenced > project which is of course also opened in NB. > I already tried to disable all ~/.m2 Sources under Window->Debugging->Sources > but that doesn't change the behaviour (also not after restarting). > Even if it would change the behavior I then would have to disable all those > automatically added ~/.m2 (which are somehow preferred) references for every > project. > Maybe I'm just to stupid to find the right (global) option but ATM I think > this behavior is a bug. > — > Attached Test Case: > - open both projects in Netbeans > - deploy both project to local maven repo via custom rungradle action (clean > build publishToMavenLocal) > - go to NewClass in providedlib > - ctrl click on the new Lib2Class statement > Expectation: Lib2Class gets opened from local filesystem, one can directly > edit the referenced file. > Actual: Lib2Class gets opened from local maven repo, read only. > > > -- 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-3115) Netbeans (gradle) opens sources from source-jar files instead of (opened) projects
[ https://issues.apache.org/jira/browse/NETBEANS-3115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16979895#comment-16979895 ] Laszlo Kishalmi commented on NETBEANS-3115: --- Thanks for reporting this issue! I have some suspections what is going on... > Netbeans (gradle) opens sources from source-jar files instead of (opened) > projects > -- > > Key: NETBEANS-3115 > URL: https://issues.apache.org/jira/browse/NETBEANS-3115 > Project: NetBeans > Issue Type: Bug > Components: projects - Gradle >Affects Versions: 11.1 >Reporter: Björn Schmidt >Assignee: Laszlo Kishalmi >Priority: Major > Labels: usability > Attachments: nbtest.tbz2 > > > I'm using many independent gradle (java-library style) projects opened in NB. > They are not part of a big multi module project! > Whenever I want to navigate to a source file from another project relative to > the current one, Netbeans opens the source from > ~/.m2/repository.../project.jar and not from the local file of the referenced > project which is of course also opened in NB. > I already tried to disable all ~/.m2 Sources under Window->Debugging->Sources > but that doesn't change the behaviour (also not after restarting). > Even if it would change the behavior I then would have to disable all those > automatically added ~/.m2 (which are somehow preferred) references for every > project. > Maybe I'm just to stupid to find the right (global) option but ATM I think > this behavior is a bug. > — > Attached Test Case: > - open both projects in Netbeans > - deploy both project to local maven repo via custom rungradle action (clean > build publishToMavenLocal) > - go to NewClass in providedlib > - ctrl click on the new Lib2Class statement > Expectation: Lib2Class gets opened from local filesystem, one can directly > edit the referenced file. > Actual: Lib2Class gets opened from local maven repo, read only. > > > -- 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
