True, it is "just a file". It was actually my first idea, before I emailed
this list. But though it's "just a file", it's a file I'd have to keep editing
every time I updated maven.
It's likewise a file everyone else on the team needs to be taught to edit every
time they update maven.
Fun
Well, it’s just a file to edit.
--
http://bernd.eckenfels.net
Von: mark.yagnatin...@barclays.com.INVALID
Gesendet: Thursday, December 9, 2021 6:22:46 AM
An: users@maven.apache.org
Betreff: RE: request for documentation update about mirrors
> But if you ins
> But if you insist, I heared you can remove the blocked tag in your maven/conf
> settings.. ;)
But I can't, right? I'd have edit the global settings file bundled with maven
itself.
Or no?
for documentation update about mirrors
I hope this is the right mailing list; if I not, would appreciate a redirect.
In the release notes for maven 3.8.1, here:
https://maven.apache.org/docs/3.8.1/release-notes.html
There is a helpfully titled section "How to fix when I get a HTTP repository
bl
It sounds like you have multiple repositories defined on same nexus
instance. This is similar to setup we have. We have repositories for
third party libraries we use as well as a mirror of maven central for
the stuff we need.
Key difference between the setup you have and my setup is we have
I can't speak to your question about disabling the https requirement,
though my guess is that will be impossible and/or unpopular, likely by
design. If you could just turn it off, some people would just turn it off,
which defeats the purpose.
The root of my questions is that if your Nexus is
Sorry for broken threading; I wasn't subscribed to the mailing list so I never
got your reply; not sure how to fix it now. Now I'm subscribed.
Yes, we are using nexus. One of our nexus servers is even using HTTPS. The
rest are not.
As for why we have "many" ... I'm not entirely sure. It was
>
> since we are using a settings.xml which lists many http-only repositories,
> including one with an id of "central".
> Since these are all on our internal network
>
We don't let maven access the public internet
As your repositories are all internal, and you don't let maven connect to
the
I hope this is the right mailing list; if I not, would appreciate a redirect.
In the release notes for maven 3.8.1, here:
https://maven.apache.org/docs/3.8.1/release-notes.html
There is a helpfully titled section "How to fix when I get a HTTP repository
blocked?"
