Eclipse Community Forums: Buckminster » team --> commit integration

Help

Home

Home » Archived » Buckminster » team --> commit integration

Show: Today's Messages :: Show Polls :: Message Navigator

team --> commit integration [message #531963]

Thu, 06 May 2010 15:28

arve

Messages: 5
Registered: May 2010

Junior Member

No Message Body

[Updated on: Thu, 06 May 2010 15:29]

Report message to a moderator

Re: team --> commit integration [message #532049 is a reply to message #531963]

Thu, 06 May 2010 22:04

Henrik Lindberg

Messages: 2509
Registered: July 2009

Senior Member

Afaik (but I am no expert) there is little in common between the ui's
for different scm technologies. You would have to implement a part that
is specific to each. How easy this is depends in the respective
implementations (if the have hooks for 'pre-commit' asserts etc. If not
you may be required to use aop to weave ligic into the implementations
in inorder to get the logic into the rught place. You would also need to
concider hooking your functionality on 'push' rather than commit for
git.

Alternatively, you could try replacing the commit commands provided by
each impl and delegate from your own asserting impl. How well this will
work depends again on how each technology calls the underlying commit
(there are several places this can be done by a user- one is in the sync
view).

There is a new mylyn project dealing with SCMs, maybe the functionality
you are interested in is/should be part of that project.

Regards
- henrik

arve <arunvenkatesh.v@hotmail.com> wrote:
> We are trying to write a plug-in that will run a quality tool every
> time users tries to commit using "Right Click -->team --> Project" and
> depending on the quality tool score allow/disallow to commit.
>
> The requirements are that the plug-in should be independent of the SCM
> (svn,cvs,clearcase)and the corresponding eclipse (subclipse
> subversive, cvs, clearcase)plug-in. But for Team --> commit seem not
> have have extension point for commit action.
>
> The actual commit action of the subclipse SVN plugin uses the generic
> extension point 'org.eclipse.ui.popupMenus' and extends
> WorkbenchWindowAction
>
> Is there any possibility of extending / implementing hooks in
> org.eclipse.team.ui to implement the same.??
> Is there any possibility of writing filters for the Workbench actions
> to filter out the commit action.??
> Is it possible to borrow some concepts from usage data collector?
>

--
- henrik

Report message to a moderator

Re: team --> commit integration [message #532111 is a reply to message #531963]

Fri, 07 May 2010 08:17

Johannes Utzig

Messages: 329
Registered: July 2009

Senior Member

Hi,

>
> The actual commit action of the subclipse SVN plugin uses the generic
> extension point 'org.eclipse.ui.popupMenus' and extends
> WorkbenchWindowAction
>

Actually I wrote my own team provider just a few months ago and there
definetly is no notion of a standard commit action in eclipse that a
team provider could reuse, so it's all just generic popup menus for all
the team providers.

> Is there any possibility of extending / implementing hooks in
> org.eclipse.team.ui to implement the same.??

Not to my knowledge

> Is there any possibility of writing filters for the Workbench actions to
> filter out the commit action.??

You can use activities/capabilities to filter out actions, but you'd
have to do it for all team providers seperatly since all their actions
will have different IDs.

Best regards,
Johannes

Report message to a moderator

Previous Topic:	internalization build
Next Topic:	create.product action not finding the IU

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 18 07:10:08 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter