Skip to content
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

Jump to bottom

Remove duplicate logback from jetty-maven-plugin's classpath #38

Merged
merged 1 commit into from Jul 10, 2015
Merged

Remove duplicate logback from jetty-maven-plugin's classpath #38

merged 1 commit into from Jul 10, 2015

Conversation

ksclarke
Copy link
Contributor

@ksclarke ksclarke commented Jul 7, 2015

When running a build, I get the following warning in the Maven output:

SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/tmp/jetty-0.0.0.0-0-fcrepo.war-_fcrepo-any-8021681995411204556.dir/webapp/WEB-INF/lib/logback-classic-1.1.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/home/kevin/.m2/repository/ch/qos/logback/logback-classic/1.1.2/logback-classic-1.1.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]

This pull request removes the logback dependency from the jetty-maven-plugin configuration since there is already a version of it on the app's classpath.

@acoburn
Copy link
Contributor

acoburn commented Jul 8, 2015

👍 pending iCLA

acoburn added a commit that referenced this pull request Jul 10, 2015
@acoburn
Merge pull request #38 from ksclarke/multiple-slf4j-fix
d47fd00 
Remove duplicate logback from jetty-maven-plugin's classpath
@acoburn acoburn merged commit d47fd00 into fcrepo-exts:master Jul 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@ksclarke @acoburn