Skip to content
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

Migrate build scripts to new Kotlin DSL #123

Closed
aaschmid opened this issue Dec 22, 2019 · 1 comment
Closed

Migrate build scripts to new Kotlin DSL #123

aaschmid opened this issue Dec 22, 2019 · 1 comment

Comments

@aaschmid
Copy link
Member

No description provided.

@aaschmid aaschmid self-assigned this Dec 22, 2019
@aaschmid aaschmid added this to the next version milestone Dec 22, 2019
aaschmid added a commit that referenced this issue Dec 23, 2019
* only required stuff goes to new build file (Kotlin DSL)
* everything else is kept in legacy but renamed build file (Groovy DSL)

Note:
* `withType` does no longer work with full qualified import (no idea why) so comment it and mark it with TODO
aaschmid added a commit that referenced this issue Dec 23, 2019
Note: Using a `String` for dependency configuration is ugly but the
alternative is to apply `java-library` plugins within `plugins` closure
which would also apply it to root project which is very much unwanted.
This also does not allow to use `java` closure and `javadoc` task.

Alternative: We could split build into multiple files with a lot
duplicated code, though.

Which one is better?
aaschmid added a commit that referenced this issue Dec 23, 2019
aaschmid added a commit that referenced this issue Dec 24, 2019
* only required stuff goes to new build file (Kotlin DSL)
* everything else is kept in legacy but renamed build file (Groovy DSL)

Note:
* `withType` does no longer work with full qualified import (no idea why) so comment it and mark it with TODO
aaschmid added a commit that referenced this issue Dec 24, 2019
Note: Using a `String` for dependency configuration is ugly but the
alternative is to apply `java-library` plugins within `plugins` closure
which would also apply it to root project which is very much unwanted.
This also does not allow to use `java` closure and `javadoc` task.

Alternative: We could split build into multiple files with a lot
duplicated code, though.

Which one is better?
aaschmid added a commit that referenced this issue Dec 24, 2019
aaschmid added a commit that referenced this issue Dec 24, 2019
@aaschmid aaschmid changed the title Mgrate build scripts to new Kotlin DSL Migrate build scripts to new Kotlin DSL Dec 28, 2019
aaschmid added a commit that referenced this issue Dec 29, 2019
* only required stuff goes to new build file (Kotlin DSL)
* everything else is kept in legacy but renamed build file (Groovy DSL)

Note:
* `withType` does no longer work with full qualified import (no idea why) so comment it and mark it with TODO
aaschmid added a commit that referenced this issue Dec 29, 2019
Note: Using a `String` for dependency configuration is ugly but the
alternative is to apply `java-library` plugins within `plugins` closure
which would also apply it to root project which is very much unwanted.
This also does not allow to use `java` closure and `javadoc` task.

Alternative: We could split build into multiple files with a lot
duplicated code, though.

Which one is better?
aaschmid added a commit that referenced this issue Dec 29, 2019
aaschmid added a commit that referenced this issue Dec 29, 2019
@aaschmid
Copy link
Member Author

Tested and rebased quite a lot but now having a pretty much stable and consistent version :-)

aaschmid added a commit that referenced this issue Jan 5, 2020
* migrate.to.kotlin.#123: (25 commits)
  fix file includes for resulting JARs
  centralize and upgrade dependencies
  get rid of not required LifecyclePlugin wrapper
  use Kotlins "it" for simple closures
  prefer methods which favor configuration avoidance
  introduce caching for travis CI builds
  use Bnd Gradle Plugins via plugins {} API
  migrate remaining publishing configuration to Kotlin DSL (#123)
  migrate cpd config (#123)
  migrate coveralls and its required jacoco config (#123)
  remove no longer used TouchTestResults class in legacy build file (#123)
  migrate second generic subprojects configuration to Kotlin DSL (#123)
  migrate junit-jupiter and junit-jupiter-params subprojects configuration to Kotlin DSL (#123)
  migrate junit-jupiter* subproject configuration to Kotlin DSL (#123)
  migrate junit4 subproject configuration to Kotlin DSL (#123)
  migrate core subproject configuration to Kotlin DSL (#123)
  migrate first generic subprojects configuration to Kotlin DSL (#123)
  migrate extra properties, buildScan and allprojects configuration to Kotlin DSL (#123)
  prepare stepwise migration by splitting build logic (#123)
  add parantheses which can be omitted in Groovy but not Kotlin (#123)
  ...
@aaschmid aaschmid closed this as completed Jan 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment