[GRADLE-2908] ResolvedArtifactFactory appears to retain references to Ivy's Artifact structure. Created: 30/Sep/13 Updated: 10/Feb/17 Resolved: 10/Feb/17 |
|
Status: | Resolved |
Project: | Gradle |
Affects Version/s: | None |
Fix Version/s: | None |
Type: | Bug | ||
Reporter: | Gradle Forums | Assignee: | Unassigned |
Resolution: | Won't Fix | Votes: | 0 |
Description |
While looking at DefaultResolvedArtifact, I see a comment "The artifact instance drags in a whole pile of stuff that we don't want to retain references to." But I believe the artifactSource being passed in from DefaultResolvedConfigurationBuilder has some closures which retain a reference on the artifact object nonetheless, in line 43 of ResolvedArtifactFactory. If you truly want to the artifact to be able to be garbage collected, then ResolvedArtifactFactory needs to be changed. This is not necessarily affecting me, I just noticed this in the code. Honestly I'd rather have easier access to the ModuleDescriptor from a ResolvedModule. |
Comments |
Comment by Benjamin Muschko [ 15/Nov/16 ] |
As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub. We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to. Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:
We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle! |
Comment by Benjamin Muschko [ 10/Feb/17 ] |
Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved. |