#96 plugin extention point required

[Anonymous]

Excellent plugin ;o)

It would be really nice if you provided extention points to
allow other plugins to take advantage of the functionality
provided by your. I am currently trying to write a plugin
to allow me to replace sections of java code on mass
but at present I am required to check out the code from
the repository prior to processing. While one option is to
write my code to perform the checkout this is off course
recoding what you already do well.

Is there any chance of you providing this flexability?

Thanks

[Marcus Nylander]

Logged In: YES
user_id=373462

What exactly are the kind of extention points you would like
to have?

[Nobody/Anonymous]

Logged In: NO

Excuse my ignorance if what I want to do is already possible
as I am new to both Eclipse and developing plugins. What I
would like to 'have' is a way to call your code to perform the
checkout of a file so I can modify it and then use your code
to perform the check-in along with comments, label etc.

I also want to make my plugin depend on yours so it
becomes disabled when yours is not installed.

Any pointers into this are extreamly appreciated.

Thanks for the prompt response. I gather you get quite a few
questions with such a good plugin.

[Marcus Nylander]

Logged In: YES
user_id=373462

Ok, normally what you need to do is something like the
following (and also add org.vssplugin to you plugin.xml):

VSSPluginProvider provider =
VSSPluginProvider.getProvider(project);
provider.checkout(...);
// modify file..
// This is currenlty no support for labeling resources
from the provider..
provider.checkin(...);

more example can be found in the action-classes in package:
org.vssplugin.ui.actions

[Nobody/Anonymous]

Logged In: NO

Thank you for the info.

Much appreciated