Profile activation based on JDK, how it works?

[Jan <ra...@gmail.com>]

Hi All,

I was just wondering  about the following situation

I'm using maven 2.2.1 which requires jdk 1.5 to run, but my modules will
compile only with 1.4, so i used the 1.4 executable in my compiler plugin.

In this case if i create profile with the activation rule for <jdk>1.4</jdk>
when this profile will get activated?

Any one had this situation

Re: Profile activation based on JDK, how it works?

[Jörg Schaible <jo...@gmx.de>]

Hi Jan,

Jan wrote:

> Hi All,
> 
> I was just wondering  about the following situation
> 
> I'm using maven 2.2.1 which requires jdk 1.5 to run, but my modules will
> compile only with 1.4, so i used the 1.4 executable in my compiler plugin.
> 
> In this case if i create profile with the activation rule for
> <jdk>1.4</jdk> when this profile will get activated?
> 
> Any one had this situation

the profile is activated on the JDK version that is used running Maven. The
profile is evaluated at very early stage, since it defines the effective
(=resulting) POM that is used for your build. However, you should really
know, what you do within this profile. It is e.g. a bad idea to manage a
different set of dependencies in profiles based on the JDK version for
artifacts although this seems a good example at first glance. Especially in
your cases where you try to build using a different compiler version (or
even build for a different JDK target), such dependencies might give you a
surprise.

- Jörg



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org