-
Notifications
You must be signed in to change notification settings - Fork 92
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 support for org.apache.commons:commons-dbcp2:2.9.0
#224
Conversation
317383c
to
a941fc5
Compare
a941fc5
to
bc4a1be
Compare
bc4a1be
to
53ae997
Compare
76ca968
to
5d08c45
Compare
5d08c45
to
d8eae9c
Compare
|
@linghengqian there are a lot of tests in this PR. Did you write all of those tests, or they were copied from somewhere? Also, is it possible to have the same coverage of metadata with fewer tests? |
|
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.
Including this file (and probably many of the others) is a copyright violation. It is copied from https://commons.apache.org/proper/commons-dbcp/xref-test/org/apache/commons/dbcp2/managed/TestManagedDataSourceInTx.html which clearly is under Apache License. Neither can we simply copy this file without further approvals, nor - and this is an absolute no-go - can we change the license. @dnestoro @vjovanov
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.
-
@wirthi Hi, I can do a massive rewrite of this PR with known test coverage. How about this proposal?
-
The Git of the DBCP ontology does not hook into the conditions of the Maven Plugin test of GraalVM Native Build Tools, because some tests are not compatible with GraalVM.
|
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.
What does this PR do?
org.apache.commons:commons-dbcp2:2.9.0
#202 .Checklist before merging