It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,854

question asked: Dec 01 '09, 7:06 a.m.
question was seen: 4,569 times
last updated: Dec 01 '09, 7:06 a.m.

Related questions

Build Tool JDKs

0
Alan D (156●3●13●11) | asked Dec 01 '09, 7:06 a.m.
Why does the build tool require a different JDK (the version shipped with the Client) to the one I want to use to compile my applications (IBM/Java 50)?

Is there a regression test risk here?

2 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Jose Miguel Ordax Cassa (2.4k●4●126●100) | answered Dec 01 '09, 7:23 a.m.
On 01-Dec-09 1:08 PM, 1.21Jigawatts wrote:
Why does the build tool require a different JDK (the version shipped
with the Client) to the one I want to use to compile my applications
(IBM/Java 50)?

Is there a regression test risk here?


I think the requirement is just for the Build Engine run itself.
But within your build scripts, you will be able to compile code using
the JDK you choose.

Regards,

Chemi.
0
permanent link
Nick Edgar (6.5k●7●11) | answered Dec 03 '09, 1:45 p.m.
JAZZ DEVELOPER
That's correct. For more info, see
https://jazz.net/wiki/bin/view/Main/BuildFAQ#WhichJDK

The main reason is that the IBM 1.5.0 SR9 JDK had several defects, which the JDK we shipped in RTC 2.0 had fixes for. The main one for JBE was a pipe leak problem, which was an issue for a long-running process like JBE. It's less of an issue for a short-lived process like the Ant invocation.
These have since been fixed in SR11, so you should be fine if you want to use that instead.

Also note that in the Ant page of the build definition, you can configure it to use a different JDK than the one used to run JBE (the default behaviour).

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.