You need to provide the repositoryId=VeggieCorp (not id) property so that maven knows from which <server> configuration it has to read the credentials. $ mvn deploy:deploy-file \ -Durl=http://repo.veggiecorp.com/artifactory/ext-release-local \ -Dfile=crypto.jar \ -DpomFile=pom.xml \ -DrepositoryId=VeggieCorp See http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html
I don’t think Gradle has any built in support for accomplishing this, but you can clean the artifacts out from the classpath yourself. Inspired by this thread on the Gradle forums I came up with this: // The artifacts we don’t want, dependency as key and artifacts as values def unwantedArtifacts = [ “dep.location:example”: [ … Read more
The problem is that a plugin (location in this case) didn’t specify a fixed version of an Android library. So in order to find which versions are available, Gradle must go to the repository to check. In this case, that repository is Bintray, which has been down for days and returning HTTP 502 Bad Request. … Read more
Something like the following bash script will retrieve the lastest com.company:artifact snapshot from the snapshot repo: # Artifactory location server=http://artifactory.company.com/artifactory repo=snapshot # Maven artifact location name=artifact artifact=com/company/$name path=$server/$repo/$artifact version=$(curl -s $path/maven-metadata.xml | grep latest | sed “s/.*<latest>\([^<]*\)<\/latest>.*/\1/”) build=$(curl -s $path/$version/maven-metadata.xml | grep ‘<value>’ | head -1 | sed “s/.*<value>\([^<]*\)<\/value>.*/\1/”) jar=$name-$build.jar url=$path/$version/$jar # Download echo $url … Read more
That’s because you don’t have any publications. The artifactory-publish plugin works with maven-publish plugin and uploads publications. If you prefer working with the old maven plugin, you need artifactory plugin, not artifactory-publish. Take a look at the Overview part in “Working with Gradle” page of the official docs.
Gradle looks for gradle.properties files in these places: in project build dir (that is where your build script is) in sub-project dir in gradle user home (defined by the GRADLE_USER_HOME environment variable, which if not set defaults to USER_HOME/.gradle) Properties from one file will override the properties from the previous ones (so file in gradle … Read more
I’m sure that if you only talk about storing binaries from “mvn deploy” both will do fine. We use Artifactory very extensively with all upgrades along the way. Lots of projects, numerous snapshots deployed and external repos proxied. Not a single problem. I find it hard to explain how other people experience issues with its … Read more
Thanks for the question, it’s a good one! The main difference between artifactory and bintray is in the intended usage. Artifactory is a development-time tool, while Bintray is a release, distribution-time tool. It might look like a subtle difference, but it has a great impact on the feature set of the products: For development, you … Read more
I used to solve this issue by deleting the corresponding failed to download artifact directory in my local repo. Next time I run the maven command the artifact download is triggered again. Therefore I’d say it’s a client side setting. Nexus side (server repo side), this issue is solved configuring a scheduled task. Client side, … Read more