Results 1 to 3 of 3

Thread: SDK under Source Control / Revision Control?

  1. #1
    Sencha User
    Join Date
    Feb 2012
    Vote Rating

    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 - Sr Software Engineer mitchellsimoens's Avatar
    Join Date
    Mar 2007
    Gainesville, FL
    Vote Rating


    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
    Sencha Inc, Senior Software Engineer
    Learn BBCode and use it!

    Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2

    Think my support is good? Get more personalized support via a support subscription.

    Need more help with your app? Hire Sencha Services

    Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is in print!

    When posting code, please use BBCode's CODE tags.

  3. #3
    Sencha User
    Join Date
    Apr 2012
    Vote Rating

    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