This repository stores the project templates that are available in jDeploy.
-
Fork this repo
-
Copy an existing template inside the
projectsdirectory as a starting point for your template. -
Modify the template as desired.
-
Add
<template>entry to the projects.xml file in the root of the repository. This file contains a list of all available templates. -
Make a pull request with your new changes.
jDeploy clones this repository into ~/.jdeploy/templates, and works with all files locally.
If you checkout your fork of this repository into ~/.jdeploy/templates, you can test your changes locally.
The following placeholders are available in the template files:
Here is the table of placeholders and their descriptions in AsciiDoc format:
| Placeholder | Description |
|---|---|
|
Replaced with the project name. |
|
Replaced with the application title. |
|
Replaced with the Maven group ID. |
|
Replaced with the Maven artifact ID. |
|
Replaced with the fully qualified name of the main class. |
|
Replaced with the simple name of the main class. |
|
Replaced with the base package name. |
|
Replaced with the base package name as a file path (dots replaced by |
|
Replaced with the Java version being used. |
|
Replaced with the GitHub repository URL. |
|
Replaced with the GitHub releases repository URL. |
|
Replaced with the URL for the releases. |
|
Tip
|
You can use placeholders in file names also. This is particularly useful for {{ packagePath }} so that you can generate your source files in the correct package structure.
|
Post questions into the jdeploy discussion forum at https://github.com/shannah/jdeploy/discussions