[
https://issues.apache.org/jira/browse/NETBEANS-3115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laszlo Kishalmi resolved NETBEANS-3115.
---------------------------------------
Resolution: Not A Problem
Thanks for the sample project. Now I can see what happens. I think the behavior
of the IDE is kind of correct. Once you published something to a repository and
use the published artifact, then the source shall come from that published
artifact.
However I feel the need of your use case as well. It is actually supported by
Gradle called composite builds. If you add a settings.gradle into the project
libthatuseslib with the following content:
{code:java}
includeBuild '../justalib'{code}
Then it will work just as you wished, maybe even better.
> 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: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
