On 6/4/07, EJ Ciramella <[EMAIL PROTECTED]> wrote:
Please enlighten me - how do you avoid using profiles entirely?
You will need to describe your use case. Basically a profile should only be used to either a) externalise OS dependent settings, e.g. location of eclipse installation. In general for all most all maven plugins you never need to do this b) to turn on additional plugins that you dont want include in the default build, e.g. an integration test suite run. You are using -Ppersonal,StackDefaults,ca-lime,root which just feels wrong. Why are you having to select these values? Why are they not the defined defaults? There was a discussion a while ago about multiple build for different configurations, e.g. Tomcat/War, JBoss/Ear, etc. I can't recall the result of the discussion. But if you always want to build each of these configurations then you may want to consider creating a module per configuration that has all the correct settings defined for that build. e.g. Root + configurationA (contains A's specific configurationd details) + configurationB (contains B's specific configurationd details) + module1 + ... where all configurations depend upon independent artifacts. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
