[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[mylyn-integrators] Re: [Subclipse-dev] Mylyn Integration with History view
|
Mark,
Remote repositories will work if corresponding connector were able to
recognize pattern for given task. For example, try to open
http://jira-dashboard.tigris.org/svn/jira-dashboard/trunk/org.tigris.jira.ui
in the History view and add make sure that
http://developer.atlassian.com/jira JIRA repository is registered in Mylyn.
Never the less, I do see that current workflow can be improved for the
case when Mylyn can't find matching tasks. For example, allow user to
select task repository and then try the task matching using selected
repository.
I don't think we can prototype such repository selection in Subclipse
integration without any changes in Mylyn API because there is a watch
dog in Mylyn that literally kills any repository link provider that
takes more then 5 seconds to execute (even for the first time), because
those call can came from hyperlink detectors activated in text editors
with Ctrl modifier (e.g. Ctrl-C will acticate them too). So we can't
actually have any UI interaction right now. See bug 213085.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=213085
I am CCing Mylyn integrators mailing list in case if someone have
other comments on that.
The only option for Subclipse would be to maintain mapping between
task repositories and SVN repositories like you suggested (or maybe even
per-url mapping). But I am not sure where we can store such mapping. Do
you have any ideas on that?
BTW, it seem like History view for remote repository don't populate
the bugs column...
regards,
Eugene
Mark Phippard wrote:
This question is most likely directed to Eugene.
Can you think of good ways to enable the Mylyn integration when the
History view is showing a remote resource, as opposed to local? I
think without the local resource it does not currently "find" the
linkage. In this particular case, I am starting the process with a
local resource so I could potentially give some information to the
view that it uses to hook-up the integration automatically.
In other cases where we do not have this, could there be an option
that prompted you to select the Task Repository on the fly, and then
figured out the associated task in the log and opened it? Or maybe we
could store some local association between an SVN repository and Task
repository that we fallback to when using the remote view?
