You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Sönke Liebau (Jira)" <ji...@apache.org> on 2020/03/11 20:31:00 UTC

[jira] [Commented] (KAFKA-1265) SBT and Gradle create jars without expected Maven files

    [ https://issues.apache.org/jira/browse/KAFKA-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17057365#comment-17057365 ] 

Sönke Liebau commented on KAFKA-1265:
-------------------------------------

While it still holds true that the jar itself doesn't contain these files, the appropriate pom is published to maven central by Gradle and serves this purpose to a large extent.
Also, as this has been open and uncommented for more than 6 years now, the pain seems not to be too great here :)

I'd suggest we can close this?

> SBT and Gradle create jars without expected Maven files
> -------------------------------------------------------
>
>                 Key: KAFKA-1265
>                 URL: https://issues.apache.org/jira/browse/KAFKA-1265
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 0.8.0, 0.8.1
>            Reporter: Clark Breyman
>            Priority: Minor
>              Labels: build
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> The jar files produced and deployed to maven central do not embed the expected Maven pom.xml and pom.properties files as would be expected by a standard Maven-build artifact. This results in jars that do not self-document their versions or dependencies. 
> For reference to the maven behavior, see addMavenDescriptor (defaults to true): http://maven.apache.org/shared/maven-archiver/#archive
> Worst case, these files would need to be generated by the build and included in the jar file. Gradle doesn't seem to have an automatic mechanism for this.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)