-
Notifications
You must be signed in to change notification settings - Fork 318
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
Upgrading to maven version 3 #170
Comments
which version would you need? |
@muuki88 if you use jdeb as Maven dependency you could force any slf4j version you want using . But you setup may be more complex. But the general issue if that even if jdeb upgrade now its dependency of slf4j you may have the same issue again an again (and with other dependencies since you seems to use more than jdeb). |
@tcurdt 1.6.x would be great. @tmortagne , that's the current "workaround". The problem is more between maven, ivy and sbt |
Well the latest version is 1.7.7. |
But there seem to be no problems between the 1.6.x and the 1.7.x releases. Both worked for me (which is a nice job by the slf4j guys). However I would not argue against 1.7. The later the better. |
+1 just ran into this exact issue with jdeb pulling in an old version of slf4j |
Here's a pull request for this: #174 |
Hi,
This plugin is awesome. It finally made its way as an experimental feature to the sbt-native-packager project. Using the API was pleasing. Keep up the good work.
However we have an issue [sbt/sbt-native-packager/issues/291] with slf4j. It seems
the maven-core dependency pulls in a lot of slf4j stuff. Is there any chance to update the maven version or updating slf4j?
The text was updated successfully, but these errors were encountered: