Kevin Schroeder

I've _never_ read technical manuals in the dark. This is the code for either pulling the data from cache or executing the annotator shown above. ``` protected CoreDocument annotate(String filename)...

Well, I know it's lame but this works: ``` Class tokensAnnotationKey = EnvLookup.getDefaultTokensAnnotationKey(env); List tokens = (List)document.annotation().get(tokensAnnotationKey); int size = tokens.size(); for (int i = 0; i < size; i++)...

I've not had a chance to go into it, but it's still on my TODO list.

When upgrading to 4.5 a number of my tests started breaking and I'll need to fix those before being certain, but it looks like the `NullPointerException` is now gone.

Ahh, I got it to replicate using the following text for `foo.txt`: ``` I love pizza. I like pizza. I REALLY like pizza so much that I love pizza. But...

If I replace the `fromCache` method with this: ``` public static CoreDocument fromCache(String filename) { AnnotationSerializer serializer = new ProtobufAnnotationSerializer(); try { File cacheFilename = getCacheFilename(filename); // cacheFilename.delete(); if (cacheFilename.canRead())...

Oh! I figured it out. The text file was using Windows EOLs. When I switched to Unix LF the problem went away. When I switched back to `\r\n` the problem...

Since I only use this to cache annotations to avoid reprocessing during tests, and I have a workaround, I'm in no immediate need.

Thanks. I'll try to give it a shot if I get some time.

It's now three years later and the issue is still open, but I have a simple working solution. I figured out that the autocomplete, for some reason, thought that it...