-
-
Notifications
You must be signed in to change notification settings - Fork 419
Android release docs #5957
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
base: main
Are you sure you want to change the base?
Android release docs #5957
Conversation
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") } |
There was a problem hiding this comment.
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> |
There was a problem hiding this comment.
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
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 |
Lgtm |
Uh oh!
There was an error while loading. Please reload this page.