Yes, it's simple enough.
Have a look at this pom:
http://code.google.com/p/swjang00/source/browse/trunk/kims_2.5/pom.xml?r=17
See how the maven.compiler.target is a variable? All you'd have to do
is define two profiles, one for 1.5, one for 1.6. and away you go. You
can have the 1.5 profile active by default, and switch on the 1.6
release when you want to cut a release for a certain client.
On 27/08/2008, at 3:51 PM, Peter Horlock wrote:
No, you don't understand, I want Maven to change the JDK itself!
To release a new version for this client, I have to change my JDK
from 1.5
to 1.6, and all this manually. Wouldn't it be possible to automate
this with
Maven?!
Thanks,
Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
