[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ee4j-pmc] Migration to Jakarta installation of Nexus
|
Mikael Barbero wrote on 1/23/20 2:08 AM:
There is no change to do in the settings.xml file. It only
contains credentials for repositories with the id "ossrh":
<settings>
<servers>
<server>
<id>ossrh</id>
<username>jaf-bot</username>
<password>*********</password>
</server>
</servers>
</settings>
Where do the credentials for the jakarta
repository come from?
Where should they come from?
If I use the -Pstaging profile, I seem to get the required
credentials.
Isn't the parent pom redefining "ossrh" to refer to the Jakarta
Nexus? Isn't that supposed to make everything "just work"?
Credentials are defined by the Foundation and setup in your Jenkins instance. Yes, it should just work, that was the purpose of my reply: no need to touch to the settings.xml file.
I don't understand your comment at all, sorry.
Back in the java.net days, I had profiles defined in my pom.xml for
deployment. With the move to Eclipse, most of the configuration for
those profiles disappeared and was moved to the parent pom. I kept
the profile names around to avoid break scripts, but it sometimes
meant that I had to use two profiles when deploying - one from the
parent pom and one from my pom.
You can see in the comments in the commit above the reason that
profile exists.
I was just mentioning this commit as it appeared to have been done right after the previous release and you may never have tried to push to staging with this commit.
To conclude: I don't know why it does it does not work as before for you, but it's certainly not an issue with the configuration of .m2/settings.xml on the Jenkins instance.
Mikaël Barbero Team Lead - Release Engineering | Eclipse Foundation 🐦 @mikbarbero
|
Attachment:
signature.asc
Description: Message signed with OpenPGP
