aboutsummaryrefslogtreecommitdiffstats
path: root/Makefile
AgeCommit message (Collapse)Author
2023-04-30Makefile: Allow custom `mvn` executableTeddy Wing
Allow `mvn` to be redefined so we can use `mvn3` explicitly in the MacPorts port.
2023-04-29Makefile: Remove snapshot for tag editing in `release` targetTeddy Wing
Need to remove the "-SNAPSHOT" string from the tagged version.
2023-04-29Makefile: Edit Git tag made by `mvn release:prepare`Teddy Wing
Make it so that we can actually add a proper message to the tag generated by Maven.
2023-04-29Makefile: Remove `mvn release:perform` lineTeddy Wing
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.
2023-04-28Makefile: Move shell script wrapper template exec to a new targetTeddy Wing
When I tried packaging with MacPorts, the path written to the shell wrapper was the temporary MacPorts build path, not the final install path. My plan is to extract the shell wrapper build to the `package` stage, and do something with the variables to give it the correct install path. Not sure what that something is yet, but that's the idea.
2023-04-27Makefile: Add `MVNFLAGS` variable to pass custom flags to MavenTeddy Wing
Need this to package with MacPorts.
2023-04-27Set up Maven release pluginTeddy Wing
2023-04-26Makefile: Add an `install` targetTeddy Wing
Facilitate installation for package management. Package our `pdf-form-replace-font2` shell script so that it runs the JAR at the correct install location.
2023-04-26Makefile: Add `package` targetTeddy Wing
2023-04-26Add license (GNU GPLv3+)Teddy Wing
2023-04-26Makefile: Remove old `all` targetTeddy Wing
No longer used now that we switched to Maven.
2023-04-26Add man pageTeddy Wing
Copy from 'pdf-form-replace-font' with small modifications to align with the present project.
2023-04-23Move 'Main.java' to 'App.java'Teddy Wing
Build our earlier code with Maven.
2023-04-22Change PDF form field fontTeddy Wing
Use iText to change the font of interactive form fields in a PDF. Changes the font in 'f1040.pdf' to Courier. This code is based on the following example from iText: https://kb.itextsupport.com/home/it7kb/ebooks/itext-7-jump-start-tutorial-for-net/chapter-5-manipulating-an-existing-pdf-document-net#Chapter5:ManipulatinganexistingPDFdocument|.NET-Changingthepropertiesofformfields For now I just downloaded the dependencies' JAR files and put them in a 'lib/' directory rather than have to learn how to use a dependency management tool like Maven. Here is the contents of the 'lib/' directory: barcodes-7.2.2.jar commons-7.2.2.jar font-asian-7.2.2.jar forms-7.2.2.jar hyph-7.2.2.jar io-7.2.2.jar kernel-7.2.2.jar layout-7.2.2.jar pdfa-7.2.2.jar pdftest-7.2.2.jar sign-7.2.2.jar slf4j-api-1.7.9.jar styled-xml-parser-7.2.2.jar svg-7.2.2.jar To run this: $ make $ make run