-
Notifications
You must be signed in to change notification settings - Fork 25.2k
SQL: incorrect artifactId inside the JDBC Maven pom #34399
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
Labels
Comments
Pinging @elastic/es-search-aggs |
@nik9000 if you could have a look at this one, I would appreciate it. |
nik9000
added a commit
to nik9000/elasticsearch
that referenced
this issue
Oct 15, 2018
We're publishing jdbc into our maven repo as though its artifactId is `x-pack-sql-jdbc` but the pom listed the artifactId as `jdbc`. This fixes the pom to line up with where we're publishing the artifact. Closes elastic#34399
nik9000
added a commit
that referenced
this issue
Oct 16, 2018
We're publishing jdbc into our maven repo as though its artifactId is `x-pack-sql-jdbc` but the pom listed the artifactId as `jdbc`. This fixes the pom to line up with where we're publishing the artifact. Closes #34399
nik9000
added a commit
that referenced
this issue
Oct 16, 2018
We're publishing jdbc into our maven repo as though its artifactId is `x-pack-sql-jdbc` but the pom listed the artifactId as `jdbc`. This fixes the pom to line up with where we're publishing the artifact. Closes #34399
kcm
pushed a commit
that referenced
this issue
Oct 30, 2018
We're publishing jdbc into our maven repo as though its artifactId is `x-pack-sql-jdbc` but the pom listed the artifactId as `jdbc`. This fixes the pom to line up with where we're publishing the artifact. Closes #34399
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
At the moment (6.4.2), we state in the documentation that the JDBC jar has the
artifactId
asx-pack-sql-jdbc
, but the pom itself is incorrect with respect to theartifactId
:The text was updated successfully, but these errors were encountered: