Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
Currently, on a project without <scm> configured, mvn release:update-versions ends up with:
Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.0:update-versions (default-cli) on project wicketstuff-dojo: Missing required setting: scm connection or developerConnection must be specified.
Updating versions recursively definitely does not need SCM.
Could this restriction be removed? Thanks.
Attachments
Issue Links
- is duplicated by
-
MRELEASE-584 Skip checking SCM setting for update-versions
- Closed