This shows the way to get gradle to use a local Archiva server to resolve dependencies (where the Archiva server in turn resolves to maven central).<\/p>\n
(Side comment: documentation for gradle is sparse, incomplete and out-of-date – e.g. ‘mavenRepo’ shows up in many searches.)<\/p>\n
So, if you’re interested in how to use a local Apache Archiva server in your environment, then this shows the correct ‘repositories’ section of your build.gradle file. In an upcoming post, I’ll document how to publish to your local Archiva server. Feel free to substitute “localhost” for the actual machine name or IP address of your Archiva server.<\/p>\n
Versions:
\narchiva: 2.0.1
\ngradle: 1.10<\/p>\n
\nrepositories {\n maven {\n url 'http:\/\/localhost:8080\/repository\/internal'\n }\n maven {\n url 'http:\/\/localhost:8080\/repository\/snapshots'\n }\n\n \/\/ if your Archiva is set up correctly, \n \/\/ then you don't need mavenCentral() here:\n \/\/ mavenCentral()\n}\n<\/pre>\nJust for documentation, this shows the “dependencies” section of the build.gradle file. If your Archiva is set up correctly, these 3 dependencies will actually download\/store 8 .jar files (because of transitive dependencies).<\/p>\n
\ndependencies {\n testCompile group: 'info.cukes', name: 'cucumber-java', version: '1.1.5'\n testCompile group: 'info.cukes', name: 'cucumber-junit', version: '1.1.5'\n testCompile group: 'junit', name: 'junit', version: '4+'\n}\n<\/pre>\nFiles that end up in your apache-archiva\/repositories directory (showing just the .jar files):<\/p>\n
\napache-archiva-2.0.1\/repositories\/internal\/junit\/junit\/4.11\/junit-4.11.jar\napache-archiva-2.0.1\/repositories\/internal\/org\/hamcrest\/hamcrest-core\/1.3\/hamcrest-core-1.3.jar\napache-archiva-2.0.1\/repositories\/internal\/info\/cukes\/cucumber-html\/0.2.3\/cucumber-html-0.2.3.jar\napache-archiva-2.0.1\/repositories\/internal\/info\/cukes\/cucumber-java\/1.1.5\/cucumber-java-1.1.5.jar\napache-archiva-2.0.1\/repositories\/internal\/info\/cukes\/gherkin\/2.12.1\/gherkin-2.12.1.jar\napache-archiva-2.0.1\/repositories\/internal\/info\/cukes\/cucumber-junit\/1.1.5\/cucumber-junit-1.1.5.jar\napache-archiva-2.0.1\/repositories\/internal\/info\/cukes\/cucumber-jvm-deps\/1.0.3\/cucumber-jvm-deps-1.0.3.jar\napache-archiva-2.0.1\/repositories\/internal\/info\/cukes\/cucumber-core\/1.1.5\/cucumber-core-1.1.5.jar\n<\/pre>\nDocumentation – The good stuff:
\nhttp:\/\/www.gradle.org\/docs\/1.8-rc-1\/release-notes.html<\/a> — shows the change from mavenRepo to maven.
\nhttp:\/\/gradleproject.wordpress.com\/2013\/02\/14\/multiple-maven-repositories-in-gradle\/<\/a> – now NOT to set up your repositories entry.<\/p>\nMore Documentation – The list of things that don’t work:
\nhttp:\/\/gradle.1045684.n5.nabble.com\/using-Archiva-maven-repo-w-Gradle-td4579298.html<\/a>
\nhttp:\/\/joshdiehl.com\/2011\/07\/11\/using-apache-archiva-with-gradle\/<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"This shows the way to get gradle to use a local Archiva server to resolve dependencies (where the Archiva server in turn resolves to maven central). (Side comment: documentation for gradle is sparse, incomplete and out-of-date – e.g. ‘mavenRepo’ shows … Continue reading