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.

Sign up for GitHub

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

Jump to bottom

Add Maven Build #217

Closed

ALRubinger opened this issue Feb 5, 2024 · 5 comments

Assignees

Contributor

ALRubinger commented Feb 5, 2024 •

edited

Implement a Maven build; from some team notes we'd like to move to this build system for clarity and inter-project consistency.

This process will also lay bare the necessary auditing of dependencies to align versions.

WIP in PR #261 and upstream branch issue-217/maven-build

The text was updated successfully, but these errors were encountered:

ALRubinger self-assigned this

ALRubinger added a commit to ALRubinger/web5-kt that referenced this issue


          Issue TBD54566975#217 - Begin laying out Maven build for web5-kt

9a2a559

Stopped where cyclic dependency was found common<>crypto packages. Ping team for guidance on how to split this up.

Contributor Author

ALRubinger commented Feb 5, 2024

WIP on my branch: https://github.com/ALRubinger/web5-kt/tree/issue-217/maven-build

ALRubinger added a commit to ALRubinger/web5-kt that referenced this issue


          Issue TBD54566975#217 - Fix cyclic dependency by moving ZBase32Test t…

bbabb4e

…o crypto

Now compilation fails due to weird Kotlin compiler error with no info

ALRubinger added a commit to ALRubinger/web5-kt that referenced this issue


          Issue TBD54566975#217 - Begin laying out Maven build for web5-kt

2e5a300

Stopped where cyclic dependency was found common<>crypto packages. Ping team for guidance on how to split this up.

ALRubinger added a commit to ALRubinger/web5-kt that referenced this issue


          Issue TBD54566975#217 - Fix cyclic dependency by moving ZBase32Test t…

ff9b2e6

…o crypto

Now compilation fails due to weird Kotlin compiler error with no info

Contributor Author

ALRubinger commented Feb 6, 2024

WIP now in an upstream branch for sharing with others: https://github.com/TBD54566975/web5-kt/tree/issue-217/maven-build

Contributor Author

ALRubinger commented Feb 10, 2024

Closing this, going to address version alignment in the existing Gradle builds in #226

ALRubinger closed this as completed

ALRubinger added a commit that referenced this issue


          Issue #217 - Begin laying out Maven build for web5-kt

04e734d

Stopped where cyclic dependency was found common<>crypto packages. Ping team for guidance on how to split this up.

ALRubinger added a commit that referenced this issue


          Issue #217 - Fix cyclic dependency by moving ZBase32Test to crypto

26ad953

Now compilation fails due to weird Kotlin compiler error with no info

Contributor Author

ALRubinger commented Mar 5, 2024

Re-opening; needed for version alignment between Web5 and tbDEX

ALRubinger reopened this

ALRubinger added a commit that referenced this issue


          Issue #217: Common, Testing, Crypto compiling and passing tests

2f3235a

ALRubinger added a commit that referenced this issue


          Issue #217: Set deps for DIDs package, compile failure as they are no…

c2e48e4

…t on CP?

ALRubinger added a commit that referenced this issue


          Issue #217: DID component Mavenized, build passing

4af67e5

ALRubinger added a commit that referenced this issue


          Issue #217: Full Maven build for all modules working and tests pass

d3439b0

ALRubinger added a commit that referenced this issue


          Issue #217 - Begin laying out Maven build for web5-kt

ee487df

Stopped where cyclic dependency was found common<>crypto packages. Ping team for guidance on how to split this up.

ALRubinger added a commit that referenced this issue


          Issue #217 - Fix cyclic dependency by moving ZBase32Test to crypto

6b3990d

Now compilation fails due to weird Kotlin compiler error with no info

ALRubinger added a commit that referenced this issue


          Issue #217: Common, Testing, Crypto compiling and passing tests

13105a3

ALRubinger added a commit that referenced this issue


          Issue #217: Set deps for DIDs package, compile failure as they are no…

1195f0b

…t on CP?

ALRubinger added a commit that referenced this issue


          Issue #217: DID component Mavenized, build passing

6c66018

ALRubinger added a commit that referenced this issue


          Issue #217: Full Maven build for all modules working and tests pass

d88d6fb

ALRubinger added a commit that referenced this issue


          Issue #217: Fixes to keep pace with upstream

9e34b4d

ALRubinger added a commit that referenced this issue


          Issue #217: Set 3rdparty repo to TBD, not externals

5253ca7

ALRubinger added a commit to ALRubinger/web5-kt that referenced this issue


          Issue TBD54566975#217: Remove Gradle scripts and configs

b6e3917

* Will help license and security scanning read this as a Maven project only

ALRubinger added a commit that referenced this issue


          Issue #217 - Begin laying out Maven build for web5-kt

944d025

Stopped where cyclic dependency was found common<>crypto packages. Ping team for guidance on how to split this up.

ALRubinger added a commit that referenced this issue


          Issue #217 - Fix cyclic dependency by moving ZBase32Test to crypto

485a43f

Now compilation fails due to weird Kotlin compiler error with no info

ALRubinger added a commit that referenced this issue


          Issue #217: Common, Testing, Crypto compiling and passing tests

c11ae47

ALRubinger added a commit that referenced this issue


          Issue #217: Set deps for DIDs package, compile failure as they are no…

7f394b9

…t on CP?

ALRubinger added a commit that referenced this issue


          Issue #217: Fix failing dokka.sh in CI

7ed5160

ALRubinger added a commit that referenced this issue


          Issue #217: Remove testing configs to be ready for merge

93948e8

ALRubinger added a commit that referenced this issue


          Issue #217: Update to latest web5-spec from submodule

669ebb0

ALRubinger added a commit that referenced this issue


          Issue #217: Update to bring in changes from f5a0488

f4c586c

ALRubinger added a commit that referenced this issue


          Issue #217 - Convert and port Gradle to Maven build for web5-kt

6ee4a5d

* No security or license issues
* All modules build and tests pass
* Dependencies all correctly set via dependencyManagement which may be consumed by other projects (ie. tbDEX)
* Ported Dokka to use Dokka CLI in GitHub Actions and instructions to run locally
* Change: API Docs via Dokka now have no left sidebar because Gradle plugin enabled multimodule for us.
* Detekt ported through Maven plugin
* Ported Kover; we have coverage via CodeCov
* Switched to use TBD Artifactory for single repo declaration to get 3rdparty deps not in Maven Central
* Update README to reflect new build usage
* Publish to TBD Artifactory
* While we are at it, renames to GitHub Actions for clarity and correctness
* Set Surefire patterns to run Test Vectors
* Publish every build as a SNAPSHOT in format X.Y.Z-commit-$shortSHA-SNAPSHOT
* Validate that SNAPSHOT publishing has a version defined that ends in -SNAPSHOT
* SNAPSHOTs deployed to TBD Artifactory for every push to main, with version commit-$shortSHA-SNAPSHOT
* TBD Artifactory Release and Publish, with tagging of git
* API Docs Publishing - Verifiable at: https://alrubinger.github.io/web5-kt/docs/htmlMultiModule/index.html
* Maven Central Publishing
* Include sources in publishing
* Sign all artifacts (POMs, JARs, Source JARs) with GPG in deploy to Artifactory and Maven Central
* Only require one input (the release version) to trigger a release. Infer the next development version as a patch increment above the release version
* Introduce a distribution POM to bring in all Web5 deps in a single declaration
* Keep pom.xml effectively versionless at 0.0.0-main-SNAPSHOT; version at release time
* Publish to Maven Central on successful release and publish to TBD
  Artifactory
* Update README to reflect changes above and document all build and
  pipeline features
* Do not double-trigger uploads to Artifactory, Test Vectors, or CodeCov by separating out MacOS and Ubuntu jobs
* Make 'distribution' folder for the distribution pom.xml so that tbdex-kt can follow same convention
* Rebased all work atop b8a1a13

TODO:
* Switch ALRubinger in SCM configuration of pom.xml to TBD again
* Remove the comments at the end of build-test-publish workflow to
  re-enable sdk-report-runner

ALRubinger added a commit that referenced this issue


          Issue #217: Remove testing configs to be ready for merge

03cd9d2

This was referenced Mar 29, 2024

Create Android distribution #287

Open

[USE CASE]: Document android usage TBD54566975/developer.tbd.website#1262

Open

ALRubinger added a commit that referenced this issue


          Issue #217 - Convert and port Gradle to Maven build for web5-kt

fd3acf6

* No security or license issues
* All modules build and tests pass
* Dependencies all correctly set via dependencyManagement which may be consumed by other projects (ie. tbDEX)
* Ported Dokka to use Dokka CLI in GitHub Actions and instructions to run locally
* Change: API Docs via Dokka now have no left sidebar because Gradle plugin enabled multimodule for us.
* Detekt ported through Maven plugin
* Ported Kover; we have coverage via CodeCov
* Switched to use TBD Artifactory for single repo declaration to get 3rdparty deps not in Maven Central
* Update README to reflect new build usage
* Publish to TBD Artifactory
* While we are at it, renames to GitHub Actions for clarity and correctness
* Set Surefire patterns to run Test Vectors
* Publish every build as a SNAPSHOT in format X.Y.Z-commit-$shortSHA-SNAPSHOT
* Validate that SNAPSHOT publishing has a version defined that ends in -SNAPSHOT
* SNAPSHOTs deployed to TBD Artifactory for every push to main, with version commit-$shortSHA-SNAPSHOT
* TBD Artifactory Release and Publish, with tagging of git
* API Docs Publishing - Verifiable at: https://alrubinger.github.io/web5-kt/docs/htmlMultiModule/index.html
* Maven Central Publishing
* Include sources in publishing
* Sign all artifacts (POMs, JARs, Source JARs) with GPG in deploy to Artifactory and Maven Central
* Only require one input (the release version) to trigger a release. Infer the next development version as a patch increment above the release version
* Introduce a distribution POM to bring in all Web5 deps in a single declaration
* Keep pom.xml effectively versionless at 0.0.0-main-SNAPSHOT; version at release time
* Publish to Maven Central on successful release and publish to TBD
  Artifactory
* Update README to reflect changes above and document all build and
  pipeline features
* Do not double-trigger uploads to Artifactory, Test Vectors, or CodeCov by separating out MacOS and Ubuntu jobs
* Make 'distribution' folder for the distribution pom.xml so that tbdex-kt can follow same convention
* Rebased all work atop b8a1a13

TODO:
* Switch ALRubinger in SCM configuration of pom.xml to TBD again
* Remove the comments at the end of build-test-publish workflow to
  re-enable sdk-report-runner

ALRubinger added a commit that referenced this issue


          Issue #217: Remove testing configs to be ready for merge

f199a55

ALRubinger added a commit that referenced this issue


          Issue #217 - Convert and port Gradle to Maven build for web5-kt

fa1573a

* No security or license issues
* All modules build and tests pass
* Dependencies all correctly set via dependencyManagement which may be consumed by other projects (ie. tbDEX)
* Ported Dokka to use Dokka CLI in GitHub Actions and instructions to run locally
* Change: API Docs via Dokka now have no left sidebar because Gradle plugin enabled multimodule for us.
* Detekt ported through Maven plugin
* Ported Kover; we have coverage via CodeCov
* Switched to use TBD Artifactory for single repo declaration to get 3rdparty deps not in Maven Central
* Update README to reflect new build usage
* Publish to TBD Artifactory
* While we are at it, renames to GitHub Actions for clarity and correctness
* Set Surefire patterns to run Test Vectors
* Publish every build as a SNAPSHOT in format X.Y.Z-commit-$shortSHA-SNAPSHOT
* Validate that SNAPSHOT publishing has a version defined that ends in -SNAPSHOT
* SNAPSHOTs deployed to TBD Artifactory for every push to main, with version commit-$shortSHA-SNAPSHOT
* TBD Artifactory Release and Publish, with tagging of git
* API Docs Publishing - Verifiable at: https://alrubinger.github.io/web5-kt/docs/htmlMultiModule/index.html
* Maven Central Publishing
* Include sources in publishing
* Sign all artifacts (POMs, JARs, Source JARs) with GPG in deploy to Artifactory and Maven Central
* Only require one input (the release version) to trigger a release. Infer the next development version as a patch increment above the release version
* Introduce a distribution POM to bring in all Web5 deps in a single declaration
* Keep pom.xml effectively versionless at 0.0.0-main-SNAPSHOT; version at release time
* Publish to Maven Central on successful release and publish to TBD
  Artifactory
* Update README to reflect changes above and document all build and
  pipeline features
* Do not double-trigger uploads to Artifactory, Test Vectors, or CodeCov by separating out MacOS and Ubuntu jobs
* Make 'distribution' folder for the distribution pom.xml so that tbdex-kt can follow same convention
* Rebased all work atop b8a1a13

TODO:
* Switch ALRubinger in SCM configuration of pom.xml to TBD again
* Remove the comments at the end of build-test-publish workflow to
  re-enable sdk-report-runner

ALRubinger added a commit that referenced this issue


          Issue #217: Remove testing configs to be ready for merge

bbf3a1f

ALRubinger added a commit to ALRubinger/web5-kt that referenced this issue


          Issue TBD54566975#217: Add jose to API Docs generation

ff715f9

ALRubinger added a commit that referenced this issue


          Issue #217 - Convert and port Gradle to Maven build for web5-kt

453a13c

* No security or license issues
* All modules build and tests pass
* Dependencies all correctly set via dependencyManagement which may be consumed by other projects (ie. tbDEX)
* Ported Dokka to use Dokka CLI in GitHub Actions and instructions to run locally
* Change: API Docs via Dokka now have no left sidebar because Gradle plugin enabled multimodule for us.
* Detekt ported through Maven plugin
* Ported Kover; we have coverage via CodeCov
* Switched to use TBD Artifactory for single repo declaration to get 3rdparty deps not in Maven Central
* Update README to reflect new build usage
* Publish to TBD Artifactory
* While we are at it, renames to GitHub Actions for clarity and correctness
* Set Surefire patterns to run Test Vectors
* Publish every build as a SNAPSHOT in format X.Y.Z-commit-$shortSHA-SNAPSHOT
* Validate that SNAPSHOT publishing has a version defined that ends in -SNAPSHOT
* SNAPSHOTs deployed to TBD Artifactory for every push to main, with version commit-$shortSHA-SNAPSHOT
* TBD Artifactory Release and Publish, with tagging of git
* API Docs Publishing - Verifiable at: https://alrubinger.github.io/web5-kt/docs/htmlMultiModule/index.html
* Maven Central Publishing
* Include sources in publishing
* Sign all artifacts (POMs, JARs, Source JARs) with GPG in deploy to Artifactory and Maven Central
* Only require one input (the release version) to trigger a release. Infer the next development version as a patch increment above the release version
* Introduce a distribution POM to bring in all Web5 deps in a single declaration
* Keep pom.xml effectively versionless at 0.0.0-main-SNAPSHOT; version at release time
* Publish to Maven Central on successful release and publish to TBD
  Artifactory
* Update README to reflect changes above and document all build and
  pipeline features
* Do not double-trigger uploads to Artifactory, Test Vectors, or CodeCov by separating out MacOS and Ubuntu jobs
* Make 'distribution' folder for the distribution pom.xml so that tbdex-kt can follow same convention
* Add jose to Dokka API Docs generation
* Rebased all work atop b8a1a13

TODO:
* Switch ALRubinger in SCM configuration of pom.xml to TBD again
* Remove the comments at the end of build-test-publish workflow to
  re-enable sdk-report-runner

Issue #217: Add jose to API Docs generation

ALRubinger added a commit that referenced this issue


          Issue #217: Remove testing configs to be ready for merge

ee3a24a

ALRubinger added a commit that referenced this issue


          Issue #217 - Convert and port Gradle to Maven build for web5-kt

5cea635

* No security or license issues
* All modules build and tests pass
* Dependencies all correctly set via dependencyManagement which may be consumed by other projects (ie. tbDEX)
* Ported Dokka to use Dokka CLI in GitHub Actions and instructions to run locally
* Change: API Docs via Dokka now have no left sidebar because Gradle plugin enabled multimodule for us.
* Detekt ported through Maven plugin
* Ported Kover; we have coverage via CodeCov
* Switched to use TBD Artifactory for single repo declaration to get 3rdparty deps not in Maven Central
* Update README to reflect new build usage
* Publish to TBD Artifactory
* While we are at it, renames to GitHub Actions for clarity and correctness
* Set Surefire patterns to run Test Vectors
* Publish every build as a SNAPSHOT in format X.Y.Z-commit-$shortSHA-SNAPSHOT
* Validate that SNAPSHOT publishing has a version defined that ends in -SNAPSHOT
* SNAPSHOTs deployed to TBD Artifactory for every push to main, with version commit-$shortSHA-SNAPSHOT
* TBD Artifactory Release and Publish, with tagging of git
* API Docs Publishing - Verifiable at: https://alrubinger.github.io/web5-kt/docs/htmlMultiModule/index.html
* Maven Central Publishing
* Include sources in publishing
* Sign all artifacts (POMs, JARs, Source JARs) with GPG in deploy to Artifactory and Maven Central
* Only require one input (the release version) to trigger a release. Infer the next development version as a patch increment above the release version
* Introduce a distribution POM to bring in all Web5 deps in a single declaration
* Keep pom.xml effectively versionless at 0.0.0-main-SNAPSHOT; version at release time
* Publish to Maven Central on successful release and publish to TBD
  Artifactory
* Update README to reflect changes above and document all build and
  pipeline features
* Do not double-trigger uploads to Artifactory, Test Vectors, or CodeCov by separating out MacOS and Ubuntu jobs
* Make 'distribution' folder for the distribution pom.xml so that tbdex-kt can follow same convention
* Add jose to Dokka API Docs generation
* Rebased all work atop c1c8f3e, tag: v0.17.0

TODO:
* Switch ALRubinger in SCM configuration of pom.xml to TBD again
* Remove the comments at the end of build-test-publish workflow to
  re-enable sdk-report-runner

ALRubinger added a commit that referenced this issue


          Issue #217: Remove testing configs to be ready for merge

ac0e1c8

ALRubinger added a commit to ALRubinger/web5-kt that referenced this issue


          Issue TBD54566975#217 - Convert and port Gradle to Maven build for we…

fc0697d

…b5-kt

* No security or license issues
* All modules build and tests pass
* Dependencies all correctly set via dependencyManagement which may be consumed by other projects (ie. tbDEX)
* Ported Dokka to use Dokka CLI in GitHub Actions and instructions to run locally
* Change: API Docs via Dokka now have no left sidebar because Gradle plugin enabled multimodule for us.
* Detekt ported through Maven plugin
* Ported Kover; we have coverage via CodeCov
* Switched to use TBD Artifactory for single repo declaration to get 3rdparty deps not in Maven Central
* Update README to reflect new build usage
* Publish to TBD Artifactory
* While we are at it, renames to GitHub Actions for clarity and correctness
* Set Surefire patterns to run Test Vectors
* Publish every build as a SNAPSHOT in format X.Y.Z-commit-$shortSHA-SNAPSHOT
* Validate that SNAPSHOT publishing has a version defined that ends in -SNAPSHOT
* SNAPSHOTs deployed to TBD Artifactory for every push to main, with version commit-$shortSHA-SNAPSHOT
* TBD Artifactory Release and Publish, with tagging of git
* API Docs Publishing - Verifiable at: https://alrubinger.github.io/web5-kt/docs/htmlMultiModule/index.html
* Maven Central Publishing
* Include sources in publishing
* Sign all artifacts (POMs, JARs, Source JARs) with GPG in deploy to Artifactory and Maven Central
* Only require one input (the release version) to trigger a release. Infer the next development version as a patch increment above the release version
* Introduce a distribution POM to bring in all Web5 deps in a single declaration
* Keep pom.xml effectively versionless at 0.0.0-main-SNAPSHOT; version at release time
* Publish to Maven Central on successful release and publish to TBD
  Artifactory
* Update README to reflect changes above and document all build and
  pipeline features
* Do not double-trigger uploads to Artifactory, Test Vectors, or CodeCov by separating out MacOS and Ubuntu jobs
* Make 'distribution' folder for the distribution pom.xml so that tbdex-kt can follow same convention
* Add jose to Dokka API Docs generation
* Rebased all work atop c1c8f3e, tag: v0.17.0

TODO:
* Switch ALRubinger in SCM configuration of pom.xml to TBD again
* Remove the comments at the end of build-test-publish workflow to
  re-enable sdk-report-runner

ALRubinger added a commit that referenced this issue


          Issue #217 - Convert and port Gradle to Maven build for web5-kt

c9f6e15

* No security or license issues
* All modules build and tests pass
* Dependencies all correctly set via dependencyManagement which may be consumed by other projects (ie. tbDEX)
* Ported Dokka to use Dokka CLI in GitHub Actions and instructions to run locally
* Change: API Docs via Dokka now have no left sidebar because Gradle plugin enabled multimodule for us.
* Detekt ported through Maven plugin
* Ported Kover; we have coverage via CodeCov
* Switched to use TBD Artifactory for single repo declaration to get 3rdparty deps not in Maven Central
* Update README to reflect new build usage
* Publish to TBD Artifactory
* While we are at it, renames to GitHub Actions for clarity and correctness
* Set Surefire patterns to run Test Vectors
* Publish every build as a SNAPSHOT in format X.Y.Z-commit-$shortSHA-SNAPSHOT
* Validate that SNAPSHOT publishing has a version defined that ends in -SNAPSHOT
* SNAPSHOTs deployed to TBD Artifactory for every push to main, with version commit-$shortSHA-SNAPSHOT
* TBD Artifactory Release and Publish, with tagging of git
* API Docs Publishing - Verifiable at: https://alrubinger.github.io/web5-kt/docs/htmlMultiModule/index.html
* Maven Central Publishing
* Include sources in publishing
* Sign all artifacts (POMs, JARs, Source JARs) with GPG in deploy to Artifactory and Maven Central
* Only require one input (the release version) to trigger a release. Infer the next development version as a patch increment above the release version
* Introduce a distribution POM to bring in all Web5 deps in a single declaration
* Keep pom.xml effectively versionless at 0.0.0-main-SNAPSHOT; version at release time
* Publish to Maven Central on successful release and publish to TBD
  Artifactory
* Update README to reflect changes above and document all build and
  pipeline features
* Do not double-trigger uploads to Artifactory, Test Vectors, or CodeCov by separating out MacOS and Ubuntu jobs
* Make 'distribution' folder for the distribution pom.xml so that tbdex-kt can follow same convention
* Add jose to Dokka API Docs generation
* Rebased all work atop c1c8f3e, tag: v0.17.0

TODO:
* Switch ALRubinger in SCM configuration of pom.xml to TBD again
* Remove the comments at the end of build-test-publish workflow to
  re-enable sdk-report-runner

ALRubinger added a commit that referenced this issue


          Issue #217: Remove testing configs to be ready for merge

4746fe5

ALRubinger added a commit that referenced this issue


          Issue #217 - Convert and port Gradle to Maven build for web5-kt

a4ca94f

* No security or license issues
* All modules build and tests pass
* Dependencies all correctly set via dependencyManagement which may be consumed by other projects (ie. tbDEX)
* Ported Dokka to use Dokka CLI in GitHub Actions and instructions to run locally
* Change: API Docs via Dokka now have no left sidebar because Gradle plugin enabled multimodule for us.
* Detekt ported through Maven plugin
* Ported Kover; we have coverage via CodeCov
* Switched to use TBD Artifactory for single repo declaration to get 3rdparty deps not in Maven Central
* Update README to reflect new build usage
* Publish to TBD Artifactory
* While we are at it, renames to GitHub Actions for clarity and correctness
* Set Surefire patterns to run Test Vectors
* Publish every build as a SNAPSHOT in format X.Y.Z-commit-$shortSHA-SNAPSHOT
* Validate that SNAPSHOT publishing has a version defined that ends in -SNAPSHOT
* SNAPSHOTs deployed to TBD Artifactory for every push to main, with version commit-$shortSHA-SNAPSHOT
* TBD Artifactory Release and Publish, with tagging of git
* API Docs Publishing - Verifiable at: https://alrubinger.github.io/web5-kt/docs/htmlMultiModule/index.html
* Maven Central Publishing
* Include sources in publishing
* Sign all artifacts (POMs, JARs, Source JARs) with GPG in deploy to Artifactory and Maven Central
* Only require one input (the release version) to trigger a release. Infer the next development version as a patch increment above the release version
* Introduce a distribution POM to bring in all Web5 deps in a single declaration
* Keep pom.xml effectively versionless at 0.0.0-main-SNAPSHOT; version at release time
* Publish to Maven Central on successful release and publish to TBD
  Artifactory
* Update README to reflect changes above and document all build and
  pipeline features
* Do not double-trigger uploads to Artifactory, Test Vectors, or CodeCov by separating out MacOS and Ubuntu jobs
* Make 'distribution' folder for the distribution pom.xml so that tbdex-kt can follow same convention
* Add jose to Dokka API Docs generation
* Rebased all work atop c1c8f3e, tag: v0.17.0

TODO:
* Switch ALRubinger in SCM configuration of pom.xml to TBD again
* Remove the comments at the end of build-test-publish workflow to
  re-enable sdk-report-runner

ALRubinger added a commit that referenced this issue


          Issue #217: Remove testing configs to be ready for merge

131944c

ALRubinger added a commit that referenced this issue


          Issue #217 - Convert and port Gradle to Maven build for web5-kt

d5b6ad6

* No security or license issues
* All modules build and tests pass
* Dependencies all correctly set via dependencyManagement which may be consumed by other projects (ie. tbDEX)
* Ported Dokka to use Dokka CLI in GitHub Actions and instructions to run locally
* Change: API Docs via Dokka now have no left sidebar because Gradle plugin enabled multimodule for us.
* Detekt ported through Maven plugin
* Ported Kover; we have coverage via CodeCov
* Switched to use TBD Artifactory for single repo declaration to get 3rdparty deps not in Maven Central
* Update README to reflect new build usage
* Publish to TBD Artifactory
* While we are at it, renames to GitHub Actions for clarity and correctness
* Set Surefire patterns to run Test Vectors
* Publish every build as a SNAPSHOT in format X.Y.Z-commit-$shortSHA-SNAPSHOT
* Validate that SNAPSHOT publishing has a version defined that ends in -SNAPSHOT
* SNAPSHOTs deployed to TBD Artifactory for every push to main, with version commit-$shortSHA-SNAPSHOT
* TBD Artifactory Release and Publish, with tagging of git
* API Docs Publishing - Verifiable at: https://alrubinger.github.io/web5-kt/docs/htmlMultiModule/index.html
* Maven Central Publishing
* Include sources in publishing
* Sign all artifacts (POMs, JARs, Source JARs) with GPG in deploy to Artifactory and Maven Central
* Only require one input (the release version) to trigger a release. Infer the next development version as a patch increment above the release version
* Introduce a distribution POM to bring in all Web5 deps in a single declaration
* Keep pom.xml effectively versionless at 0.0.0-main-SNAPSHOT; version at release time
* Publish to Maven Central on successful release and publish to TBD
  Artifactory
* Update README to reflect changes above and document all build and
  pipeline features
* Do not double-trigger uploads to Artifactory, Test Vectors, or CodeCov by separating out MacOS and Ubuntu jobs
* Make 'distribution' folder for the distribution pom.xml so that tbdex-kt can follow same convention
* Add jose to Dokka API Docs generation
* Rebased all work atop c1c8f3e, tag: v0.17.0

TODO:
* Switch ALRubinger in SCM configuration of pom.xml to TBD again
* Remove the comments at the end of build-test-publish workflow to
  re-enable sdk-report-runner

ALRubinger added a commit that referenced this issue


          Issue #217: Remove testing configs to be ready for merge

2fb9066

ALRubinger added a commit that referenced this issue


          Issue #217: Address PR feedback:

da028e3

* Document SNAPSHOTs version naming convention in README
* Add TBD OSS Releases and Snapshots repos to POM

ALRubinger added a commit that referenced this issue


          Issue #217 - Convert and port Gradle to Maven build for web5-kt

a6b70ac

* No security or license issues
* All modules build and tests pass
* Dependencies all correctly set via dependencyManagement which may be consumed by other projects (ie. tbDEX)
* Ported Dokka to use Dokka CLI in GitHub Actions and instructions to run locally
* Change: API Docs via Dokka now have no left sidebar because Gradle plugin enabled multimodule for us.
* Detekt ported through Maven plugin
* Ported Kover; we have coverage via CodeCov
* Switched to use TBD Artifactory for single repo declaration to get 3rdparty deps not in Maven Central
* Update README to reflect new build usage
* Publish to TBD Artifactory
* While we are at it, renames to GitHub Actions for clarity and correctness
* Set Surefire patterns to run Test Vectors
* Publish every build as a SNAPSHOT in format X.Y.Z-commit-$shortSHA-SNAPSHOT
* Validate that SNAPSHOT publishing has a version defined that ends in -SNAPSHOT
* SNAPSHOTs deployed to TBD Artifactory for every push to main, with version commit-$shortSHA-SNAPSHOT
* TBD Artifactory Release and Publish, with tagging of git
* API Docs Publishing - Verifiable at: https://alrubinger.github.io/web5-kt/docs/htmlMultiModule/index.html
* Maven Central Publishing
* Include sources in publishing
* Sign all artifacts (POMs, JARs, Source JARs) with GPG in deploy to Artifactory and Maven Central
* Only require one input (the release version) to trigger a release. Infer the next development version as a patch increment above the release version
* Introduce a distribution POM to bring in all Web5 deps in a single declaration
* Keep pom.xml effectively versionless at 0.0.0-main-SNAPSHOT; version at release time
* Publish to Maven Central on successful release and publish to TBD
  Artifactory
* Update README to reflect changes above and document all build and
  pipeline features
* Do not double-trigger uploads to Artifactory, Test Vectors, or CodeCov by separating out MacOS and Ubuntu jobs
* Make 'distribution' folder for the distribution pom.xml so that tbdex-kt can follow same convention
* Add jose to Dokka API Docs generation
* Rebased all work atop c1c8f3e, tag: v0.17.0
* Address Jiyoon PR Review: add names for all workflow jobs, document SNAPSHOT version format, add TBD OSS SNAPSHOT and Release repos to POM

TODO:
* Switch ALRubinger in SCM configuration of pom.xml to TBD again
* Remove the comments at the end of build-test-publish workflow to
  re-enable sdk-report-runner

ALRubinger added a commit that referenced this issue


          Issue #217: Remove testing configs to be ready for merge

680f237

leordev added a commit that referenced this issue


          Convert Gradle to Maven Build (#261)

89fc453

* Issue #217 - Convert and port Gradle to Maven build for web5-kt

* No security or license issues
* All modules build and tests pass
* Dependencies all correctly set via dependencyManagement which may be consumed by other projects (ie. tbDEX)
* Ported Dokka to use Dokka CLI in GitHub Actions and instructions to run locally
* Change: API Docs via Dokka now have no left sidebar because Gradle plugin enabled multimodule for us.
* Detekt ported through Maven plugin
* Ported Kover; we have coverage via CodeCov
* Switched to use TBD Artifactory for single repo declaration to get 3rdparty deps not in Maven Central
* Update README to reflect new build usage
* Publish to TBD Artifactory
* While we are at it, renames to GitHub Actions for clarity and correctness
* Set Surefire patterns to run Test Vectors
* Publish every build as a SNAPSHOT in format X.Y.Z-commit-$shortSHA-SNAPSHOT
* Validate that SNAPSHOT publishing has a version defined that ends in -SNAPSHOT
* SNAPSHOTs deployed to TBD Artifactory for every push to main, with version commit-$shortSHA-SNAPSHOT
* TBD Artifactory Release and Publish, with tagging of git
* API Docs Publishing - Verifiable at: https://alrubinger.github.io/web5-kt/docs/htmlMultiModule/index.html
* Maven Central Publishing
* Include sources in publishing
* Sign all artifacts (POMs, JARs, Source JARs) with GPG in deploy to Artifactory and Maven Central
* Only require one input (the release version) to trigger a release. Infer the next development version as a patch increment above the release version
* Introduce a distribution POM to bring in all Web5 deps in a single declaration
* Keep pom.xml effectively versionless at 0.0.0-main-SNAPSHOT; version at release time
* Publish to Maven Central on successful release and publish to TBD
  Artifactory
* Update README to reflect changes above and document all build and
  pipeline features
* Do not double-trigger uploads to Artifactory, Test Vectors, or CodeCov by separating out MacOS and Ubuntu jobs
* Make 'distribution' folder for the distribution pom.xml so that tbdex-kt can follow same convention
* Add jose to Dokka API Docs generation
* Rebased all work atop c1c8f3e, tag: v0.17.0
* Address Jiyoon PR Review: add names for all workflow jobs, document SNAPSHOT version format, add TBD OSS SNAPSHOT and Release repos to POM

TODO:
* Switch ALRubinger in SCM configuration of pom.xml to TBD again
* Remove the comments at the end of build-test-publish workflow to
  re-enable sdk-report-runner

* Issue #217: Remove testing configs to be ready for merge

* Removes unnecessary comment

* adding more git command examples for pushing to web5-spec module

---------

Co-authored-by: Leo Ribeiro <leordev@gmail.com>
Co-authored-by: Jiyoon Koo <jiyoon@squareup.com>

Contributor Author

ALRubinger commented Apr 7, 2024

Done in 89fc453

ALRubinger closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment