{ "id": "63633", "key": "TIMOB-3001", "fields": { "issuetype": { "id": "2", "description": "A new feature of the product, which has yet to be developed.", "name": "New Feature", "subtask": false }, "project": { "id": "10153", "key": "TIMOB", "name": "Titanium SDK/CLI", "projectCategory": { "id": "10100", "description": "Titanium and related SDKs used in application development", "name": "Client" } }, "fixVersions": [], "resolution": { "id": "7", "description": "", "name": "Invalid" }, "resolutiondate": "2011-04-15T03:34:27.000+0000", "created": "2011-04-15T03:34:26.000+0000", "priority": { "name": "Trivial", "id": "5" }, "labels": [ "feature", "request" ], "versions": [], "issuelinks": [], "assignee": { "name": "rseagraves", "key": "rseagraves", "displayName": "Reggie Seagraves", "active": true, "timeZone": "America/Los_Angeles" }, "updated": "2017-03-09T23:01:58.000+0000", "status": { "description": "The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.", "name": "Closed", "id": "6", "statusCategory": { "id": 3, "key": "done", "colorName": "green", "name": "Done" } }, "components": [ { "id": "10206", "name": "iOS", "description": "iOS Platform" } ], "description": "{html}
Feature request - please move the i18n folder within Resources.\nThis will make it easier to manage version control with SVN/etc. I\ncould then version control the Resources folder for a project and\nknow I'd be grabbing all the files needed to re-create the project\nor a development stage.
\nI don't use version control on the PROJECT folder because build\nfolder is dynamic and I don't want to waste repository space for\nit.
Just for information: You could use the PROJECT folder and just\nset a svn:ignore property on the build folder. So it will not be\ncommited on \"svn commit\" or displayed on \"svn status\"...
No reason to do this. Files other than Resources also need to be\naccounted for as part of a project (manifest, tiapp.xml, build\nfolders, etc).