This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 269546 - Gradle plugin fails to load sub-project and main project
Summary: Gradle plugin fails to load sub-project and main project
Status: NEW
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Code (show other bugs)
Version: -FFJ-
Hardware: PC All
: P3 normal (vote)
Assignee: issues@serverplugins
Depends on:
Reported: 2017-01-12 23:18 UTC by aplatypus
Modified: 2017-01-12 23:18 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

IDE log (291.16 KB, text/plain)
2017-01-12 23:18 UTC, aplatypus

Note You need to log in before you can comment on or make changes to this bug.
Description aplatypus 2017-01-12 23:18:11 UTC
Product Version = NetBeans IDE 8.2 (Build 201609300101)
Operating System = Windows 10 version 10.0 running on amd64
Java; VM; Vendor = 1.8.0_112
Runtime = Java HotSpot(TM) 64-Bit Server VM 25.112-b15

Reproducibility: Happens every time

Gradle plugin: Version:

  * We hava a project with several sub-projects
  * When one the sub-projects has an error on a Runtime dependency
  *  When you attempt to load just that sub-project, gradle barfs with this error:
        * What went wrong:
           A problem occurred evaluating project ':EventServer'.
           > Could not resolve all dependencies for configuration ':EventServer:runtime'.
           > Could not find

  * Somehow this error prevents the Gradle plugin from loading EVERY sub-project
  * Making resolving the actual problem very difficult, since the dependency is likely to be IN these same sub-projects!

  Gradle project is not usable in netbeans with this issue.

  In my view a  *runtime* dependency ought not prevent the project loading at all.
  We aren't running anything.  Surely the objective of a development environment is to facilitate development and needs to tolerate incidental errors like this one.
  I would expect the master project to load all Subprojects, including the sub-project with an error so that the problem may be resolved.

Further in this particular case, a missing dependency, it would be useful if the Gradle Plugin supported a repository search/resolution function like the maven repository search function.  I expect you can crib the code, if not just reuse it from the Maven plugin.
Comment 1 aplatypus 2017-01-12 23:18:18 UTC
Created attachment 163388 [details]
IDE log