build

logic to get remote settings.xml file, test in this order (as maven do)
1. configured alternateSettings
2. ~/.m2/settings.xml
3. $M2_HOME/conf/settings.xml

This is a proof of concept to core modulizarion (by binary integration.)
A module is built like a plugin but it's packaged to the war as a
WEB-INF/lib/*.jar, not as a plugin.

Compared to plugins, jars integrated in this way do not double-package
dependency jars, and they are not visible to the users. I plan to try a
few of these and if it's useful, this could be an useful mechanism for
modularizing core.

[FIXED JENKINS-9102] Changed buildListTable column name from Date to Time Since, to reflect actual content.

Added a configuration option to control initialization of the
environment of the Jenkins server process.

For openSUSE it doesn't make sense to require a specific flavor of JRE
for Jenkins. Even if the RPM explicitly requires the Oracle JDK, thus
causing it to be installed together with Jenkins, some previously installed
JRE may still be used to run Jenkins, due to the update-alternatives(8) setting.
The JRE to use is a sysadmin issue, and not usually part of the RPM spec.

I have not been able to reproduce the scenario described by David.
Installing Jenkins on fresh installs of openSUSE since v11.1 pulls in openJDK
1.6 with it, with which Jenkins runs just fine. Even on Live CDs.

type references by default (can now be done by passing "true" parameter).
This restores ability to use %VAR% references for ant build steps on windows.