It's all about the answers!

Ask a question

How do you package a custom link type and move it to a different environment from where it's developed?

Shawn Carroll (286) | asked Dec 11 '19, 4:09 p.m.

 I walked through this documentation to create and deploy a custom link type:

It worked well in my development environment and I was able to install the new software in the develoment RTC client fine. When I moved the link type extension to my production server, I tried to package up the update-site directory for my production side RTC client but when I tried to install the feature, it keeps telling me it's missing a dependency:

Cannot complete the install because one or more required items could not be found.
  Software being installed:  Feature (
  Missing requirement: Common (.common requires 'bundle 1.4.5000' but it could not be found

I tried adding the file to the RTC Clients plugins folder but then I started getting these errors:

Cannot complete the install because of a conflicting dependency.
  Software being installed: Feature (
  Software currently installed: IBM Rational Team Concert Client 2019.11.12.065339 (IBM Rational Team Concert Client 2019.11.12.065339)
  Only one of the following can be installed at once: 
    Repository component - common 1.4.5000.v20190306_1746 ( 1.4.5000.v20190306_1746)
    Repository component - common 1.4.4000.v20171031_1821 ( 1.4.4000.v20171031_1821)
  Cannot satisfy dependency:
    From: IBM Rational Team Concert Client 2019.11.12.065339 (IBM Rational Team Concert Client 2019.11.12.065339)
    To: [1.1.4000.v20171031_1821]
  Cannot satisfy dependency:
    From: Common (.common
    To: bundle 1.4.5000
  Cannot satisfy dependency:
    From: Feature (
    To: .common []
  Cannot satisfy dependency:
    From: Repository Common Feature 1.1.4000.v20171031_1821 ( 1.1.4000.v20171031_1821)
    To: [1.4.4000.v20171031_1821]

One answer

permanent link
Ralph Schoon (62.7k33643) | answered Dec 12 '19, 2:32 a.m.
edited Dec 12 '19, 5:01 a.m.
Shawn, you have issues in the dependencies in the different plugins. You should be able to deploy the extensions anywhere without issues.

The error messages look a bit funny. I have usually used full package names such as in the feature names to make sure I can distinguish between my extensions and the target environment (and search for my stuff).

Note that you seem to have the version numbers in the dependencies. If you do, the environment you deploy in have to have that version or at least that version, dependent on how you do it.

Please check the last lab of the RTC Extensions Workshop (article 1000). I have added some experience I gained over the years in the last updates. Please check how to find the dependencies. I have not always followed these steps closely when creating examples on Maybe looking into that helps.

I have seen numerous times that stuff work on the Jetty server and do not when deployed. This was usually due to dependency issues. Jetty has a lot more libraries in the path than a real server, because the target platform contains client, common and server API. 

Your answer

Register or to post your answer.