I was wondering if this might be a good case to use a profile that is activated by default? I was thinking that you could define the plugin within the development profile and then configure the source and target elements as normal. This profile could then be placed in the .m2/settings.xml file and would cover all projects.
Trent On 15/08/2008, Stephen Connolly <[EMAIL PROTECTED]> wrote: > > Have all your projects with a common parent. > > In the common parent add a pluginManagement section that defines the > defaults for the compiler plugin. > > On Fri, Aug 15, 2008 at 1:51 PM, monika7 <[EMAIL PROTECTED]> wrote: > > > > > I know that current default for maven-compiler-plugin is java 1.3 and > that > > I > > can override it in pom.xml file by adding source and target attributes to > > the plugin configuration. > > However I would prefer to override the default compiler version > permanently > > without having to include the plugin in pom.xml. > > I don't see anything in the settings.xml that would allow me to do it. Is > > that possible and if yes, can someone suggest how to do it? > > -- > > View this message in context: > > > http://www.nabble.com/Changing-default-compiler-version-for--maven-compiler-plugin-%28outside-pom.xml%29-tp18998146p18998146.html > > Sent from the Maven - Users mailing list archive at Nabble.com. > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > >
