Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[stp-dev] 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


Back to the top