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 parameter is not documented #15

Closed
DVanderstoken opened this issue May 1, 2016 · 14 comments
Closed

settings parameter is not documented #15

DVanderstoken opened this issue May 1, 2016 · 14 comments

Comments

@DVanderstoken
Copy link

Is this parameter intended to specify a settings file?

@aleksandr-m
Copy link
Owner

You mean this settings? It is maven settings, and not a settable property.

@DVanderstoken
Copy link
Author

Yes. This one. Is-it possible to specify maven settings file to be used during release ?

@aleksandr-m
Copy link
Owner

aleksandr-m commented May 4, 2016

@DVanderstoken
Copy link
Author

Yes, i know how to launch maven command line with specific settings file. But in your mojo, you re-launch maven command without allowing to specify a specific settings file. So, the default settings file is used and it isn't what i want...

@aleksandr-m
Copy link
Owner

What do you want to achieve then?

@aleksandr-m
Copy link
Owner

@DVanderstoken ping

@srsp
Copy link

srsp commented Jun 26, 2017

When I start

mvn gitflow:release-start -s ../jenkins-settings/mvn/settings.xml

then artifacts from a certain repository defined in the above settings.xml cannot be downloaded, because the repository answers with unauthorized. The settings file contains the credentials for this repository. So I think one of the mvn subprocesses does not honor the settings given to the parent mvn process.

I think this is what @DVanderstoken meant and currently I have the same problem. Is there a way to hand down the settings file to the child mvn process?

@aleksandr-m
Copy link
Owner

@srsp Could be. Any thoughts on how it can be reproduced w/o messing with custom repository?

@srsp
Copy link

srsp commented Jun 29, 2017

My setup is a bit complicated with a commercial artifact only available in repository that needs authentication. I tried to setup a minimal configuration to show the problem, but was not yet successful.

I found a way to work around this by changing our infrastructure. I will still try to reproduce it in a simple setup, but since the pressure is gone it might take a while.

@aleksandr-m
Copy link
Owner

@srsp I think new parameter can be introduced that will take arguments as a string and put them to underlying maven commands.

Thanks for reporting.

@aleksandr-m
Copy link
Owner

@srsp The argLine parameter was added in 1.8.0.

@srsp
Copy link

srsp commented Nov 6, 2017

@aleksandr-m Thank you! I will try it out.

@srsp
Copy link

srsp commented Aug 15, 2018

I know this is old and closed, but here's my feedback anyway: We use the argLine parameter and it works like a charm!

@aleksandr-m
Copy link
Owner

@srsp Feedback is always welcome! :)

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

No branches or pull requests

3 participants