Eric, We are using ant to do value replacement in the flex-config then taking the basic flex.war and dumping all our our custom stuff in. This approach works well for us since we do value replacements elsewhere as well. If you want my ant scripts I would be happy to post them.
-James On Fri, 2005-03-11 at 20:37 +0000, Eric Raymond wrote: > > I'm curious how people handle the flex-config.xml file when they > deploy their application to a public server? > > The issue we have is that the flex config has both development > settings which should not be released and other settings like > RemoteObject settings which need to be released when they change with > respect to a build. > > One idea is to have some ant task which modifies the config file prior > to to creating a .war file. > > Another idea is to somehow split up the flex-config file into two > files: a file that contains the release/development specific info and > a file which has the common, but likely to change settings like > remoteobject configurations. We would have two versions of the former > file. > > Has anyone dealt with this in a nice way? FYI, we like to deploy > straight from version control with no/minimal manual steps involved. > > > > > > > Yahoo! Groups Links > > > > > > > >
