https://github.com/eitco/maven-template
a template repository containing a minimal maven build and the eitco default maven github actions
https://github.com/eitco/maven-template
Last synced: 5 months ago
JSON representation
a template repository containing a minimal maven build and the eitco default maven github actions
- Host: GitHub
- URL: https://github.com/eitco/maven-template
- Owner: eitco
- License: mit
- Created: 2024-05-10T16:01:50.000Z (about 2 years ago)
- Default Branch: main
- Last Pushed: 2024-07-23T09:16:01.000Z (almost 2 years ago)
- Last Synced: 2024-07-23T14:14:24.069Z (almost 2 years ago)
- Size: 13.7 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
[](https://opensource.org/license/mit)
# eitco maven project template
This [github template repository](https://docs.github.com/en/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template)
contains a basic maven project ready for the eitco open source ci. It contains:
# README.md
This readme, you are currently viewing. In a generated project it needs to be replaced. See the TODO-commentary for
some ideas.
# LICENSE
By default, eitco open source software is licensed under the [MIT license](https://opensource.org/license/mit).
To change this, simply replace this file
# continuous integration
The directories `.github` and `deployment` contain the CI. While the directory `.github` contains actions that build
each commit and release the project on demand, the directory `deployment` contains configuration for the release.
A lot of the build however is configured by the project object model (pom.xml).
# pom.xml
This file specifies the build for your project. Make sure to adapt it according to the TODOs. A lot of the
CI is inherited from the [`eitco-oss-parent`](https://github.com/eitco/eitco-oss-parent) pom.
# .mvn
The `.mvn` directory activates and configures the `maven-git-versioning-extension`. This extension changes the
projects version depending on the current branch. This way every branch can be deployed without their artifacts
overriding each other.