New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support programmatic configuration of Kotlin plugin #26

Closed
cbeams opened this Issue May 30, 2016 · 1 comment

Comments

Projects
None yet
2 participants
@cbeams
Contributor

cbeams commented May 30, 2016

When this work is complete, it will eliminate the current need for a static gradle.ktscfg.xml (#19) file to be generated (by generateKtsConfig) at the root of each project.

The general idea is to expose a configuration API on the Kotlin plugin side and to then integrate with it via the Gradle Tooling API.

@cbeams cbeams added this to the 1.0.0-M2 milestone May 30, 2016

@cbeams cbeams added -u and removed -u labels May 30, 2016

@cbeams cbeams changed the title from ligee to Support programmatic configuration of Kotlin plugin May 30, 2016

@cbeams

This comment has been minimized.

Show comment
Hide comment
@cbeams

cbeams Jun 13, 2016

Contributor

@ligee, could you provide an update on this? We're considering cutting M2 on Monday the 20th (a couple days earlier than planned). Can this issue still make it?

Contributor

cbeams commented Jun 13, 2016

@ligee, could you provide an update on this? We're considering cutting M2 on Monday the 20th (a couple days earlier than planned). Can this issue still make it?

@bamboo bamboo closed this in 2ed5c20 Jun 20, 2016

cbeams added a commit that referenced this issue Jun 20, 2016

Remove generateKtsConfig and patchIdeaConfig tasks
These tasks are obsolete as of the resolution of #26 and #43.

Resolves #79
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment