[
https://issues.apache.org/jira/browse/NETBEANS-2755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16874455#comment-16874455
]
Travis commented on NETBEANS-2755:
----------------------------------
Unfortunately, the workaround doesn't seem to be working for me.
My multi-project build has a lib/test/hamcrest-2.1.jar, and I added a
lib/test/hamcrest-2.1-sources.jar. The source attachment isn't working in the
editor when I browse into a hamcrest API. My gradle settings have "download
dependencies" as "never" (I also tried it with "only if required"), and the
"download sources" select is disabled and set to "always", and the "download
javadoc" is disabled and set to "never".
There is no dependency in the build.gradle for the source jar file. There is
only a dependency for the compiled jar file.
Does the code get confused because my dependencies are organized into an
additional level of hierarchy underneath the "lib" directory (which isn't the
default gradle project structure)? Or is there something I'm doing wrong here?
> Gradle project properties: Support for attaching sources for project
> libraries (in gradle.properties, or any project-versionable file)
> --------------------------------------------------------------------------------------------------------------------------------------
>
> Key: NETBEANS-2755
> URL: https://issues.apache.org/jira/browse/NETBEANS-2755
> Project: NetBeans
> Issue Type: Wish
> Components: projects - Gradle
> Reporter: Travis
> Assignee: Laszlo Kishalmi
> Priority: Minor
>
> I have a large multi-project build which we store in a git repo. Some of our
> developers use Netbeans and would like the library dependency .jar files to
> have attached sources, so that they can conveniently review their
> sources/javadocs during IDE code development. Although it's possible to
> attach sources, the attachment isn't saved inside the project properties, and
> isn't relative to the project root directory. So it doesn't seem possible to
> set up our repo so that netbeans users automatically get attaches library
> source files (where the source files are stored inside the same repo).
>
> Perhaps it would work if I modified our build.gradle to declare the sources
> as build dependencies, but this is bogus and undesirable.
>
> With the older gradle plug-in, I was able to add the sources as dependencies
> in the netbeans-init.gradle, and this worked fine.
>
> Is it possible for the new build-in Gradle support to be enhanced to allow
> library source attachments to be tracked, in a manner that allows both the
> sources and their attachment settings to live inside the project's source
> repo?
>
> (By the way, other than a few missing features and a couple of minor
> exceptions thrown, the new built-in gradle support is really nice, and
> generally works well. The existing customizability is also really good!
> Thank you!)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
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
