[GRADLE-1981] build script dependencies classloader problem Created: 04/Dec/11 Updated: 10/Feb/17 Resolved: 10/Feb/17 |
|
Status: | Resolved |
Project: | Gradle |
Affects Version/s: | 1.0-milestone-6 |
Fix Version/s: | None |
Type: | Bug | ||
Reporter: | Martin Kováčik | Assignee: | Unassigned |
Resolution: | Won't Fix | Votes: | 1 |
Attachments: | build.gradle |
Description |
I'm not able to use dom4j in my build scripts due to (what is seems to me) classloader issue. In my buildscript I have: buildscript { dependencies { classpath 'dom4j:dom4j:1.6.1' }} .... eclipseClasspath << { def classpathFile = file('.classpath') def reader = new org.dom4j.io.SAXReader() def doc = reader.read(classpathFile) .... }When I do the build I get: Execution failed for task ':eclipseClasspath'. It seems to me that there is a classloader issue between gradle's internal dom4j and my declared dom4j. I don't know if prior versions are affected, I just switched from M1 to M6 |
Comments |
Comment by Jisung, Ahn [ 08/Dec/11 ] |
I meet this problem also. build.gradle buildscript { dependencies { classpath group:'org.apache.poi', name:'poi', version:'3.7' classpath group:'org.apache.poi', name:'poi-ooxml', version:'3.7' }} import org.apache.poi.ss.usermodel.WorkbookFactory; task ttt << { return WorkbookFactory.create(new FileInputStream(file("a.xlsx"))); }and Run on M6 – FAIL gradle ttt FAILURE: Build failed with an exception.
but on M3 - OK gradle-1.0-milestone-3/bin/gradle ttt BUILD SUCCESSFUL I thin, This problem is critical bug. |
Comment by Jisung, Ahn [ 08/Dec/11 ] |
Attach Real exception log ---------------- |
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. |