Simply installing the bundle directly and catching errors is what I was thinking of doing. If I did that, what would be the best way to disable FileInstall from scanning for JARs entirely?
As for implementing a feature - what would that entail? Making each JAR a feature isn't an option - we don't control all the JARs built for Cytoscape ourselves. The ArtifactTransformer sounds like it may be promising (and perhaps simpler than loading everything ourselves) - does someone have an example of this? FileInstall doesn't provide much in the way of documentation... -- View this message in context: http://karaf.922171.n3.nabble.com/Capturing-bundle-load-errors-tp4039419p4039434.html Sent from the Karaf - User mailing list archive at Nabble.com.
