vbhanuchander-lang opened a new pull request, #18056:
URL: https://github.com/apache/iceberg/pull/18056

   Closes #18052.
   
   The BOM adds every leaf project, but `iceberg-kafka-connect-runtime` builds 
ZIP distributions rather than Maven artifacts and [disables its publishing 
tasks](https://github.com/apache/iceberg/blob/main/kafka-connect/build.gradle#L237-L240),
 so its POM is never published — the [1.11.0 
POM](https://repo.maven.apache.org/maven2/org/apache/iceberg/iceberg-kafka-connect-runtime/1.11.0/iceberg-kafka-connect-runtime-1.11.0.pom)
 returns 404. The BOM therefore advertises a coordinate that cannot resolve.
   
   The grouping project `iceberg-kafka-connect` is already excluded by the 
existing `childProjects.isEmpty()` check, so the runtime module is the only 
affected one — it is the only publishing-disabled *leaf* project in the build.
   
   ## Verifying this change
   
   `./gradlew :iceberg-bom:generatePomFileForApachePublication`, then 
inspecting `bom/build/publications/apache/pom-default.xml`:
   
   | | artifacts in BOM | `iceberg-kafka-connect-runtime` |
   |---|---|---|
   | before | 30 | present |
   | after | 29 | absent |
   
   Exactly one entry is removed. `iceberg-kafka-connect`, 
`iceberg-kafka-connect-events` and `iceberg-kafka-connect-transforms` are real 
published artifacts and remain.
   
   I used an explicit exclusion list rather than deriving "does not publish" 
from the project state, because publishing is disabled inside that project's 
`afterEvaluate` while the BOM's `constraints` block is evaluated during 
configuration, so keying off task state here would depend on configuration 
ordering. Happy to switch to a shared property (for example a `skipPublish` 
flag set by the project and read here) if you would prefer something that 
cannot be forgotten when the next distribution-only module is added.
   
   Generated-by: Claude Code (Opus 5)
   


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


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to