-
Notifications
You must be signed in to change notification settings - Fork 147
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
Add conformance tests #35
Conversation
6767541
to
f112d11
Compare
* Add kotlin-gradle app * Rename java-gradle to kotlin-gradle to expand language coverage * Add travis configuration Signed-off-by: Javier Romero <jromero@pivotal.io>
7585a9b
to
747afbe
Compare
747afbe
to
fed9130
Compare
Signed-off-by: Javier Romero <jromero@pivotal.io>
fed9130
to
9040645
Compare
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.
I'm worried that we'll have trouble keeping the example app up-to-date, but I don't think that should block this.
If we can't auto depend on latest fixes maybe we could setup a vetting process on the apps that run as part of CI as well. Something like OWASP dependency check: https://jeremylong.github.io/DependencyCheck/dependency-check-gradle/index.html |
Resolves #31
Signed-off-by: Javier Romero jromero@pivotal.io