Take a copy of a build.xml from CFInternet 2.10 or CFCrm 2.10 and place it in your manufactured project's java directory. Edit the build.xml to replace the version numbers, source directory names, and so on with the names associated with your project. Note the presence of the various "custom" directories -- you'll use those in the future if you are customizing your user interface code for the project, and will have to create them and their source trees by hand.
You can also copy and modify the Package* and Archive* scripts, provided that you create an "installer" directory under your project's java directory.
For now remove the dependencies on the "custom" targets from the "alljars" and "compileall" targets of the build.xml so you don't get "missing directory" errors during your build.
Manually create the java/bin and java/tomcat8jars directories, and populate them with the jar files from the project you copied. All projects use a common set of jars.
You should be able to do an "ant" in your project's java directory now, and see it build your source tree. Presuming your build.xml was correctly migrated, you should see everything compile, get packaged in jars, and 14 files copied to the WebContent directories of the web server projects.
You won't have any *custom* source trees, so remove those dependencies from the compileall and alljars targets of your build.xml.
Note that I've had some issues with Oracle JDK 8 for MSS Code Factory itself, so I stick with Open JDK 8. However, Oracle JDK 8 will build those javafx directories successfully, and it is only in the MSS Code Factory CFCore code that a problem arises with Oracle JDK 8 being too aggressive about optimization, so give Oracle JDK 8 a shot if you wish.