no no, if you look at how bamboo is configured it is actually building the projects against 1.4jdk, not against 1.5jdk with compatibility set to 1.4
it does what you do when you release, sets javahome to point to 1.4 jdk instead of the 1.5 one. check out the link almaw provided and look under build configuration tab. -igor On 2/5/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
I still am not convinced that using a JDK 1.5 for building a 1.4 library will not complain about a JDK 1.5 dependency. And if bamboo compiles running inside a JDK 1.4 I still don't trust us to actively keep supporting the continuous integration server, just as we still don't always run the unit tests before we commit. Call me a cynic, but I've been bitten by these cross JDK issues too often to trust anything other than completely isolating the projects during a release. Martijn On 2/5/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > so really if bamboo actually compiles against 1.4 we shouldnt have any > > problems "trusting" that the code is correct martijn? > > That would be a lot better than the semi-manual check which Martijn > does now. I think the whole build should ideally be one step, and it > would be best to filter out wrongly committed code *long before* we're > even thinking about doing a release. > > Eelco > -- Vote for Wicket at the http://www.thebeststuffintheworld.com/vote_for/wicket Wicket 1.2.4 is as easy as 1-2-4. Download Wicket now! http://wicketframework.org
