Skip to content
This repository has been archived by the owner on Aug 19, 2020. It is now read-only.

Support programmatic configuration of Kotlin plugin #26

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

Support programmatic configuration of Kotlin plugin #26

cbeams opened this issue May 30, 2016 · 1 comment
Assignees
@ligee
Labels
a:feature in:kt-idea-plugin re:ease-of-use
Milestone
0.2.0

Comments

@cbeams
Copy link
Contributor

cbeams commented May 30, 2016 •
edited
Loading

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 ligee Support programmatic configuration of Kotlin plugin May 30, 2016
@cbeams
Copy link
Contributor Author

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?

@cbeams cbeams mentioned this issue Jun 13, 2016
Closed
@bamboo bamboo closed this as completed in 2ed5c20 Jun 20, 2016
@cbeams cbeams mentioned this issue Jun 20, 2016
Closed
cbeams added a commit that referenced this issue Jun 20, 2016
@cbeams
Remove generateKtsConfig and patchIdeaConfig tasks
4251247 
These tasks are obsolete as of the resolution of #26 and #43.

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

@ligee ligee

Labels
a:feature in:kt-idea-plugin re:ease-of-use
Projects
None yet
Milestone
0.2.0
Development

No branches or pull requests
2 participants
@cbeams @ligee