Java issue detection

[thelastinuit]

Weird stuff: somehow when it analyze a java web app project, it triggers belugas-ruby.

[thelastinuit]

Btw, I have my reasons to believe that Belugas-Linguist can't recognize Java projects. Belugas-Java can recognize them, though.

[vovimayhem]

@thelastinuit we need some sort of project library for both belugas and whales, so we have a common ground and see why they are not behaving the way we're expecting to...

A static code analysis needs code, not artifacts, to do it's stuff. belugas-linguist figures out the language used by the code of the project. Won't actually work if there's no code to analyze.

We could do some sort of artifact analysis on the belugas-java side, if no code is available. But that would make belugas-java not dependant of belugas-linguist, requiring it to do it's own checks to see if it continues to run or not.

Can't do nothing in any case if I don't have access to whatever you tried to analyze.

[thelastinuit]

For Java Web Apps I just noticed that you can get enough information for production deployment. But yeah there is no code and linguist fails.
I want to believe that it's a plus that Whales brings to the game, right?