Fokko opened a new pull request, #3041:
URL: https://github.com/apache/avro/pull/3041

   This will avoid an error:
   
   ```
   [INFO] Reactor Summary for Apache Avro Java 1.12.0-SNAPSHOT:
   [INFO]
   [INFO] Apache Avro Java ................................... SUCCESS [  2.043 
s]
   [INFO] Apache Avro ........................................ SUCCESS [  8.623 
s]
   [INFO] Apache Avro Android Compatibility .................. SUCCESS [  1.571 
s]
   [INFO] Apache Avro IDL .................................... SUCCESS [  5.358 
s]
   [INFO] Apache Avro Compiler ............................... SUCCESS [  3.918 
s]
   [INFO] Apache Avro Maven Plugin ........................... SUCCESS [  4.313 
s]
   [INFO] Apache Avro IPC .................................... SUCCESS [  5.228 
s]
   [INFO] Apache Avro IPC Jetty .............................. SUCCESS [  2.087 
s]
   [INFO] Apache Avro IPC Netty .............................. SUCCESS [  2.386 
s]
   [INFO] Trevni Java ........................................ SUCCESS [  0.132 
s]
   [INFO] Trevni Java Core ................................... SUCCESS [  0.345 
s]
   [INFO] Apache Avro Mapred API ............................. SUCCESS [  8.466 
s]
   [INFO] Trevni Java Avro ................................... FAILURE [  2.180 
s]
   [INFO] Trevni Specification ............................... SKIPPED
   [INFO] Apache Avro Tools .................................. SKIPPED
   [INFO] Apache Avro Protobuf Compatibility ................. SKIPPED
   [INFO] Apache Avro Thrift Compatibility ................... SKIPPED
   [INFO] Apache Avro Maven Archetypes ....................... SKIPPED
   [INFO] Apache Avro Maven Service Archetype ................ SKIPPED
   [INFO] Apache Avro gRPC ................................... SKIPPED
   [INFO] Avro Integration Tests ............................. SKIPPED
   [INFO] Apache Avro Codegen Test dependencies .............. SKIPPED
   [INFO] Apache Avro Codegen Test ........................... SKIPPED
   [INFO] Apache Avro Performance Test Suite ................. SKIPPED
   [INFO] Apache Avro interop-data-test ...................... SKIPPED
   [INFO] 
------------------------------------------------------------------------
   [INFO] BUILD FAILURE
   [INFO] 
------------------------------------------------------------------------
   [INFO] Total time:  47.480 s
   [INFO] Finished at: 2024-07-24T10:18:12Z
   [INFO] 
------------------------------------------------------------------------
   [ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:3.8.0:jar (module-javadocs) on 
project trevni-avro: Execution module-javadocs of goal 
org.apache.maven.plugins:maven-javadoc-plugin:3.8.0:jar failed: Unable to 
derive module descriptor for 
/home/fokko.driesprong/.m2/repository/org/apache/hadoop/thirdparty/hadoop-shaded-protobuf_3_7/1.1.1/hadoop-shaded-protobuf_3_7-1.1.1.jar:
 hadoop.shaded.protobuf.3.7: Invalid module name: '3' is not a Java identifier 
-> [Help 1]
   [ERROR]
   [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
   [ERROR] Re-run Maven using the -X switch to enable full debug logging.
   [ERROR]
   [ERROR] For more information about the errors and possible solutions, please 
read the following articles:
   [ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
   [ERROR]
   [ERROR] After correcting the problems, you can resume the build with the 
command
   [ERROR]   mvn <args> -rf :trevni-avro
   ```
   
   <!--
   
   *Thank you very much for contributing to Apache Avro - we are happy that you 
want to help us improve Avro. To help the community review your contribution in 
the best possible way, please go through the checklist below, which will get 
the contribution into a shape in which it can be best reviewed.*
   
   *Please understand that we do not do this to make contributions to Avro a 
hassle. In order to uphold a high standard of quality for code contributions, 
while at the same time managing a large number of contributions, we need 
contributors to prepare the contributions well, and give reviewers enough 
contextual information for the review. Please also understand that 
contributions that do not follow this guide will take longer to review and thus 
typically be picked up with lower priority by the community.*
   
   ## Contribution Checklist
   
     - Make sure that the pull request corresponds to a [JIRA 
issue](https://issues.apache.org/jira/projects/AVRO/issues). Exceptions are 
made for typos in JavaDoc or documentation files, which need no JIRA issue.
     
     - Name the pull request in the form "AVRO-XXXX: [component] Title of the 
pull request", where *AVRO-XXXX* should be replaced by the actual issue number. 
       The *component* is optional, but can help identify the correct reviewers 
faster: either the language ("java", "python") or subsystem such as "build" or 
"doc" are good candidates.  
   
     - Fill out the template below to describe the changes contributed by the 
pull request. That will give reviewers the context they need to do the review.
     
     - Make sure that the change passes the automated tests. You can [build the 
entire project](https://github.com/apache/avro/blob/main/BUILD.md) or just the 
[language-specific 
SDK](https://avro.apache.org/project/how-to-contribute/#unit-tests).
   
     - Each pull request should address only one issue, not mix up code from 
multiple issues.
     
     - Each commit in the pull request has a meaningful commit message 
(including the JIRA id)
   
     - Every commit message references Jira issues in their subject lines. In 
addition, commits follow the guidelines from [How to write a good git commit 
message](https://chris.beams.io/posts/git-commit/)
       1. Subject is separated from body by a blank line
       1. Subject is limited to 50 characters (not including Jira issue 
reference)
       1. Subject does not end with a period
       1. Subject uses the imperative mood ("add", not "adding")
       1. Body wraps at 72 characters
       1. Body explains "what" and "why", not "how"
   
   -->
   
   ## What is the purpose of the change
   
   *(For example: This pull request improves file read performance by buffering 
data, fixing AVRO-XXXX.)*
   
   
   ## Verifying this change
   
   *(Please pick one of the following options)*
   
   This change is a trivial rework / code cleanup without any test coverage.
   
   *(or)*
   
   This change is already covered by existing tests, such as *(please describe 
tests)*.
   
   *(or)*
   
   This change added tests and can be verified as follows:
   
   *(example:)*
   - *Extended interop tests to verify consistent valid schema names between 
SDKs*
   - *Added test that validates that Java throws an AvroRuntimeException on 
invalid binary data*
   - *Manually verified the change by building the website and checking the new 
redirect*
   
   
   ## Documentation
   
   - Does this pull request introduce a new feature? (yes / no)
   - If yes, how is the feature documented? (not applicable / docs / JavaDocs / 
not documented)
   


-- 
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: dev-unsubscr...@avro.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to