[
https://issues.apache.org/jira/browse/CB-11374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15472358#comment-15472358
]
Frederico Costa Galvão commented on CB-11374:
---------------------------------------------
I understand the general idea of trying to wait for the full implementation, I
really do and agree, but I don't know what bad would it make to make
config.xml#root.android-applicationId available, which if present, would output
it's value to build.gradle in the line where it sets applicationId in the
android block. That is, by the way, exactly what I do right now, but in my case
I need to either change it by hand or automate a string replacement which
doesn't play well with platform upgrades or new environments.
> Support applicationId for android on config.xml
> -----------------------------------------------
>
> Key: CB-11374
> URL: https://issues.apache.org/jira/browse/CB-11374
> Project: Apache Cordova
> Issue Type: New Feature
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Android, CLI
> Affects Versions: 6.2.0
> Reporter: Frederico Costa Galvão
> Assignee: Joe Bowser
>
> After discovering these hidden/undocumented options \[1\], while trying to
> set up my cordova project to be whitelabel-friendly, I realized that a
> *android-applicationId* setting should be made available on config.xml now
> that android decoupled *applicationId* from *packageName*.
> An initial PR related to this topic was
> https://github.com/apache/cordova-android/pull/247, but the "more robust"
> thing was left for later. This second step should be fairly easy to set up, I
> guess.
> \[1\] https://issues.apache.org/jira/browse/CB-11373
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
