May 16 Scala IDE 4. But this allows us, on a per-project basis, to make the Scala IDE deal with projects in 2. Beware this choice will also have an impact on your choice of Scala installation and associated compiler settings. In that process, it usually rewrites the required classpath of your project, to replace the scala-compiler and scala-library with a generic, version-less compiler resp. Scala-IDE will then figure out wich version of scala your project is using from its classpath, and configures itself correctly based on that.
| Uploader: | Mik |
| Date Added: | 6 November 2011 |
| File Size: | 53.31 Mb |
| Operating Systems: | Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X |
| Downloads: | 45236 |
| Price: | Free* [*Free Regsitration Required] |
How about dealing with custom, personal installations of Scala that you may want to use in conjunction with your project? But its typechecker can run with a specific option, -Xsource: To do that, sbteclipse introduces since version 2. There you can add and remove an installation according to your needs. Scala IDE support for simultaneous 2. But this allows us, on a per-project basis, to make the Scala IDE deal with projects in 2. Scala Multi Version Support The gist of it is the following: If you are dealing mostly with 2.
If you have a significant project that uses 2. Files in that classpath will possibly contain a scala-library jar, in which we know where to look for a version, or other, external jar files which filename might hint at a Scala version. You can witness that by expanding your project in the Package Explorer. If there are source jars in that directory, the IDE will also try to incorporate them in the installation.
But it no longer knows about old typing ways of the past. Since whitebox macros have some incompatible improvements between 2. All of this is brought to you by a single toggle, that we will deal with first, so that those of you in a hurry can start hacking.
But so far, we have only seen how to manage the pre-installed, embedded versions of the scala library and compiler. Besides, we firmly intend to implement more ways of defining a custom scala installation for use in your IDE. You can also see that in the Java Build Path preference page in the project settings:. Apr 06 Scala IDE 4.
Basically, classpath containers are an indirection in your classpath that is elaborated by the platform Eclipse using settings. Finally, note that so far, we only support Scala Versions posterior to 2. This probably will remain a long-term limitation of this mode.
Scala IDE support for simultaneous 2.11 and 2.10 projects
This is because your project is using a Classpath Container. It will not report errors in some situations where the 2. The second occurence should not affect any settings. How about setting a custom, die installation that your projects can then reuse? If just removing scala-version-related makes your project configuration equivalent to workspace settings, it will automatically revert the project-specific toggle. The meaning of a fixed version is just that: This is what you can do from the Scala Installations preference page.
Scala Installation detection The IDE will try to understand what version of Scala your project is designed to work with. Sep 29 Scala IDE 4. It displays a list of versioned Scala installations that should include at least both a 2.
Scala IDE support for simultaneous and projects - Scala IDE for Eclipse
Multiple Scala Installation Settings at once Many of you sala multiple projects which version they want to switch quickly, without having to open project preferences for each project.
Note that if you decide to revert that change and come back to a 2. Scala Multiple Installation Support.
Комментариев нет:
Отправить комментарий