Custom check-in policy for Team Explorer Everywhere 2010

Question

Hello All,

Is there any good example on "How to create custom check-in policy for TEE 2010" ?? And Deploy steps too..

I appreciate your time...

Thanks,

Answer 1

Have you downloaded the TFS SDK for Java?  It contains sample check-in policy code that works for the TEE CLC and TEE Plug-in for Eclipse.  The documentation with the sample describes testing and basic deployment steps, but you can use any supported Eclipse plug-in deployment mechanism for your project (update sites are popular).

Also check out Martin's article Getting Started with the TFS SDK for Java for a work item tracking code sample.

Answer 2

Unfortunately, neither of those two links has anything about deploying a custom checkin policy to TEE. Does anyone have this info?

Answer 3

The readme.html in the checkin policy sample provided with the SDK does discuss deployment, and recommends using an update site:

Since check-in policies for Team Explorer Everywhere Plug-in for Eclipse are simply Eclipse plug-ins, they can be deployed to a target IDE using any method it supports. Refer to Eclipse documentation on building and deploying plug-ins for more information.

A simple method of deployment is to export the plug-in project to a deployable plug-in, the output of which can be copied into the dropins directory (or plugins directory for older Eclipse versions) of the target IDE.

• In Package Explorer, right-click on the sample plug-in project and choose Export....
• In the dialog that appears, select Plug-in Development > Deployable plug-ins and fragments as the destination and click Next.
• Choose your preferred output format and name, then complete the wizard.

The process for installing your exported plug-in into a target IDE is specific to the target IDE, but most support a dropins directory. If you exported to a directory, copy all the plug-ins that were written to the plugins subdirectory of the output directory to the dropins directory in the target IDE, then restart the target IDE. If the target IDE does not have a dropins directory, copy the files to the pluginsdirectory instead. See the target IDE's documentation on installing additional plug-ins for more information.