Manu Sridharan

Thanks for digging in! We still shouldn't crash for missing jars. We should add some catch blocks that log a warning.

@edwardmp that's what I was suggesting above. A hackish fix would be to add null checks and then just soldier on without the relevant method / field. WALA is generally...

I'm fine with cutting a new release. Let me check with Julian. --Manu On Mon, May 9, 2016 at 9:41 PM Edward Poot [email protected] wrote: > @msridhar https://github.com/msridhar OK. Regarding...

I have tagged release 1.3.9 in the git repository (`R_1.3.9`). Still working on pushing new jars to Maven Central, should be done in the next day or so.

Haven't had time to look at this yet, and not sure when I will. At the least, anyone trying to fix will need a test case for reproducing the error,...

Sure, that would be greatly appreciated! By the way, as you may have noticed, I've done some refactoring on the master branch. From now on, you should be able to...

@edwardmp do you really need to use the Java source front end? All the problems here are in the source front end. The Java bytecode front end is _much_ more...

Ok. What makes you think this is not due to missing jars? In any case, as a patch-up fix, my approach would be to add null checks around any relevant...

By bailing out I generally mean for whatever operation the binding is being used for (typically adding something to a class or class hierarchy), don't do that operation. But if...

Thanks for digging in! So is adding a call to setRecoveryBindings somewhere sufficient to fix this? On Tue, May 31, 2016, 11:17 AM Edward Poot [email protected] wrote: > @msridhar https://github.com/msridhar...