TEZ UI depends on Maven and Yeoman standards for the directory structure.
Color codes
■ Maven standard
■ Additional files
■ Yeoman/Ember standard
Directory hierarchy:
I have just listed things that devs must know to start working. 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
- README.TXT
- target - On maven build the tar and war would be put here
- src
- assembly - Maven plugin for creating the web tar
- main
- resources - xml that must be included in war file.
- 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...
- app
- index.html - The first file that would be loaded, index the loads all scripts and style files.
- img
- styles - Less files
- templates - Handlebar files
- scripts
- app.js - Where everything start
- router.js
- configs.js
default-configs.js
- controllers
- models
- routes
- views
- components
- helpers
- adapters
- Other TEZ files and directories