[
https://issues.apache.org/jira/browse/KAFKA-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14146289#comment-14146289
]
Joe Stein edited comment on KAFKA-1490 at 9/24/14 1:31 PM:
-----------------------------------------------------------
Thanks [~szczepiq] for jumping in I think the current solution in any form for
Apache projects is kludgy. :( Besides Samza I just checked and Aurora does it
that way too (keeping jar files checked in but excluding from source release)
but I am not sure that is better though.
For source releases we have to exclude it and we will have to explain to folks
they have to bootstrap (and they will ask). I feel like there would be less
confusion and questions from folks using a source release if their experience
with the repo is the same.
My preference would be to not have to "bootstrap" at all. Maybe the gradle
team could modify things so we could pull the wrapper jar first without it
being there. Any chance of that? :) It seems like a legitimate ask since
"source only releases" are such a big thing it is is kludgy now no matter where
you cut it... this solution just makes it consistency kludgy.
I think this solution favors consistency of how to interact with the repo and
source release which leads to less community confusion.
Also, the way we have always done releases
https://cwiki.apache.org/confluence/display/KAFKA/Release+Process has been to
copy the repository 1:1 for the source release. This means what is tagged is
exactly what is in the source release. Technically speaking we could change
that (of course) and create a source release task but not sure if we would want
to-do that. If we decide to keep the jar in the repo we need to make sure the
release manager has a way to create a source release differently than has been
done before.
was (Author: joestein):
Thanks [~szczepiq] for jumping in I think the current solution in any form for
Apache projects is kludgy. :( Besides Samza I just checked and Aurora does it
that way too (keeping jar files checked in but excluding from source release)
but I am not sure that is better though.
For source releases we have to exclude it and we will have to explain to folks
they have to bootstrap (and they will ask). I feel like there would be less
confusion and questions from folks using a source release if their experience
with the repo is the same.
My preference would be to not have to "bootstrap" at all. Maybe the gradle
team could modify things so we could pull the wrapper jar first without it
being there. Any chance of that? :) It seems like a legitimate ask since
"source only releases" are such a big thing it is is kludgy now no matter where
you cut it... this solution just makes it consistency kludgy.
I think this solution favors consistency of how to interact with the repo and
source release which leads to less community confusion.
> 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)
