-
-
Notifications
You must be signed in to change notification settings - Fork 78
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
Hardcoded logic might cause maven issue (protoc-3.19.0) #133
Comments
Hello - yes, can you share your configuration and ping me on gitter? |
Thank you, will do
…On Sun, Nov 20, 2022 at 8:31 PM os72 ***@***.***> wrote:
Hello - yes, can you share your configuration and ping me on gitter?
https://gitter.im/os72/community
—
Reply to this email directly, view it on GitHub
<#133 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOIHF3OEMSRJQSSFBDBUB6TWJJU7RANCNFSM6AAAAAASCCDXOI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
In our CI, our platform start prohibit anonymous access to our central maven repository.
Since restriction was applied I start getting the following error:
[ERROR] Failed to execute goal com.github.os72:protoc-jar-maven-plugin:3.11.4:run (default) on project ********: Error extracting protoc for version 3.19.0: Unsupported platform: protoc-3.19.0-osx-x86_64.exe ->
So far, we came up with the following guess regarding the root cause:
it is caused by hardcoded logic in plugin protoc-jar-maven-plugin. It will read the ${user.home}/.m2/settings.xml
https://github.com/os72/protoc-jar/blob/master/src/main/java/com/github/os72/protocjar/MavenUtil.java#L60
And it won't use user name/password when access artifact:https://github.com/os72/protoc-jar/blob/master/src/main/java/com/github/os72/protocjar/Protoc.java#L329-L337
So even you use customized settings.xml won't resolve this issue.
Any advise you might have?
Thanks,
Lior
The text was updated successfully, but these errors were encountered: