update ArchUnit-Examples dependencies on release #1290
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We automatically keep the code of the separate ArchUnit-Examples repository in sync with the
archunit-example
module in this repository. However, sometimes an example makes an update of the dependencies necessary (as seen in 1d1a990). Up to now this made it necessary to manually update the dependencies in ArchUnit-Examples, or the release will fail when testing the updated ArchUnit-Examples. We now keep the (production) dependencies of ArchUnit-Examples automatically in sync with thearchunit-example
module.Since ArchUnit-Examples should be purely driven from this repository, I think it's an okay compromise to simply keep a static template here and fully overwrite the build file.
Changes to the root build file should always be controlled from this repository.