Loading Profile...
EMPLOYEE
Help Us Get the Word Out about Nexus
cjodea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
-
Inappropriate?One problem we've noticed is that people might not be aware that the best practice in Maven is to run a proxy between you and the public repository. It really does enable a whole different level of use with Maven. Allowing you to deploy your own artifacts and have some control over what is being downloaded from the Central repository. When you run Sonatype Nexus, and you configure a mirror, Maven is going to consult Nexus whenever it needs to locate an artifact. If Nexus doesn't have the artifact it is going to retrieve it and the cache the result for the next person to request the same artifact.
Nexus really speeds up Maven builds as your Maven instance is going to be hitting a local, dedicated resource and not the shared resource that is the Central Maven repository. If you run into someone who is complaining that Maven's interaction with the Central Repository is slow, you should let the know that the best way to solve the problem is to download Sonatype Nexus.
You can learn more about Sonatype Nexus at the Sonatype Nexus Pages on the Sonatype web site.
Oh and thanks cjodea.
I’m confident
-
Inappropriate?Nexus is great, but what I am missing is an "added security layer" - and I am not talking about the website and so on - I mean, when deploying a file to nexus that has already deployed, it would be nice if nexus would reply:
This artifact has already been deployen on 12/12/07 12:10:45 by Dooing. Do you really want to overwrite this file?!
(The name and date could be retrieved from the jars manifest file for example...)
I’m excited
2 Comments
Add a comment
This is one of the best points
-
I agree, there should be a configurable option to block attempts to overwrite non-snapshot artifacts. Perhaps this could be part of the upcoming security and authorization infrastructure. -
Beta-5 introduced role based security. In 1.0 you will have the ability to control who can redeploy artifacts based on the path.
