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 configured properly, https shouldn't be an issue to begin with. You should get in touch with your Nexus admin, get familiar with the historical and/or bureaucratic reasons for what exists, and get one of them configured to meet your needs, e.g. serving over https, a group that contains the aggregate of all the repos your settings.xml is referencing. They are likely already familiar with the need for https access. On Wed, Dec 8, 2021 at 6:26 PM <mark.yagnatin...@barclays.com.invalid> wrote: > 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 like that > when I got here. > I could ask around, but I'm not sure how much it matters. Could be > > * Historical reasons > > * Bureaucratic reasons > > * Or maybe even very good reasons that I happen to not know. > As it happens, many of these "separate" nexus repositories are on the same > server, but maven treats them all as if they are distinct, because they > have different paths. E.g. one might be > http://nexus.example.com:8080/nexus/content/groups/main/ > while another might be > > http://nexus.example.com:8080/nexus/content/repositories/UPLOAD-EXTERNAL-RELEASES/ > > Not sure if any of this answers your question. > > > _________________________________________________________________________________________________________________________________________________________________________________________________________________________________ > “This message is for information purposes only, it is not a > recommendation, advice, offer or solicitation to buy or sell a product or > service nor an official confirmation of any transaction. It is directed at > persons who are professionals and is not intended for retail customer use. > Intended for recipient only. This message is subject to the terms at: > www.barclays.com/emaildisclaimer. > > For important disclosures, please see: > www.barclays.com/salesandtradingdisclaimer regarding market commentary > from Barclays Sales and/or Trading, who are active market participants; > https://www.investmentbank.barclays.com/disclosures/barclays-global-markets-disclosures.html > regarding our standard terms for the Investment Bank of Barclays where we > trade with you in principal-to-principal wholesale markets transactions; > and in respect of Barclays Research, including disclosures relating to > specific issuers, please see http://publicresearch.barclays.com.” > > _________________________________________________________________________________________________________________________________________________________________________________________________________________________________ > If you are incorporated or operating in Australia, please see > https://www.home.barclays/disclosures/importantapacdisclosures.html for > important disclosure. > > _________________________________________________________________________________________________________________________________________________________________________________________________________________________________ > How we use personal information see our privacy notice > https://www.investmentbank.barclays.com/disclosures/personalinformationuse.html > > _________________________________________________________________________________________________________________________________________________________________________________________________________________________________ >
