Re: POM relocation to an other version number is not fully supported in Gradle

2018-09-21 Thread Taher Alkhateeb
I think we can safely ignore. If a problem arises we hardwire the dependency, so not a big deal at all On Fri, Sep 21, 2018, 6:15 PM Girish Vasmatkar < girish.vasmat...@hotwaxsystems.com> wrote: > Hi Jacques > > It looks like every transitive dependency defined in our build.gradle to > xml-apis

Re: POM relocation to an other version number is not fully supported in Gradle

2018-09-21 Thread Girish Vasmatkar
Hi Jacques It looks like every transitive dependency defined in our build.gradle to xml-apis is getting resolved to xml-apis:2.0.2. +--- xom:xom:1.2.5 ||+--- xml-apis:xml-apis:1.3.03 -> 2.0.2 +--- xml-apis:xml-apis:1.3.04 -> 2.0.2 org.apache.xmlrpc:xmlrpc-client:3.1.3 |\---

Re: POM relocation to an other version number is not fully supported in Gradle

2018-09-21 Thread Jacques Le Roux
Le 21/09/2018 à 13:29, Jacques Le Roux a écrit : Hi, I cleared by Gradle cache, so had to reload all. my I stumbled upon this is in log    Download https://jcenter.bintray.com/xml-apis/xml-apis/2.0.2/xml-apis-2.0.2.pom    POM relocation to an other version number is not fully supported in