jlebowskii

Finding the right version of the source code is definitely a challenge. However, it's a solvable one. What you're suggesting is actually what ExceptError does. It indexes all versions of each library, and uses context from the entire stack-trace, including line-numbers, method-names, etc, to find the exact match.

Agree that IDE is the best way, especially when it comes to Java, but it's not always possible. For example you may be debugging distributed systems in production.

Thanks! Good point, I'll look into adding that.

"versions" tells you all the software versions which match, based on the context derived from the exception. For example, if you're unsure what version of Hadoop you're running, it'll tell you.

The other thing is that even with an IDE, I think folks may find this useful. Not everyone uses Gradle, Maven, etc, and also not every library on Maven comes with the source jars.

It doesn't integrate with any IDE right now. As @arturnt noted, debugging and jumping to the right source code is generally not a problem when you're inside an IDE.

The main use-case that I see for this is when an exception is thrown in production on some random server inside a third party library. Such exceptions can be excruciatingly hard to run down without the source code.