-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RFE: Make the description of the Nexus staging repo configurable #31
Comments
Agreed.
Since a staging repo can have more than one group id, artifact id, and version, it's not clear which should be used. That of the root project? |
@szpak We currently replace the description when closing/releasing the staging repo. Is passing a new description mandatory for these operations? |
The description can now be customized on the extension or individual tasks and now defaults to the GAV of the root project. Resolves #31.
The description can now be customized on the extension or individual tasks and now defaults to the GAV of the root project. Resolves #31.
Most likely not and some default comment would be assigned by Nexus. However, I've always passed my own comment, so I'm not sure. |
The description can now be customized on the extension or individual tasks and now defaults to the GAV of the root project. Resolves #31.
Oh, right, you can have more than one "coordinate". Think, it doesn't really matter which artifact's used to create the description, as long it allows to distinguish different staging repos when you look into the list of staging repos in the Nexus UI. Maybe just the first artifact in a publication or so. If people really care, they can set their own description. |
It would be handy to be able to provide a custom description for the staging repo instead of just a string saying which plugin created it.
Additionally, can you mention the groupId+artifactId+version in the default description of the staging repo?
The text was updated successfully, but these errors were encountered: