[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-4056) cooperation with mylyn?

[arne anka (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-4056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12459592#action_12459592 ] 

arne anka commented on JBIDE-4056:
----------------------------------

well, mylyn seems to be the only sensible thing to distinguish between open projects that are "active" (ie actively being worked on) and "inactive". 
but i absolutely do not insist on mylyn -- if you get a better idea.

i append the metadata of my two projects, "seamproj" is the jboss seam project, "nonseamproj" the other one. nonseamproj only got .project and .classpath.

> cooperation with mylyn?
> -----------------------
>
>                 Key: JBIDE-4056
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-4056
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>    Affects Versions: 3.0.0.GA
>            Reporter: arne anka
>            Priority: Minor
>         Attachments: jboss.png, jbossbug.zip
>
>
> i work on two projects alternately, one is a jboss seam project (say, A), one is totally unrelated (say, B).
> both projects are, in eclipse terms, always open. i swotch between them by using mylyn and working sets.
> the last week i worked on B and frequently experienced rather heavy resource usage because jboss tools did some operations, which were unnecessary because nothing changed in in A.
> looking into the progress view there was an entry about building workspace, "invoking JProject ARchives Builder on A", "System: Jboss Tools Update" (see attached screenshot).
> i don't know, if there's a more intelligent way, but maybe jboss tools could try to detect if the project is part of the mylyn task currently active and if not, stop any activity?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira