[ 
https://issues.apache.org/jira/browse/CB-11374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15471792#comment-15471792
 ] 

Joe Bowser edited comment on CB-11374 at 9/7/16 9:03 PM:
---------------------------------------------------------

The more I read about applicationId, the less I think this needs to be changed 
from the status quo, and the more I think we need re-do our whole build to be 
more gradle friendly.  I don't think that config.xml is the right place to add 
this support.


was (Author: bowserj):
The more I read about applicationId, the less I think this needs to be changed, 
and the more I think we need re-do our whole build to be more gradle friendly.  
I don't think that config.xml is the right place to add this support.

> 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]

Reply via email to