You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some companies use the DTP artifact registered in the Maven repository (https://mvnrepository.com/) in their deploy processes, but the release to the Maven repository has not been automated.
One step required for that is to get a Maven credential that can be used in GitHub Actions . I'll get @jzacsh or @holachuy and @calumcalder's help with setting that up and applying it.
The text was updated successfully, but these errors were encountered:
From what I can tell I think we're publishing through OSSRH, which is the 'legacy' path, but there doesn't seem to be official support for publishing via gradle through the new mechanism, so I think we can stick with OSSRH for now.
Docs for adding a new account for OSSRH publishing are here https://central.sonatype.org/register/legacy/. We already have the org.datatransferproject namespace, so once the account is created we just need to contact sonatype to add the account to that namespace.
Some companies use the DTP artifact registered in the Maven repository (https://mvnrepository.com/) in their deploy processes, but the release to the Maven repository has not been automated.
One step required for that is to get a Maven credential that can be used in GitHub Actions . I'll get @jzacsh or @holachuy and @calumcalder's help with setting that up and applying it.
The text was updated successfully, but these errors were encountered: