[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-vcm-dev] Using CVS plug-ins in other plug-ins - everything is internal
|
Jean-Michel Lemieux wrote:
Just to clarify, these packages are marked as internal but can be accessed
from other plugins. The
marking of them as internal is more a design intention than a runtime
constraint. We don't want to commit
to maintaining binary compatibility between releases. This has allowed us
to implement features in the
CVS plugin that wouldn't of been allowed otherwise.
OK, I see.
Many other plugins are using the CVS classes, and luckily they aren't
changing much. You shouldn't
have to extract the classes, just add the dependency to your plugin.xml
file.
That's the way I did it. But up to now I had no time to ask the mailing
list.
Additionally, I would like to understand how you are using the CVS plugin
so that we can understand
if the Team API (e.g. see the bug 37705) would address your needs.
I'm developing a plug-in for Eclipse for automated debugging. The
plug-in narrows down failure inducing code changes.
In general, I need to checkout the project and to generate diffs (diff
rev1/date1 against date2) (java) resources, and to handle different
branches.
More about the underlying techniques can be accessed here:
http://uni.martin-burger.de/cs/papers/Automated_Debugging_in_Eclipse.pdf
An improved team API would be great, so I could use some version control
systems other than CVS. Additionaly, I see a huge benefit of official
APIs as they are well documented.
I will be attending the CampEclipse Plug-in Clinic in Zurich, perhaps
some of you are attending, too, so we could talk about the Team API, there.
Regards, Martin
