Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

Upgrade Logback #442

Closed
fynnfeldpausch opened this Issue · 3 comments

3 participants

@fynnfeldpausch

Are there any plans on using a more recent version of the Logback lib? I am running into problems using Neo4j embedded and the play! framework, since there seems to be a dependency conflict...

See: http://stackoverflow.com/questions/14373029/play-2-1-and-neo4j-wrappingneoserver-errors-with-logback-xml

@jakewins
Collaborator

This is a continuing issue, unfortunately - upgrading logback means clashes with other external libraries. Neo4j does ship with a minimal internal logging service that it falls back on if logback is not found. Perhaps we can make it configurable, such that you can tell neo4j to use it's internal logging, and then exclude the older logback that neo4j pulls in?

We are fairly strained capacity-wise, so if you don't want to wait for that to be fixed by the team, you could contribute a fix to it yourself, it's fairly localized:

https://github.com/neo4j/neo4j/blob/master/community/kernel/src/main/java/org/neo4j/kernel/InternalAbstractGraphDatabase.java#L748

@wargre

Why the dependencies on logback?

neo4j embeded should ONLY have the slf4j-api dependencies and let the outter application the choice of the logger.

The logback dependencies prevent the use of other logger with slf4j.

@sslavic sslavic referenced this issue in lordofthejars/nosql-unit
Merged

Ignore all Maven target & Eclipse specific files #68

@jakewins
Collaborator

The kernel dependency for logback is now optional.

@jakewins jakewins closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.