Add Webapp to the root sbt project

[bhargav]

Add Webapp to the root sbt project so that we can compile and test it in our CI.

[kordjamshidi]

The webApp needs an update still does not work with the recent changes, it seems. This is what I get when running spam example.

error: line 34: value testWith is not a member of object test.spamDataModel
spamDataModel.testWith(testData)
^
error: line 48: value testWith is not a member of object test.spamDataModel
spamDataModel.testWith(testData)
^
error: line 59: value testWith is not a member of object test.spamDataModel
spamDataModel.testWith(testData)
^
error: line 74: java.net.URL does not take parameters
deserializedSpamClassifier.load(spamClassifier.lcFilePath(), spamClassifier.lexFilePath())
^
error: line 74: java.net.URL does not take parameters
deserializedSpamClassifier.load(spamClassifier.lcFilePath(), spamClassifier.lexFilePath())
^

[kordjamshidi]

@bhargav : any input for this? it needs update with the latest changes. @danyaljj I wonder whether semaphore cares about the tests in the webApp? How we have been able to merge when the tests there are failing?

[danyaljj]

I think this needs non-trivial changes/fixes. I won't get to it before weekend. If you need it now, feel free to dig in.

[kordjamshidi]

which part: to fix it to run? or to make Semaphore use the tests?

[danyaljj]

Either.

[bhargav]

Right now Semaphore does not compile or test the web-app. This ticket was opened to make sure that semaphore builds and runs the test on the web-app code.

[kordjamshidi]

I see. Ok. The other part was a question for @bhargav if he can update the webApp with the latest name changes.

[bhargav]

Tried with updated code but get the following error. Any ideas @danyaljj

Changes are in https://github.com/bhargav/saul/tree/webapp-content-fix

warning: line 0: Class de.bwaldvogel.liblinear.SolverType not found - continuing with a stub.
error: line 0: missing or invalid dependency detected while loading class file 'Logging.class'. Could not access type Logger in value org.slf4j, because it (or its dependencies) are missing. Check your build definition for missing or conflicting dependencies. (Re-run with `-Ylog-classpath` to see the problematic classpath.) A full rebuild may help if 'Logging.class' was compiled against an incompatible version of org.slf4j.
error: line 0: missing or invalid dependency detected while loading class file 'Logging.class'. Could not access term slf4j in package org, because it (or its dependencies) are missing. Check your build definition for missing or conflicting dependencies. (Re-run with `-Ylog-classpath` to see the problematic classpath.) A full rebuild may help if 'Logging.class' was compiled against an incompatible version of org.
error: line 0: missing or invalid dependency detected while loading class file 'Logging.class'. Could not access term ch in package , because it (or its dependencies) are missing. Check your build definition for missing or conflicting dependencies. (Re-run with `-Ylog-classpath` to see the problematic classpath.) A full rebuild may help if 'Logging.class' was compiled against an incompatible version of .
error: line 0: missing or invalid dependency detected while loading class file 'Logging.class'. Could not access term qos in value ch, because it (or its dependencies) are missing. Check your build definition for missing or conflicting dependencies. (Re-run with `-Ylog-classpath` to see the problematic classpath.) A full rebuild may help if 'Logging.class' was compiled against an incompatible version of ch.
error: line 0: missing or invalid dependency detected while loading class file 'Logging.class'. Could not access term logback in value .qos, because it (or its dependencies) are missing. Check your build definition for missing or conflicting dependencies. (Re-run with `-Ylog-classpath` to see the problematic classpath.) A full rebuild may help if 'Logging.class' was compiled against an incompatible version of .qos.
error: line 0: missing or invalid dependency detected while loading class file 'Logging.class'. Could not access term core in value .logback, because it (or its dependencies) are missing. Check your build definition for missing or conflicting dependencies. (Re-run with `-Ylog-classpath` to see the problematic classpath.) A full rebuild may help if 'Logging.class' was compiled against an incompatible version of .logback.
error: line 0: missing or invalid dependency detected while loading class file 'Logging.class'. Could not access term classic in value .logback, because it (or its dependencies) are missing. Check your build definition for missing or conflicting dependencies. (Re-run with `-Ylog-classpath` to see the problematic classpath.) A full rebuild may help if 'Logging.class' was compiled against an incompatible version of .logback.

[danyaljj]

My 20 cents is that, the logger inside Saul-core gets overriden by the Webapp's (Play's?) logger dependency. I would exclude the logging that Play brings in. (one easy way of inspecting this might be using the dependency graph plugin: > sbt dependencyGraph I think)

[kordjamshidi]

@bhargav

[danyaljj]

I will look into the issue.

[bhargav]

I had tried removing the logging dependency and it did not work then. Hope Daniel figures out how to handle this.

[danyaljj]

@onlinecco you think you can have a look at this?