Hi All, We have been able to resolve the issue, we are using Scala and sbt for specifying dependencies. Because the hadoop-core is resolved from cloudera respositories, we have to add the below resolver to our sbt conf.
*resolvers += "Cloudera" at "https://repository.cloudera.com/artifactory/public/ <https://repository.cloudera.com/artifactory/public/>"* this solves the problem. We looked into the pom.xml for mlcp and found that the repo url. Cheers, Basu On Mon, Feb 16, 2015 at 9:50 PM, Basavaraj Kalloli < [email protected]> wrote: > Hi MarkLogic Devs, > > Anything on this will really help, this just prevents MLCP from being used > as a managed dependency in so many Java projects. MLCP is an awesome tool > and we should definitely look at resolving this long standing bug. I have > tried with the recent version of content pump with MarkLogic 8 and this > issue still persists. AFAIK this should be a simple hadoop version fix in > the pom. > > Cheers, > Basu > > On Mon, Feb 16, 2015 at 4:31 PM, Basavaraj Kalloli < > [email protected]> wrote: > >> Hey All, >> >> Anyone has any updates/comments on this? We are stuck with committing all >> of the jars in our code for now. >> >> On Mon, Feb 2, 2015 at 3:56 PM, Basavaraj Kalloli < >> [email protected]> wrote: >> >>> Hi, >>> >>> We are trying to use mlcp (content pump) via the maven dependencies. We >>> are using it in a Scala app with ivy dependencies as below: >>> >>> "com.marklogic" % "mlcp-Hadoop1" % "1.1-1" >>> >>> using the repo: http://developer.marklogic.com/maven2 >>> >>> we get the below issues using either of the versions as below: >>> >>> *For mlcp-Hadoop1* >>> >>> "com.marklogic:mlcp-Hadoop1:1.1-1" --> unresolved dependency: >>> com.marklogic#marklogic-mapreduce1;1.2: >>> >>> *For mlcp-Hadoop2 (for all versions)* >>> >>> "com.marklogic:mlcp-Hadoop2:1.2-3" --> unresolved dependency: >>> org.apache.hadoop#hadoop-core;2.0.0-mr1-cdh4.3.0:: >>> >>> Both the jars are not available in any of the repos. As a result we have >>> to commit all the jars without having an automatic jar version dependency. >>> Can someone highlight if they have been able to resolve this issue in any >>> other way? >>> >>> Thanks, >>> >>> >>> >> >
_______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
