maven: use 'https' instead of 'http'

[sullis]

No description provided.

[Stephan202]

While less important, the xsi:schemaLocations can also be updated to reference https.

(Not the namespace URI itself, thus:)

xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd"

[hazendaz]

@Stephan202 All of maven bits can be 'https' but requires this added to release plugin <addSchema>false</addSchema>.

See here with project already using https for maven bits for this purpose.

[Stephan202]

@hazendaz I didn't know that; TIL 😄

This doesn't seem like a trade-off I'd advocate though. In general the namespace is a URI rather than a URL, so tools should not try to resolve it. (That's what the schema location is for, after all.) Since it'd mean that the schema is then missing from the released artifact, that seems like a bit too much to give up.

(But I can see how one would go this route to avoid any and all http:// references. 🙂.)

[hazendaz]

@Stephan202 Glad to pass on some knowledge :) As long as the schema is present to start with, what that flag does is tell maven to not delete and re-add during the release process. Basically maven is trying to fix invalid information and I guess probably since they changed it a long time ago its preferable to be the proper one. The 'hack', if you will, came directly from the maven team when I was checking with them feasibility of removing all 'http' so global searches on real items that need resolved were much easier to find especially in 100s of poms :) While there were zero plans at that time to change and I suspect that is still the case due to same reasons you mention, this was a great compromise. All the IDE's still behave properly as well which was mostly to be expected.