THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
TEZ UI depends on Maven and Yeoman standards for the directory structure.
Color codes
■ Maven
■ Yeoman/Ember
Directory hierarchy:
I have just listed things that some one must know to start working with the system. There are configurations files that I have omitted. feel free to modify.
- tez - Repo root
- Other TEZ files and directories
- tez-ui
- pom.xml - Maven configuration file
- target - The web tar and Ambari jar can be found here post build
- src
- assembly - Maven plugin for creating the web tar
- main
- java - For Ambari view
- resources - For Ambari view
- webapp
- package.json - Define node js dependencies -> node_modules
- bower.json - Define bower dependencies -> app/bower_components (.bowerrc)
Gruntfile.js - Web build script. For minification, compilation, unit testing, linting etc...
- dist - Created by grunt to put the final files for distribution
node_modules
- test
- app
- index.html - The first file that would be loaded, all the scripts and styles will be linked in it.
- bower_components
- images
- styles - Less files
- templates - Handlebar files
- scripts
- app.js - Where everything start
- router.js
- controllers
- models
- routes
- views
- components
- components
- helpers
- adapters
- Other TEZ files and directories