You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cordova.apache.org by "Filip Maj (JIRA)" <ji...@apache.org> on 2017/07/15 03:55:00 UTC

[jira] [Commented] (CB-11581) Add target configuration support and management

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

Filip Maj commented on CB-11581:
--------------------------------

I know there is some appetite for the different-environment use case you present.

Having multiple config.xml's opens up a whole new can of worms: when issuing cordova commands (platform/plugin ones, for example), you'd have to have the ability to specify against which config.xml (or both / all?). Lots of potential pitfalls here to think through.

I think first the idea needs to be more fleshed out and a vision for the workflow needs to be articulated.

> Add target configuration support and management
> -----------------------------------------------
>
>                 Key: CB-11581
>                 URL: https://issues.apache.org/jira/browse/CB-11581
>             Project: Apache Cordova
>          Issue Type: New Feature
>          Components: cordova-cli
>         Environment: N/A
>            Reporter: Ricardo Panaggio
>
> It would be awesome if it was possible to set target configuration. This would interact with the build-related tools, which would expect (possibly) different targets, instead of assuming a single target. This could be used by some people to maintain within a single project several different environments (i.e. development, qa, production, ...), several different build types (i.e. demo, full, deluxe, ...), and I'm sure many other uses would come up.
> This is a major change, and probably something that needs to be widely discussed before it's implemented, but something like supporting several config.xml (one per target) could be a good start, opening a great new avenue to improve this side of the CLI and Cordova tools in a broader way.
> For instance, if we had two targets (say, dev and prod) and we would like to build them on iOS, the CLI could be called like:
> ```
> $ cordova build ios # for the default target, say dev (and nothing different from current syntax)
> $ cordova build ios:prod # for the production target, defined by prod.config.xml or config.prod.xml, or some other convention/configuration
> ```



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org