Run gradlew ide and it'll start an IDE with the xtend plugins. It first downloads the plugins if necessary using bundlepooling.
A barrier to entry for me with xtend has been getting an IDE setup. This PR hopefully makes it easier for people to contribute to this project, and also to try out xtend in general.
There are .project files checked into the repo, but for me they don't work initially. I have to run gradlew eclipse to generate new, dirty eclipse files which work. Perhaps we should remove the .project, add them to .gitignore, and then make ide depend on eclipse so that the ide always opens with valid projects?
Run
gradlew ide
and it'll start an IDE with the xtend plugins. It first downloads the plugins if necessary using bundlepooling.A barrier to entry for me with xtend has been getting an IDE setup. This PR hopefully makes it easier for people to contribute to this project, and also to try out xtend in general.
There are
.project
files checked into the repo, but for me they don't work initially. I have to rungradlew eclipse
to generate new, dirty eclipse files which work. Perhaps we should remove the.project
, add them to.gitignore
, and then makeide
depend oneclipse
so that the ide always opens with valid projects?