I also think decoupling it from jclouds-core is a good idea. However, as Everett, I'm not sure about making it jclouds independent.
Decoupling it shouldn't introduce any incompatibility issues as long as we keep the groupId and artifactId of the project. These are the few things to take care of, that come to my mind: * The jclouds-compute module depends on it to create the bootstrap scripts (the "wrapInitScript" option in the RunScriptOptions is enabled by default and very very useful). We want to make sure we don't break this and keep jclouds-compute working without changes here. * There is specific code to parse the license headers when joining several script fragments into the final script, to remove the repeated ones. This is a requirement to properly license the source code, but generate proper scripts. This is very jclouds specific but shouldn't be lost. * I'm pretty sure many people is using the scriptbuilder tools/recipes to bootstrap the nodes they deploy. Let's try to break the minimum! :) Having said this, I look forward to see that PR! Ignasi El 30/11/2013 19:21, "Everett Toews" <[email protected]> escribió: > I agree that decoupling script builder from jclouds-core is a good idea. > > I'm concerned about what, if any, backwards incompatible changes this > would introduce to our users. > > Ioannis, before the PR, please give us an indication of any backwards > incompatible changes this might cause. If there are considerable > incompatibilities it would be best if you approached our users and gave > them your plan and a chance to voice their opinions. Jeremy did this in > this thread, New RegionScopedSwiftBlobStore in jclouds 1.7 [1]. So > something like that would be appropriate. > > I'm not as sure about making it completely jclouds independent . It > certainly needs to be decoupled as a first step and we can explore things > after that. > > Thanks, > Everett > > [1] > http://www.mail-archive.com/[email protected]/msg00477.html > > > On Nov 29, 2013, at 8:47 AM, Ioannis Canellos wrote: > > > I agree! > > > > I'll work an PR! > >
