fvaleri commented on PR #23828:
URL: https://github.com/apache/kafka/pull/23828#issuecomment-6251281435

   > Thanks for the update, @fvaleri. Could you take a look at the build error?
   
   The error is caused by the addition of javadoc:
   
   ```sh
   [MISSING_PUBLICAPI_ANNOTATION] 
org.apache.kafka.common.errors.ReadOnlyTopicException: Class appears in javadoc 
but lacks @InterfaceAudience.Public annotation
   [MISSING_PUBLICAPI_ANNOTATION] 
org.apache.kafka.common.errors.ClusterMirrorAuthorizationException: Class 
appears in javadoc but lacks @InterfaceAudience.Public annotation
   [MISSING_PUBLICAPI_ANNOTATION] 
org.apache.kafka.common.errors.UnknownClusterMirrorException: Class appears in 
javadoc but lacks @InterfaceAudience.Public annotation
   [MISSING_PUBLICAPI_ANNOTATION] 
org.apache.kafka.common.errors.TopicAlreadyInClusterMirrorException: Class 
appears in javadoc but lacks @InterfaceAudience.Public annotation
   [MISSING_PUBLICAPI_ANNOTATION] 
org.apache.kafka.common.errors.MirrorConfigNotAvailableException: Class appears 
in javadoc but lacks @InterfaceAudience.Public annotation
   [MISSING_PUBLICAPI_ANNOTATION] 
org.apache.kafka.common.errors.ClusterMirrorAlreadyExistsException: Class 
appears in javadoc but lacks @InterfaceAudience.Public annotation
   [MISSING_PUBLICAPI_ANNOTATION] 
org.apache.kafka.common.errors.SourceMetadataNotAvailableException: Class 
appears in javadoc but lacks @InterfaceAudience.Public annotation
   [MISSING_PUBLICAPI_ANNOTATION] 
org.apache.kafka.common.errors.TopicNotInClusterMirrorException: Class appears 
in javadoc but lacks @InterfaceAudience.Public annotation
   [MISSING_PUBLICAPI_ANNOTATION] 
org.apache.kafka.common.errors.InvalidMirrorStateException: Class appears in 
javadoc but lacks @InterfaceAudience.Public annotation
   ```
   
   The problem is that most/all these exceptions are planned to be internal. 
What about removing Javadoc and adding back when if any of them surface to the 
user?


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