[
https://issues.apache.org/jira/browse/CB-11374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15472014#comment-15472014
]
Joe Bowser commented on CB-11374:
---------------------------------
[~kikoalemao] The applicationId changing is an advanced Android build feature
and 90% of the time it is the same as the package id. There are certain
circumstances where it's not the application ID, and we need to anticipate
those, but I don't know if adding support to config.xml or the CLI makes a
whole lot of sense, since the people using these builds would already be
editing the gradle anyway.
If we're going to do this, we should probably wait until we redo the whole way
we build Android apps, IMO, and sadly that's a long ways off unless we get more
contributors helping out.
> 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]
