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

["John D. Ament (JIRA)" <ji...@apache.org>]

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

John D. Ament edited comment on LEGAL-288 at 1/25/17 11:28 AM:
---------------------------------------------------------------

Ok - so then following the on going incubator discussion, do you see the binary nature of the build tool as being an issue for a project to use as its source release?

And you're right, I wasn't interpreting it as the Cat X question.


was (Author: johndament):
Ok - so then following the on going incubator discussion, do you see the binary nature of the build tool as being an issue for a project to use as its source release?

> 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
>            Reporter: John D. Ament
>
> 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
(v6.3.4#6332)

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