-
Notifications
You must be signed in to change notification settings - Fork 14
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
CodeAnalyzer Update/Download Versioning #58
Comments
Hi @alibrahimzada Thanks for reporting this but this change was made on purpose. You should be using Release v0.1.4 of CLDK and installing it with: pip install cldk==0.1.4 The commit you pointed to ( BTW, Code Analyzer has moved to semantic versioning and no longer uses simple timestamps because they cannot convey the nuance of fixes, features, and breaking changes like semantic versioning can. |
Hi, @rofrano , I installed the CLDK with pip, but when running the demo raise a exception, like:
I try to download the
Although analysis can be initialized, run tothe for loop, the
I'm sure there's code in the |
Reopening this to that the team can take a look at it. @rahlk |
Thanks @alibrahimzada @rofrano, I will investigate this issue. |
@alibrahimzada can you check to see if this issue still persists in the lastest CLDK? (version v0.3.0) |
I didn't have any problems when I did |
@alibrahimzada , I reopened if because @zhangxii found a problem that we still need to investigate. I'm glad it's working for you. |
There is a problem when downloading the latest codeanalyzer. In https://github.com/IBM/codenet-minerva-code-analyzer/releases, the last two releases do not have datetime format in the release name (instead its
v1.0.1
). Also the last release adds an extra-1.0.1
in the.jar
file name. As a result this line never becomesTrue
. I think a good solution would be to continue releasing with proper tag name (e.g.,YYYYMMDDTHHMMSS
) and.jar
file name (e.g.,codeanalyzer.jar
) in https://github.com/IBM/codenet-minerva-code-analyzer, and add a rule to make sure there is no conflict in tag and file names in the future.The text was updated successfully, but these errors were encountered: