Community
Participate
Working Groups
Steps: 1. Add a Maven parent project to the workspace 2. Add Maven module projects to the workspace If a file is added to the context it shows up twice: In the module project as well as the parent project, since the parent project contains all modules.
The work-around is to add a resource filter for the parent project. Not sure if there is anything that can be done in the context framework to support this better out of the box.
The context framework must remember "remove from context" and not repeatedly reincarnate visibility on resources visible trough the parent projects when they gain interest from user activities on them trough child projects. Now that m2e project is part of several Eclipse distributions this issue is becoming severe and makes Mylyn context almost impossible to use with most Maven projects.
Created attachment 275758 [details] screenshot I'm not sure whether I do address this correctly, but looking up the bug database, this existing bug report seems the closed I could find ... While working with Maven projects, provided screenshot depicts what happens when we open a Java source file, when it gets added to the 'Task-focused View'. 1) The focused project's parent project also gets added to the 'Task-focused View' context, even though the focused (child) project is marked as a 'derived' resource.(We regard this as minor.) 2) The focused project's 'src' folder gets displayed twice. Which currently prevents me from using the 'Task-focused View', due too much visual clutter. I'm using Mylyn for some months now, it otherwise is doing great. Cheers, Andi!
Mylyn has been restructured, and our issue tracking has moved to GitHub [1]. We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub. [1] https://github.com/orgs/eclipse-mylyn
