Community
Participate
Working Groups
I suppose it would be up to the JDT/PDE to contribute a resource provider, but first that would have to be an option. Currently I can open a *.js file (from a target bundle's jar) by finding it in the package explorer, navigating to plugin dependencies, finding the jar, and expanding until I get to the .js file I want to open. This is very cumbersome. There needs to be an easier way to open that resource that doesn't require importing into my workspace.
This bug is about 'Open Resource' to provide an extension, so that files inside archives can be found too.
It would be strange to have only Open Resource work for Jars, but not Search, etc. See also bug 23341 and bug 23265.
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.