Loading Profile...
Does Nexus Download Artifacts to a Server Cache or a Developer's Workstation?
I'm confused about you are supposed to use Nexus to download artifacts/poms from the Maven Central Repository. The documentation is clear on how to search for artifacts, and it says you just need to click the 'Download' link to download (section 4.4 of the PDF 'Repository Management with Nexus', edition 0.7). However, I would expect that clicking this link would automatically download the artifact into the appropriate location in the Nexus filesystem. However, on IE at least, the user is prompted to provide a download location. Does this mean the user needs to save every artifact off to some location, then use the 'Upload Artifact' feature to incorporate the file into Nexus? Thanks.
I’m confused and frustrated
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
The company marked this question as answered.
-
Inappropriate?The download option is available as a convenience for users ywho want to download a specific artifact or POM to their computer. When you choose "Download" from this interface you are not telling Nexus to download the artifact from the remote repository and store it in the local cache, you are attempting to download the artifact from Nexus. A side-effect of downloading an artifact to your computer is that Nexus will retrieve the artifact from the remote repository and store it in the local cache for the proxy repository.
When your build interacts with Maven as a repository manager it will retrieve the artifacts from the remote repository and store them in a local cache.
I’m happy
2 Comments
Add a comment
This answers the question
-
Hi Tim, thanks for replying so promptly. I think my misunderstanding comes from a pre-conception I had about Nexus: I assumed that Nexus would not automatically download an artifact from an External Remote Repository (e.g. Maven Central) to the Internal Remote Repository as a result of a developer's build referring to that artifact. I would have thought that an administrator would need to manually select each artifact to be downloaded from the net. So if a developer referenced an artifact in his/her build that does not exist in the Nexus repository, the build would fail.
Does Nexus provide any means of achieving this? One of the key reasons we are investigating repository managers is so we can control the artifacts that are available to developers' builds. For example, we would download 'approved' versions of Spring, etc., and it would be impossible for developer's builds to access non-approved versions.
Thanks,
Fred -
Fred, thanks for the question. Nexus Professional has support for Artifact Procurement which allows you to specify explicit rules for the artifacts allowed into an organization. For more information, you can watch the video and demonstration of the Procurement feature at the following URL: http://www.sonatype.com/products/nexu...
EMPLOYEE
