[stp-dev] RE: Build failed in Hudson: stp.policy.trunk #36

[Andrei Shakirin <andrei.shakirin@xxxxxxxxx>]

Hi Oisin,

Thanks for you mail!
As far as it is not critical point at the moment, I have rolled back it to 1.5.
I think it makes sense to migrate all STP projects in one step. Let put it in our TODO list.

Other thing: I am not very happy with state of PolicyEditor online documentation.
Page http://www.eclipse.org/stp/policy/index.php still shows under construction message.
What it the best way to update it: put online docs first into STP wiki and than link it to this page?
Or it is easier to provide docs in other form?

Regards,
Andrei.

-----Original Message-----
From: Oisin Hurley [mailto:oisin.hurley@xxxxxxxxx] 
Sent: Dienstag, 8. September 2009 00:15
To: Andrei Shakirin
Cc: stp-dev@xxxxxxxxxxx
Subject: Re: Build failed in Hudson: stp.policy.trunk #36

Hi Andrei,

> Changes:
>
> [ashakirin] Updated java version to 1.6

Moving the project up to Java 1.6 default has a few knock-on effects that you might not be aware of. First, there'll have to be a corresponding change in the Hudson build to use 1.6 as the JVM for compiling (it uses 1.5 right now). Second, the default JVM version should also be set in the standalone policy build (this defaults to 1.5, but can be set by a property in the Hudson build configuration). Finally, and this is the most important part, everything else in STP uses 1.5 as the default. If one element of the build is uses a different version, it means we will have to split the builds - e.g. have a 1.5 version of STP with no policy part and a 1.6 version of STP which has everything (provided everyone else is ok with making sure that their stuff works with 1.6).

Of course, what you wish to do with policy is totally up to the committers :)  If you are moving to 1.6, please put in a bugzilla for the build component so I can update the Hudson build and the STP build, etc. Anyone else wanting to move to 1.6, same applies.

 cheers
   --oh