Home » Eclipse Projects » Eclipse Platform » Programmatically working with CVS resources
| Programmatically working with CVS resources [message #283528] |
Tue, 05 April 2005 02:16  |
Eclipse User |
|
|
|
Originally posted by: esteban_5.yahoo.com
I have a project that requires my plug-in to work with shared projects (CVS
resources) which I have so far handled by using the
org.eclipse.team.internal.ccvs.core package to manipulate individual
ICVSResource objects. My plug-in needs annotation and log information from
CVS, which I could not find another way to access other than the internal
classes (Command.ANNOTATE and Command.LOG). I realize there are caveats to
using the internal code (my code has been broken by new releases a couple
times) and was wondering if anyone had encountered similar problems and any
workarounds, or solutions. Are there public methods for CVS operations?
Thanks!
Stephen
|
|
| | | |
| Re: Programmatically working with CVS resources [message #283584 is a reply to message #283570] |
Wed, 06 April 2005 09:50  |
| Eclipse User |
|
|
|
Originally posted by: Michael_Valenta.oti.com
Stephen,
As I said, there is no CVS API so the only way to use the CVS plugin
programmatically is to use internal classes. People do this but, as you have
experienced, there is always the possibility of breakage accross releases.
This is a decision you have to make. If breakage is not something you are
willing to live with, you will need to find another CVS client to use.
Michael
"Stephen Q" <esteban_5@yahoo.com> wrote in message
news:d2va87$nao$1@news.eclipse.org...
> Thanks for the replies. I'm wondering what, specifically, people are
> doing (or not doing) to avoid using the internal classes. How do people
> avoid using the internal classes to access CVS logs and annotations, for
> instance? I've had to use ICVSResource and ICVSRemoteResource classes to
> access annotations and logs respectively, but with Eclipse 3.1 (I don't
> know about 3.0.2) my code has been broken.
>
> -Stephen
>
>
> "Michael Valenta" <Michael_Valenta@oti.com> wrote in message
> news:d2u61c$4el$1@news.eclipse.org...
>> Stephen,
>>
>> The CVS plugin does not have any official API but I know that there are
>> quite a few people who are using internal classes to make CVS based
>> tools. The main caveat is that you have no gaurantee of backwards
>> compatibility accross releases.
>>
>> Michael
>>
>> "Stephen Q" <esteban_5@yahoo.com> wrote in message
>> news:d2talt$rar$1@news.eclipse.org...
>>>I have a project that requires my plug-in to work with shared projects
>>>(CVS resources) which I have so far handled by using the
>>>org.eclipse.team.internal.ccvs.core package to manipulate individual
>>>ICVSResource objects. My plug-in needs annotation and log information
>>>from CVS, which I could not find another way to access other than the
>>>internal classes (Command.ANNOTATE and Command.LOG). I realize there are
>>>caveats to using the internal code (my code has been broken by new
>>>releases a couple times) and was wondering if anyone had encountered
>>>similar problems and any workarounds, or solutions. Are there public
>>>methods for CVS operations?
>>>
>>>
>>>
>>> Thanks!
>>>
>>> Stephen
>>>
>>
>>
>
>
|
|
|
| Re: Programmatically working with CVS resources [message #283599 is a reply to message #283584] |
Wed, 06 April 2005 20:03 |
| Eclipse User |
|
|
|
What is another CVS client?
I see no other Java CVS client better then I see in Eclipse.
And another decision would be to make public CVS API.
Regards,
Alexey
"Michael Valenta" <Michael_Valenta@oti.com> wrote in message
news:d30pmd$kd9$1@news.eclipse.org...
> Stephen,
>
> As I said, there is no CVS API so the only way to use the CVS plugin
> programmatically is to use internal classes. People do this but, as you
> have experienced, there is always the possibility of breakage accross
> releases. This is a decision you have to make. If breakage is not
> something you are willing to live with, you will need to find another CVS
> client to use.
>
> Michael
>
> "Stephen Q" <esteban_5@yahoo.com> wrote in message
> news:d2va87$nao$1@news.eclipse.org...
>> Thanks for the replies. I'm wondering what, specifically, people are
>> doing (or not doing) to avoid using the internal classes. How do people
>> avoid using the internal classes to access CVS logs and annotations, for
>> instance? I've had to use ICVSResource and ICVSRemoteResource classes to
>> access annotations and logs respectively, but with Eclipse 3.1 (I don't
>> know about 3.0.2) my code has been broken.
>>
>> -Stephen
>>
>>
>> "Michael Valenta" <Michael_Valenta@oti.com> wrote in message
>> news:d2u61c$4el$1@news.eclipse.org...
>>> Stephen,
>>>
>>> The CVS plugin does not have any official API but I know that there are
>>> quite a few people who are using internal classes to make CVS based
>>> tools. The main caveat is that you have no gaurantee of backwards
>>> compatibility accross releases.
>>>
>>> Michael
>>>
>>> "Stephen Q" <esteban_5@yahoo.com> wrote in message
>>> news:d2talt$rar$1@news.eclipse.org...
>>>>I have a project that requires my plug-in to work with shared projects
>>>>(CVS resources) which I have so far handled by using the
>>>>org.eclipse.team.internal.ccvs.core package to manipulate individual
>>>>ICVSResource objects. My plug-in needs annotation and log information
>>>>from CVS, which I could not find another way to access other than the
>>>>internal classes (Command.ANNOTATE and Command.LOG). I realize there
>>>>are caveats to using the internal code (my code has been broken by new
>>>>releases a couple times) and was wondering if anyone had encountered
>>>>similar problems and any workarounds, or solutions. Are there public
>>>>methods for CVS operations?
>>>>
>>>>
>>>>
>>>> Thanks!
>>>>
>>>> Stephen
>>>>
>>>
>>>
>>
>>
>
>
|
|
|
| Re: Programmatically working with CVS resources [message #283618 is a reply to message #283599] |
Thu, 07 April 2005 09:55 |
| Eclipse User |
|
|
|
Originally posted by: Michael_Valenta.oti.com
Alexey,
We have often thought about providing CVS API. However, the main issue is
that there is actually a large amount of effort required to define and
maintain an API and there are just too many other higher priority items on
the Eclipse Platform to-do list.
Michael
"Alexey Yakimovich" <aiy@ferens.net> wrote in message
news:d31tk7$ckh$1@news.eclipse.org...
> What is another CVS client?
> I see no other Java CVS client better then I see in Eclipse.
> And another decision would be to make public CVS API.
>
> Regards,
> Alexey
>
> "Michael Valenta" <Michael_Valenta@oti.com> wrote in message
> news:d30pmd$kd9$1@news.eclipse.org...
>> Stephen,
>>
>> As I said, there is no CVS API so the only way to use the CVS plugin
>> programmatically is to use internal classes. People do this but, as you
>> have experienced, there is always the possibility of breakage accross
>> releases. This is a decision you have to make. If breakage is not
>> something you are willing to live with, you will need to find another CVS
>> client to use.
>>
>> Michael
>>
>> "Stephen Q" <esteban_5@yahoo.com> wrote in message
>> news:d2va87$nao$1@news.eclipse.org...
>>> Thanks for the replies. I'm wondering what, specifically, people are
>>> doing (or not doing) to avoid using the internal classes. How do people
>>> avoid using the internal classes to access CVS logs and annotations, for
>>> instance? I've had to use ICVSResource and ICVSRemoteResource classes
>>> to access annotations and logs respectively, but with Eclipse 3.1 (I
>>> don't know about 3.0.2) my code has been broken.
>>>
>>> -Stephen
>>>
>>>
>>> "Michael Valenta" <Michael_Valenta@oti.com> wrote in message
>>> news:d2u61c$4el$1@news.eclipse.org...
>>>> Stephen,
>>>>
>>>> The CVS plugin does not have any official API but I know that there are
>>>> quite a few people who are using internal classes to make CVS based
>>>> tools. The main caveat is that you have no gaurantee of backwards
>>>> compatibility accross releases.
>>>>
>>>> Michael
>>>>
>>>> "Stephen Q" <esteban_5@yahoo.com> wrote in message
>>>> news:d2talt$rar$1@news.eclipse.org...
>>>>>I have a project that requires my plug-in to work with shared projects
>>>>>(CVS resources) which I have so far handled by using the
>>>>>org.eclipse.team.internal.ccvs.core package to manipulate individual
>>>>>ICVSResource objects. My plug-in needs annotation and log information
>>>>>from CVS, which I could not find another way to access other than the
>>>>>internal classes (Command.ANNOTATE and Command.LOG). I realize there
>>>>>are caveats to using the internal code (my code has been broken by new
>>>>>releases a couple times) and was wondering if anyone had encountered
>>>>>similar problems and any workarounds, or solutions. Are there public
>>>>>methods for CVS operations?
>>>>>
>>>>>
>>>>>
>>>>> Thanks!
>>>>>
>>>>> Stephen
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
|
|
|
Goto Forum:
Current Time: Wed Nov 05 17:23:08 EST 2025
Powered by FUDForum. Page generated in 0.24854 seconds |
Home