kalencaya opened a new issue #1463:
URL: https://github.com/apache/incubator-seatunnel/issues/1463


   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/incubator-seatunnel/issues?q=is%3Aissue+label%3A%22bug%22)
 and found no similar issues.
   
   
   ### What happened
   
   location on `seatunnel/pom.xml`, `flink-connector-jdbc_2.11` scope is 
`provided` and seatunnel release doesn't contain flink-connector-jdbc 
dependency.
   ```
   <flink.scope>provided</flink.scope>
   
   ......
   
   <dependency>
       <groupId>org.apache.flink</groupId>
       <artifactId>flink-connector-jdbc_${scala.binary.version}</artifactId>
       <version>${flink.version}</version>
       <scope>${flink.scope}</scope>
   </dependency>
   ```
   The same problem is MySQL JDBC driver dependency, and for license 
compliance, we have to warn people adding driver by themselves.
   ```
   <!--Because the license is not in compliance, if you need to use MySQL, you 
can add it yourself-->
   <dependency>
       <groupId>mysql</groupId>
       <artifactId>mysql-connector-java</artifactId>
       <version>${mysql.version}</version>
       <scope>test</scope>
   </dependency>
   ```
   
   
   ### SeaTunnel Version
   
   dev
   
   ### SeaTunnel Config
   
   ```conf
   not needed
   ```
   
   
   ### Running Command
   
   ```shell
   not needed
   ```
   
   
   ### Error Exception
   
   ```log
   not needed
   ```
   
   
   ### Flink or Spark Version
   
   _No response_
   
   ### Java or Scala Version
   
   _No response_
   
   ### Screenshots
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [X] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to