I have followed the guide of http://jroller.com/holy/entry/releasing_a_project_to_maven, and deployed my project into sonatype release repository successfully.
You can see my project in https://oss.sonatype.org/content/repositories/releases.
But I still can't find my project in Maven's Central Repository. And not everyone's nexus has config sonatype release repo , but I'm very sure everyone has Maven central repository.
So who can tell me how to let Maven central repo collect my project?
What should I need to do now?
Did you read and follow step 6 in the description you link to:
When the artifacts are in the release repository, add a comment to the
original ticket asking for them to be published to Maven Central. For
the first time they need to do it manually but since that on it will
be synchronized automatically every hour
Related
I'd like to mvn deploy an artifact with the suffix -DEVELOP into the pre-defined snapshot repo, but maven decides to push it into the release repository. I guess it is due to naming policy, the artifact withouth -SNAPSHOT goes to the release repo.
But if I set the snapshot repo explicitly for this deploy job, I get a 400 Bad request error. Is it because the snapshop repo only permits artifacts with the snap suffix?
Thanks in advance!
I am trying to promote artifact repository from Snapshot to Release in Nexus using Single artifact uploader in Jenkins . But this is not working for me.
Getting error like :
Could not resolve artifact: Could not find artifact
Snapshots.net.iin:snapshots:jar:0.0.1-SNAPSHOT in stagingrepo.
And I check from configuring the staging suite and got to know that Staging is part of the Nexus Repository Manager Pro.
I am using Nexus version - Nexus Repository Manager OSS 2.14.8-01.
I wanted to promote these snapshot artifacts to Release .So what's the best way to take this forward?
I would like to configure a nexus repository to only manage jars that I install. Right now it also retrieves jars from maven central and stores them in the repository. I don't want that to happen.
Can anyone point me in the right direction how this can be achieved?
When you say to store the "jars that are installed" , if you are referring to the artifacts being created by your project, you can have a hosted maven repository snapshot/release and use maven deploy plugin to upload it on to your nexus repository.
You can either create a profile in your pom and activate in your install it on mvn install phase to upload the artifacts to your nexus repository.
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.
How do I deploy an artifact into my archva repository? I want to configure my pom.xml to do this but I'm not sure how to set the groupdId and artifactId and version.
I'm under the impression this artifact must first be copied to my local repo via the install phase. How does it then get deployed to my archiva repo?
Take a look here - http://archiva.apache.org/docs/2.0.1/userguide/deploy.html Archiva have a nice guide, explaining how to deploy your artifact into it.
I hope it will help.