Change URL in poms to use HTTPS
See original GitHub issueThere are quite a few places in the jackson framework that use http links, these should be replaced with https links.
https://github.com/FasterXML/jackson-core/blob/master/pom.xml#L21 https://github.com/FasterXML/jackson-databind/blob/master/pom.xml#L17 https://github.com/FasterXML/jackson-databind/blob/master/pom.xml#L23
and probably many more
https://github.com/FasterXML/jackson-core/blob/master/pom.xml#L17 is already https
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:5
Top Results From Across the Web
Redirecting and Remapping with mod_rewrite
Solution: You can use mod_rewrite to redirect these URLs to the new server, but you might also consider using the Redirect or RedirectMatch...
Read more >SSA's Policy Information Site - POMS - Help - Social Security
If you wish to provide your users a link to a specific location in the POMS, please use the following syntax: The site...
Read more >Author Instructions - POMS
Submit your papers for consideration by the Production and Operations Management (POM) Journal to an appropriate Department Editor at the journal's ...
Read more >Welcome to Leader Dogs for the Blind |
Blindness changes everything. For people who are blind or visually impaired, the loss of sight is only the beginning of a life-changing reality....
Read more >Home - Duo Dogs, Inc.
Assistance Dogs · Facility Dogs ... that trains and connects dogs with people to cultivate positive change in individuals, families, and communities.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Using HTTP is the best way because of certificate expiration, maven SSL inconsistencies, maintenance not being performed, revocation lists being updated, and many many many MANY more.
While it is a nice idea, and does fit most portfolio’s, for open source fast moving projects, SSL in POM files is nothing more than a serious and very destructive practice.
Good for in house projects, terrible for maven open source.
Very dangerous yes. Research it please, like I said, don’t have the time or urge to google for you.
We all keep our repository on HTTP because we have all felt the burn when SSL slips, wasn’t a month ago no one could deploy to Sonartype Central for 4 days because the SSL cert went invalid and all overrides had to be done on the CI’s
No, you do not put HTTPS into Maven artifacts. Not on fast moving, fast deploying, open source projects. If you deploy once every 6 months, fine whatever, an SSL break isn’t the end of the world. If you are a fast moving open source project, you cannot allow 3rd party failures to impact your deployment cycle.
Turning off the HTTPS validation turned out to be the only way (check you stack overflows, check your maven error imports, look at the thousands of complaints about it).
Sorry, but full on disagreement with you. Not in Maven, Not on fast moving projects, not with such a dependency on a 3rd party. No 3rd party is immune, and every 3rd party has been affected by it, and many many open source developers have felt the pain., You will find this intentional “problem” in almost all repositories that have deployment cycles on-demand or less than 6 months.
Not going to happen.