https://github.com/toolisticon/jmolecules-archunit-kotlin
Opinionated ArchUnit Test library for usage from Kotlin
https://github.com/toolisticon/jmolecules-archunit-kotlin
Last synced: over 1 year ago
JSON representation
Opinionated ArchUnit Test library for usage from Kotlin
- Host: GitHub
- URL: https://github.com/toolisticon/jmolecules-archunit-kotlin
- Owner: toolisticon
- License: apache-2.0
- Created: 2023-11-29T17:54:51.000Z (over 2 years ago)
- Default Branch: develop
- Last Pushed: 2023-12-15T02:38:00.000Z (over 2 years ago)
- Last Synced: 2025-01-14T18:11:36.066Z (over 1 year ago)
- Language: Kotlin
- Size: 29.3 KB
- Stars: 1
- Watchers: 5
- Forks: 0
- Open Issues: 3
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# jmolecules-archunit-kotlin
Template repository for usage in organizations: toolisticon, holunda-io, holixon...
[](https://github.com/holisticon#open-source-lifecycle)
[](https://github.com/toolisticon/jmolecules-archunit-kotlin/actions)
[](https://holisticon.de/)
[](https://maven-badges.herokuapp.com/maven-central/io.toolisticon.jmolecules.archunit/jmolecules-archunit-kotlin)
This repository is a **template repository** designed to be a template for the next project.
## How to use
* create a new repo on github (can be in any organization). Choose this project as template repository. Copy all branches, so the `master`exists in your repo (for the github actions)
* on the command line: clone your new repo locally
* in the `setup.sh` script: set your organization, repository and base package
* run the `setup.sh` script, all placeholders are filled with your information
* delete the setup-script
* Update the `README.md`
* in the `developers` section of the `pom.xml`: mention yourself ... it is your project.
## Things to change after usage of template
To change the following values, modify the placeholders in `setup.sh` and run it.
This is a one-time operation, you can safely delete the `setup.sh` file afterwards.
Of course, you can also edit manually .... and do not forget to change this `README.md` with YOUR project specific information :-).
### Maven pom.xml
* Maven coordinates: `groupId`, `artifactId` and `version`
* Main description: `name`, `url`, `description`
* SCM: `connection`, `url`, `developerConnection`
### Issue Template
* correct the URL to repo
### Issue Labels
* Check the release-notes.yml for details, but create the following labels: Type: dependencies, Type: bug, Type: documentation, Type: question, Type: enhancement