Skip to content
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

settings/global settings file not propagated to mvn versions #55

Closed
raksja opened this issue Jul 12, 2017 · 1 comment
Closed

settings/global settings file not propagated to mvn versions #55

raksja opened this issue Jul 12, 2017 · 1 comment

Comments

@raksja
Copy link

raksja commented Jul 12, 2017

Ran this in a docker which has connectivity only to enterprise mvn repos/plugin repos.

mvn -B gitflow:release-start -DreleaseVersion=2.0.0 --global-settings enterprisesettings.xml -X

After it created a release branch, its trying to set the version using this below plugin. But it fails as its not using the settings file initially passed.

[DEBUG] mvn org.codehaus.mojo:versions-maven-plugin:2.1:set -DnewVersion=2.0.0 -DgenerateBackupPoms=false

[ERROR] [ERROR] Plugin org.codehaus.mojo:versions-maven-plugin:2.1 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.codehaus.mojo:versions-maven-plugin:jar:2.1: Could not transfer artifact org.codehaus.mojo:versions-maven-plugin:pom:2.1 from/to central (https://repo.maven.apache.org/maven2): repo.maven.apache.org: Name does not resolve: Unknown host repo.maven.apache.org: Name does not resolve

Error makes sense as we have no connectivity to outside, but that plugin is available in our enterprise repo which is defined in enterprisesettings.xml.

@aleksandr-m
Copy link
Owner

See #53

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants