[forge-dev] Where is forge planning to store configuration not possible to encode into source artifacts ?

Lincoln Baxter, III lincolnbaxter at gmail.com
Thu Jun 16 14:33:24 EDT 2011


I'll take a look :) But most likely, even if we use it, the API will be
wrapped in a Forge API.

On Thu, Jun 16, 2011 at 2:26 PM, Max Rydahl Andersen <
max.andersen at redhat.com> wrote:

> > 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?
>
>
> The less dependencies the tools have on frameworks jars the better.
>
> (been burnt too many times :)
>
> > In design, it's basically a glorified map where local settings take
> precedence over global settings, stored in XML.
>
>
> That sounds exactly like Java Preferences API !?
>
> /max
>
> >
> > ~Lincoln
> >
> > On Thu, Jun 16, 2011 at 12:40 PM, Max Rydahl Andersen <
> max.andersen at redhat.com> wrote:
> >
> > > 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.
> >
> > 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 ?
> >
> > /max
> >
> > >
> > > ~Lincoln
> > >
> > > On Thu, Jun 16, 2011 at 4:31 AM, Max Rydahl Andersen <
> max.andersen at 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 at 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 at lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/forge-dev
> >
> > /max
> > http://about.me/maxandersen
> >
> >
> >
> >
> > _______________________________________________
> > forge-dev mailing list
> > forge-dev at 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 at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/forge-dev
>
> /max
> http://about.me/maxandersen
>
>
>
>
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
>



-- 
Lincoln Baxter, III
http://ocpsoft.com
http://scrumshark.com
"Keep it Simple"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20110616/0aace5b4/attachment.html 


More information about the forge-dev mailing list