Functional interface wrappers should work now
Implementing a method with a signature differing from the actual one (e.g. when dealing with generics) now creates a proper bridge method
The Java Bytecde compiler used an incorrect method in checkCast
We now no longer use hardcoded 'accept's as method names but whatever the context tells us to.

Currently only supports 'accepts' methods, until we can get a way to get the actual method signature/name from the class

Directly using the lambda where the functional interface is requested works.
The lambda class will then directly implement the functionalInterface and not use a wrapper class

- Fixed a number of bugs
- Upgrading build system to a more uniform system
- Improving error output (for IDE)
- Changed parser to generate line offsets differently (easier for IDE to process)

- Save collapse state of the project browser tree

- Added support for INTERFACE calls in java source code generation
- Minor source code generation quality improvements

- Added support to have a native method both as operator and named method

- Fix float suffixes on integers

- Fix getters for globals not having their corresponding fields registered correctly in the native implementation
- Added java sources for JavaScripting

Lokking at you ForgeModLoader that needs to reinitialize about every class it comes across