-
Notifications
You must be signed in to change notification settings - Fork 440
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
Maven plugin is not using maven repositories #2118
Comments
I'm now using contractMode=LOCAL and just add the contracts jar to module dependencies. Pros:
|
Even better I add the contracts jar to plugin dependencies. It's not polluting the project dependencies, and it makes sense - it's the plugin that uses the artifact. Interestingly you could use LOCAL or CLASSPATH mode with this approach to the same effect. Using
|
Can you provide more details on what you're trying to achieve? I'm a little bit lost |
I'm building with maven, I want to use existing repository settings (in pom.xml and/or settings.xml) instead of duplicating them in the plugin confiuration |
Describe the bug
I've tried adding repositories to the maven project and to settings but none of those work.
Instead I see
which makes no sense.
The downloading stubs fails with:
It works if I set the
contractsRepositoryUrl
(and credentials) manually in the plugin.But I'd rather not repeat the repository configuration there and use the built in maven mechanism for resolving dependencies.
It's all rather confusing. I'm building with Maven, why do I have to setup this artifact resolution manually?
The text was updated successfully, but these errors were encountered: