Amol Grover

As indicated by the traceback, [this line](https://gitlab.com/coala/package_manager/blob/master/dependency_management/requirements/RscriptRequirement.py#L48) is the cause of error: ``` if version: raise NotImplementedError( 'Setting version is not implemented by JuliaRequirement') ``` If a version string is...

Are these 2 the only bears throwing this error? In that case, we can remove the version string from both of them. Though we have other alternatives aswell: 1. implement...

@jayvdb Currently, the `generate_bear_requirement.py` gets the version number from each bears' `.py` file and then generates a curated list of requirements as `bear-requirements.yaml`. In this [issue](https://gitlab.com/coala/package_manager/issues/5), the `NotImplementedError` exception was...

> Well the YAML doesnt give a false expectation -- it only describes the bears. I was referring to the `version` argument passed during instantiation of `RscriptRequirement` as stated by...

> Those entries are not redundant - they are the mechanism by which we will be able to create installers which can choose versions, or fail to install problematic versions....

> Also we do have a hosted version of coala inside the deployed coala webservices (fully functional, exposed via an API) Which deployed web service are we talking about here?...

My bad. Can see them now. I was looking for the report link in the uncompleted projects.

Sidenote: You may want to check everything in the checklist

Here's the [gist](https://gist.github.com/frextrite/76dd5fe8031c8d7c856ccef67fa7121f) While testing I found 2 things 1. Removing `set -e` makes the script work perfectly. Does this mean the script is exiting somewhere with non zero status?...

I am facing the same issue ``` ##[error]HttpError: Resource not accessible by integration ##[error]Resource not accessible by integration ##[error]Node run failed with exit code 1 ```