These are chat archives for sbt/sbt-native-packager

26th
Jan 2016
Matt Hughes
@matthughes
Jan 26 2016 01:12
Posted a PR: sbt/sbt-native-packager#733
Matt Hughes
@matthughes
Jan 26 2016 01:38
So I have both sbt-docker and sbt-native on my project’s classpath. They both provide docker as a TaskKey via auto plugin. Anyway to disable the one from sbt-native?
Nepomuk Seiler
@muuki88
Jan 26 2016 06:26
disablePlugins(full.path.to.DockerPlugin). I'm not sure if it works.
Matt Hughes
@matthughes
Jan 26 2016 15:58
Yeah that doesn’t work. My problem is I want to use JavaAppPackaging, but not your DockerPlugin, but the former pulls in the latter.
Nepomuk Seiler
@muuki88
Jan 26 2016 16:30
I'm afraid you have to decide which one to use. What kind of features do you need in order to use the DockerPlugin from native-packager?
Matt Hughes
@matthughes
Jan 26 2016 17:15
Yeah, that’s the path I’m going down now. Going to to just use native. Why use DockerPlugin over DockerSpotifyClientPlugin?
Nepomuk Seiler
@muuki88
Jan 26 2016 17:22
DockerSpotifyClientPlugin uses the Java client implemented by spotify. AFAIK this helps if you don't have docker in your local environment.
Can you give some details on what you are missing in the DockerPlugin from native-packger?
Matt Hughes
@matthughes
Jan 26 2016 17:24
I don’t think there is anything missing. I was using sbt-docker before DockerPlugin was integrated with native-plugin and am now just trying to upgrade my deps. Rather than try to fight the conflicts, I’m going to try to use native-plugin directly.
Nepomuk Seiler
@muuki88
Jan 26 2016 17:24
Okay, cool :)
Matt Hughes
@matthughes
Jan 26 2016 17:26
I did like how sbt-docker created types for everything in a Dockerfile as opposed to having everything just go through CmdLike
Nepomuk Seiler
@muuki88
Jan 26 2016 17:46
Yes, I understand that. We discussed this as well and decided against, because the maintainance overhead would have possible too big as native-packager supports not only docker