[
https://issues.apache.org/jira/browse/KAFKA-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14146365#comment-14146365
]
Joe Stein edited comment on KAFKA-1490 at 9/24/14 2:33 PM:
-----------------------------------------------------------
A source release is meant for general public consumption and use and not just
for developers. Technically speaking any version we put out is really about
the source release the binaries are only an aid for folks that don't have the
tools to make their own build from source
http://www.apache.org/dev/release.html#what and
http://www.apache.org/dev/release.html#what-must-every-release-contain
Any chance of the core gradle team making the gradle-wrapper.jar hosted and
signed and then it can get downloaded (and signatures checked) if not found? I
think this would start to help wider adoption within apache projects and create
a better uses experience for everyone always using gradle (assuming that
approach satisfies apache requirements I believe it would best to get more
Apache folks to verify that which we could do of course). Let me know if you
can get that change going and I can kick a discussion off (having a link to
your ticketing change would help drive it) to make sure it will be workable
within the Apache foundation (prior to you doing the work).
was (Author: joestein):
A source release is meant for general public consumption and use and not just
for developers. Technically speaking any version we put out is really about
the source release the binaries are only an aid for folks that don't have the
tools to make their own build from source
http://www.apache.org/dev/release.html#what and
http://www.apache.org/dev/release.html#what-must-every-release-contain
Any chance of the core gradle team making the gradle-wrapper.jar hosted and
signed and then it can get downloaded (and signatures checked) if not found? I
think this would start to help wider adoption within apache projects and create
a better uses experience for everyone always using gradle (assuming that
approach satisfies apache requirements I believe it would best to get more
Apache folks to verify that which we could do of course). Let me know if you
can get that change going and I can kick a discussion off (having a link to
your ticketing change would help drive it) to make sure it will be workable
(prior to you doing the work).
> remove gradlew initial setup output from source distribution
> ------------------------------------------------------------
>
> Key: KAFKA-1490
> URL: https://issues.apache.org/jira/browse/KAFKA-1490
> Project: Kafka
> Issue Type: Bug
> Reporter: Joe Stein
> Assignee: Ivan Lyutov
> Priority: Blocker
> Fix For: 0.8.2
>
> Attachments: KAFKA-1490-2.patch, KAFKA-1490.patch, rb25703.patch
>
>
> Our current source releases contains lots of stuff in the gradle folder we do
> not need
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
