Home » Eclipse Projects » Mylyn » From a task to a list of CVS history enties
| From a task to a list of CVS history enties [message #15781] |
Wed, 18 July 2007 10:42  |
Eclipse User |
|
|
|
Originally posted by: mauro.molinari.cardinis.com
Hello all!
From the CVS history view it is possible to open the task corresponding
to an entry.
But, is there a way to do the opposite, from within Eclipse?
In other words, is there a way, given a task, to get a list of all the
CVS entries corresponding to that task and/or a list of all files with
entries corresponding to that task?
It would be a great feature.
Mauro.
P.S.: Mylyn is brilliant: among the other features, it provides the
necessary glue to link together a programmer's everyday tasks, the CVS
repository, the bug repository and the IDE!!! It is the answer to what
me and my co-workers feeled we missed until some months ago!
|
|
|
| Re: From a task to a list of CVS history enties [message #17394 is a reply to message #15781] |
Thu, 19 July 2007 19:17  |
| Eclipse User |
|
|
|
Originally posted by: beatmik.acm.org
Thanks for the kind words Mauro. That's exactly what we're trying to
provide: an implicitly linking of the tasks that you work on with the
resources that are involved with those tasks.
Could you please elaborate on the use case that you're after? For
example, if your use cases is to see what all the files that were
modified before committing we simply rely on the Synchronize view's
grouping of outgoing changes with task contexts. However, the Context
tab on the task editor could be used to display additional information
about the state of the task context.
Mik
Mauro Molinari wrote:
> Hello all!
> From the CVS history view it is possible to open the task corresponding
> to an entry.
> But, is there a way to do the opposite, from within Eclipse?
> In other words, is there a way, given a task, to get a list of all the
> CVS entries corresponding to that task and/or a list of all files with
> entries corresponding to that task?
>
> It would be a great feature.
>
> Mauro.
>
> P.S.: Mylyn is brilliant: among the other features, it provides the
> necessary glue to link together a programmer's everyday tasks, the CVS
> repository, the bug repository and the IDE!!! It is the answer to what
> me and my co-workers feeled we missed until some months ago!
|
|
|
| Re: From a task to a list of CVS history enties [message #17435 is a reply to message #17394] |
Fri, 20 July 2007 07:33 |
| Eclipse User |
|
|
|
Originally posted by: mauro.molinari.cardinis.com
Mik Kersten ha scritto:
> Could you please elaborate on the use case that you're after? For
> example, if your use cases is to see what all the files that were
> modified before committing we simply rely on the Synchronize view's
> grouping of outgoing changes with task contexts. However, the Context
> tab on the task editor could be used to display additional information
> about the state of the task context.
>
> Mik
Suppose Mik you worked on a task and you completed it. While working on
this task, you changed some files and you committed them to CVS
repository, keeping the commit template that Mylyn suggests.
Then, one month later you are going to pick that completed task up
again, because, for instance, you need to port the corresponding
modifications to another branch of your project. You can't remember ALL
the files you modified while performing that task, so you ask Mylyn for
help :-)
The point is this: if Mylyn could remember all the resources you
modified (and is is related to bug #175765, in some way... see my
comment #8) while working on a task, you would be at a good starting
point. Then, if Mylyn could also query the CVS repository on those
files, it could highlight the exact revisions of those files that were
committed while working on that task.
Once you have this list, you could procceed with your work of porting to
the new branch, using Eclipse built-in functions (annotations, compare,
patch and so on).
As far as I know, the only way to achieve a similar result would be to
launch a cvslog and then grep on the commit message template. But this
isn't so much integrated in the IDE and you have to cope with a lot of
overhead activities (i.e.: find the resource, query the CVS history,
locate the correct revision... and this for every modified resource!!).
Other use cases I can think of are: reports on bugfixes, statistics,
knowledge sharing between team members (i.e.: "how X solved this bug?",
"which classes where involved in the implementation of that
functionality?"...), etc..
I think this feature would complete the circle of integration that Mylyn
provides for the development workflow and that we're talking about.
Mauro.
|
|
|
| Re: From a task to a list of CVS history enties [message #19223 is a reply to message #17435] |
Thu, 26 July 2007 01:13 |
| Eclipse User |
|
|
|
Originally posted by: beatmik.acm.org
Hi Mauro,
As you know we already have the following bug:
175765: Add commit comment template variable for modified files
https://bugs.eclipse.org/bugs/show_bug.cgi?id=175765
This is one approach to storing the information in a more accessible
way. Note that this is something we hope to see contributed since it
would be straightforward to add and is currently low priority in terms
of 3.0 planning.
However, what you are suggesting is a more generic facility which would
allow you to navigate from a task to a set of changes. Part of the
issue here is that given our current scope we rely on such information
coming from the issue tracker, and as you indicate it is not explicit in
CVS and would need to be parsed out. But your use cases below are
clear, so please create a new bug report so that we can consider
further. Also mention the way that you would want the UI to work.
Firexample, you might want to navigate from a comment in the task to the
corresponding changes, since a task can be involved in many commits.
Mik
Mauro Molinari wrote:
> Suppose Mik you worked on a task and you completed it. While working on
> this task, you changed some files and you committed them to CVS
> repository, keeping the commit template that Mylyn suggests.
>
> Then, one month later you are going to pick that completed task up
> again, because, for instance, you need to port the corresponding
> modifications to another branch of your project. You can't remember ALL
> the files you modified while performing that task, so you ask Mylyn for
> help :-)
>
> The point is this: if Mylyn could remember all the resources you
> modified (and is is related to bug #175765, in some way... see my
> comment #8) while working on a task, you would be at a good starting
> point. Then, if Mylyn could also query the CVS repository on those
> files, it could highlight the exact revisions of those files that were
> committed while working on that task.
>
> Once you have this list, you could procceed with your work of porting to
> the new branch, using Eclipse built-in functions (annotations, compare,
> patch and so on).
>
> As far as I know, the only way to achieve a similar result would be to
> launch a cvslog and then grep on the commit message template. But this
> isn't so much integrated in the IDE and you have to cope with a lot of
> overhead activities (i.e.: find the resource, query the CVS history,
> locate the correct revision... and this for every modified resource!!).
>
> Other use cases I can think of are: reports on bugfixes, statistics,
> knowledge sharing between team members (i.e.: "how X solved this bug?",
> "which classes where involved in the implementation of that
> functionality?"...), etc..
>
> I think this feature would complete the circle of integration that Mylyn
> provides for the development workflow and that we're talking about.
>
> Mauro.
|
|
|
| Re: From a task to a list of CVS history enties [message #19528 is a reply to message #19223] |
Thu, 26 July 2007 07:45 |
| Eclipse User |
|
|
|
Originally posted by: mauro.molinari.cardinis.com
Mik Kersten ha scritto:
> This is one approach to storing the information in a more accessible
> way. Note that this is something we hope to see contributed since it
> would be straightforward to add and is currently low priority in terms
> of 3.0 planning.
Just for my curiosity, is there a webpage reporting wanted new
features/enhancements for Mylyn 3.0?
Sorry if I should know the answer...
> However, what you are suggesting is a more generic facility which would
> allow you to navigate from a task to a set of changes. Part of the
> issue here is that given our current scope we rely on such information
> coming from the issue tracker, and as you indicate it is not explicit in
> CVS and would need to be parsed out. But your use cases below are
> clear, so please create a new bug report so that we can consider
> further. Also mention the way that you would want the UI to work.
> Firexample, you might want to navigate from a comment in the task to the
> corresponding changes, since a task can be involved in many commits.
Well, your last example sounds very interesting, because it assumes
there's a link between task comments and change sets/commit operations.
But for now it would be enough if Mylyn could enforce the link between
tasks and change sets/commit operations (if there have been more commit
operations, it would be surely acceptable, as a first step, to get the
list of all commits, even if made in different times).
Thanks again. By the way, I created bug #197924
https://bugs.eclipse.org/bugs/show_bug.cgi?id=197924
Mauro.
|
|
|
| Re: From a task to a list of CVS history enties [message #25865 is a reply to message #19528] |
Thu, 06 September 2007 21:28 |
| Eclipse User |
|
|
|
Originally posted by: beatmik.acm.org
Mauro Molinari wrote:
> Mik Kersten ha scritto:
>> This is one approach to storing the information in a more accessible
>> way. Note that this is something we hope to see contributed since it
>> would be straightforward to add and is currently low priority in terms
>> of 3.0 planning.
>
> Just for my curiosity, is there a webpage reporting wanted new
> features/enhancements for Mylyn 3.0?
The plan is evolving here (linked from the Mylyn homepage's navigation
bar). Note that will be iterating on it considerably over the next few
days.
http://wiki.eclipse.org/index.php/Mylyn_3.0_Plan
To be notified of updates add yourself as a Cc to:
200628: plan Mylyn 3.0 release cycle
https://bugs.eclipse.org/bugs/show_bug.cgi?id=200628
Mik
|
|
|
| Re: From a task to a list of CVS history enties [message #573671 is a reply to message #15781] |
Thu, 19 July 2007 19:17 |
 Mik Kersten
Messages: 287
Registered: July 2009 |
Senior Member |
|
|
Thanks for the kind words Mauro. That's exactly what we're trying to
provide: an implicitly linking of the tasks that you work on with the
resources that are involved with those tasks.
Could you please elaborate on the use case that you're after? For
example, if your use cases is to see what all the files that were
modified before committing we simply rely on the Synchronize view's
grouping of outgoing changes with task contexts. However, the Context
tab on the task editor could be used to display additional information
about the state of the task context.
Mik
Mauro Molinari wrote:
> Hello all!
> From the CVS history view it is possible to open the task corresponding
> to an entry.
> But, is there a way to do the opposite, from within Eclipse?
> In other words, is there a way, given a task, to get a list of all the
> CVS entries corresponding to that task and/or a list of all files with
> entries corresponding to that task?
>
> It would be a great feature.
>
> Mauro.
>
> P.S.: Mylyn is brilliant: among the other features, it provides the
> necessary glue to link together a programmer's everyday tasks, the CVS
> repository, the bug repository and the IDE!!! It is the answer to what
> me and my co-workers feeled we missed until some months ago!
|
|
|
| Re: From a task to a list of CVS history enties [message #574068 is a reply to message #17394] |
Fri, 20 July 2007 07:33 |
Mauro Molinari
Messages: 285
Registered: July 2009 |
Senior Member |
|
|
Mik Kersten ha scritto:
> Could you please elaborate on the use case that you're after? For
> example, if your use cases is to see what all the files that were
> modified before committing we simply rely on the Synchronize view's
> grouping of outgoing changes with task contexts. However, the Context
> tab on the task editor could be used to display additional information
> about the state of the task context.
>
> Mik
Suppose Mik you worked on a task and you completed it. While working on
this task, you changed some files and you committed them to CVS
repository, keeping the commit template that Mylyn suggests.
Then, one month later you are going to pick that completed task up
again, because, for instance, you need to port the corresponding
modifications to another branch of your project. You can't remember ALL
the files you modified while performing that task, so you ask Mylyn for
help :-)
The point is this: if Mylyn could remember all the resources you
modified (and is is related to bug #175765, in some way... see my
comment #8) while working on a task, you would be at a good starting
point. Then, if Mylyn could also query the CVS repository on those
files, it could highlight the exact revisions of those files that were
committed while working on that task.
Once you have this list, you could procceed with your work of porting to
the new branch, using Eclipse built-in functions (annotations, compare,
patch and so on).
As far as I know, the only way to achieve a similar result would be to
launch a cvslog and then grep on the commit message template. But this
isn't so much integrated in the IDE and you have to cope with a lot of
overhead activities (i.e.: find the resource, query the CVS history,
locate the correct revision... and this for every modified resource!!).
Other use cases I can think of are: reports on bugfixes, statistics,
knowledge sharing between team members (i.e.: "how X solved this bug?",
"which classes where involved in the implementation of that
functionality?"...), etc..
I think this feature would complete the circle of integration that Mylyn
provides for the development workflow and that we're talking about.
Mauro.
|
|
|
| Re: From a task to a list of CVS history enties [message #575224 is a reply to message #17435] |
Thu, 26 July 2007 01:13 |
Mik Kersten
Messages: 287
Registered: July 2009 |
Senior Member |
|
|
Hi Mauro,
As you know we already have the following bug:
175765: Add commit comment template variable for modified files
https://bugs.eclipse.org/bugs/show_bug.cgi?id=175765
This is one approach to storing the information in a more accessible
way. Note that this is something we hope to see contributed since it
would be straightforward to add and is currently low priority in terms
of 3.0 planning.
However, what you are suggesting is a more generic facility which would
allow you to navigate from a task to a set of changes. Part of the
issue here is that given our current scope we rely on such information
coming from the issue tracker, and as you indicate it is not explicit in
CVS and would need to be parsed out. But your use cases below are
clear, so please create a new bug report so that we can consider
further. Also mention the way that you would want the UI to work.
Firexample, you might want to navigate from a comment in the task to the
corresponding changes, since a task can be involved in many commits.
Mik
Mauro Molinari wrote:
> Suppose Mik you worked on a task and you completed it. While working on
> this task, you changed some files and you committed them to CVS
> repository, keeping the commit template that Mylyn suggests.
>
> Then, one month later you are going to pick that completed task up
> again, because, for instance, you need to port the corresponding
> modifications to another branch of your project. You can't remember ALL
> the files you modified while performing that task, so you ask Mylyn for
> help :-)
>
> The point is this: if Mylyn could remember all the resources you
> modified (and is is related to bug #175765, in some way... see my
> comment #8) while working on a task, you would be at a good starting
> point. Then, if Mylyn could also query the CVS repository on those
> files, it could highlight the exact revisions of those files that were
> committed while working on that task.
>
> Once you have this list, you could procceed with your work of porting to
> the new branch, using Eclipse built-in functions (annotations, compare,
> patch and so on).
>
> As far as I know, the only way to achieve a similar result would be to
> launch a cvslog and then grep on the commit message template. But this
> isn't so much integrated in the IDE and you have to cope with a lot of
> overhead activities (i.e.: find the resource, query the CVS history,
> locate the correct revision... and this for every modified resource!!).
>
> Other use cases I can think of are: reports on bugfixes, statistics,
> knowledge sharing between team members (i.e.: "how X solved this bug?",
> "which classes where involved in the implementation of that
> functionality?"...), etc..
>
> I think this feature would complete the circle of integration that Mylyn
> provides for the development workflow and that we're talking about.
>
> Mauro.
|
|
|
| Re: From a task to a list of CVS history enties [message #575604 is a reply to message #19223] |
Thu, 26 July 2007 07:45 |
Mauro Molinari
Messages: 285
Registered: July 2009 |
Senior Member |
|
|
Mik Kersten ha scritto:
> This is one approach to storing the information in a more accessible
> way. Note that this is something we hope to see contributed since it
> would be straightforward to add and is currently low priority in terms
> of 3.0 planning.
Just for my curiosity, is there a webpage reporting wanted new
features/enhancements for Mylyn 3.0?
Sorry if I should know the answer...
> However, what you are suggesting is a more generic facility which would
> allow you to navigate from a task to a set of changes. Part of the
> issue here is that given our current scope we rely on such information
> coming from the issue tracker, and as you indicate it is not explicit in
> CVS and would need to be parsed out. But your use cases below are
> clear, so please create a new bug report so that we can consider
> further. Also mention the way that you would want the UI to work.
> Firexample, you might want to navigate from a comment in the task to the
> corresponding changes, since a task can be involved in many commits.
Well, your last example sounds very interesting, because it assumes
there's a link between task comments and change sets/commit operations.
But for now it would be enough if Mylyn could enforce the link between
tasks and change sets/commit operations (if there have been more commit
operations, it would be surely acceptable, as a first step, to get the
list of all commits, even if made in different times).
Thanks again. By the way, I created bug #197924
https://bugs.eclipse.org/bugs/show_bug.cgi?id=197924
Mauro.
|
|
| |
Goto Forum:
Current Time: Thu Apr 18 22:52:17 GMT 2024
Powered by FUDForum. Page generated in 0.03015 seconds |
] 
Search
Help
Register
Login
Home
