Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-8662] Tooling: Write a CLI specification

GitHub Issuen/a
TypeSub-task
PriorityHigh
StatusClosed
ResolutionFixed
Resolution Date2012-10-07T20:06:29.000+0000
Affected Version/sn/a
Fix Version/sRelease 2.1.0, Sprint 2012-09 Core
ComponentsTooling
Labelscore
ReporterMarshall Culpepper
AssigneeStephen Tramer
Created2012-04-10T15:41:03.000+0000
Updated2012-10-07T20:06:29.000+0000

Description

Write a CLI specification that covers: * CLI workflow * Argument naming and value standards * Initial set of CLI commands * Initial set of CLI arguments * External CLI APIs (for CLI modules) The target list of commands should contain: * Validation of project (module+app) creation arguments per platform * Project creation - modules + apps * Project migration between Titanium SDK versions * Per-platform setup * Environment / project validation * Build project (APK, IPA, deployable web app in MobileWeb) * Publish (may be type of build) * Obfuscation/minification * Optional Lint * Emulator/Simulator launch * Deploy project (to a device, to an emulator) * Debugger / REPL Other requirements that were gathered: * Studio needs standardized logging and errpr message parsing * Standard interfaces to basic commands across platforms * Have a list of command capabilities / implementations per platform

Comments

  1. Stephen Tramer 2012-04-11

    Do we have any existing information on the initial CLI spec from last June? Did we take photos or notes, or is that all lost?
  2. Marshall Culpepper 2012-04-20

    AFAIK the list is completely lost, we will have to continue using the high level requirements we collected from our CLI meeting
  3. Stephen Tramer 2012-04-24

    Driving CLI spec w/input from all core members
  4. Stephen Tramer 2012-04-30

    [CLI spec](https://wiki.appcelerator.org/display/spe/Command+Line+Interface) has been taken to internal RFC: This ticket will remain open until RFC is closed (5/7) and comments from internal RFC are resolved. We will make the spec available for community input after internal RFC.
  5. Stephen Tramer 2012-05-04

    Resolving this ticket a little early; comments from RFC appear to have ended and I don't anticipate any more by EOB Monday. There may be a second email blast.
  6. Ingo Muschenetz 2012-10-07

    Reopened to fix remaining estimates.

JSON Source