RTC Extensions problem
Hi, I have this extension developed based on the IBM lab extension tutorial, which has now gone through quite a few iterations and has been working on our test server no problem for months. Recently, I added another extension to it, and changed an advisor to participant, which all works well when I test in the eclipse debug instance. However my built plugin fails to install on the server and changes not being picked up. This is the error msg
2013-02-19 08:24:26,822 [ Launch callback handler] ERROR eam.repository.provision.internal.ProvisionService - CRJAZ0291I Failed to start the bundle "com.hsbc.alm.g3.workflow.rtcext.service 1.0.0.201302181730".
org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Missing Constraint: Require-Bundle: com.ibm.team.scm.service; bundle-version="3.1.0"
One of the extensions (which I didn't amend) uses com.ibm.team.scm.service. I may inadvertently clicked/unclicked/removed something but I've looked hard and can see nothing else different. Anyone have any clue where I may go searching for the cause of this? Thanks very much
Rgds
Sola
One answer
can you check on the properties of the dependency, if it requests a specific version? Typically it requests a minimal version. 3.1.400 is RTC 4.0.1.
Comments
Thanks Ralph...In fact, I started this work with 4.0. Our deploy environments are now 4.0.1. I'm going to rebuild my dev environment with sdk4.0.1 for consistency and see how that goes.
Rgds
Sola
Hi
I've rebuilt my plugin in 4.0.1. As before, I am able to test/debug successfully, but my built plugin still fails to load in rtc. In fact, the jazz (ccm) application fails to start. Actually, I did also have this problem previously (with 4.0) before the scm error I reported earlier. I'm not building the plugin any different to how I was doing it when it worked. (Jazz starts if I remove the plugin).
I'd appreciate any ideas on this please. Thanks.
Sola,
I can't remember having seen that. I can only guess. Maybe wrong data in the generated deployment data. Missing files etc. I would also review the provisioning.ini file you deploy. This error seems to happen on a fairly high level where the provisioning mechanism seems to read that file. Are there any more hints in the CCM log?
If I want to redeploy, I first remove all generated files in the updatesite project and then I regenerate the update site.