-
Notifications
You must be signed in to change notification settings - Fork 94
Maven examples & Gradle update #14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
IntelliJ IDEA did not offer to execute the `example-junit5` tests directly from the IDE, but adding the `junit-jupiter-api` dependency changed this inconvenient behavior. I've added the dependency to the `testCompileOnly` configuration to suggest that it is not actually needed. Signed-off-by: Manfred Hanke <Manfred.Hanke@tngtech.com>
to support more modern Java versions e.g. https://docs.gradle.org/8.5/release-notes.html#full-java-21-support Signed-off-by: Manfred Hanke <Manfred.Hanke@tngtech.com>
Signed-off-by: Manfred Hanke <Manfred.Hanke@tngtech.com>
FYI: TNG/ArchUnit#1450 will update these |
I appreciate the initiative to also make these examples work with Maven, but do you think it's easy to understand if both Maven and Gradle are mixed together? Or should we have dedicated examples? 🤔 In the end we're updating those automatically anyway, right? We could also adapt that to generate two sets of examples, one for Gradle and one for Maven? Also, would it make sense to use the https://maven.apache.org/wrapper/ analogously to Gradle? |
As this repository is about ArchUnit examples, I thought it would be fair to support multiple build tools in the same module (and not duplicate the examples just because there are several ways to run them). Would it be more clear to state in the
|
Good idea! |
This PR
pom.xml
files to run the examples with Maven