cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tommy-carlos Williams <>
Subject Re: New directory structure in cordova-cli's future branch
Date Tue, 09 Apr 2013 20:48:45 GMT
Sorry, but as someone that helps users everyday, the almost "it's alpha, they shoulda seen
it coming" tone of this is a bit upsetting. 

It reminds me of before the deprecation policy, etc when PhoneGap would completely break everything
whenever a new version came out. 

I feel like we have come a long way since then (with a ways still to go, no question about
it).  I would hate to be the one in IRC and on the Google Group list having to explain this
to everyone using the cli. 

I was under the impression that the cli was "shipping" now, not just a little side thing.
I know that quite a few people are using it for real apps (myself included). If that is true,
then we have a duty to at least think very carefully before breaking something and come up
with a good plan for easing that transition. 

- tommy

On 10/04/2013, at 1:40, Braden Shepherdson <> wrote:

> This mailing list post is, or will shortly be, indexed by Google and
> others. Any newcomers will see the new docs and create new projects.
> As I mentioned on IRC, existing users are either accepting or ignoring the
> "alpha" warnings that this software is new and under heavy development, and
> if they want to jump on it early they're going to have to expect some pain.
> That said, I don't really know of any better way to socialize it. Is there
> anywhere where a brief blog post on this would make sense?
> I don't know how many people are using these tools and not on the mailing
> list, though certainly some turn up on IRC occasionally.
> Braden
> On Tue, Apr 9, 2013 at 11:24 AM, Filip Maj <> wrote:
>> How will we communicate this change to our existing users?
>> On 4/9/13 5:22 PM, "Braden Shepherdson" <> wrote:
>>> I've just pushed a change to the future branch that changes the directory
>>> structure to:
>>> app/
>>>   merges/
>>>       android/
>>>       ios/
>>>   www/
>>>   config.xml
>>> As was discussed at our video conference meeting a couple of weeks ago,
>>> this has a number of advantages:
>>> - config.xml is no longer in the www/ directory
>>> - One can easily version control the whole app/ directory, and get their
>>> web assets, merges and so on into the repo.
>>> - That repo can contain additional information: a, supplementary
>>> documentation, tests, whatever. The CLI will ignore anything outside of
>>> the
>>> merges and www directories.
>>> The downside is that this is a breaking change: running the new version of
>>> the tools on an old project will fail (but I think in a harmless way)
>>> until
>>> you rearrange the directories. You can do that with the following
>>> commands:
>>> $ mkdir app
>>> $ mv www/config.xml app
>>> $ mv www app
>>> $ mv merges app
>>> All docs and tests are updated as well. Any problems should be reported on
>>> JIRA and assigned to me.
>>> Braden

View raw message