…es the ScalaStructureBuilder failing (the exception is swallowed and an entry appear in the Error Log). To prevent this,check if the position is defined for the type parameter symbol before using it. If it's not defined then we log the problem so that we can get a better picture of why the position is undefined.
…er that can be used by classes if they want to have access to the logger (HasLogger declares a dependency to the Logger). Further, the Logger's interface is now decoupled from its implementation so that in the future we can easily replace the default logger.
…ring commit 9ba9efa
ScalaStructureBuilder now correctly expose methods with generic signature to JDT. We use the Scala compiler for generating the java signature from a symbol, since that functionality is already there (call to erasure.javaSig(Symbol)). JavaSig class encapsulate the call to erasure.javaSig. In order to correct mapping of Scala Arrays (ticket #1000586) into Java ones, a new mapType(Type) method has been added to ScalaJavaMapper class. This method is also used to map types in absence of a java signature (which can occur if the method does not have any generic type in its declaration). All snippet of code that were provided with the tickets have been added to the regression suite. I also had to make some correction to existing tests, particularly for the structurebuilder test named _traits_, as the test's oracle was wrong. While with this commit we improve a lot interoperability of Java with Scala members, works still has to be done for mapping type parameters of classes. We have an open ticket for that (#1000625), but fixing it should be relatively easy now that we have a good infrastructure for retrieving generic java signature.
… into release/scala-ide-2.0.x
…til to 'properties', to be together with the other Scala compiler settings.
…cala-library.jar exists on disk.
… the best anwser possible is returned.
…succeed once we move to 0.11.1 (tonight). Then #1000584 should be fixed.
…project name matches the bundle name and all jars are correctly exported by the project. The normal Plugin Dependencies mechanisms correctly adds the project to sdt.core's class path, so no more hard coded names to sbt jars in the sdt.core project.
…y known by the editor. This also fixed a similar problem with the 'indent' command.
…o the status of 'use project settings'
…ing is always correctly saved