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

Migrate several open source project builds #40

Closed
cbeams opened this issue May 30, 2016 · 5 comments
Closed

Migrate several open source project builds #40

cbeams opened this issue May 30, 2016 · 5 comments

Comments

@cbeams
Copy link
Contributor

cbeams commented May 30, 2016

The following projects have volunteered to work with us in migrating their builds to gradle-script-kotlin:

Please add a comment if you run an open source project and you'd like to migrate your existing Groovy-based Gradle build to Gradle Script Kotlin. Feel free to do so as well if you've already partially or completely migrated your build.

@cbeams cbeams added this to the 1.0.0-M2 milestone May 30, 2016
@cbeams cbeams changed the title re:migration Migrate several open source project builds May 30, 2016
@cbeams cbeams modified the milestones: 1.0.0 (GA), 1.0.0-M2 May 30, 2016
@ingokegel
Copy link

@DanielThomas
Copy link

DanielThomas commented Jun 2, 2016

I'd be happy to move our nebula-plugins projects. We're allergic to boilerplate though, so most of the usual build script configuration happens via plugin in https://github.com/nebula-plugins/nebula-plugin-plugin. Thought you might find us trying the support you're building for scripts, in plugins, valuable.

Incidentally, I migrated one of our plugins to Kotlin already, and except for a case of #8, the conversion with the current API went smoothly - https://github.com/nebula-plugins/gradle-resolution-rules-plugin.

@bamboo
Copy link
Member

bamboo commented Nov 23, 2016

@Barteks2x
Copy link

I already migrated to gradle script kotlin, it mostly went without issues, with a few exceptions (questions I asked on slack): https://github.com/Barteks2x/CubicChunks/blob/MC_1.11/build.gradle.kts

There are a few things that seem a bit verbose to me so I'm not sure if I did it correctly.

@elect86
Copy link
Contributor

elect86 commented Jan 10, 2017

It'd be useful to have a guide explaining the steps to take to migrate

I still didn't try, but the different with one of my project and the hello-word sample I can visually see are:

  • gradle-wrapper.jar 51.6 vs 51.7 KB
  • different distributionUrl in gradle-wrapper.properties
  • obviously different build.gradle -> build.gradle.kts
  • almost same gradlw.bat, I miss the ^M
  • different settings.gradle, rootProject.name = vs rootProject.buildFileName=

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

7 participants