WARN eam.repository.provision.internal.ProvisionService - CRJZS0383 bundle could not be resolved.
Worked through the workshop.
|
One answer
Ralph Schoon (63.5k●3●36●46)
| answered Mar 06 '17, 8:52 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER There is certainly more information in the log file than the wee bit information above. That information is usually a little bit of help. Other typical issues I have seen:
1. Deployed into the wrong context (e.g. JTS and not CCM)
2. Client API in the dependencies
3. Typos in the provision profile ini (usually crashes the server)
4. Application not built right
Comments
If I recall correctly, the Extensions workshop explains how to change the dependencies in the Feature so that com.ibm.team.repository.common would not be a dependency in the feature. although I have to admit I have skipped these steps as well. There have been examples where users had client (e.g. com.ibm.team.repository.client) in their dependencies. That works on Jetty, because the client API is available but not on Tomcat.
I have seen rare cases, where issues with the zip files caused load problems.
I have seen cases, where the plugin.xml was not selected as part of the build and was missing. I have seen countless questions like this one in this forum. Unless there is not more information e.g. a more detailed error message, there is pretty much nothing we can do.
Ralph Schoon
commented Mar 06 '17, 9:14 a.m.
| edited Mar 06 '17, 9:19 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
In addition in the new version of the Extensions Workshop I have added some details about how to manage the deploy process. Unfortunately, the update is delayed due to some changes to the site. There is no difference between advisor and participant deployment, or any other server extension. |
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.