It's all about the answers!

Ask a question

Trouble with the BuildSystem


Horia Alungulesei (1111) | asked Oct 25 '10, 10:45 a.m.
JAZZ DEVELOPER
Trying to run jbe.exe from this package: RTC-BuildSystem-Toolkit-Win_3.0.0.RTC-I20101022-1001.zip, I encouter this error:

The Jbe executable launcher was unable to locate its companion shared library.

Anything that I need to configure?

6 answers



permanent link
Nick Edgar (6.5k711) | answered Oct 30 '10, 6:08 p.m.
JAZZ DEVELOPER
Hi Horia,

Sorry for the delay in responding. It could be that the JRE/JDK on your system is configured differently than the JBE executable expects (or maybe there is none).
Try running with the JDK included in the RTC Eclipse client. See:
https://jazz.net/wiki/bin/view/Main/BuildFAQ#WhichJDK

permanent link
jonathan wells (6) | answered Oct 31 '10, 7:55 a.m.
I am having the same problem here, any help would be greatly appreciated!

permanent link
Nick Edgar (6.5k711) | answered Oct 31 '10, 11:00 a.m.
JAZZ DEVELOPER
Does specifying the java runtime using the -vm arg not help? Which JRE/JDK are you using?

You could always trying invoking java directly using the approach here:
https://jazz.net/wiki/bin/view/Main/JbeOtherPlatforms

but the JBE executable should work just fine on Windows, as long as it can find the JRE/JDK.

permanent link
Horia Alungulesei (1111) | answered Nov 01 '10, 9:54 a.m.
JAZZ DEVELOPER
Thanks for the replies.

I have found what caused the problem: it was a simple case of an incorrect unzip operation. It appears that the standard Windows unzip operation does not handle well long file names.

After using 7zip and by keeping the path short, this problem no longer occurs.

permanent link
Nick Edgar (6.5k711) | answered Nov 01 '10, 11:44 a.m.
JAZZ DEVELOPER
Can you give an example to illustrate the length of the path you were extracting to? I assume you're talking about extracting the JBE zip, not the JRE/JDK.

permanent link
kyle connor (6) | answered Nov 15 '10, 3:57 p.m.
Thanks for the replies.

I have found what caused the problem: it was a simple case of an incorrect unzip operation. It appears that the standard Windows unzip operation does not handle well long file names.

After using 7zip and by keeping the path short, this problem no longer occurs.

Thanks, I was having the same problem. Kudos!

Your answer


Register or to post your answer.