You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@netbeans.apache.org by "Björn Schmidt (Jira)" <ji...@apache.org> on 2020/01/06 08:28:00 UTC

[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&focusedCommentId=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-unsubscribe@netbeans.apache.org
For additional commands, e-mail: commits-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists