[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [mylar-dev] inducing interest on resources
|
Mik Kersten wrote:
Sorry for the slow reply on this, I've been focusing on the multiple
repository support.
Cool! Is there new dev build available?
By the way, are you finalized extension points? I guess Brock is
going to work on basic Jira integration, but I'd like to try some
other providers, e.g. email or rss.
That sounds like a great work-around and addresses the
case of newly checked out projects, which is the only problematic one that I
have noticed. I'm adding your suggestion to the report.
I am observing this issue when picking up new changes from the Sync
view that has global scope. So, changed resources added to the task
scope (not sure if all of them are added though).
Actually it may be also necessary to add these updated resources
into non-active mylar tasks that include updated projects.
regards,
Eugene
-----Original Message-----
From: mylar-dev-bounces@xxxxxxxxxxx [mailto:mylar-dev-bounces@xxxxxxxxxxx]
On Behalf Of Eugene Kuleshov
Sent: January 6, 2006 9:09 PM
To: Mylar developer discussions
Subject: Re: [mylar-dev] inducing interest on resources
Any thoughts or updates on this?
regards,
Eugene
Eugene Kuleshov wrote:
Mik,
I think it would be more natural to verify if newly added or modified
resources actually reside within one of the projects that already have
other interesting resources for currently active task.
This way you will also cover situation when user checkout new changes
for noninteresting project with automatic build enabled and Eclipse run
Ant builder registred for that project which could create new resources
(I saw this for Eclipse jdt projects)...
regards,
Eugene
Mik Kersten wrote:
There was a discussion some time back about inducing interest on newly
created resources: https://bugs.eclipse.org/bugs/show_bug.cgi?id=117352
This has been working for a while, and ensures that newly created,
copied,
and otherwise added resources become interesting. That has been
working
well, but there is an interesting side effect that was reported by
Alexander Staubo. If you open a project or check out a project while
a task
is active, every resource in the project will be added to the
context. The
work-around is obvious, but as Alexander suggests that the right
solution is
for Mylar to detect this interaction sequence and ignore resource
additions
immediately after a Check Out or Open Project command. That's
possible, but
will require additional support in the context model for using
sequences to
determine intention (currently only individual interaction events do
so).
If you have any comments or similar use cases please consider adding
them
here:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=120499
Mik