Added more nb project files

.travis.yml

@@ -1,5 +1,6 @@
-language: node_js
-node_js: 8
+language: java
+jdk:
+- oraclejdk8
 sudo: required
 git:
   depth: 5
@@ -9,7 +10,7 @@ branches:
   - master
 cache:
   directories:
-  - "./application/node_modules"
+  - "./analytics/WEB-INF/lib"
 before_install:
 - if [ "$TRAVIS_BRANCH" == "master" ] && [ "$TRAVIS_PULL_REQUEST" = "false" ] ; then ./travis_scripts/install_compose.sh ; fi
 - cd application

Dockerfile

@@ -5,7 +5,7 @@ MAINTAINER "Dejan Paunovic <[email protected]>"
 ENV SERVICE_URL_ACTIVITIES https://activitiesservice.experimental.slidewiki.org
 # ENV SERVICE_URL_ACTIVITIES http://172.17.42.1:5000
 
-ADD ./analytics /usr/local/tomcat/webapps/analytics
+ADD ./build/web /usr/local/tomcat/webapps/analytics
 RUN mkdir /home/prediction
 ADD ./temp_test.txt /home/prediction/temp_test.txt
 

build.xml

@@ -0,0 +1,71 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!-- You may freely edit this file. See commented blocks below for -->
+<!-- some examples of how to customize the build. -->
+<!-- (If you delete it and reopen the project it will be recreated.) -->
+<!-- By default, only the Clean and Build commands use this build script. -->
+<!-- Commands such as Run, Debug, and Test only use this build script if -->
+<!-- the Compile on Save feature is turned off for the project. -->
+<!-- You can turn off the Compile on Save (or Deploy on Save) setting -->
+<!-- in the project's Project Properties dialog box.-->
+<project name="Analytics" default="default" basedir=".">
+    <description>Builds, tests, and runs the project Analytics.</description>
+    <import file="nbproject/build-impl.xml"/>
+    <!--
+
+    There exist several targets which are by default empty and which can be 
+    used for execution of your tasks. These targets are usually executed 
+    before and after some main targets. They are: 
+
+      -pre-init:                 called before initialization of project properties 
+      -post-init:                called after initialization of project properties 
+      -pre-compile:              called before javac compilation 
+      -post-compile:             called after javac compilation 
+      -pre-compile-single:       called before javac compilation of single file
+      -post-compile-single:      called after javac compilation of single file
+      -pre-compile-test:         called before javac compilation of JUnit tests
+      -post-compile-test:        called after javac compilation of JUnit tests
+      -pre-compile-test-single:  called before javac compilation of single JUnit test
+      -post-compile-test-single: called after javac compilation of single JUunit test
+      -pre-dist:                 called before archive building 
+      -post-dist:                called after archive building 
+      -post-clean:               called after cleaning build products 
+      -pre-run-deploy:           called before deploying
+      -post-run-deploy:          called after deploying
+
+    Example of pluging an obfuscator after the compilation could look like 
+
+        <target name="-post-compile">
+            <obfuscate>
+                <fileset dir="${build.classes.dir}"/>
+            </obfuscate>
+        </target>
+
+    For list of available properties check the imported 
+    nbproject/build-impl.xml file. 
+
+
+    Other way how to customize the build is by overriding existing main targets.
+    The target of interest are: 
+
+      init-macrodef-javac:    defines macro for javac compilation
+      init-macrodef-junit:   defines macro for junit execution
+      init-macrodef-debug:    defines macro for class debugging
+      do-dist:                archive building
+      run:                    execution of project 
+      javadoc-build:          javadoc generation 
+
+    Example of overriding the target for project execution could look like 
+
+        <target name="run" depends="<PROJNAME>-impl.jar">
+            <exec dir="bin" executable="launcher.exe">
+                <arg file="${dist.jar}"/>
+            </exec>
+        </target>
+
+    Notice that overridden target depends on jar target and not only on 
+    compile target as regular run target does. Again, for list of available 
+    properties which you can use check the target you are overriding in 
+    nbproject/build-impl.xml file. 
+
+    -->
+</project>

build/generated-sources/ap-source-output/rs/ac/bg/imp/analytics/prediction/entities/PredictionJob_.java

@@ -0,0 +1,23 @@
+package rs.ac.bg.imp.analytics.prediction.entities;
+
+import java.util.Date;
+import javax.annotation.Generated;
+import javax.persistence.metamodel.SingularAttribute;
+import javax.persistence.metamodel.StaticMetamodel;
+
+@Generated(value="EclipseLink-2.5.2.v20140319-rNA", date="2018-10-01T15:22:06")
+@StaticMetamodel(PredictionJob.class)
+public class PredictionJob_ { 
+
+    public static volatile SingularAttribute<PredictionJob, Double> result;
+    public static volatile SingularAttribute<PredictionJob, Integer> noOfDecks;
+    public static volatile SingularAttribute<PredictionJob, String> deckId;
+    public static volatile SingularAttribute<PredictionJob, Integer> noOfUsers;
+    public static volatile SingularAttribute<PredictionJob, Double> accuracy;
+    public static volatile SingularAttribute<PredictionJob, Date> started;
+    public static volatile SingularAttribute<PredictionJob, Date> finished;
+    public static volatile SingularAttribute<PredictionJob, Integer> id;
+    public static volatile SingularAttribute<PredictionJob, String> userId;
+    public static volatile SingularAttribute<PredictionJob, String> relatedPredictionActivityId;
+
+}