[ 
https://issues.apache.org/jira/browse/TINKERPOP3-713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

stephen mallette updated TINKERPOP3-713:
----------------------------------------
    Issue Type: Improvement  (was: Bug)

ok - well i was evaluating this issue based on an apache licensing problem 
which would have been pretty high priority and non-negotiable.  It doesn't seem 
like there really is a problem given Apache's stance in the FAQ.  Perhaps you 
should point your lawyer at that link as some information for them to consider.

Licensing issues aside, I think this is still a good pull request and expect to 
merge it based on the fact that your approach is more explicit in the 
dependencies required for each of the modules that depend on groovy.  Less 
dependencies is better - so in that sense - good PR.  

The problem I have at the moment is that your PR at:

https://github.com/apache/incubator-tinkerpop/pull/70

blends in commits from TINKERPOP3-714.  I'd like to deal with these separately. 
 Could you please re-issue this PR with just your changes related to the Groovy 
issue?

> Remove dependency on groovy-console which contains creative commons licenses
> ----------------------------------------------------------------------------
>
>                 Key: TINKERPOP3-713
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP3-713
>             Project: TinkerPop 3
>          Issue Type: Improvement
>          Components: build-release
>            Reporter: David Robinson
>            Assignee: stephen mallette
>              Labels: easyfix
>             Fix For: 3.0.0.GA
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> Current build of gremlin-driver and gremlin-groovy have dependencies on 
> groovy-all. 
> groovy-all includes the groovy-console jar which contains open source icons 
> licensed under the creative commons license -which is not Apache 2 friendly.
> Specifically, the silk icons from this link 
> http://www.famfamfam.com/lab/icons/silk/ are the ones in question.
> Solution is to change the project dependencies to the specific groovy jars 
> needed rather than groovy-all.
> I'll submit a pull request.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to