Open ops4j-issues opened 12 years ago
Achim Nierbeck commented
I'm gonna take care of it, cause in Pax-Web there are usecases for using this also in different places ...
Achim Nierbeck commented
Is the method you depend on right now this one?
https://github.com/ops4j/org.ops4j.pax.web/blob/master/pax-web-api/src/main/java/org/ops4j/pax/web/utils/ClassPathUtil.java#L55
If so, yes this makes absolute sense to move it to Swissbox...
Tuomas Kiviaho created PAXSB-59
Swissbox BundleUtils could have one static method for translating Bundle-Classpath to URLs. This functionality already exists at pax-web-jsp/src/main/java/org/ops4j/pax/web/jsp/internal/JasperClassLoader.java but using of it requires an inconvenient dependency to pax-web-jsp an on top of that a classloader needs to be created and immediately discarded.
This feature is needed for projects like RestEASY that require classpath scanning and I'm unaware of an alternative approach.
Fixed in: 1.9.0 Votes: 0, Watches: 0