[
https://issues.apache.org/jira/browse/KAFKA-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14497680#comment-14497680
]
Ewen Cheslack-Postava commented on KAFKA-2098:
----------------------------------------------
The original issue is here: https://issues.apache.org/jira/browse/KAFKA-1490
The first post of the mailing list thread linked to in that post gives a good
rundown of the issues:
http://mail-archives.apache.org/mod_mbox/incubator-general/201406.mbox/%3CCADiKvVs%3DtKDbp3TWRnxds5dVepqcX4kWeYbj7xUx%2BZoDNM_Lyg%40mail.gmail.com%3E
Sadly, the deeper you dig, the more confusing things get. "export" vs
"checkout" is hinted at here
http://incubator.apache.org/guides/releasemanagement.html#best-practice-source
which would indicate you can include binaries in the repo as long as they
aren't included in the release.
https://www.apache.org/dev/release-publishing.html#valid talks about all source
code being appropriately licensed and under the right CLA, the latter
potentially being a problem for an Apache source release since gradle wouldn't
be covered by an Apache CLA.
As a side note, downstream packagers sometimes dislike any binaries in source
releases. See, e.g.,
https://www.debian.org/doc/packaging-manuals/java-policy/x84.html which
indicates debian maintainers regularly need to repack source releases to remove
the binary bits. Making sure they don't make them into source releases makes
things a lot less painful for packagers.
If you look into the source release for Samza, you'll see it doesn't contain
any jars. They're stripped out during the release process (I haven't checked
how, but just run find on the source tgz contents -- you won't find any jars).
This matches the export vs. checkout distinction. It also addresses the
potential CLA issues with a source release. I'm guessing that, given the
complaints about the missing wrapper, this might be the right thing to do to
appease Apache, downstream packagers, and developers/users.
Personally, I'm surprised this causes as much frustration as it does -- the
only time it's been an issue for me is on platforms where the native gradle
packages are too old. But
> Gradle Wrapper Jar gone missing in 0.8.2.1
> ------------------------------------------
>
> Key: KAFKA-2098
> URL: https://issues.apache.org/jira/browse/KAFKA-2098
> Project: Kafka
> Issue Type: Bug
> Components: build
> Affects Versions: 0.8.2.1
> Reporter: Rekha Joshi
> Assignee: Rekha Joshi
>
> ./gradlew idea
> Error: Could not find or load main class org.gradle.wrapper.GradleWrapperMain
> This was working in 0.8.2.Attaching patch.Thanks
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
