[GRADLE-2518] import dependencies list from maven pom.xml file Created: 12/Oct/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.2
Fix Version/s: None

Type: New Feature
Reporter: Vyacheslav Sakhno Assignee: Unassigned
Resolution: Won't Fix Votes: 0


Ability to import dependencies list from maven build file(either read during each build or generate gradle script dependencies) would make transition from maven to Gradle easier.

Comment by Vyacheslav Sakhno [ 11/Jul/13 ]

Something like this

def loadLibs(config) {
config.each { name ->
file("${name}.lib.properties").eachLine { line->
if (!line.trim().empty)

{ project.dependencies.add(name, line) }



and this

def parsedProjectXml = (new XmlParser()).parse('dependencies-pom.xml')
println parsedProjectXml.@name
println parsedProjectXml.@version
println "ModuleList name : " + parsedProjectXml.modulelist[0].@name +
", shortName : " + parsedProjectXml.modulelist[0].@shortName

{ module -> println "Name : " + module.@name + ", version : " + module.@version }

println parsedProjectXml.description.text()

Comment by Adam Murdoch [ 16/Jul/13 ]

Does the build-setup plugin in Gradle 1.6 not solve this problem for you?

Comment by Vyacheslav Sakhno [ 22/Aug/13 ]

Sorry for long time before answer: it is not well documented. There is procedure where in the code which can be used as snippet though it is private now.

I consider the case then migrating from buggy, not satisfying all requirements Maven script to Gradle. That is why i want to import dependencies only from maven script.

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:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

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.

Generated at Wed Jun 30 12:24:08 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.