I am able to download the snapshots in Nexus Repo using Maven but not with Gradle?
Isn't Gradle compatible to get snapshots?
Related
I have artifacts in artifactory and I would like to download using maven. Could you please advise on how to download the artifacts from artifactory using specific build number?
I have added a repository to download artifacts and I have seen maven using that repository to download artifacts, but only for particular artifacts of that repository maven tries to download from mvn central repository. When I chek that artifact on added repository it's available. What could be the issue ? In which situations maven tries to download from central repository ?
Specific issues is highlighted in ,
Magnolia Demo project mvn build failed due to not able to fetch magnolia-setproperty-maven-plugin
All the Maven dependencies are first downloaded from your local repository, then if they are not found, Maven will try in any remote repository that you define in your POM file or the settings.xml and for last it will try to download from Maven Central.
Is there an option available to add the Gradle dependency cache to Sonatype Nexus repository so that i can use that cached dependencies for my project later.
The easiest way will be writing a Gradle script, that will exact all the artifacts from Gradle cache using Gradle Artifact Query API and save them in a Maven layout. Then you can import them to Nexus or Artifactory.
I am actually searching for an solution on how to automatically release artifacts for my open source projects to maven central/our company nexus. I am using Maven/Gradle and Travis CI to build the artifacts.
Ideally i just change the version of my maven gradle module to an release version, travis recognizes that and deploys the resulting artifact to nexus/maven central.
Has anyone ideas how to do that without building releases locally.
I've been trying to publish a rpm file (built using Gradle-custom plugin) to a yum snapshot repo using Gradle (nexus-yum plugin installed on repo). However, the upload fails and I get an error 400. I further understand that this is because my build script is attempting to upload my rpm artifact to a release repo instead of the snapshot repo. It would be great if anyone could share thoughts as to where I could be going wrong ?
Are you specifying the snapshots area of your repo?
The answer to : using gradle to deploy features.xml to nexus? explains how to update your maven settings.xml to exclude locations from a public repo and upload archives to releases area (same applies for snapshot)
Of course if you are publishing to a snapshot dir you must have a -SNAPSHOT extension.