Avoiding Hiccups in Building Oracle JET Applications
By Geertjan-Oracle on Aug 27, 2016
The first time you do this, you'll be prompted as follows:
Say Yes and you'll be here (your version of the below may be different to mine since I'm using a development build of NetBeans IDE):
Note that I checked the "Build Project" checkbox, which has "build" in there by default. When I click OK out of the dialog above, and then try to build the project again, I see the following in the Output window:
"C:\nodejs\grunt.cmd" "build" Running "build" task Running "oraclejet-build:undefined" (oraclejet-build) task Oracle JET Grunt plugin Processing Grunt command... [Warning] Missing platform. Default to web. Theme Name:Platform - alta:web Theme Version - 2.1.0 cleaning staging path..... copy files to staging directory..... copy finished... compiling sass.... sass compile skipped... running theme injection task..... indexHtml theme path injection finished.. running theme copy task..... theme copy finished... running injection task..... mainJs paths injection finished.. Done. Done.
At this point, you need to be very careful. The process above has created a "web" folder, as shown below:
Note: The "web" folder is where things need to be "run" from to see the real app, while the source files should only be edited in the "src" folder. Be careful that you do not run into the issue of editing the "web" files and then losing your work when you do the next build. Be aware that the "web" folder is completely overwritten when you do a build.
Only after you have done the build, can you do "grunt serve", which will serve up the application into the platform of choice, which is the browser by default.