aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorTeddy Wing2023-04-29 01:31:44 +0200
committerTeddy Wing2023-04-29 01:31:44 +0200
commit10f77f15b4b1ef462f726cf7b5e79a94f3366997 (patch)
tree0319653664e11b60da4a6215a452a121bc19067d
parentb3ae919034625a8a87007e3978d8e7fac1c57a6f (diff)
downloadpdf-form-replace-font2-10f77f15b4b1ef462f726cf7b5e79a94f3366997.tar.bz2
Makefile: Remove `mvn release:perform` line
That command resulted in this error: [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project pdf-form-replace-font2: Deployment failed: repository element was not specified in the POM inside distributionManagement element or in -DaltDeploymentRepository=id::layout::url parameter -> [Help 1] I had added `release:perform` because it's described as the second step in releasing in this document: https://maven.apache.org/maven-release/maven-release-plugin/usage.html However, as explained in https://maven.apache.org/maven-release/maven-release-plugin/usage/perform-release.html , `release:perform` runs the `deploy` target, which doesn't make sense for this project. It seems like we only need `release:prepare` to do a Maven-driven release.
-rw-r--r--Makefile1
1 files changed, 0 insertions, 1 deletions
diff --git a/Makefile b/Makefile
index bc9bd73..c48fe70 100644
--- a/Makefile
+++ b/Makefile
@@ -65,7 +65,6 @@ pdf-form-replace-font2: pdf-form-replace-font2.in
.PHONY: release
release:
mvn release:prepare $(MVNFLAGS)
- mvn release:perform $(MVNFLAGS)
.PHONY: install