Server Side plugin are not visible in RTC6.0
Chandan M B (50●12●59)
| asked Jul 20 '15, 2:21 a.m.
edited Jul 21 '15, 4:52 a.m. by Ralph Schoon (56.6k●2●36●42)
Hi,
I used to deploy the plugins in 5.0.2 ccm->conf->sites folder and ini in provision_profile folder. I used to configure it to the project area as a follow up action. I have upgraded the server to 6.0. I am deploying plugins in the similar way. My plugin is not visible in follow up action to configure to the Project Area. Please help what needs to be done in 6.0!! Regards, Chandan |
One answer
Ralph Schoon (56.6k●2●36●42)
| answered Jul 20 '15, 2:34 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
There is no change in how to deploy RTC extensions in RTC, however, it is common sense to test if the extension still runs with RTC 6.0. I have seen no breaking API changes in 6.0 https://rsjazz.wordpress.com/2015/07/15/rtc-6-0-does-the-api-change-and-break-my-code/ however, that does not mean that there aren't any.
Also the extensions contain dependencies to the API which can include a version info. If done wrong, this can result in the plugin not being deployable. You would see all this in a 6.0 development environment. Comments Hello Ralph,
You can see and edit the dependency versions in the development environment in the plugin.xml. You can also see errors there if you look at it in 6.0.
why component status of a plugin is not visible in 6.0 like in 5.0.2 ?
I have proven, at least to me, that there is no change in how deployment works in RTC 6.0 and my extensions deploy fine the same way they ever have.
|
