- if the problem is related to the update stage or a dodgy ENSIME classpath, try nuking your ivy cache and
ensime-reload. - check the tickets flagged as FAQ on the server and tickets flagged as FAQ for Emacs.
- check the most recently updated tickets.
- do a few keyword searches using the github search (top of the page) to see if anybody has reported this already.
If you use this software you are already well placed, as a Scala developer, to make it even better.
All interactions within the ENSIME community have been friendly and open: we want this to continue, formalised by our Code of Conduct.
Please help out by:
- Picking up some low hanging fruit (also for the server)
- Fixing a bug (also for the server)
- Helping with the current Milestone (also for the server)
- Sending an unsolicited pull request with a new feature
- Joining the conversation on
(also for the server)
- Telling your co-workers!
We are using some great technologies to automate our build and testing process:
- Kanban project planning from waffle.io
- Continuous Integration from shippable.com
- Coverage reports from coveralls.io coveralls.io
- Binary distribution from sonatype.org
- Emacs distributions from MELPA
Along with unit testing, we have automated coverage checks and code formatting as part of our build process. Pull requests will only be accepted if the build and tests are successful, coverage has not decreased, and the formatting style has not been changed (it is automated, so you don't need to think about it).
Pull requests will be reviewed and should not be merged by the person who created the request (except for trivial changes and hotfixes).
We have branches for older versions of scala, which are merged regularly.