yuqi1129 opened a new issue, #4298:
URL: https://github.com/apache/gravitino/issues/4298

   ### Version
   
   main branch
   
   ### Describe what's wrong
   
   When running `gradle publishToMavenLocal -PdefaultScalaVersion=2.13`, we 
will meet the following error 
   
   <img width="1640" alt="image" 
src="https://github.com/user-attachments/assets/388f13b7-8d8c-44ca-b291-098fced732ad";>
   
   
   ### Error message and/or stacktrace
   
   ```
   * What went wrong:
   Execution failed for task ':flink-connector:compileJava'.
   > Could not resolve all files for configuration 
':flink-connector:compileClasspath'.
      > Could not find org.apache.flink:flink-connector-hive_2.13:1.18.0.
        Searched in the following locations:
          - 
https://repo.maven.apache.org/maven2/org/apache/flink/flink-connector-hive_2.13/1.18.0/flink-connector-hive_2.13-1.18.0.pom
          - 
file:/Users/yuqi/.m2/repository/org/apache/flink/flink-connector-hive_2.13/1.18.0/flink-connector-hive_2.13-1.18.0.pom
        Required by:
            project :flink-connector
   
   * Try:
   > Run with --stacktrace option to get the stack trace.
   > Run with --info or --debug option to get more log output.
   > Run with --scan to get full insights.
   > Get more help at https://help.gradle.org.
   
   Deprecated Gradle features were used in this build, making it incompatible 
with Gradle 9.0.
   
   You can use '--warning-mode all' to show the individual deprecation warnings 
and determine if they come from your own scripts or plugins.
   
   For more on this, please refer to 
https://docs.gradle.org/8.2/userguide/command_line_interface.html#sec:command_line_warnings
 in the Gradle documentation.
   
   BUILD FAILED in 2m 52s
   81 actionable tasks: 33 executed, 48 up-to-date
   ```
   
   ### How to reproduce
   
   Please see above.
   
   ### Additional context
   
   _No response_


-- 
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