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

v0.5.0 release #49

Merged
merged 59 commits into from
Dec 5, 2024
Merged

v0.5.0 release #49

merged 59 commits into from
Dec 5, 2024

Conversation

ShreckYe
Copy link
Member

@ShreckYe ShreckYe commented Dec 5, 2024

No description provided.

…ojects so the build is always reproducible by others
… run "check" instead of "build", and use gradle/actions of a the latest release version
The fix in the previous commit doesn't work.
The error message from the GitHub Actions workflow:
```text
> Could not resolve all files for configuration ':buildSrc:compileClasspath'.
   > Could not resolve com.android.tools.build:gradle:8.5.2.
     Required by:
         project :buildSrc
      > Dependency requires at least JVM runtime version 11. This build uses a Java 8 JVM.
```
The error message from the GitHub Actions workflow:
```text
An exception occurred applying plugin request [id: 'com.android.library']
> Failed to apply plugin 'com.android.internal.library'.
   > Android Gradle plugin requires Java 17 to run. You are currently using Java 11.
      Your current JDK is located in /usr/lib/jvm/temurin-11-jdk-amd64
      You can try some of the following options:
       - changing the IDE settings.
       - changing the JAVA_HOME environment variable.
       - changing `org.gradle.java.home` in `gradle.properties`.
```
Android Gradle plugin requires Java 17 to run. See commit 82a9e40 for more details.
Publish the demo site to GitHub Pages

Resolve #25
Enable GitHub Actions and host the demo with GitHub Pages
…e README.md and modules correspondingly

Changes:

1. update README.md, replacing old names, reorganizing and updating its content, and fixing some formatting issues, typos, and grammar mistakes
1. rename the subjects/modules and adopt the "concatenated project name" approach
1. run `apiDump` and remove the old dumped files

A source commit: huanshankeji/kotlin-common@477978d
…mposeUi"/"ComposeUi" in files and filenames

To replace strings in the filenames, the "rename" program is installed and the following command is run:

```sh
find . -name "*androidxCommon*" -exec rename 's/androidxCommon/composeUi/' {} ";"
find . -name "*AndroidxCommon*" -exec rename 's/AndroidxCommon/ComposeUi/' {} ";"
```
Rename the project to "Compose Multiplatform HTML Unified"
…project name "Compose Multiplatform HTML Unified", and revert a change that's not needed
… the files, review and update one, and replace the others with "compose-multiplatform-html-unified"
More on renaming the project to "Compose Multiplatform HTML Unified"
…" directories, and run `apiDump` and `check` to verify it works
…pose.ui` dependency to the common `composeUiMain` source set
… "concatenated project name" approach, introduced in commit 902b931
@ShreckYe ShreckYe self-assigned this Dec 5, 2024
@ShreckYe ShreckYe merged commit 0632000 into release Dec 5, 2024
6 checks passed
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.

1 participant