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

Moved to new MPP format, kotlin dsl #81

Merged
merged 2 commits into from
Jul 24, 2019
Merged

Moved to new MPP format, kotlin dsl #81

merged 2 commits into from
Jul 24, 2019

Conversation

leodamsky
Copy link
Contributor

@leodamsky leodamsky commented Jul 21, 2019

This PR is for issue #64

As there is a discussion about Kotlin DSL in this issue, I've added it too(upgrading Gradle to 5.5.1 and Kotlin to 1.3.41)

Compatibility version of Kotlin in kotlin-logging-jvm I kept 1.1. Tried not to change an existing codebase to make easier to review the PR. It seems I fixed all backward-incompatible stuff, but review though, please.

@oshai
Copy link
Owner

oshai commented Jul 21, 2019

Thanks! I will review it as soon as I have some time.

Copy link
Contributor Author

@leodamsky leodamsky left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, check out these comments, please.

compilations.named("main") {
kotlinOptions {
metaInfo = true
sourceMap = true
Copy link
Contributor Author

@leodamsky leodamsky Jul 21, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I removed outputFile, but the result js jar seems the same

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok

kotlin("multiplatform") version "1.3.41"
id("com.jfrog.bintray") version "1.8.4"
`maven-publish`
`java-library` //todo: ask whether we need javadoc at all as it is always empty
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you need javadocs? The jars are empty

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you check this you'll see jars are not empty: https://repo1.maven.org/maven2/io/github/microutils/kotlin-logging/1.6.26/

It is required by maven central

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think dokka would help

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry, by empty I meant jar contains only MANIFEST.MF

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But there are no javadocs themselves

@oshai
Copy link
Owner

oshai commented Jul 24, 2019

Thanks, it looks good!
Before merging it, I will publish a release from the PR to make sure it works.
I guess we will have a separate issue for the dokka docs. I will open that later.

@oshai
Copy link
Owner

oshai commented Jul 24, 2019

I released version 1.7.0-mpp, will test it and then merge. you're welcome to check also.

@oshai oshai merged commit b516627 into oshai:master Jul 24, 2019
@oshai
Copy link
Owner

oshai commented Jul 24, 2019

It looks good, I merged it. Thanks again!
Will release version 1.7.1 with it.

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

Successfully merging this pull request may close these issues.

2 participants