Initial steps at supporting placing breakpoints in JAR libraries
Initial steps at supporting placing breakpoints in JAR libraries
Merge branch 'Java_Breakpoints_2' of https://github.com/ivmarkov/sdbg into Java_Breakpoints_2

Conflicts:
	com.github.sdbg.debug.core/src/com/github/sdbg/debug/core/ISourceLookupExtensions.java
	com.github.sdbg.debug.core/src/com/github/sdbg/debug/core/internal/jdt/JDTSourceLookupExtensions.java
	com.github.sdbg.debug.core/src/com/github/sdbg/debug/core/internal/source/SDBGSourceLookupDirector.java

Signed-off-by: ivmarkov <ivan.markov@gmail.com>
PackageFragmentRootSourceContainer is now used for Java project. The net
result: .class files are opened with the Java class file editor; placing
breakpoints in these is possible.
Move the JDT support into a separate project
Establish a formal target platform - 3.7+ (Indigo)
Raise the version to 0.1.0
Raise the version to 0.1.1
Try to implement support for the strange source maps of GWT 2.5.1
Raised version to 0.1.2
Bugfixing
Version raised to 0.1.3
Include the line numbers in the stack frame rendering
Better name for the one and only javascript thread in the Chrome
debugger
Better names for the stackframes
Make the Chrome debug launch more reliable; fix the logging messages not
to mention Dartium
Source not found editor was not properly appearing
Merge branch 'Java_Breakpoints_2' of https://github.com/ivmarkov/sdbg into Java_Breakpoints_2
Change the Chrome launch icon from Chromium to Chrome
More fixes for GWT 2.5.1 sourcemaps...