Community
Participate
Working Groups
In my workflow, I always have the whole Platform code loaded in the workspace, with the "root" Git repositories as top-level elements and projects as children (I'm using hierachical view). I usually remove all the projects I'm not working on, so I can see the files, but they are not processed by the IDE as .java files nor as plugin projects. That makes me more efficient as it remove noise and improve perfs. Because of this workflow, I often have to reopen a dependency chain. I often see "Bundle x.y.z cannot be resolved" in MANIFEST and have to dig in my workspace and import the project x.y.z in the workspace so it's visible as a plugin. I would love to get a quick fix doing it for me, something like "Locate and import project in workspace" that would look in the MANIFEST.MF or .project for a folder that contains that bundle as a project and that would import and open it in my IDE.
*** Bug 559836 has been marked as a duplicate of this bug. ***
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
Still relevant.
In Import plugin and fragments, there is an option "Import plugins and fragments required by existing workspace plugins". Will that not work for your use case?
(In reply to Vikas Chandra from comment #4) > In Import plugin and fragments, there is an option "Import plugins and > fragments required by existing workspace plugins". > > Will that not work for your use case? I almost always stick to textual view of the manifest, what I'd like to see here is that such option would be provided a quickfix on MANIFEST.MF when it can help.
(In reply to Mickael Istria from comment #5) > (In reply to Vikas Chandra from comment #4) > > In Import plugin and fragments, there is an option "Import plugins and > > fragments required by existing workspace plugins". > > > > Will that not work for your use case? > > I almost always stick to textual view of the manifest, what I'd like to see > here is that such option would be provided a quickfix on MANIFEST.MF when it > can help. So will a quickfix opening "Import plugin and fragments" wizard with the relevant option selected work for you?
(In reply to Vikas Chandra from comment #6) > So will a quickfix opening "Import plugin and fragments" wizard with the > relevant option selected work for you? Yes, I think it would be already a great improvement.
