nasa/mct — pull request #143 by VWoeltjen (2013-08-12 23:53:52+00:00)
Title: [Launcher] Modify build & start-up code to allow MCT to launch without arguments

Modification support simplified launch specified in #109 (that is, remove need for ant script or complicated command line invocation) as follows:

* Move startup.jar to top-level of MCT distribution archive to act as primary executable jar
* Bundle Derby & MySQL connectors in databasePersistence such that they no longer need to be added to boot classpath
* Change default properties configurations to those appropriate for a first-time developer or evaluator (creates Derby db, for instance)
* Specify certain needed run-time properties (such as rwRoot) to useful defaults if they are unset
* Show user-selection dialog if mct.user has not been set on command line (also, create non-MCC-specific Identity Manager to support this)

Wrote or re-wrote unit tests (Y/N): Y
Ran entire suite of unit tests successfully (Y/N): Y
Verified bug fix with the described replication steps or verified the implementation meets the requirement cited (Y/N): Y
Code coverage requirements satisfied (new code=80%, changed code=at least as high as existing) (Y/N): Y
Code review date and attendees: Code review by pull request
Describe potential impact on other areas of the code: Startup, identity management
Describe any test prerequisites for this fix (e.g., restart the database): Clean rebuild from command line, attempt to invoke as "java -jar startup-1.8b3.jar"
For bugs marked "Regression - Yes", describe the cause of the regression: N/A
Did you modify any pom.xml file? If yes, did you thoroughly document your changes and reasons? Y (changes are documented in commit logs)