[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [buckminster-dev] Running Buckminster via java -jar fails to import with JDK 1.5
|
Thanks for the response,
Johannes Utzig wrote on Fri, 14 May 2010 11:30
Hi Andreas,
>
> If I replace in the above code the java-execution with running the
> buckminster shell script (and removing the -jar argument) then it works
> just fine. No idea why that makes a difference.
> Also using a JDK 1.6 < Update 19 (due to the certificate problems) the
> java-invocation version works just fine. I'd really like to use a 1.5
> JDK as we've had some problems with Eclipse accepting 1.6 code even
> though we tried to set 1.5 source compliance everywhere.
if you execute the shell script without a -vm parameter, it will use the
'java' in the system path which naturally will not be the latest 1.5 you
install with hudson.
Hmm, I think I had JAVA_HOME and PATH set up pointing to the downloaded JDK in hudson,
which should be sufficient, right?
Quote:
Can you try running the buckminster script and
point it to the exact same JDK as in your build? i.e.
buckminster -vm /home/andreas/.hudson/tools/1.5_JDK/bin/java ...
Just to narrow it down if it's an issue with the java version or
something else.
That works fine too, I get to see only the "Import complete" message, no errors.
But I've just noticed that the problem doesn't happen with the launcher-invocation either anymore. What I did in the meantime is delete the downloaded buckminster install in hudson and let it re-fetch it. This was done with JDK 1.6.
I now switched back to using JDK 1.5 in hudson and let it build and then it failed again. Now it also fails when I switch back to using JDK 1.6. It almost looks like something gets broken in the buckminster installation itself.
After moving the downloaded buckminster directory out of the way and letting hudson refetch it with JDK 1.6 being enabled it builds with JDK 1.6. When
I now execute the mentioned two commands with the launcher it also works.
So I tested execute with a commands.txt containg the two commands, works too. As last I used the complete commands.txt containing import, build, site.p2 and a product-zip and that too works.
So to conclude: I can only reproduce the problem when running the build from inside hudson. I'll compare the environements between hudson and my terminal on monday to check if there's any difference there.
