I'd be surprised if it didn't ;) since JSon is just structured data, which is what the forge config api uses :)

@Inject
private Configuration config;


On Tue, May 14, 2013 at 1:05 PM, Sebastien Blanc <sblanc@redhat.com> wrote:
On 05/13/2013 06:56 PM, Max Rydahl Andersen wrote:
>> Hi Max,
>> as Vineet said, it's a specific config file to set specific "flags" and
>> options for the aerogear scaffolding. I'm using this to not break the
>> current Scaffold API, in the future, Aerogear may become a plugin on its
>> own and some of the config will be mirgrated to command line options.
>> I'm trying to upload right now with a higher res, hope it will be more
>> watchable. Otherwise, I'm planning to a new one, with voice over and
>> also showing the push to cloud option.
>> Sebi
> Okey - any reason why it can't use forge preferences for this ?
>
> and if it needs to be external file shouldn't we name it something more specific
> than config.yml ? maybe forgescaffold.yml (assuming its not aerogear specific)
>
> /max
>
> _______________________________________________
> forge-dev mailing list
> forge-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
Hi Max,
Well the main reason right now it's to be able to use JSON instead of
XML. BTW, it's not a .yml extension but just a classic .json extension.

The config file is very specific to AeroGear (and the project itself)
and might be used in the future for JS based tooling (Yeoman extension
etc ...) where JSON is more appropriate.

I could take a look if Forge Preferences API offers the same flexibility
as the current JSONConfig object file I'm using right now.

Seb

_______________________________________________
forge-dev mailing list
forge-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev



--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."