|
#2 - we can actually see what jars import/use the annotation?
#3 - yes. #2 yes, just run a query with those Java XXX-Level Annotations. The quirk we briefly touched on before was the awkward query clause (natural would be IN, but smth else had to be used). freeform would give more options, of course
#3 that's a major enhancement (just think that this is exactly what IDEA/Eclipse do), but with our ASM infrastructure already integrated in Galaxy should be possible. Other classes can be detected via imports analysis, the trick is the 'same-package' classes, will have to bounce some ideas here. it will be quite an intensive operation, but we can easily detect when it has to be done (e.g. on new version upload only), so the risk can be controlled. |
||||||||||||||||||||||||||||||||||||||||||||||||||
1 will have to be implemented
2 is almost possible today (search for a class and also for a class annotation). unless there is a queryable way to store complex graphs, I don't see how we could combine class+annotation search)
3 do you mean jars with depend on the class? (not ones containing it?)