Svatopluk Dedic created NETBEANS-6307:
-----------------------------------------
Summary: Gradle project fails to identify artifact, if loaded by
different NB instance
Key: NETBEANS-6307
URL: https://issues.apache.org/jira/browse/NETBEANS-6307
Project: NetBeans
Issue Type: Bug
Components: projects - Gradle
Affects Versions: 12.6
Reporter: Svatopluk Dedic
Assignee: Svatopluk Dedic
Gradle projects have two caches. One stored in project, in *.gradle/nbcache*
directory. This cache stores project information and artifact coordinates. The
other cache is in *var/cache/gradle* and stores artfiact paths and for a binary
artifact it registers javadocs and sources.
When a project is primed for the first time, it is fully loaded and those two
caches are populated. Now imagine that the user *deletes* var/cache for some
reason, or starts a new instance of NetBeans.
Since the project already contains cached data and project is not trusted, it's
loaded from the cache to prevent gradle execution in an untrusted source tree.
But - the var/cache/gradle/* global cache *in this instance* of NetBeans is not
populated.
As a result, ModuleDependency objects from GradleConfiguration have proper
coordinates, but list no .jar artifact - even though the artifact is already
downloaded, and gradle daemon/compiler can work with it.
// cc: [~lkishalmi]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
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
