<div dir="ltr">I'd be surprised if it didn't ;) since JSon is just structured data, which is what the forge config api uses :)<div><br></div><div style>@Inject</div><div style>private Configuration config;</div></div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, May 14, 2013 at 1:05 PM, Sebastien Blanc <span dir="ltr"><<a href="mailto:sblanc@redhat.com" target="_blank">sblanc@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On 05/13/2013 06:56 PM, Max Rydahl Andersen wrote:<br>
>> Hi Max,<br>
>> as Vineet said, it's a specific config file to set specific "flags" and<br>
>> options for the aerogear scaffolding. I'm using this to not break the<br>
>> current Scaffold API, in the future, Aerogear may become a plugin on its<br>
>> own and some of the config will be mirgrated to command line options.<br>
>> I'm trying to upload right now with a higher res, hope it will be more<br>
>> watchable. Otherwise, I'm planning to a new one, with voice over and<br>
>> also showing the push to cloud option.<br>
>> Sebi<br>
> Okey - any reason why it can't use forge preferences for this ?<br>
><br>
> and if it needs to be external file shouldn't we name it something more specific<br>
> than config.yml ? maybe forgescaffold.yml (assuming its not aerogear specific)<br>
><br>
> /max<br>
><br>
> _______________________________________________<br>
> forge-dev mailing list<br>
> <a href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
</div></div>Hi Max,<br>
Well the main reason right now it's to be able to use JSON instead of<br>
XML. BTW, it's not a .yml extension but just a classic .json extension.<br>
<br>
The config file is very specific to AeroGear (and the project itself)<br>
and might be used in the future for JS based tooling (Yeoman extension<br>
etc ...) where JSON is more appropriate.<br>
<br>
I could take a look if Forge Preferences API offers the same flexibility<br>
as the current JSONConfig object file I'm using right now.<br>
<br>
Seb<br>
<div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
forge-dev mailing list<br>
<a href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Lincoln Baxter, III<br><a href="http://ocpsoft.org" target="_blank">http://ocpsoft.org</a><br>"Simpler is better."
</div>