zhuyufeng0809 opened a new issue, #3267:
URL: https://github.com/apache/fluss/issues/3267

   ### Search before asking
   
   - [x] I searched in the [issues](https://github.com/apache/fluss/issues) and 
found nothing similar.
   
   
   ### Fluss version
   
   main (development)
   
   ### Please describe the bug 🐞
   
   According to the log prompt, copy the missing dependencies in the log to the 
NOTICE file, but it is still unable to pass the verification.
   
   <img width="1437" height="699" alt="Image" 
src="https://github.com/user-attachments/assets/094db083-cd98-43ef-af14-08f044aed015";
 />
   
   This is because the format of the log prompt is different from the order of 
the actual parsing format.
   
   The parsing format is:  `groupId:artifactId:classifier:version`
   ```
   // NoticeParser
   private static final Pattern NOTICE_DEPENDENCY_PATTERN =
           Pattern.compile(
                   "- "
                           + "(?<groupId>[^ ]*?):"
                           + "(?<artifactId>[^ ]*?):"
                           + "(?:(?<classifier>[^ ]*?):)?"  // ← classifier
                           + "(?<version>[^ ]*?)"           // ← version 
                           + "($| )");
   ```
   
   The log format is: `groupId:artifactId:version:classifier`
   ```
   // Dependency.toString()
   return groupId
           + ":"
           + artifactId
           + ":"
           + version
           + (classifier != null ? ":" + classifier : "")  // ← classifier
           + (scope != null ? ":" + scope : "")
           + (isOptional != null && isOptional ? " (optional)" : "");
   ```
   
   ### Solution
   
   Adjusted the order of classifier and version to be consistent with the 
parsing format.
   
   ### Are you willing to submit a PR?
   
   - [x] I'm willing to submit a PR!


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