-
Notifications
You must be signed in to change notification settings - Fork 275
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
0.35.6: Log4j and JUnit are in the compile scope #291
Comments
@markkolich, thanks for catching it. I missed a few dependencies and had debug code left in the document parser. Next release, coming in an hour or so will have these fixed. |
Thanks @vsch! Fwiw, I only noticed this because I'm using the <plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-enforcer-plugin</artifactId>
<version>3.0.0-M2</version>
<executions>
<execution>
<id>enforce-banned-dependencies</id>
<phase>prepare-package</phase>
<goals>
<goal>enforce</goal>
</goals>
<configuration>
<rules>
<requireUpperBoundDeps/>
<bannedDependencies>
<!-- List of artifacts to ban -->
<excludes>
<exclude>log4j:log4j:compile</exclude>
<exclude>junit:junit:compile</exclude>
<exclude>org.apache.logging.log4j:log4j-api</exclude>
<exclude>org.apache.logging.log4j:log4j-core</exclude>
<exclude>commons-logging:commons-logging</exclude>
</excludes>
</bannedDependencies>
</rules>
<!-- Fail on the first rule that doesn't pass. -->
<failFast>true</failFast>
</configuration>
</execution>
</executions>
</plugin> |
@markkolich, repo updated. Be careful if forking. Old, Java 9 incompatible version is in branch v0.35, and version 0.35.8 was updated on maven. Version 0.40.0 and up are made Java 9+ module compatible and will break existing code without migration. |
Hi @vsch ... I upgraded my project from version
0.35.0
to0.35.6
and am now seeingjunit:junit
andlog4j:log4j
in thecompile
scope:I believe these dependencies were meant to stay in the
test
scope?CC // @larrysteinke
The text was updated successfully, but these errors were encountered: