Re: files.customize

2017-04-28 Thread Geoff Macartney
+1 to copyResources being protected not private > > +1 to adding `templates.customize` and `files.customize` a la > `{templates,files}.runtime` (but before `customize.command`) > > > Graham if you're able to do either or both in a PR I'll see it's added > as quick

Re: files.customize

2017-04-24 Thread Alex Heneveld
+1 to copyResources being protected not private +1 to adding `templates.customize` and `files.customize` a la `{templates,files}.runtime` (but before `customize.command`) Graham if you're able to do either or both in a PR I'll see it's added as quickly as possible. If not

Re: files.customize

2017-04-24 Thread Aled Sage
iting Java. We should also add config for `templates.customize` and `files.customize` that will be uploaded at the start of the customize phase. However, I don't think we'd get that into the Brooklyn 0.11.0 release as we do a feature-freeze after the first RC is produced. Coul

files.customize

2017-04-17 Thread Graham Ashby
I've done is reuse copyPreInstallResources(), saving its templates and files, and restoring them after I'm done. So, what would be really nice is to have files.customize and templates.customize already taken care of. Or make copyResources() protected. Thanks Graham