[jira] [Commented] (LEGAL-288) Can the allowed embedded build tools be expanded?

["Dawid Weiss (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LEGAL-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17071269#comment-17071269 ] 

Dawid Weiss commented on LEGAL-288:
-----------------------------------

I realize this issue has been closed but there's strong evidence that people do commit gradle-wrapper.jar in and use it.
https://github.com/search?q=org%3Aapache+filename%3Agradle-wrapper.jar

And trying to come up with a workaround for having this script checked in as a binary blob is both error-prone, complex and unreliable.

> Can the allowed embedded build tools be expanded?
> -------------------------------------------------
>
>                 Key: LEGAL-288
>                 URL: https://issues.apache.org/jira/browse/LEGAL-288
>             Project: Legal Discuss
>          Issue Type: Question
>          Components: Policy Question
>            Reporter: John D. Ament
>            Priority: Major
>
> http://www.apache.org/legal/resolved.html#build-tools
> This section lists out some basic build tools that are allowed to be included within a release.  I would like to propose adding two tools to this list:
> - Gradle Wrapper - https://github.com/gradle/gradle
> - Maven Wrapper - https://github.com/takari/maven-wrapper
> Both tools are Apache v2 licensed.  However, to work 100% they should include an associated precompiled JAR file.  This JAR file is responsible for retrieving the associated distribution of the build tool for local use.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org