Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Similar issue with authorization with maven as with gradle
See original GitHub issueWhat happened?
Maven tries to upload jar without authorization header which is then declined. Previously experienced elsewhere: https://stackoverflow.com/questions/48631422/maven-not-adding-authorization-header
Extending the config in settings.xml beyond username and password helps:
<server> <id>some.repo</id> <configuration> <httpHeaders> <property> <name>Authorization</name> <value>Basic (hash)</value> </property> </httpHeaders> </configuration> <username>... </username> <password>... </password> </server>
perhaps something to update the documentation with (and not really a bug)
Many thanks for your efforts.
Reposilite version
2.x
Relevant log output
No response
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I think we can close this 😃
To avoid strange behaviours, I also recommend to bump plugins to latest versions, e.g.
maven-deploy-plugin:2.7is already 11 years old. There were a lot of changes since then and in most cases it’s fully compatibile with previous setups.