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 Thu, 29 Dec 2016 21:44:01 GMT
>What I'd like though is to keep it self-contained without any additional dependencies like
guice, guava or jclouds logging. That's to allow anyone using it without pulling in jclouds
dependencies.
Don't think that would fit with the dev/support model of jclouds, wdyt?

There are no issues for keeping a the non-dependency approach (I love that!). However, if
we want the project to be part of jclouds we should stick to some conventions (such as using
the jclouds logging). jclouds is about portability, and that not only refers to implement
some interfaces, but also to having common ways and patterns to configure stuff and operate.
jclouds users should "feel" they use consistent APIs that follow a concrete set of principles,
not that jclouds is a "grouping" of random libraries.

With this considerations in mind, I'd say it is better to keep the project as an external
dependency, if you prefer to keep it as-is.

-- 
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-269698205
Mime
View raw message