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
logbook-core and logbook-api contain the same package org.zolando.logbook with a duplicate class - org/zalando/logbook/package-info.class.
logbook-core
logbook-api
org.zolando.logbook
org/zalando/logbook/package-info.class
After adding those dependencies, the maven enforcer plugin with the configured rule BanDuplicateClasses fails the build:
BanDuplicateClasses
[ERROR] Rule 6: org.apache.maven.plugins.enforcer.BanDuplicateClasses failed with the message: Duplicate classes found: Found in: org.zalando:logbook-core:jar:2.14.0:compile org.zalando:logbook-api:jar:2.14.0:compile Duplicate classes: org/zalando/logbook/package-info.class
Package names should be unique across jars.
I think it will be fixed as a part of #625 Enable JDK9+ module-info.
Until then, one can use as a workaround the following configuration of the maven enforcer plugin:
<banDuplicateClasses> <ignoreClasses> <ignoreClass>org.zalando.logbook.package-info</ignoreClass> </ignoreClasses> </banDuplicateClasses>
The configuration of the maven enforcer plugin:
<plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-enforcer-plugin</artifactId> <version>3.1.0</version> <executions> <execution> <id>enforce-versions</id> <goals> <goal>enforce</goal> </goals> </execution> </executions> <configuration> <rules> <banDuplicateClasses /> </rules> </configuration> <dependencies> <dependency> <groupId>org.codehaus.mojo</groupId> <artifactId>extra-enforcer-rules</artifactId> <version>1.6.1</version> </dependency> </dependencies> </plugin>
The text was updated successfully, but these errors were encountered:
This should be fixed now as we moved the logbook-core module into its own package (#625).
Sorry, something went wrong.
No branches or pull requests
logbook-core
andlogbook-api
contain the same packageorg.zolando.logbook
with a duplicate class -org/zalando/logbook/package-info.class
.After adding those dependencies, the maven enforcer plugin with the configured rule
BanDuplicateClasses
fails the build:Expected Behavior
Package names should be unique across jars.
Possible Fix
I think it will be fixed as a part of #625 Enable JDK9+ module-info.
Until then, one can use as a workaround the following configuration of the maven enforcer plugin:
Steps to Reproduce
The configuration of the maven enforcer plugin:
The text was updated successfully, but these errors were encountered: