Right, so the build configurations can specify which JAVA_HOME they wish to use as an environment variable setting.
On Mon, May 5, 2008 at 11:06 AM, Johan Compagner <[EMAIL PROTECTED]> wrote: > Everything can run under Java6 thats not a problem > What cant be done is that the maven build of a project should use Java4 or > Java5 > > johan > > > On Mon, May 5, 2008 at 4:52 PM, James Carman <[EMAIL PROTECTED]> > wrote: > > > > > You can also set up JAVA_HOME as an environment variable through your > > run configuration in TeamCity. > > > > On Mon, May 5, 2008 at 10:49 AM, Sebastiaan van Erk <[EMAIL PROTECTED]> > > wrote: > > > Hi, > > > > > > The good news: > > > I installed Java 6. > > > > > > The bad news: > > > Java 6 is now the system default VM. This will probably mess up > > some > > > stuff if you execute java through the path (/usr/local/bin/java) instead > > of > > > having set JAVA_HOME environment variable to the Java 5 home. I don't > > know > > > if you guys do this, so it may not be an issue. > > > > > > The workaround: > > > Make sure JAVA_HOME variable is set in the wicket user env to > > the > > > Java 5 home; then /usr/local/bin/java will run Java 5. This can be put > > in > > > your .bashrc/.cshrc or something. Testing advised. ;-) > > > > > > > > > > > > Regards, > > > Sebastiaan > > > > > > Martijn Dashorst wrote: > > > > > > > Best is to install it on our server, so yes please! > > > > > > > > Martijn > > > > > > > > On 5/5/08, Sebastiaan van Erk <[EMAIL PROTECTED]> wrote: > > > > > > > > > Sure, that's fine with me, but a Java 6 install isn't a big deal, so > > if > > > you > > > > > want it on the machine, just say so. :-) > > > > > > > > > > > > > > > Regards, > > > > > Sebastiaan > > > > > > > > > > > > > > > Martijn Dashorst wrote: > > > > > > > > > > > > > > > > Another option would be to obtain some additional server that has > > java > > > > > > 6 available and run a build agent on it. TC supports build > > agents... > > > > > > > > > > > > Martijn > > > > > > > > > > > > On 5/5/08, Sebastiaan van Erk <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > > > > > > > Considering it's freebsd and it needs a patched java compiled > > from > > > > > > > > > > > > > > > > > > source, I > > > > > > > > > > > > > > > > > > guess it's going to be me who does the install. ;-) > > > > > > > > > > > > > > Regards, > > > > > > > Sebastiaan > > > > > > > > > > > > > > > > > > > > > Martijn Dashorst wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I know we have to compile everything using Java 5. But as many > > of > > > our > > > > > > > > users are running Java 6 already, perhaps we should add a > > testing > > > > > > > > build profile that builds Wicket using Java 6. One problem: we > > > don't > > > > > > > > have Java 6 installed on the box. > > > > > > > > > > > > > > > > (Java 6 would also be a big improvement performance wise I > > think) > > > > > > > > > > > > > > > > Should we install java 6? And if so, who is going to do so? > > > > > > > > > > > > > > > > Martijn > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
