Welcome to Kotlin! Some handy links:
- Getting Started Guide
- Web Demo
- Kotlin Site
- API
- Issue Tracker
- Forum
- Kotlin Blog
- follow Kotlin on twitter
- TeamCity CI build
To build this project, first time you try to build you need to run this (requires Apache Ant 1.8 or higher):
ant -f update_dependencies.xml
which will setup the dependencies on
- intellij-core: is a part of command line compiler and contains only necessary APIs.
- idea-full: is a full blown IntelliJ IDEA Community Edition to be used in former plugin module.
Then, you need to run
ant -f build.xml
which will build the binaries of the compiler and put them into the 'dist' directory.
Maven distribution is built separately, run
mvn install
from 'libraries' directory after building the compiler.
The root kotlin project already has an IDEA project, you can just open it in IDEA.
Note though that you need a recent IDEA build (e.g. 11 EAP) which should not contain the Kotlin plugin!
If you want to have an IDEA installation without the Kotlin plugin which is separate to your default IDEA installation which has the Kotlin plugin see this document which describes how to have mutliple IDEA installs using different configurations and plugin directories.
From this root project there are Run/Debug Configurations for running IDEA or the Compiler Tests for example; so if you want to try out the latest greatest IDEA plugin
- VCS -> Git -> Pull
- Run IDEA
- a child IDEA with the Kotlin plugin will then startup
- you can now open the kotlin libraries project to then work with the various kotlin libraries etc.
You can download the latest Kotlin IDEA Plugin from the IDEA Plugin and Tests CI build
Or in a recent IDEA 11 EAP build install the Kotlin plugin:
Preferences -> Plugins -> Browse Repositories -> Manage Repositories... -> + to add a new repository URL
You can now open any Kotlin based projects. Its advisable you don't open the root kotlin project as thats intended to be used to build the kotlin compiler and plugin itself; instead open the kotlin libraries project
We love contributions! There's lots to do on kotlin and on the standard library so why not chat with us on the forum about what you're interested in doing?
If you want to find some issues to start off with, try this query which should find all issues that are not resolved assigned to Kontributor.
Currently only committers can assign issues to themselves so just add a comment if you're starting work on it.
A nice gentle way to contribute would be to review the API docs and find classes or functions which are not documented very well and submit a patch.
In particular it'd be great if all functions included a nice example of how to use it such as for the filter() function on Collection. This is implemented using the @includeFunctionBody macro to include code from a test function. This serves as a double win; the API gets better documented with nice examples to help new users and the code gets more test coverage.
Also the JavaScript translation could really use your help. See the JavaScript contribution section for more details.
The Kotlin compiler is currently all written in Java (we plan to port it to Kotlin later). So the easiest way to work on the compiler or IDEA plugin is
- download a clean IDEA 11 EAP build
- don't install the Kotlin plugin
- open the root kotlin project in IDEA (opening the kotlin directory)
You can now run the various Run/Debug Configurations such as
- IDEA
- All Compiler Tests
- All IDEA Plugin Tests
- download a clean IDEA 11 EAP build
- Preferences -> Plugins -> Browse Repositories -> Manage Repositories... -> + to add a new repository URL
- http://www.jetbrains.com/kotlin/eap-plugin-repository/updatePlugins.xml
- open the kotlin libraries project
Then build via
cd libraries
mvn install
The best way to submit a patch is to fork the project on github then send us a pull request via github.
If you create your own fork, it might help to enable rebase by default when you pull which will avoid your local repo having too many merge commits which will help keep your pull request simple and easy to apply.
If you include in your comment this text (where KT-1234 is the Issue ID in the Issue Tracker, the issue will get automatically marked as fixed.
#KT-1234 Fixed