| Sharing contexts between developers [message #23568] |
Thu, 23 August 2007 12:53  |
Eclipse User |
|
|
|
Let's say we have 2 developers. One has checked out source code from a
repository under the project name 'myproject' and the other checks the
SAME source under a different project name 'hisproject'.
How do we share contexts between the two? Below the project name,
everything else is the same. However, in the context itself I can see
where the project name is part of a context path, thus keeping either of
these 2 developers sharing it. I've made a little mini test and my
suspicion is correct.
Is this a known issue or am I attempting to use something the way it
shouldn't be? Is there an easy workaround? Telling all developers to
name their projects the same way won't work as I have a hard enough time
telling them to use something other than vi to do their work with :)
Thanks all,
Eric
|
|
|
|
| Re: Sharing contexts between developers [message #24114 is a reply to message #23693] |
Mon, 27 August 2007 02:22  |
| Eclipse User |
|
|
|
Originally posted by: beatmik.acm.org
While I wish I could simply ask you to convince all Eclipse users to use
the same project names, it makes sense that this is not feasible in some
scenarios. Please file a bug explaining your situation.
Adding support for this will not be straightforward, because Mylyn
necessarily needs to include the project's name in identifying the
identity of elements in the task context. However, in the 3.0 cycle we
will be doing related work on refactoring contexts and may be able to
include support for this kind of manual mapping.
Mik
BigEHokie wrote:
> RTFM
>
> http://wiki.eclipse.org/index.php/Mylyn_FAQ#Why_is_interest_ lost_when_I_retrieve_someone_else.27s_context.3F
>
>
> That would answer my question. This is rather tough to get a bunch of
> developers (most who don't use Eclipse now as is) to accept using
> Eclipse AND require we all name our projects the same way (we have
> hundreds of projects).
>
> Does anyone else have any experience in dealing with this issue?
> Pointers you can provide?
|
|
|
| Re: Sharing contexts between developers [message #578234 is a reply to message #23568] |
Fri, 24 August 2007 12:38 |
| Eclipse User |
|
|
|
RTFM
http://wiki.eclipse.org/index.php/Mylyn_FAQ#Why_is_interest_ lost_when_I_retrieve_someone_else.27s_context.3F
That would answer my question. This is rather tough to get a bunch of
developers (most who don't use Eclipse now as is) to accept using
Eclipse AND require we all name our projects the same way (we have
hundreds of projects).
Does anyone else have any experience in dealing with this issue?
Pointers you can provide?
Thanks!
Eric
BigEHokie wrote:
> Let's say we have 2 developers. One has checked out source code from a
> repository under the project name 'myproject' and the other checks the
> SAME source under a different project name 'hisproject'.
>
> How do we share contexts between the two? Below the project name,
> everything else is the same. However, in the context itself I can see
> where the project name is part of a context path, thus keeping either of
> these 2 developers sharing it. I've made a little mini test and my
> suspicion is correct.
>
> Is this a known issue or am I attempting to use something the way it
> shouldn't be? Is there an easy workaround? Telling all developers to
> name their projects the same way won't work as I have a hard enough time
> telling them to use something other than vi to do their work with :)
>
> Thanks all,
> Eric
|
|
|
| Re: Sharing contexts between developers [message #578421 is a reply to message #23693] |
Mon, 27 August 2007 02:22 |
| Eclipse User |
|
|
|
While I wish I could simply ask you to convince all Eclipse users to use
the same project names, it makes sense that this is not feasible in some
scenarios. Please file a bug explaining your situation.
Adding support for this will not be straightforward, because Mylyn
necessarily needs to include the project's name in identifying the
identity of elements in the task context. However, in the 3.0 cycle we
will be doing related work on refactoring contexts and may be able to
include support for this kind of manual mapping.
Mik
BigEHokie wrote:
> RTFM
>
> http://wiki.eclipse.org/index.php/Mylyn_FAQ#Why_is_interest_ lost_when_I_retrieve_someone_else.27s_context.3F
>
>
> That would answer my question. This is rather tough to get a bunch of
> developers (most who don't use Eclipse now as is) to accept using
> Eclipse AND require we all name our projects the same way (we have
> hundreds of projects).
>
> Does anyone else have any experience in dealing with this issue?
> Pointers you can provide?
|
|
|
Powered by
FUDForum. Page generated in 0.03435 seconds
Home