-
Notifications
You must be signed in to change notification settings - Fork 121
Use Bundle#getResources to discover embedded SPI resources #2137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
iloveeclipse
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
@HannesWell : would be nice if you could review that. We should get the fix in RC1. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks reasonable to me.
But due to a recent outage at Github regarding git operations I'm not able to fetch this change to try it locally. But from what I see in the web-UI this is fine.
Thanks for the fix.
I just have two style remarks, that would be nice to have.
...lipse.pde.junit.runtime/src/org/eclipse/pde/internal/junit/runtime/SPIBundleClassLoader.java
Outdated
Show resolved
Hide resolved
ui/org.eclipse.pde.junit.runtime/src/org/eclipse/pde/internal/junit/runtime/SPIMapping.java
Outdated
Show resolved
Hide resolved
Currently we use bundle.getEntry but this has some limitations, e.g. fragments and embedded jars. While the first can be avoided with findEntries, the second can not. As we previously already used bundle.getResources it seems fine to continue using that method.
HannesWell
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the updates.
Still look good to me :)
Currently we use bundle.getEntry but this has some limitations, e.g. fragments and embedded jars.
While the first can be avoided with findEntries, the second can not. As we previously already used bundle.getResources it seems fine to continue using that method.
Fixes #2132