- About Scala
- Documentation
- Code Examples
- Software
- Scala Developers
configuring eclipse for dev
Fri, 2009-12-04, 01:15
hi All,
i just noticed the extract below from the https://lampsvn.epfl.ch/trac/scala/wiki/EclipsePlugin. does this mean i can skip steps "Locate your installed Equinox Aspects bundles", "Creating a Run configuration" and "Creating a config.ini file"? i've always hated doing this.
although i'm using linux at the moment, i wonder how many people use windows for IDE dev.
---
—Mohamed
i just noticed the extract below from the https://lampsvn.epfl.ch/trac/scala/wiki/EclipsePlugin. does this mean i can skip steps "Locate your installed Equinox Aspects bundles", "Creating a Run configuration" and "Creating a config.ini file"? i've always hated doing this.
although i'm using linux at the moment, i wonder how many people use windows for IDE dev.
---
Hacking and Testing
Assuming you've followed all the steps above up to this point, you should be ready to start hacking on the Scala IDE sources. Proceed as you would with any other Eclipse plugin development work. When you're ready you can launch an Eclipse runtime workspace to test.
Currently (as of April 2009) creating an Eclipse run configuration that works with Equinox Aspects is a partly manual process. This is resolved on very recent builds of Eclipse 3.5 (post M6).
—Mohamed
On Fri, Dec 4, 2009 at 12:15 AM, Mohamed Bana wrote:
> i just noticed the extract below from
> the https://lampsvn.epfl.ch/trac/scala/wiki/EclipsePlugin. does this mean i
> can skip steps "Locate your installed Equinox Aspects bundles", "Creating a
> Run configuration" and "Creating a config.ini file"? i've always hated
> doing this.
Locating the Equinox Aspects bundles should no longer be necessary,
but you'll still need to create a config.ini to launch a runtime
workspace. I have some ideas about how to simplify this process, but
just don't have the time at the moment ... contributions
(documentation or otherwise) would be most welcome.
Cheers,
Miles