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

Version 0.21.0 #305

Merged
merged 11 commits into from
Jun 23, 2023
Merged

Version 0.21.0 #305

merged 11 commits into from
Jun 23, 2023

Conversation

mvicsokolova
Copy link
Collaborator

No description provided.

Tapchicoma and others added 7 commits April 26, 2023 10:21
@qwwdfsad qwwdfsad self-requested a review May 25, 2023 15:27
@ImUrX ImUrX mentioned this pull request May 29, 2023
@qwwdfsad
Copy link
Collaborator

qwwdfsad commented Jun 1, 2023

Some observations about the commit history we got here: there is a sequence of commits that exist out-of-context (e.g. neither tested nor thoroughly explained (e.g. 5f05039), with the final issue that is fixed also non-tested. They should've been squashed, with the detailed explanation why the changes are done.

I'd suggest using Kotlin/kotlinx-kover#386 as an inspiration: the Gradle tweaks are documented, the test is provided, the commit message is extensive (e.g. why file collection was replaced with the provider, not the fact it was done)

@mvicsokolova
Copy link
Collaborator Author

Thank you, yes, all these out-of-context commits from c201c53 to c41d50a were merged with this PR: #303. My mistake they were not squashed. The issue fixed there was reproduced by the existing test kotlinx.atomicfu.plugin.gradle.test.JvmLegacyTransformationTest.

I can fix the history in this branch and merge it to master in a proper way (squash + extended comment).

I would also add comments to all the changes for future understanding (some of them were just caused by using the new KGP API).

@mvicsokolova
Copy link
Collaborator Author

mvicsokolova commented Jun 2, 2023

Currently, the release depends on this issue #307 that is fixed here #308 (waiting for review and approval).
It is only reproduced for now with Kotlin 1.9.0-RC, but I want to add the fix to this release.

Tapchicoma and others added 2 commits June 7, 2023 12:37
Jar task for JVM-only projects packed both original and transformed classes with Kotlin 1.8.20 and Gradle 7.3.
This commit contains fix for the issue, plus some refactoring in AtomicfuGradlePlugin using KGP API introduced in 1.7.0.

* Fixed configuration of outputs classesDir: remove outputs of Kotlin compilation task and replace with atomicfu transformation task output
* Refactoring:
    - Renamed the directory with original classes to `classes/atomicfu-orig/`
    - Introduced 'destinationDirectory' for AtomicFUTransformTask
    - Lazy registration of AtomicFU transform tasks
* Added minimal supported version of KGP and Gradle (KGP >= 1.7.0, Gradle >= 7.0)
Always configure test compilation dependencies

Fixes #307
@mvicsokolova
Copy link
Collaborator Author

Commit fixing the issue with building JVM-only projects merged (88a5e14).

develop history fixed

mvicsokolova and others added 2 commits June 22, 2023 11:13
For targets that require IR transformation modification of compilation tasks output directories is not required. Classes from the original directories are transformed by the compiler plugin in place.

Fixes #311
@mvicsokolova mvicsokolova merged commit 8c3b92a into master Jun 23, 2023
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.

3 participants