[
https://issues.apache.org/jira/browse/SAMZA-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14028061#comment-14028061
]
Jakob Homan commented on SAMZA-283:
-----------------------------------
After a small discussion on incubator-dev
* Changing the source-only policy may be possible but requires approval from
the board and will likely entail a lengthy discussion and be out of the
reasonable time frame for the 0.7.0 release.
* Aurora dealt with this issue in its first release by removing the gradle
wrapper from the source release and only including it in the binary release.
This leaves us with a couple options:
# Remove gradlew entirely and rely on the more traditional model of requiring
devs and source code users to have the build tool, gradle, installed.
# Follow Aurora and remove gradlew, et al, from the source release, but keep it
in the source code and include it in the eventual binary release. Gradle would
simply then be included as another prerequisite for building the software, same
as a JDK and scalac. This somewhat defeats the purpose of having gradlew but
is the fastest route to a release. Further, since binary releases exist only
as a convenience to the end user, gradlew's inclusion therein just extends this
idea by not only pre-including pre-built artifacts, but also the build tool
that was used to generate them.
The second option lets us follow up with the Board in the future in terms of
getting this particular jar pre-approved, should that be useful.
I'd like to go with #2 for now. Thoughts?
> 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)
