Re: [forge-dev] Where is forge planning to store configuration not possible to encode into source artifacts ?
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(a)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(a)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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev
/max
http://about.me/maxandersen