+ The main goal is to compile/test sources against the targeted jvm, mvn/maven version, ant version and to add defined envvar (MAVEN_OPTS, ANT_OPTS ...).
This is now possible at the build definition level (in 1.1-beta-1).
+
+ Use case : a solaris with a JAVA_HOME set to a jdk1.4 in the .profile user, a continuum instance running with JAVA_HOME defined in the starting script (NOTE : 1.5 requirement to run continuum), a project which need to be jdk1.4 compliant and some developpers which have ide with jdk1.5 (and fautly add 1.5 methods ;-) ). +
+ ++ Steps : +
-
+
- adding the jdk in installations. +
- create a profile. +
- attached jdk to the new profile. +
- set profile in the build definition. +
Here you must provide a JAVA_HOME path
Enter a profile name (the name is free)
The list box contains all availables installations (jdk, mvn etc..). The installation's type is automatically recognized.
In the modification mode of a profile, adding an already attached type will override the existing one.
+
The list box contains all availables installations (jdk, mvn etc..). The installation's type is automatically recognized.
In the modification mode of a profile, adding an already attached type will override the existing one.
+
Now the notification mail contains the following informations : +
-
+
- Java Home version : coming from $JAVA_HOME/bin/java -version. +
- Builder version : coming from builder used version arg (mvn used -v, ant use -version). +