Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release 3.1.4 #105

Closed
vorburger opened this issue Apr 17, 2023 · 4 comments
Closed

Release 3.1.4 #105

vorburger opened this issue Apr 17, 2023 · 4 comments

Comments

@vorburger
Copy link
Owner

exec-3.1.3...master

The last release 3.1.3 was on over 1 year ago on 2021-12-03.

This 3.1.4 contains lots of chore type work; the important "functional" changes (which motivate the release) are really:

@vorburger
Copy link
Owner Author

The last release 3.1.3 was on over 1 year ago on 2021-12-03.

And I have since lost my settings.xml ... 🤣 to be able to deploy.

How did this all work again? What user, what credz?

PS BTW this also blocks https://github.com/vorburger/MariaDB4j/issues/696...

@vorburger
Copy link
Owner Author

https://central.sonatype.org/publish/publish-maven/ reminded me how to use ~/.m2/settings.xml :

<settings>
  <servers>
    <server>
      <id>ossrh</id>
      <username>vorburger</username>
      <password>PASS</password>
    </server>
  </servers>
</settings>

but then I ran into [ERROR] Failed to execute goal org.sonatype.plugins:nexus-staging-maven-plugin:1.6.13:deploy (injected-nexus-deploy) on project exec: Execution injected-nexus-deploy of goal org.sonatype.plugins:nexus-staging-maven-plugin:1.6.13:deploy failed: Cannot decipher credentials to be used with Nexus!: org.sonatype.plexus.components.sec.dispatcher.shaded.SecDispatcherException: java.io.FileNotFoundException: /home/vorburger/.m2/settings-security.xml (No such file or directory) -> [Help 1]

I'll deal with this another time...

@vorburger
Copy link
Owner Author

https://maven.apache.org/guides/mini/guide-encryption.html explains what this ^^^ problem was about.

It happened because password happens to have contained ...{...}....

I could change it, but using mvn --encrypt-password is actually a good idea.

With that configured comme il faut:

    [INFO]  * Remote staging into staging profile ID "12bb4759cb85ae"
    [INFO]  * Created staging repository with ID "chvorburger-1051".
    [INFO]  * Staging repository at https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/chvorburger-1051

As usual, it wil take a moment for the release to replicate on mirrors.

I'll close this issue when I have manage to use this in a MariaDB4j PR.

@vorburger
Copy link
Owner Author

https://github.com/vorburger/MariaDB4j/pull/718, somewhat to my surprise (it used to take longer?), actually passed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant