mirror of
https://github.com/digital-asset/daml.git
synced 2024-09-20 01:07:18 +03:00
631db446f0
I've seen reports of Artifactory returning 409 when it detects an invalid POM file, which would map cleanly to our observed behaviour (as other files do seem to upload fine). I'm not a POM expert so not entirely sure how to check the actual files, but I do see one error in the existing, commented code: the path is not a valid Maven repository path. It should be `groupid/artifactid/version`, i.e. it is currently missing the `artifactid` bit. So I'd like to try adding that. I don't know how to test this without making a release, so my plan is to make a release once this is merged. Open to suggestion on faster ways to test this. CHANGELOG_BEGIN CHANGELOG_END |
||
|---|---|---|
| .. | ||
| cron | ||
| da-ghc-lib | ||
| docker | ||
| patch_bazel_windows | ||
| bash-lib.yml | ||
| build-unix.yml | ||
| build-windows.yml | ||
| build.yml | ||
| check-changelog.sh | ||
| clean-up.yml | ||
| clear-shared-segments-macos.yml | ||
| compatibility_ts_libs.yml | ||
| compatibility-windows.yml | ||
| compatibility.yml | ||
| configure-bazel.sh | ||
| copy-unix-release-artifacts.sh | ||
| copy-windows-release-artifacts.sh | ||
| dev-env-install.sh | ||
| dev-env-push.py | ||
| postgresql.conf | ||
| prs.yml | ||
| publish-artifactory.sh | ||
| report-end.yml | ||
| report-start.yml | ||
| slack_user_ids | ||
| tell-slack-failed.yml | ||
| windows-diagnostics.ps1 | ||