[
https://issues.apache.org/jira/browse/KAFKA-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14157865#comment-14157865
]
Szczepan Faber commented on KAFKA-1490:
---------------------------------------
Hey
The current bootstrap workflow in kafka is something like. The user:
- clones the repo
- looks into the 'build.gradle' file to find out which Gradle version he needs
- downloads this version of gradle (or maybe already has it)
- sets up this version of gradle, ensures it is on the PATH, etc.
- invokes this version of gradle to grab the wrapper
- now can build kafka OS via ./gradlew
Steps like above increase complexity and offer ways to break stuff (e.g. wrong
version of gradle on PATH causing unexpected behavior, etc.). The wrapper was
invented to avoid those kind of situations.
It's a bit of a shame that the jar file is involved - I would much prefer if
there was no need for any jar to have 'wrapper' functionality available.
Hopefully, in future version of Gradle it will be improved!
> 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)
