We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi @vsch, I was tempted to re-open #291 but I opted to file a separate bug instead.
I migrated my project to com.vladsch.flexmark:flexmark version 0.40.0 and I still see junit:junit in the compile scope:
com.vladsch.flexmark:flexmark
0.40.0
junit:junit
compile
[INFO] +- com.vladsch.flexmark:flexmark:jar:0.40.0:compile [INFO] | +- com.vladsch.flexmark:flexmark-test-util:jar:0.40.0:compile [INFO] | | \- junit:junit:jar:4.12:compile << -- !! [INFO] | | \- org.hamcrest:hamcrest-core:jar:1.3:compile [INFO] | \- com.vladsch.flexmark:flexmark-util:jar:0.40.0:compile
Is that intentional?
The text was updated successfully, but these errors were encountered:
@markkolich, I will check, I thought I marked the dependency as test scope.
Sorry, something went wrong.
@markkolich, I removed the code but left in the redundant import and forgot to add test scope in the pom.
0.40.2 fixes this.
Fix for this is available. Repo updated, maven updated but may take a while to show up in maven central.
@vsch confirmed fixed with 0.40.2. Thanks!
0.40.2
Closing.
No branches or pull requests
Hi @vsch, I was tempted to re-open #291 but I opted to file a separate bug instead.
I migrated my project to
com.vladsch.flexmark:flexmark
version0.40.0
and I still seejunit:junit
in thecompile
scope:Is that intentional?
The text was updated successfully, but these errors were encountered: