[
https://issues.apache.org/jira/browse/SLING-1092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750294#action_12750294
]
Felix Meschberger commented on SLING-1092:
------------------------------------------
According to [1] the idea of the JRuby tri-license is for the "user" to pick
one.
So I suggest we change the wording in the NOTICE file to
This product includes software developed at http://jruby.org
Licensed under the CPL 1.0
Copyright ...
... and remove the first line in the LICENSE.jruby file (or just plain copy the
CPL 1.0 license (with formatting))
... and upgrade to JRuby 1.3.1 (we still refer to 1.1.3)
[1] http://www.nabble.com/Question-about-licenses-to16727559.html#a16727673
> ohloh mistakenly thinks Sling contains some GPL stuff
> -----------------------------------------------------
>
> Key: SLING-1092
> URL: https://issues.apache.org/jira/browse/SLING-1092
> Project: Sling
> Issue Type: Task
> Components: Documentation
> Reporter: Bertrand Delacretaz
> Priority: Minor
>
> https://www.ohloh.net/p/sling says "Apache License 2.0 may conflict with
> GPL", explained at https://www.ohloh.net/p/sling/factoids/1848201
> https://www.ohloh.net/p/sling/analyses/latest says that's because ohloh found
> one file to have a GPL license.
> According to https://www.ohloh.net/topics/3160 they seem to be using a
> somewhat broken license detector regexp to come to this conclusion. A few of
> our NOTICE files contain the word "GPL", that might be the cause.
> I have posted at https://www.ohloh.net/topics/3160?page=2#post_11504 to ask
> for more details about which file that is.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
