Why is my plugin for server side development giving the following error?
CRJZS0436I Invalid bundle diagnosis:
CRJAZ1218E The "com.ibm.team.repotools.commands.remote" bundle with the id 469 is invalid, the bundle is not RESOLVED. Examine the the diagnostics that follow this message to determine why the bundle cannot be resolved.
com.ibm.team.repotools.commands.remote [469]
Unresolved requirement: Import-Package: com.ibm.team.repository.client
CRJAZ1218E The "com.ibm.team.repotools.commands.remote.stats" bundle with the id 470 is invalid, the bundle is not RESOLVED. Examine the the diagnostics that follow this message to determine why the bundle cannot be resolved.
com.ibm.team.repotools.commands.remote.stats [470]
Unresolved requirement: Require-Bundle: com.ibm.team.repotools.commands.remote
-> Bundle-SymbolicName: com.ibm.team.repotools.commands.remote; bundle-version="0.10.4000.v20171013_1943"; singleton:="true"
com.ibm.team.repotools.commands.remote [469]
Unresolved requirement: Import-Package: com.ibm.team.repository.client
One answer
Somewhere in your code, the plugin xml's, the plugin dependencies or somewhere else in a feature dependency, you have a reference to com.ibm.team.repository.client which is a client API. It is not available in the server, so you can not deploy.
Comments
Thank you I will double check the plugins and dependencies.
The workshop was created for Windows. I added the shell script and it worked at some point. I know users have done it in Linux.
Error message from WorkshopSetup.sh as downloaded from Jazz.net (directory/file Paths are correct):
The whole WorkshopSetup.sh is completely broken. I will try to look at it tomorrow. I have a sh on my windows system.
JAVA_HOME=../JazzTeamServer/server/jre
PLAIN_JAVA=../PlainJavaAPI
REPOSITORY="https://localhost:9443/ccm"
USERID="myadmin"
PASSWORD="myadmin"
# export PASSWORD
$JAVA_HOME/bin/java -classpath ${PLAIN_JAVA}:. com.ibm.js.rtcext.serversetup.ServerSetup ${REPOSITORY} ${USERID} ${PASSWORD} "$@"
Yes, now my file looks like the first one you put. Now I am also receiving that same error "main class can not be found".
Kieran, at the moment I can't get it to work. This might be related to how the JAR is build (on windows). The JAR works on Windows when started as batch but fails when I try to start it with SH or BASH on Windows. I used the sh and basch that comes with GIT.
Thank you for looking into this! Back to the original question, I did a grep for '.client*' and found some occurrences in the following paths:
yes it goes through the source code as well, but it found no occurrence of any '.client' anywhere else.