Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Mylyn » Mylyn context incorrect after source code branch is merged.
Mylyn context incorrect after source code branch is merged. [message #53116] Thu, 17 July 2008 20:53 Go to next message
Jeff Grimshaw is currently offline Jeff GrimshawFriend
Messages: 4
Registered: July 2009
Junior Member
We're very interested in using Mylyn, however one concern is how it would
support code that is merged from a branch.

For instance, say we create a Project_A_branch_24 off of Project_A head. In
Eclipse I have both Project_A_branch_24 and Project_A as projects. The
team does a bunch of work on Project_A_branch_24 using Mylyn. This
includes saving the context of the work on bug_2301. In the end we merge
the changes in the branch back into head. Much later someone checks out
Project_A head and wants to know what files were involved with bug_2301.
They access the Mylyn task (via Jira) but all the referenced files are in
Project_A_branch_24.

Is there a way around this?

Thanks,
Jeff
Re: Mylyn context incorrect after source code branch is merged. [message #53216 is a reply to message #53116] Thu, 17 July 2008 21:39 Go to previous messageGo to next message
Steffen Pingel is currently offline Steffen PingelFriend
Messages: 706
Registered: July 2009
Senior Member
This bug has some discussion about the problem where the same project is
shared with different names:

201739: [context] support sharing contexts between developers in spite of
the project being named differently in each workspace
https://bugs.eclipse.org/bugs/show_bug.cgi?id=201739

Jeff, it would be great if you could comment on the bug report and add your
specific use-case and requirements.

Steffen


Jeff Grimshaw wrote:

> We're very interested in using Mylyn, however one concern is how it would
> support code that is merged from a branch.
>
> For instance, say we create a Project_A_branch_24 off of Project_A head.
> In
> Eclipse I have both Project_A_branch_24 and Project_A as projects. The
> team does a bunch of work on Project_A_branch_24 using Mylyn. This
> includes saving the context of the work on bug_2301. In the end we merge
> the changes in the branch back into head. Much later someone checks out
> Project_A head and wants to know what files were involved with bug_2301.
> They access the Mylyn task (via Jira) but all the referenced files are in
> Project_A_branch_24.
>
> Is there a way around this?
>
> Thanks,
> Jeff
Re: Mylyn context incorrect after source code branch is merged. [message #53421 is a reply to message #53216] Fri, 18 July 2008 14:56 Go to previous message
Jeff Grimshaw is currently offline Jeff GrimshawFriend
Messages: 4
Registered: July 2009
Junior Member
Steffen,

Thanks, I've added my two cents to the bug report.

If anyone else needs to move Mylyn task contexts from a project representing
a source code branch to one representing the head I'd encourage you to vote
for this bug.

-- Jeff


"Steffen Pingel" <steffen.pingel@tasktop.com> wrote in message
news:g5oe6j$84g$1@build.eclipse.org...
> This bug has some discussion about the problem where the same project is
> shared with different names:
>
> 201739: [context] support sharing contexts between developers in spite of
> the project being named differently in each workspace
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=201739
>
> Jeff, it would be great if you could comment on the bug report and add
> your
> specific use-case and requirements.
>
> Steffen
>
>
> Jeff Grimshaw wrote:
>
>> We're very interested in using Mylyn, however one concern is how it would
>> support code that is merged from a branch.
>>
>> For instance, say we create a Project_A_branch_24 off of Project_A head.
>> In
>> Eclipse I have both Project_A_branch_24 and Project_A as projects. The
>> team does a bunch of work on Project_A_branch_24 using Mylyn. This
>> includes saving the context of the work on bug_2301. In the end we merge
>> the changes in the branch back into head. Much later someone checks out
>> Project_A head and wants to know what files were involved with bug_2301.
>> They access the Mylyn task (via Jira) but all the referenced files are in
>> Project_A_branch_24.
>>
>> Is there a way around this?
>>
>> Thanks,
>> Jeff
>
Re: Mylyn context incorrect after source code branch is merged. [message #591382 is a reply to message #53116] Thu, 17 July 2008 21:39 Go to previous message
Steffen Pingel is currently offline Steffen PingelFriend
Messages: 706
Registered: July 2009
Senior Member
This bug has some discussion about the problem where the same project is
shared with different names:

201739: [context] support sharing contexts between developers in spite of
the project being named differently in each workspace
https://bugs.eclipse.org/bugs/show_bug.cgi?id=201739

Jeff, it would be great if you could comment on the bug report and add your
specific use-case and requirements.

Steffen


Jeff Grimshaw wrote:

> We're very interested in using Mylyn, however one concern is how it would
> support code that is merged from a branch.
>
> For instance, say we create a Project_A_branch_24 off of Project_A head.
> In
> Eclipse I have both Project_A_branch_24 and Project_A as projects. The
> team does a bunch of work on Project_A_branch_24 using Mylyn. This
> includes saving the context of the work on bug_2301. In the end we merge
> the changes in the branch back into head. Much later someone checks out
> Project_A head and wants to know what files were involved with bug_2301.
> They access the Mylyn task (via Jira) but all the referenced files are in
> Project_A_branch_24.
>
> Is there a way around this?
>
> Thanks,
> Jeff
Re: Mylyn context incorrect after source code branch is merged. [message #591458 is a reply to message #53216] Fri, 18 July 2008 14:56 Go to previous message
Jeff Grimshaw is currently offline Jeff GrimshawFriend
Messages: 4
Registered: July 2009
Junior Member
Steffen,

Thanks, I've added my two cents to the bug report.

If anyone else needs to move Mylyn task contexts from a project representing
a source code branch to one representing the head I'd encourage you to vote
for this bug.

-- Jeff


"Steffen Pingel" <steffen.pingel@tasktop.com> wrote in message
news:g5oe6j$84g$1@build.eclipse.org...
> This bug has some discussion about the problem where the same project is
> shared with different names:
>
> 201739: [context] support sharing contexts between developers in spite of
> the project being named differently in each workspace
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=201739
>
> Jeff, it would be great if you could comment on the bug report and add
> your
> specific use-case and requirements.
>
> Steffen
>
>
> Jeff Grimshaw wrote:
>
>> We're very interested in using Mylyn, however one concern is how it would
>> support code that is merged from a branch.
>>
>> For instance, say we create a Project_A_branch_24 off of Project_A head.
>> In
>> Eclipse I have both Project_A_branch_24 and Project_A as projects. The
>> team does a bunch of work on Project_A_branch_24 using Mylyn. This
>> includes saving the context of the work on bug_2301. In the end we merge
>> the changes in the branch back into head. Much later someone checks out
>> Project_A head and wants to know what files were involved with bug_2301.
>> They access the Mylyn task (via Jira) but all the referenced files are in
>> Project_A_branch_24.
>>
>> Is there a way around this?
>>
>> Thanks,
>> Jeff
>
Previous Topic:Problem with 3.0.1 update
Next Topic:Mylyn 3.0.1 is now available
Goto Forum:
  


Current Time: Mon Dec 30 16:32:08 GMT 2024

Powered by FUDForum. Page generated in 0.06822 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top