|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
RTC support for symbolic links requires one or two libraries (.dll/.so files).
The reason is Java 6 and earlier don't have support for creating/looking at properties of symbolic links. So RTC uses some C code to manage symbolic links.
Java 7 has symbolic link support that works on linux, but on Windows it has some limitations when creating links when the target has not yet been created (type is defaulted to file which is not good if its a directory).
If you are running Linux and can use Java 7 then the only .so you need is for the Eclipse natives. Otherwise, you will need both.
I'll describe what has to happen on Windows, but the steps are similar for linux.
In the Build engine directory (buildengine\eclipse\plugins), look for the
com.ibm.team.filesystem.client_3.1.600.v20130415_0257.jar
org.eclipse.core.filesystem.win32.x86_1.1.201.R36x_v20100727-0745.jar or equivalent jars for your platform/release.
From the com.ibm.team.filesystem.client jar you want to extract the winfsnatives.dll (libfsnatives.so on linux). Take all the .dll/.so from the org.eclipse.core.filesystem jar. Place them directly in a directory (eg. c:\natives\winfsnatives.dll).
Now when you start Jenkins, we need to tell java about the directory so that it can load the libraries from it. This is done through the -Djava.library.path variable.
eg. java -Djava.library.path="c:\natives;%Path%" -jar jenkins-1.509.1.war
We are just adding to what the default would be for Java. You could also add the directory to your path instead.
I realize the setup is a little convoluted, we could probably help by packaging the toolkit a bit differently. But this might be simpler than trying to load the component through the CLI.