- About Scala
- Documentation
- Code Examples
- Software
- Scala Developers
Re: Can nightlies of the Eclipse plug-in be used with Beta1 of the library?
Sun, 2010-02-07, 15:35
Even if it did work today there's no reason to assume it will continue to work, if I'm not mistaken.
Maybe use two eclipse installatations, one with the beta plugin and one with the nightly, pointing to the same workspace, and use one for projects that need the beta and the other for those that are updated with the nightly?
-------------------------------------
Erkki Lindpere wrote:
I've done that 10s of times, no help.
Kevin Wright wrote:
> Try doing a full clean and see if that sorts your problem.
>
> I have one project where I'm working with the nightly plugin and
> maven-supplied 2.8 beta 1 on my classpath, things are generally good
> for me except for the otherwise known issues in eclipse.
>
>
>
> On 7 February 2010 13:57, Erkki Lindpere > wrote:
>
> I'm writing a Lift project and am using the lift build compatible
> with Scala-2.8.0.Beta1
>
> However, Miles recommends using nightlies of the Eclipse plug-in,
> which has a newer snapshot of Scala-2.8.0
>
> Is it ok if I use the Scala-2.8.0.Beta1 in the classpath (I'm
> using M2Eclipse and am using Scala library from Maven
> Dependencies, not the one provided by the plug-in)
>
> I get an error "no-symbol does not have owner" in one project and
> I'm wondering if it might come from incompatibility between the
> compiler and library versions.
>
> Erkki L
>
>
>
>
Otherwise, you're probably better off just using the eclipse-provided scala libraries. The only real catch here is if you need scala-compiler on the classpath as well, as this isn't included in the plugin.
One option then is to manually download scala-compiler.jar from hudson, making sure that it matches the version used in building the compiler plugin - repeat this every time you update the plugin. You can be sure that everything else will then be in sync, as scala-library and the eclipse plugin are all built together as part of the same Hudson task.
Another option is to run scala-compiler (and in fact the entire eclipse plugin) from source and fire up your project in a runtime workspace. This *does* give you debugging inside the compiler, and hot-swapping of code changes, but also adds the rather nasty memory and CPU overhead of having to run two concurrent eclipse instances; so it could well be overkill unless you're doing something especially hardcore, like compiler-plugin hacking.
On 7 February 2010 14:34, Naftoli Gugenheim <naftoligug@gmail.com> wrote:
--
Kevin Wright
mail/google talk: kev.lee.wright@googlemail.com
wave: kev.lee.wright@googlewave.com
skype: kev.lee.wright
twitter: @thecoda