Directory Structure
Hubble follows a standary directory structure for Angular projects higer level division is by functionality and lower level dicision is by component types. Here is the relevant directory structure
.
├── segmentList
│ ├── SegmentListView.html
│ └── SegmentListCtrl.js
├── login
│ └── LoginController.js
├── libs
│ └── angular-ui-router.js
├── jquery
│ ├── jquery.ui.widget.js
│ ├── jquery.ui.tabs.js
│ ├── jquery.ui.position.js
│ ├── jquery.ui.menubar.js
│ ├── jquery.ui.menu.js
│ ├── jquery.ui.core.js
│ ├── jquery.ui.button.js
│ ├── jquery.layout-latest.js
│ ├── jquery-ui-1.10.4.custom.js
│ ├── jquery-1.10.2.js
│ └── jMenu.jquery.js
├── countryList
│ ├── CountryListView.html
│ └── CountryListCtrl.js
├── controllers.js
├── companyList
│ ├── CompanyListView.html
│ └── CompanyListCtrl.js
└── app.js
Hubble Build System
Build System: https://www.playframework.com/documentation/3.0.x/Build
Hubble Dependency Management
Dependency Management: https://www.playframework.com/documentation/2.0.4/SBTDependencies
If you update build.sbt to add any new library dependency, then you would need to regenerate the IDE files so that libraries are downloaded from the repository and added to Classpath. This is done by executing on Play console: idea [For Intellj] or eclipsify [For eclipse ]
Debugging
JPDA Transport mechanism http://docs.oracle.com/javase/7/docs/technotes/guides/jpda/conninv.html
The communication between VM being debugged and the debugger is connection oriented, i.e. the VM will act as a server and the debugger as a client (reverse is also possible). The VM needs to create a new socket, bind it to a port and listen for incoming connections from debugger. To do this, execute the following on the play console to create a JPDA port on which the debugger will attach.
activator -jvm-debug 9999
The following shows up on command line
[HubbleClient]
Type run to run the app