Fix checkstyle warnings
Fix checkstyle warnings
Merge branch 'dhleong/EclimJavaImplAtCursor' into dhleong/all
Merge branch 'dhleong/ImplementorSearch' into dhleong/all
Super hacky and disorganized first stab at Android XML completion

Need to move the vim stuff out of core and into adt, get vim
to actually use it (seems to be doing boring namespace stuff,
even though the completion command actually works) and then
figure out how to deal with the results, as well as the triggering
fix a couple cygwin specific issues

- when loading eclim vim settings, the call to get the user's home dir
  for cywin requires a system call, which in turn needs a couple of
  eclim's logging vars to already exist
- the function which constructs the eclim nailgun command was not
  returning the status along with the command when running in a cygwin
  environment.
Merge remote-tracking branch 'dhleong/dhleong/OnlyShowJUnitWindowOnFailure'
minor updates to latest :JUnit behavior patch

- remove setting of unnecessary global variables
- use eclim's Echo function when diplaying the status on a successful
  junit run.

refs #351
Merge remote-tracking branch 'dhleong/dhleong/UseWindowForLocateFile'
Reorganize; add ftdetect+syntax; make completion more reliable
Merge remote-tracking branch 'dhleong/dhleong/BreadthFirstClasspath'
Improve reliability work more mocking

Also, lots of experiment code copied from ADT source:

https://android.googlesource.com/platform/sdk/+/master/eclipse/plugins/com.android.ide.eclipse.adt/src/com/android/ide/eclipse/adt/internal/editors/common/

Can't seem to get ADT to return resource name suggestions, or really
any attribute value. I also can't seem to find the code where it
*would* provide that, either. It doesn't look like the
LayoutContentAssist even attempts to provide anything besides
layout/view names and their attributes, but I don't see anything
that would suggest that the ContentAssists are composed in any way
(and I don't see anything else providing resource suggestions
inside of attribute values, either... argh.) It's got to be there
somewhere.....
Some wacky hacks to get @res suggestions for layouts

I think with some more hacking we can get proper values
for the elements (eg: wrap_content, etc.). It looks like
the first branch from ValuesContentAssist is not completing

Still not sure how Eclipse is doing it normally, since it
does *not* look like the LayoutContentAssist tries to do it
at *all*, and even ValuesContentAssist requires specific input
to do anything.
Refactor, refactor, refactor
consolidate search result handling into lang.vim

also clear the loclist on a single result to prevent unnecessary sign
placement. fixes #355
Support multiple content assist types
fix django/jinja multiple tag completion when %} already exists
Add semantic triggers to ycm for android-xml filetype
Clean up suggestions before passing to omnifunc

We now mostly work! No idea how to get layout_width, etc.,
but what we DO have is pretty good, I think...
Fix checkstyle warnings