[
https://issues.apache.org/jira/browse/NETBEANS-3115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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: [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
