Setup Github Action for Maven release about hdt-java HOT 18 CLOSED

@D063520 Seems to have worked: https://mvnrepository.com/artifact/org.rdfhdt/hdt-java-core

from hdt-java.

It is now in maven central:

https://repo1.maven.org/maven2/org/rdfhdt/hdt-java-core/

but not available in the search yet ....

not sure why it is taking so long

from hdt-java.

Hi,

we are done for now with the changes we needed:

• hdtCat
• hdtDiff
• new dictionary

we would need a dependency now for the new branch ... maybe a pre-release? How can we proceed on that?

from hdt-java.

@mielvds do you have the credentials? We can try to take care of this ....

from hdt-java.

I have, but they are personal. I'll see if i can create some for you or have some neutral ones.

FYI, this that need to be done for every manual MVM release

Set the ~/.m2/settings.xml

<settings>
  ...
  <servers>
    ...
    <server>
      <id>sonatype-nexus-snapshots</id>
      <username>your-sonatype-id</username>
      <password>your-sonatype-pwd</password>
    </server>
    <server>
      <id>sonatype-nexus-staging</id>
      <username>your-sonatype-id</username>
      <password>your-sonatyp-pwd</password>
    </server>
    <server>
      <id>github</id>
      <username>your-github-id</username>
      <password>your-github-pwd</password>
    </server>
  </servers>
  ...
</settings>

export RC_VERSION=X.X.X

from hdt-java.

Maybe one option is to add your credentials in the github action secrets
https://github.com/rdfhdt/hdt-java/settings/secrets/actions
I'm not sure but no one else might be able to see them, but we can still use them ....
https://docs.github.com/en/actions/publishing-packages/publishing-java-packages-with-maven#publishing-packages-to-the-maven-central-repository

from hdt-java.

sounds good! credentials are added

from hdt-java.

Mhmm ... was not that successfull ..... I created a new workflow for this:

https://github.com/rdfhdt/hdt-java/blob/master/.github/workflows/main.yml

This will be triggered on release and it is fine but it fails

https://github.com/rdfhdt/hdt-java/runs/5392029498?check_suite_focus=true

with a 401 Unauthorized

from hdt-java.

I'll see if I can figure out what the issue is

from hdt-java.

I have a theory .... this ID might be wrong

from hdt-java.

yep, that's definitely an issue!

from hdt-java.

@D063520 I believe Nexus staging rejects everything not -SNAPSHOT... but in any case: there are very cumbersome rules to deploy maven packages and I think you better check how this is handled first. Last time, @awoods helped me out, but it didn't stick with me.

from hdt-java.

It worked in fact .... we need just to check it appears on mvn central .....

from hdt-java.

@mielvds I think something went wrong .... which is strange since the CI did not complain
could you try to do it locally and note down the steps? It would be easier to configure the CI than properly ....

Other thing, could it be that you need to do a manual step by logging in:

To release your components, you can either release them directly from the command line, if you are using the Nexus Staging Maven Plugin or Ant Tasks or open your favorite browser and go to https://s01.oss.sonatype.org/ or follow our [detailed instructions](https://central.sonatype.org/publish/release/).
from https://central.sonatype.org/publish/release/#locate-and-examine-your-staging-repository

from hdt-java.

@mielvds I checked again the documentation. If I'm not wrong all went fine, but there is currently still a manual action required described here:

https://central.sonatype.org/publish/release/
https://oss.sonatype.org/service/local/staging/deploy/maven2/org/rdfhdt/hdt-java-parent/2.2/hdt-java-parent-2.2.pom

can you check?

from hdt-java.

Ok, I advanced a bit ... so I added and configured a plugin that automatically passes from the staging step to the release step. So this is fine. Also I'm signing now the artifcat. I think all should be fine this time. Let's see if it appears in mvn central tomorrow morning ...

from hdt-java.

yes i think it is ..

from hdt-java.

Hi @D063520 , awesome, you made it work! The delay is normal. IIRC the sonatype repo is not maven central, but syncs everything to maven central with a delay.

from hdt-java.