Reviews from AWS Marketplace
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
External reviews are not included in the AWS star rating for the product.
Great tool. Easy to use and maintain
What do you like best about the product?
Simple tool that is easy to use. Wish some extra features and enhancements in the UI can be developed for better management.
What do you dislike about the product?
The documentation in https://help.sonatype.com/repomanager3 can be improved to be much more specific. Information on HA needs attention. Most of the questions related to HA are deflected by the customer support team to these documents that do not help.
What problems is the product solving and how is that benefiting you?
Storing binaries of different types of repo formats in an easy to consume manner.
- Leave a Comment |
- Mark review as helpful
Very powerful product for dependencies management
What do you like best about the product?
Easy to configure in order to setup dependencies directories from different sources : Maven, Python, .Net , ...
Many functionalities in order to control actions different users can realize on a specific repository for writing or reading access.
You can also use it as a proxy for your different packages managers : npm, python, .... so everything is downloaded to your Nexus repositories and cached for future consumers.
Many functionalities in order to control actions different users can realize on a specific repository for writing or reading access.
You can also use it as a proxy for your different packages managers : npm, python, .... so everything is downloaded to your Nexus repositories and cached for future consumers.
What do you dislike about the product?
Interface of version 3 is very limited. Repositories view has disappeared for regular users, and it would be great to be able to filter by repository in the "Browse Option"
What problems is the product solving and how is that benefiting you?
Nexus Sonatype helps us to manage the dependencies of our organization.
All software used is stored in our repositories, improving control, build repeatability , and reducing network traffic.
All software used is stored in our repositories, improving control, build repeatability , and reducing network traffic.
Recommendations to others considering the product:
Very good dependencies manager.
Professional edition seems to be quite expensive, but OSS edition is perfect for standard use.
Professional edition seems to be quite expensive, but OSS edition is perfect for standard use.
Nexus Repository from Sonatype OSS
What do you like best about the product?
Quite simple to have it working for maven artifacts.
What do you dislike about the product?
The interface is useful but it isn't pretty or confortable to use
What problems is the product solving and how is that benefiting you?
We storage the private maven artifacts of some of our projects, and control user that have access to those artifacts.
Recommendations to others considering the product:
Nexus is an good private maven artifact repository, with capacity to act as other SW repository (e.g. Docker Images) It is easy to set your components to be released in this private reposiotory.
As Maven Central repository runs also a Nexus Sonatype Repository, working with the Central repository or with self hosted Nexus OSS doesn't have many implications in the maven configuration of the artifacts, neither in the flow that artifact should follow whether publish public into Central or private into your own Nexus.
User management is quite good implemented allowing different access for each user regarding different level of access to each type of repository, but also inside the repositories can be configured regarding each of the artifacts, or groups of them.
User management hasn't integration with github or other Oauth2 providers, but you can make your own connector with the scrip executor that the Nexus provides.
Over all I believe is a good choice for maven/gradle artifact repositories, and I would give it a chance for other kind of SW.
As Maven Central repository runs also a Nexus Sonatype Repository, working with the Central repository or with self hosted Nexus OSS doesn't have many implications in the maven configuration of the artifacts, neither in the flow that artifact should follow whether publish public into Central or private into your own Nexus.
User management is quite good implemented allowing different access for each user regarding different level of access to each type of repository, but also inside the repositories can be configured regarding each of the artifacts, or groups of them.
User management hasn't integration with github or other Oauth2 providers, but you can make your own connector with the scrip executor that the Nexus provides.
Over all I believe is a good choice for maven/gradle artifact repositories, and I would give it a chance for other kind of SW.
showing 21 - 23