| Attaching to CVS commit [message #168391] |
Tue, 09 December 2003 22:49  |
Eclipse User |
|
|
|
Folks,
I am developing a plug in that would be best stimulated by a successful
CVS commit from the
team tools. I must admit, I was expecting an extension point at that
place. I have been unable to
find such a point. I have been able to add my own menu item to the team
menu but I would much
prefer to be attached after a successful commit.
My question is this:
Have I missed a better extension point or does one not exist? If so,
what is it? If not, I would like
to make one. How is the best way to proceed with that?
Jeff
|
|
|
| Re: Attaching to CVS commit [message #169255 is a reply to message #168391] |
Thu, 11 December 2003 15:13  |
| Eclipse User |
|
|
|
Originally posted by: Michael_Valenta.oti.com
There is currently no API that supports post commit event notification
and there is no plan in 3.0 to support one.
Michael
Jeff McKenna wrote:
> Folks,
>
> I am developing a plug in that would be best stimulated by a successful
> CVS commit from the
> team tools. I must admit, I was expecting an extension point at that
> place. I have been unable to
> find such a point. I have been able to add my own menu item to the team
> menu but I would much
> prefer to be attached after a successful commit.
>
> My question is this:
> Have I missed a better extension point or does one not exist? If so,
> what is it? If not, I would like
> to make one. How is the best way to proceed with that?
>
> Jeff
>
>
|
|
|
| Re: Attaching to CVS commit [message #169375 is a reply to message #169255] |
Thu, 11 December 2003 17:19 |
| Eclipse User |
|
|
|
Hum,
I am new to this process. How should I proceed? Do I join the CVS
'group' and make the change?
Or do I submit a request? Or do I 'patch' things somehow? (I miss
extensions from ENVY and
Visual Age for Smalltalk!)
Any recommendations?
Thanks a bunch.
Jeff
Michael Valenta wrote:
> There is currently no API that supports post commit event notification
> and there is no plan in 3.0 to support one.
> Michael
> Jeff McKenna wrote:
> > Folks,
> >
> > I am developing a plug in that would be best stimulated by a successful
> > CVS commit from the
> > team tools. I must admit, I was expecting an extension point at that
> > place. I have been unable to
> > find such a point. I have been able to add my own menu item to the team
> > menu but I would much
> > prefer to be attached after a successful commit.
> >
> > My question is this:
> > Have I missed a better extension point or does one not exist? If so,
> > what is it? If not, I would like
> > to make one. How is the best way to proceed with that?
> >
> > Jeff
> >
> >
|
|
|
| Re: Attaching to CVS commit [message #169795 is a reply to message #169375] |
Fri, 12 December 2003 17:08 |
| Eclipse User |
|
|
|
Originally posted by: Michael_Valenta.oti.com
There are already several requests for related features. Some bugs with
similar requests are 26634, 24882, 40623). Unfortunately, the bigger
issue is that the CVS plugin has no API. Also, having a CVS specific API
is not as much of a priority as having a general Team API. There have
been discussions about the possibility of including a general Team API
in 3.0 but the discussion is still ongoing. The platform-team-dev and
platform-cvs-dev mailing lists are probably the best place to discuss
this further.
Michael
Jeff McKenna wrote:
> Hum,
> I am new to this process. How should I proceed? Do I join the CVS
> 'group' and make the change?
> Or do I submit a request? Or do I 'patch' things somehow? (I miss
> extensions from ENVY and
> Visual Age for Smalltalk!)
> Any recommendations?
> Thanks a bunch.
> Jeff
>
> Michael Valenta wrote:
>
>
>>There is currently no API that supports post commit event notification
>>and there is no plan in 3.0 to support one.
>>
>
>>Michael
>>
>
>>Jeff McKenna wrote:
>>
>
>>>Folks,
>>>
>>>I am developing a plug in that would be best stimulated by a successful
>>>CVS commit from the
>>>team tools. I must admit, I was expecting an extension point at that
>>>place. I have been unable to
>>>find such a point. I have been able to add my own menu item to the team
>>>menu but I would much
>>>prefer to be attached after a successful commit.
>>>
>>>My question is this:
>>>Have I missed a better extension point or does one not exist? If so,
>>>what is it? If not, I would like
>>>to make one. How is the best way to proceed with that?
>>>
>>>Jeff
>>>
>>>
>>>
>
|
|
|
| Re: Attaching to CVS commit [message #169811 is a reply to message #169795] |
Fri, 12 December 2003 17:53 |
| Eclipse User |
|
|
|
OK,
I'll join up at those two and poke around. And add my two cents worth!
Jeff
Michael Valenta wrote:
> There are already several requests for related features. Some bugs with
> similar requests are 26634, 24882, 40623). Unfortunately, the bigger
> issue is that the CVS plugin has no API. Also, having a CVS specific API
> is not as much of a priority as having a general Team API. There have
> been discussions about the possibility of including a general Team API
> in 3.0 but the discussion is still ongoing. The platform-team-dev and
> platform-cvs-dev mailing lists are probably the best place to discuss
> this further.
> Michael
> Jeff McKenna wrote:
> > Hum,
> > I am new to this process. How should I proceed? Do I join the CVS
> > 'group' and make the change?
> > Or do I submit a request? Or do I 'patch' things somehow? (I miss
> > extensions from ENVY and
> > Visual Age for Smalltalk!)
> > Any recommendations?
> > Thanks a bunch.
> > Jeff
> >
> > Michael Valenta wrote:
> >
> >
> >>There is currently no API that supports post commit event notification
> >>and there is no plan in 3.0 to support one.
> >>
> >
> >>Michael
> >>
> >
> >>Jeff McKenna wrote:
> >>
> >
> >>>Folks,
> >>>
> >>>I am developing a plug in that would be best stimulated by a successful
> >>>CVS commit from the
> >>>team tools. I must admit, I was expecting an extension point at that
> >>>place. I have been unable to
> >>>find such a point. I have been able to add my own menu item to the team
> >>>menu but I would much
> >>>prefer to be attached after a successful commit.
> >>>
> >>>My question is this:
> >>>Have I missed a better extension point or does one not exist? If so,
> >>>what is it? If not, I would like
> >>>to make one. How is the best way to proceed with that?
> >>>
> >>>Jeff
> >>>
> >>>
> >>>
> >
|
|
|
Powered by
FUDForum. Page generated in 0.03546 seconds
] 
Search
Help
Register
Login
Home
