[ http://jira.codehaus.org/browse/MNG-295?page=comments#action_38265 ] Michael Hinterseher commented on MNG-295: -----------------------------------------
What is also missing in my mind are a kind of "distribution channels". Normally you have several builds to do during your release cycle: A local test server, a staging environment, a test environment at customer side and the production environment. All this builds are basically the same but several files have to be customized like configuration files, catalogs, database connections and so on. What I did in former projects was defining a properties file for each channel, which was copied to a kind of build.properties file. This was read before building an all properties were set up. Files which had placeholders were called templates e.g. a file which was finally named abc.properties was stored as abcTemplate.properties. During the build the template was copied into the build dir, renamed and the placeholders were exchanged. This is functionality should become somehow a core m2 feature. It should be in addition to the build.properties which should help in my mind to overwrite these standard properties. > ./build.properties equivalent > ----------------------------- > > Key: MNG-295 > URL: http://jira.codehaus.org/browse/MNG-295 > Project: m2 > Type: Bug > Reporter: Brett Porter > Fix For: 2.0-alpha-3 > > > need a way to be able to quickly override settings in the POM for trying > things out or temporarily applying a setting locally. This might also include > a more consistent mapping of plugin configuration to system properties. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
