Added compilation exception for #1062 test: Compiler does not detect conflicting unexported modules from Java/Maven modules
Decl: squash NPE
RegularFileObject #1062: make sure we compare files using the canonical ref

otherwise /foo/../bar is not equal to /bar
CeyloncCompilerdelegate #1062: only allocate the module manager once
LanguageCompiler #1062: Only look for the matching modules in the module swe compile

Otherwise we ended up assigning the file a/foo.ceylon to the module a/2 even which was
imported by someone else even though a/module.ceylon defined the module a/1
LanguageCompiler #1062: make sure we set the parsed modules' package.module correctly

the module visitor doesn't do it for us, so we have to, otherwise we're returning null
modules left and right
CeylonEnter #1062: keep track of which modules we put in the classpath
ModelLoader #1062: added a method to tell us if a module is in the classpath or not
model loader #1062: make sure we have the current module scope info for when we need it
model loader #1062: make sure lookupModuleInternal works only with modules in the classpath and the JDK
model loader #1062: catch completion failures in isRaw
model loader #1062: fix error message

it was displaying "javac type for XX" instead of "XX"
model loader #1062: added a method which tells us if a module imports another module
model loader #1062: refuse to look up declarations from non-imported modules
LazyModuleManager #1062: only complain about conflicting modules if they are in the classpath
CMRTest #1062: refactored a method which jars a java module

and takes the module descriptors into account
CMRTest #1062: the error changed a bit
CMRTest #1062: now rejecting a case which would be rejected by the runtime anyways

missing maven dependencies
CMRTest #1062: removed a dupe and useless error
Test for #1062: Compiler does not detect conflicting unexported modules from Java/Maven modules