That's not a good solution. IMO, a good Maven build should build everything in one build execution so that it gets deployed to the repo. A correctly repo manager should prevent redeploys. If you build twice, the pom will be redeployed.
/Anders On Fri, Mar 16, 2012 at 12:34, Tim Pizey <[email protected]> wrote: > On 16 March 2012 09:49, jerem wrote: >> Hi, >> >> I wonder if it would be possible with Maven to produce, from a same module >> sources, 2 different jars with classes compiled with different source and >> target values ? >> >> I'm up to using "-d <directory>" as compilerArgument of the >> maven-compiler-plugin, but it fails with : >> " javac: invalid flag: -d <directory>" >> >> If I run maven with -X option and test the javac command-line logged, it >> works though ... >> >> If that worked I would have 2 executions of compiler (producing >> target/classes-15 and target/classes-16), then would use 2 executions of >> maven-jar-plugin to produce both jars with different classifiers if >> possible. >> >> Thanks for help, >> Jeremie > > I suggest you use profiles then you can specify different > compiler options in each profile and invoke with > > mvn deploy -Pjava15 > mvn deploy -Pjava16 > > cheers > Tim > > > > -- > Tim Pizey - http://pizey.net/~timp > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
