Uploaded image for project: 'Spring Roo'
  1. Spring Roo
  2. ROO-1077

Clearly explain intent of Roo license

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Minor
    • Resolution: Complete
    • Affects Version/s: None
    • Fix Version/s: 1.1.0.M2
    • Component/s: None
    • Labels:
      None

      Description

      Roo's strength is its plugins, but it's licensed under the GPL (except it attempts to license its annotations under the Apache License). The GPL has provisions with respect to attempting to circumvent the GPL's "viral" nature in this manner. It's possible that then the Apache License for the annotations is invalidated (and thus becomes GPL'd), and therefore everything Roo touches also in turn needs to be GPL'd.

      While I'm pretty sure this isn't the intent, as it stands until this is legally vetoed, there's a risk that organizations interested in writing Roo plugins for their systems will in turn find their code accidentally GPL'd (and anything it then depends on, etc..)

      I'd love a definitive description of the licensing usage be part of the Roo documentation!

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              balex Ben Alex
              Reporter:
              idcmp JAmes Atwill
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: