One thing we like about the svn property approach is that it is shared
between developers and that our CM administrator can control this on the
subversion end so all developers are forced to enter isue ids in their
commits to those projects requiring it in the eye of the CM team.
Frank
Mark Phippard <markphip@gmail.com>
11/27/2006 03:21 PM
Please respond to
dev@subclipse.tigris.org
To
dev@subclipse.tigris.org
cc
Mylar developer discussions <mylar-dev@eclipse.org>, Michael Valenta
<Michael_Valenta@ca.ibm.com>
Subject
Re: [Subclipse-dev] PATCH: new extension point for issue tracking
integration
Eugene Kuleshov wrote:
>
> Cross posting to Mylar's dev list.
>
> I actually think that this dialog, API and extension points belongs
> to the Eclipse's Platform Team component.
> Ideally we should have some kind of abstract class available to all
> interested parties and that class should take care of the list of
> resources for commit. However comment area and additional stuff that
> specific to issue tracking systems should be pluggable. So, 3rd party
> plugins can register and provide their own implementation.
> This can be of course implemented in Mylar, but I think that not
> everybody would want dependency on Mylar components. Michael can
> correct me, but I am not sure if there is an enhancement request for
> Eclipse. Though I recall there is a request to make commit an API.
I am not sure if a common commit dialog would be of that great of
benefit. I suppose it would depend on how many cool additions it could
have. Such as issue tracking integration, and maybe integrated compare
view? But as an example, there are some bits of essential SVN-specific
info we show for the files that I would not want to give up. That means
we have to supply that piece of the UI, at which point what is the
common dialog still providing us?
Main benefits would be if the extension points could provide instant
integration.
> I also think that using bugtraq:type property in Subclipse may not
> be flexible enough. For instance it will be a duplication of the same
> info that Mylar or Maven already have. Note that Mylar already can
> link issue tracking repositories to Eclipse projects (though that may
> not work for remote resources yet) and that link can be made
> extendable to actually pull that info from Maven's metadata (pom.xml).
I assume if we integrate with a Mylar extension point we would not need
any SVN properties. It would just recognize and use the Mylar config.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: dev-help@subclipse.tigris.org
-----------------------------------------
This e-mail and any attachments are intended only for the
individual or company to which it is addressed and may contain
information which is privileged, confidential and prohibited from
disclosure or unauthorized use under applicable law. If you are
not the intended recipient of this e-mail, you are hereby notified
that any use, dissemination, or copying of this e-mail or the
information contained in this e-mail is strictly prohibited by the
sender. If you have received this transmission in error, please
return the material received to the sender and delete all copies
from your system.
Received on Mon Nov 27 23:10:22 2006