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
Copy file name to clipboardExpand all lines: README.md
+18-1Lines changed: 18 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -187,7 +187,7 @@ Example `<profile>` section of `settings.xml` for using cdoc2 dependencies:
187
187
</profile>
188
188
```
189
189
190
-
Note: When pulling, the [package index is based on the organization level](https://stackoverflow.com/questions/63041402/github-packages-single-maven-repository-for-github-organization)
190
+
Note: When pulling, the [GitHub package index is based on the organization level](https://stackoverflow.com/questions/63041402/github-packages-single-maven-repository-for-github-organization)
191
191
, not the repository level.
192
192
193
193
So defining any Maven package repo from `open-eid` is enough for pulling cdoc2-* dependencies.
@@ -253,3 +253,20 @@ See [cdoc2-cli/README.md](cdoc2-cli/README.md)
253
253
254
254
See [VERSIONING.md](VERSIONING.md)
255
255
256
+
## Publishing
257
+
258
+
### GitHub
259
+
260
+
Create release on tag done by VERSIONING.md process. It will trigger `maven-release.yml` workflow that
261
+
will deploy Maven packages to GitHub Maven package repository.
262
+
263
+
### Manual
264
+
265
+
Since build uses `exists-maven-plugin` then `altDeploymentRepository` doesn't work as it only works
266
+
for `deploy` plugin. Set `project.distributionManagement` user properties instead:
0 commit comments