Skip to content

Conversation

vaslabs
Copy link
Contributor

@vaslabs vaslabs commented Oct 6, 2025

Docs specific for android release configuration

def androidReleaseKeyName: Option[String] = Some("releaseKey.jks")
def androidReleaseKeyAlias: T[Option[String]] = Task { Some("releaseKey") }
def androidReleaseKeyPass: T[Option[String]] = Task { Some("MillBuildTool") }
def androidReleaseKeyStorePass: T[Option[String]] = Task { Some("MillBuildTool") }
Copy link
Contributor Author

@vaslabs vaslabs Oct 6, 2025

Choose a reason for hiding this comment

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

Let's provide here a good default guide, perhaps with env vars

> keytool -genkey -v -keystore releaseKey.jks \
-storepass <PASS> -keyalg RSA \
-keysize 2048 -validity 10000 \
-alias releaseKey -keypass <PASS>
Copy link
Contributor Author

Choose a reason for hiding this comment

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

"$KEYTOOL_PASS" maybe, and use the same name above like, Task.env

@vaslabs
Copy link
Contributor Author

vaslabs commented Oct 6, 2025

Looking at the current docs we have, I'm wondering how we can make this more user friendly. Perhaps having something like app.release.androidApk , with release being an inner trait, or app.androidReleaseApk but I think with mill's design the former could work better. Of course this is not in the scope of this PR

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