Read additional bytes after invokeinterface opcode, fixes #603

Clazz.crawl() was not accounting for count operand
and additional reserved byte that always comes after
an in invokeinterface

Signed-off-by: Gregory Amerson <gregory.amerson@liferay.com>
Merge pull request #605 from gamerson/issue-603

Fixes issue #603
Use consistent EOLs when creating DS & Metatype resources

MetaTypeReader and TagResource both use PrintWriter.println() to output the XML declaration and then delegate to Tag.print() to generate the XML document.  Tag.print() uses PrintWriter.print("\n") to generate newlines in the XML document.

PrintWriter.println() on Windows will use \r\n, so we end up with inconsistent whitespace in the file.  This patch changes Tag.print() to invoke PrintWriter.println() instead of hard coding the EOL character. This is only a presentation issue, but it also "resolves" this bndtools issue (assuming you are looking at a JAR created on your platform):

https://github.com/bndtools/bndtools/issues/864

An alternate approach would be to change MetaTypeReader and TagResource to explicitly use a \n when rendering the XML declaration rather than using PrintWriter.println().

Signed-off-by: Sean Bright <sean@malleable.com>
Merge pull request #606 from seanbright/tag-consistent-eols

Use consistent EOLs when creating DS & Metatype resources