16 Mar 2012 2:50 PM #1
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?
19 Mar 2012 4:46 AM #2
- 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 @SenchaMitch
Sencha Inc, Senior Software Engineer
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. https://www.sencha.com/store/
Need more help with your app? Hire Sencha Services firstname.lastname@example.org
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.
24 Apr 2012 6:32 AM #3
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?