This is an automated email from the ASF dual-hosted git repository.
hboutemy pushed a commit to branch deploy
in repository https://gitbox.apache.org/repos/asf/maven-studies.git
The following commit(s) were added to refs/heads/deploy by this push:
new c1c63e4f8 add JReleaser
c1c63e4f8 is described below
commit c1c63e4f8214331b72ade5a8092c3167b97f0323
Author: Hervé Boutemy <[email protected]>
AuthorDate: Sat Jul 19 11:03:56 2025 +0200
add JReleaser
---
1_DISCOVERY.md | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/1_DISCOVERY.md b/1_DISCOVERY.md
index 70d29dfde..dbd50d4b2 100644
--- a/1_DISCOVERY.md
+++ b/1_DISCOVERY.md
@@ -7,6 +7,8 @@ https://maven.apache.org/archetypes/maven-archetype-j2ee-simple/
And few additions to [`pom.xml`](pom.xml) for some of the tests.
+TODO: test also everything with Maven 4
+
## basic test: deploy to local directory `target/deploy`
Instead of classical deployment to an HTTP(S) server (PUT), or scp or any
other file-oriented server, we can easily test `maven-deploy-plugin:deploy` to
deploy to a local directory using `altDeploymentRepository` parameter with a
`file:` target url (instead of updating `pom.xml`'s
`project.distributionManagement.repository.id`and `url`):
@@ -81,4 +83,6 @@ And at Maven build end of execution (through [a
MavenLifecycleParticipant](https
TODO: dig into the upload aspects explained in [Using
it](https://maveniverse.eu/docs/njord/using-it/) documentation...
-TODO: test also everything with Maven 4
+## deploy with [JReleaser](https://jreleaser.org/)
+
+TODO supports [Publishing to Maven
Central](https://jreleaser.org/guide/latest/examples/maven/maven-central.html)
