Community
Participate
Working Groups
With bug 296082 resolved, we should go ahead and provide a psf for the mylyn projects. Steffen, I wonder how to slice the psfs for the different projects. I could imagine to have one of the "classic" mylyn part (eg. tasks, context, connectors, bridges) and then one for each subproject (builds, reviews, versions).
Are you going to maintain the PSF files :)? More seriously, is there support for generating these from a git repository? In the past it was quite a bit of overhead to keep PSF files up to date. I think we should consider a separate PSF for each project (targeted at contributors) and an aggregate that has all projects (targeted at committers).
Can have a look at this while testing the psf support.
(In reply to comment #1) > is there support for generating these from a git repository? I don't think there is. You should be able to do this with a simple script. > In the past it was quite a bit of overhead to keep PSF files up to date. I'm afraid it hasn't changed since. The good news is that you can now select a plug-in from you running platform and do Import As > Project from a Repository. This is an overkill if you want to setup a dev env like this. > a separate PSF for each project (targeted at contributors) I don't see much value in this. To be honest, I wouldn't bother importing a psf file if I had an option to simply clone a repo with all the projects I need. OTOH, an aggregate with working sets defined sounds handy to me.
Moving to backlog as cloning works well enough.
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
