Results 1 to 3 of 3

Thread: SDK under Source Control / Revision Control?

  1. #1
    Sencha User
    Join Date
    Feb 2012
    Posts
    44
    Vote Rating
    3
      0  

    Default SDK under Source Control / Revision Control?

    A new empty project created by the 'sencha' tool has ~80MB of SDK copied into it. Is there a best practice for including or not including this in your project's source control repository (git, hg/Mercurial, etc.)?

    There seem to be valid arguments either way. Any convincing ones?

  2. #2
    Sencha User mitchellsimoens's Avatar
    Join Date
    Mar 2007
    Location
    Gainesville, FL
    Posts
    40,025
    Vote Rating
    1367
      0  

    Default

    I always include all but when I do a build for production then I limit what I put in to the minimum.
    Mitchell Simoens @LikelyMitch
    Modus Create, Senior Frontend Engineer
    ________________
    Need any sort of Ext JS help? Modus Create is here to help!

    Check out my GitHub:
    https://github.com/mitchellsimoens

  3. #3
    Sencha User
    Join Date
    Apr 2012
    Posts
    2
    Vote Rating
    0
      0  

    Default Is there a way to bootstrap the sdk into a project that is in SCM?

    Seems like keeping at bunch of generated code in a SCM is very wasteful, but I couldn't find any tool to put the sdk folder back into a project easily once I checked out the code. Does such a thing exist? Maybe add a sdk bootstrap command to the sencha tool?

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •