So an other approach we could use before 2.0.0 is:
i) Remove the @Nullable annotation from Chef specific functions inside
script builder (they are only serve documentation purposeless anyway).
ii) Dublicate transformEntries from Maps2 to script builder utils
iii) Modify the OSGi metadata and make the packages that are using
jclouds-core optional (luckily our current structure allows us to do
that, because packages that directly refer to jclouds-core are
isolated).
How does this sounds instead?
I'm guessing this is #219 [1]? I'm OK with the code duplication, but
the "making some of the imports optional" seems to be like a bit of a
quick fix to allow "some of" this package to be imported.
No problems with a quick fix if it solves an immediate issue, but it
would be nice to see the splitting done at the Maven project level
too, at some point.
ap
[1] https://github.com/jclouds/jclouds/pull/219
