-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Coverage binaries prevent usage of shacles #224
Comments
It's strange...I have just cloned it into a new folder and When did you clone it? because I had detected that issue about the coverage code and I had tried to repair it... |
I've just cloned it right now and still see the problem:
|
Could it be that it works in your case because you effectively have the file in |
You were right!, I think it has been solved in the new commit updating the shacl-s version. Thanks for spotting the problem, and the solution! |
Ummm...I stil think it is failing. I tried to change .travis.yml to use also scala 2.12.10 and now it fails. My guess is that the coverage code has been included in the scala 2.12 binaries for some reason. But I don't know why. In order to publish, the command we run is:
|
Yep, it doesn't work locally neither. I guess one of your published dependencies still has that coverage. I you only need to do the coverageOff when doing an interactive session. Starting sbt from the console and doing I think you best option is to publish artefacts only from Travis and bump versions in all libraries. Then you'll have your reproducible environment. |
Also make sure that your repo forbids overwriting artefacts, the moment something is published remains forever. I say so because I'm using the exact same version of shex in my own project and it works, so maybe on this library (or other) the binary got overwritten. |
Is this solved now? I still get the exception from above. |
We thought it was solved...but maybe it isn't. We will try to check which of the published libraries is generating the problem. If you know a way to detect the library, it would be great...the problem is that the only way we found was to go one by one library re-publishing it without the coverage code. |
Sorry, I have no idea how to identify the respective library. |
When trying to run shaclex from command line I get errors about coverage files not present in my path. Just cloning a master and running it we get:
The text was updated successfully, but these errors were encountered: