If JBT needs to modify Forge's settings, why just use the Forge settings API that we will create for this as a separate module? :) Should be pretty trivial to include in JBoss Tools, no?
In design, it's basically a glorified map where local settings take precedence over global settings, stored in XML.
~Lincoln
Okey - just wondering if using Java Preference API would possible to avoid having to have custom parser logic/configuration in case both JBoss tools and Forge would need to massage the settings ?
> Trying to avoid this as much as possible, but the most recent strategy is to use forge.xml for local project settings, and $FORGE_HOME/settings.xml for global settings. We haven't worked on config yet really.
/max
>
> ~Lincoln
>
> On Thu, Jun 16, 2011 at 4:31 AM, Max Rydahl Andersen <max.andersen@redhat.com> wrote:
> i.e. global preferences and things like project settings for test, prod and dev datasource configurations, defaults for package names etc. ?
>
> /max
> http://about.me/maxandersen
>
>
>
>
> _______________________________________________
> forge-dev mailing list
> forge-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
>
>
>
> --
> Lincoln Baxter, III
> http://ocpsoft.com
> http://scrumshark.com
> "Keep it Simple"
> _______________________________________________
> forge-dev mailing list
> forge-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
/max
http://about.me/maxandersen
_______________________________________________
forge-dev mailing list
forge-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev