Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@souvlakias
Copy link
Contributor

  • Extracted hardcoded values of each android module subclass into the build info component of androidlib

@souvlakias souvlakias changed the title Androidlib remove hardcoded vals Android: Replace hardoded versions with relevant versions from build info Jun 27, 2025
@souvlakias souvlakias changed the title Android: Replace hardoded versions with relevant versions from build info Android: Replace hardcoded versions with relevant versions from build info Jun 27, 2025
@souvlakias souvlakias marked this pull request as ready for review June 27, 2025 17:10
@lihaoyi lihaoyi merged commit 43069c7 into com-lihaoyi:main Jun 30, 2025
48 checks passed
Comment on lines +284 to +292
object AndroidDeps {
val manifestMergerVersion = "31.10.0"
val bundleToolVersion = "1.17.2"
val ndkVersion = "27.0.12077973"
val cmakeVersion = "3.22.1"
val layoutLibVersion = "15.1.2"
val composePreviewRendererVersion = "0.0.1-alpha09"
val uiToolingVersion = "1.7.6"
}
Copy link
Member

Choose a reason for hiding this comment

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

What's missing here is to also use these dependencies somewhere, so we can auto-detect updates. Please add these to the dummy cross module in the top-level build.mill.

Copy link
Contributor

@vaslabs vaslabs Jun 30, 2025

Choose a reason for hiding this comment

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

cool, we'll do, what happens for the tools that we can't match to maven deps? (I think it's just cmake and ndk)

Is it better to have those in package.mill instead?

Copy link
Member

Choose a reason for hiding this comment

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

Currently, nothing. If you have an idea how to check them for updates, you can add a task that check it, of course.

I already started to add some deps to the dummy module. I'll send a review request.

Copy link
Member

Choose a reason for hiding this comment

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

Here's my draft:

@vaslabs Don't know, if we need to accommodate to Android specifics. Feel free to comment or push to that PR branch.

Copy link
Contributor

Choose a reason for hiding this comment

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

no worries, @souvlakias is on it, he's also referencing the dependencies where appropriate (e.g. for layout lib and compose renderer)

Copy link
Contributor

Choose a reason for hiding this comment

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

we can do the android specifics later, for now let's go for the easy maven deps. We'll need to do some investigation for those as some of them depend on the android Sdk too.

Copy link
Member

Choose a reason for hiding this comment

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

If we need to customize the repos or other stuff, just create a second dummy module.

@lefou lefou added the post-review-required A merged PR which has still open comments or questions, which need to be clarified label Jun 30, 2025
@lefou lefou removed the post-review-required A merged PR which has still open comments or questions, which need to be clarified label Jun 30, 2025
lihaoyi added a commit that referenced this pull request Jul 1, 2025
…5399)

Extension PR of #5392, resolves
#5392 (review)
Notes:
- Added an Android Dummy module since it has a different dependency
resolution (MavenRepo)
- In build info we extract not the whole maven dep but just the
versions, so they can be easily overridden.

Thanks @lefou for your
[draft](#5397), and please let
me know if there's anything to fix/add.

---------

Co-authored-by: Li Haoyi <[email protected]>
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
Co-authored-by: Tobias Roeser <[email protected]>
lihaoyi pushed a commit that referenced this pull request Jul 4, 2025
Should resolve #5426 where
ui-tooling was having dependency conflicts.
Ui-tooling is a special case and will be handled differently, so we
remove it from the `updateable` packages sequence.
In addition, we extracted `screenshotValidationJunitEngine`s hardcoded
value that was a leftover from
#5392.
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.

4 participants