-
Notifications
You must be signed in to change notification settings - Fork 12
Simple workaround for scanning scala projects #301
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
Conversation
|
@biswajit-patra-dev please remove the CodeScene workflow 😊 so pipeline will pass |
|
@sweoggy I have removed the CodeScene workflow as suggested. |
sweoggy
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The Dockerfile changes look good and the general idea of this PR 👍
I have not tested nor reviewed the functionality of the Go code, I will let someone else with more experience review those parts
|
Here is the test scan result. |
3a985b2 to
182966c
Compare
2963126 to
6fdeb83
Compare
|
Lgtm! |
Added support sbt package support.
build.sbtfile to identify any modulessbt makePomin the project directory to generate a POM file.pomfile (typically intarget/scala-<version>/<project>-<version>.pom).pomfile topom.xmlin the same directory asbuild.sbtpom.xmlfile