-
-
Notifications
You must be signed in to change notification settings - Fork 645
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
cider-find-var doesn't work for all java classes #1666
Comments
Likely the source jar is not on the classpath. |
This happened with |
Probably. It likely pulled just the compiled classes, but you also need the source jar for source lookup to work. |
Btw, you shouldn't be getting an error, but some message saying the source can't be found. That's odd... |
I tested this and got a |
Is there a known workaround for this? I have manually built and installed maven project which contains both source and javadoc jars. CIDER cannot locate neither source nor javadoc. |
Just found a rudimentary workaround by manually adding jar files to lein's :resource-paths. |
Guess we can close this then. Unless someone wants to contribute some documentation on the subject? |
I'll have to get up to speed but I can do it tomorrow On Oct 8, 2016 12:25 PM, "Bozhidar Batsov" notifications@github.com wrote:
|
@dpsutton Sounds good. |
I've been trying to figure this out. I've built a project |
I think a larger point is that we haven't documented at all how one can add source jars to their lein/boot project. |
@vspinu I tried adding paths to jars in |
Just that, added full paths to the :resource-paths ["/home/vspinu/.m2/repository/com/interactivebrokers/tws-api/9.71.1/tws-api-9.71.1-sources.jar"
"/home/vspinu/.m2/repository/com/interactivebrokers/tws-api/9.71.1/tws-api-9.71.1-javadoc.jar"] Did the trick for me, both for refs and javadocs. |
Documenting this is just passing the ball to the user. How hard would it be to check for |
Thanks, the mistake was mine, I added the wrong jar (with only It would be easy to check for jars, but where would we check? |
In the parent directory of the class jar. |
The trick with I now see a lot "bad source file" errors like this when I first call
If I check manually I do see an interface |
Another simple workaround for this is to use tags instead ## fetch sources and javadocs
lein pom
mvn dependency:sources
mvn dependency:resolve -Dclassifier=javadoc
## build tags
mkdir java-sources && cd java-sources
jar -xvf ~/.m2/repository/io/netty/netty-all/4.0.23.Final/netty-all-4.0.23.Final-sources.jar
ctags -eR |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contribution and understanding! |
@jeffvalk is our resident expert here. I don't recall any changes in this area for quite a while until very recently. It still seems to me that the only thing needed for the lookup to work should be for the source artifacts to be on the classpath. |
Is this still an issue? If the source is on the classpath, |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contribution and understanding! |
This issues been automatically closed due to lack of activity. Feel free to re-open it if you ever come back to it. |
Not entirely sure what's special with
Period
. Jumping to e.g.java.lang.Exception
works fine. Perhaps it's that it's in a jar.The text was updated successfully, but these errors were encountered: