[
https://issues.apache.org/jira/browse/SAMZA-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14028270#comment-14028270
]
Joe Stein commented on SAMZA-283:
---------------------------------
I was looking at this for Kafka
https://issues.apache.org/jira/browse/KAFKA-1490 and I think it is the same.
the script is fine as it is but after we do builds we are including artifacts
created (through download) from that build in the src (which doesn't require
that jar but we put it in there anyways incorrectly). I think the fix is just
removing that jar from the source distribution. Bringing it up so we can be
consistent across projects I think we are all saying the same thing though
(including how Aurora works) and working the same way.
> Resolve gradle wrapper jar issue
> --------------------------------
>
> Key: SAMZA-283
> URL: https://issues.apache.org/jira/browse/SAMZA-283
> Project: Samza
> Issue Type: Sub-task
> Reporter: Jakob Homan
> Assignee: Jakob Homan
> Fix For: 0.7.0
>
>
> ASF source releases aren't supposed to have any jars within the release.
> However, the gradlew wrapper explicitly requires the jar to be checked in.
> To bootstrap a gradle build that doesn't have the jar requires the user to
> have gradle itself already installed, which defeats the purpose of the
> gradlew script.
> I'm going to bring this up on the incubator list, since there may be some
> leeway here. DataFu and Aurora are in a similar position.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
