ClasspathCrawler doesn't work in OSGi
The current ClasspathCrawler doesn't work when Orekit is deployed in an OSGi runtime as it uses ClasspathCrawler's ClassLoader (as is evidenced by the two lines: "ClasspathCrawler.class.getClassLoader()") and the Orekit data can't be made available to the Orekit bundle's classpath without modifying the bundle or creating a different bundle for each deploy.
To fix this it would be simple enough to add a constructor that takes a ClassLoader, stores it in a field, and uses that to look up resources. This would enable a bundle with data in it to pass in a ClassLoader that has access to that data. The current constructor would just delegate to the new constructor and pass "ClasspathCrawler.class.getClassLoader()" in.
(from redmine: issue id 54, created on 2011-12-31, closed on 2011-12-31)