jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ignasi Barrera <notificati...@github.com>
Subject Re: [jclouds/jclouds-labs] Vagrant provider (#160)
Date Tue, 03 Jan 2017 15:14:51 GMT
>If you prefer to avoid the additional dependency I can bring in just the bits that are
needed for the jclouds provider?

Your call :) I don't have a special issue with this dependency, because it does not add any
transitive dependencies that conflict in how jclouds works. We usually recommend not adding
dependencies because that often leads to use existing api clients instead of following the
jclouds mechanisms, but I'd say it is OK to have dependencies like this one. It is important
to note, however, that is is easier to keep things under control if they are in the jclouds
source tree (for example if future versions of your library add other dependencies or change
behaviour, etc). But your call :)

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/160#issuecomment-270136315
Mime
View raw message