[BREAKING] Move dependencies to compileOnly to exclude them from classpath by baev · Pull Request #1095 · allure-framework/allure-java
Navigation Menu
{{ message }}
allure-framework / allure-java Public
- Notifications You must be signed in to change notification settings
- Fork 237
Conversation
Copy link Copy Markdown
Member
Context
This change is considered as breaking as it may affect the resolved test versions. Make sure the test framework dependencies are specified directly in the project.
Checklist
- Sign Allure CLA
- Provide unit tests
github-actions
bot
added
theme:junit4
theme:httpclient theme:jax-rs theme:jsonunit theme:karate theme:okhttp theme:rest-assured theme:scalatest theme:servlet-api theme:spring theme:build theme:hamcrest labels
Jul 8, 2024baev added 2 commits
August 1, 2024 11:58
baev
force-pushed
the
fix-deps
branch
from
c7bce16 to
b69f280
Compare
baev
merged commit
2bc8a10
into
main
baev
deleted the
fix-deps
branch
baev
added
type:new feature
and removed type:dependencies
Pull requests that update a dependencylabels
Aug 5, 2024
baev
changed the title
Move dependencies to compileOnly to exclude them from classpath
[BREAKING] Move dependencies to compileOnly to exclude them from classpath
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
theme:build theme:cucumber-jvm
CucumberJVM related issuetheme:hamcrest theme:httpclient theme:jax-rs theme:jbehave
JBehave related issue JUnit 4 related issue JUnit 5 related issuetheme:karate theme:okhttp theme:rest-assured theme:scalatest theme:servlet-api theme:spock
Spock Framework related issue TestNG related issue Change that add something new for end users
1 participant