unable to add a plugin as a precondition for Save Work Item

You might want to look at the Extension workshop in the library, since that is somewhat more detailed.

I have seen sometimes see with Eclipse extensions that the build configuration does not export the plugin.xml or other vital information. You should check that.

You might want to look at the Extension workshop in the library, since that is somewhat more detailed.

I have seen sometimes see with Eclipse extensions that the build configuration does not export the plugin.xml or other vital information. You should check that.

Thanks Ralph.
I went through the workshop tutorials.
Found few thing useful and complecated as well.
I have tried creating the plugin few times more and still unable to add the Advisor as a Precondition for the specific project.
I am working on RTC 3.0.1.
I have started learning RTC few days back only, so not much expertised in dealing with RTC Extension.
Found the good article in the above mentioned link so tried that.
What I want to achieve is,
Customize Project Area/ Work Items.
I want to update the attributes(Built-in/Customized) of a Work Items(Parent/child) dynamically, at the time of creating a new work item.
For this I found that creating a Plug-in will be a good option, but I got stuck at the initial stage itself.

Can you please tell me whether I am moving in right direction or is there any other approach to achieve this?

I would suggest to first set up the dev environment as in the workshop. You have to add the plug-in to the debug configuration. You also have to specify the services needed in the plugin.xml as shown in the workshop. Otherwise it will not work. If you run your debug configuration with the plugins included, it should show up. You should be able to debug as well. Otherwise you got the plugin.xml or the extension point data wrong.

With no example code you use it is impossible to answer questions - there is just not enough data to narrow down the issue.

I would suggest to first set up the dev environment as in the workshop. You have to add the plug-in to the debug configuration. You also have to specify the services needed in the plugin.xml as shown in the workshop. Otherwise it will not work. If you run your debug configuration with the plugins included, it should show up. You should be able to debug as well. Otherwise you got the plugin.xml or the extension point data wrong.

With no example code you use it is impossible to answer questions - there is just not enough data to narrow down the issue.

Hi Ralph,

I just checked i don't have 10 free developer license but I do have one TRial Developer license.
I have also not configured debug setup.
Is it required?

Hi,

I would set up a local test system to develop, debug and test - maybe just run the workshop once for you. I would use exactly the setup from the workshop. It just helps in so many ways. Once your plug in works there you could be more certain you can successfully deploy and run your plug-in. If you don't you are likely go through a lot of issues and end up falling back to my proposal anyway. 8-)

I would really consider it.

I am having the exact same problem (plugin loads, but is not shown in list)

https://jazz.net/forums/viewtopic.php?t=20537

and it appears Anu and I are having the same fundamental problem.

we think we have it defined correctly, but the system doesn't behave like it should.

My Activator class loads and start() is called.. I see the message in the server console. my run() method is never called. because I can't configure it.

the fact that the activator runs tells me all the marked dependencies were met.

Sam

just fyi..

I added this plugin site directory and ini provisioning profile to my 3.0.1 instance and all works as expected.. this was a binary file copy..

so, something on 3.0 iFix 1 is different.. how can I solve that problem??

Sam

Sam,

there is a version of the workshop for 3.0 too. The only differences between 3.0 and 3.0.1 with respect of plug-ins and their deployment should be plug in versions.

I'd set up the SDK for 3.0 - you can do that in parallel. I would check if the required packages are available and try it out in debugging mode.

Another place to look are the manifest files. If there are specific versions of required dependencies, you could try to get rid of the version.

thanks.. I have two separate dev environments.. 3.0 iFix 1 (same as our production) and 3.0.1 (after the workitem comment date enhancement )

I had already removed the version from the dependencies.

still trying to get over the hump of handle to object.. see my other post. (help!)

I had removed all the other stuff in the sample and just referenced the required plugins for this precondition operationadvisor.

Sam

The completed 3.0.1 version, re-built under 3.0 works fine.. (binary worked too)

weird..

Sam