Geronimo
  1. Geronimo
  2. GERONIMO-5087 Use OSGi for the Geronimo classloading model.
  3. GERONIMO-4902

need license file modifications for imported plexus code in osgi sandbox modules/geronimo-plugin

    Details

    • Type: Sub-task Sub-task
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 3.0.0
    • Fix Version/s: 3.0-M1
    • Component/s: osgi, Plugins
    • Security Level: public (Regular issues)
    • Labels:
      None

      Description

      In order to avoid giant problems with plexus invasiveness I copied the plexus code we need to build archives into geronimo-plugin and modified it to not pull in all of the plexus infrastructure. We need to find a way to eliminate this code or fix the legal files.

      rev 821961, https://svn.apache.org/repos/asf/geronimo/sandbox/djencks/osgi/framework

      Kevan, if you don't want to do this unassign it – I thought you might be the best at figuring out what we need.

        Activity

        Hide
        Kevan Miller added a comment -

        Hmm. I think this is going to be a problem... How much code? Likely that we're going to have to find a different way of fixing this problem...

        Plexus is licensed under CPL 1.0 (http://plexus.sourceforge.net/license.shtml). CPL 1.0 is classified as a Category B license by Apache (http://www.apache.org/legal/resolved.html#category-b ). This means that we can only include CPL binaries, not CPL source. Unless we can get Plexus to relicense or if this code meets the Category B exception clause (which I doubt it will), then afraid we're going to need to remove the Plexus code...

        Show
        Kevan Miller added a comment - Hmm. I think this is going to be a problem... How much code? Likely that we're going to have to find a different way of fixing this problem... Plexus is licensed under CPL 1.0 ( http://plexus.sourceforge.net/license.shtml ). CPL 1.0 is classified as a Category B license by Apache ( http://www.apache.org/legal/resolved.html#category-b ). This means that we can only include CPL binaries, not CPL source. Unless we can get Plexus to relicense or if this code meets the Category B exception clause (which I doubt it will), then afraid we're going to need to remove the Plexus code...
        Hide
        David Jencks added a comment -

        hmm, I was going by the source file headers which, when they exist, seem to indicate apache 1.1 or 2 licensing and say the code is licensed by apache. Perhaps it originally came from apache and we can use that version.

        Would it be acceptable to use the maven-shade-plugin to generate one or more jars with different package names containing the classes, and redistirbute these modified binaries from apache? We'd need a bit more code, but that might work if legally OK.

        Show
        David Jencks added a comment - hmm, I was going by the source file headers which, when they exist, seem to indicate apache 1.1 or 2 licensing and say the code is licensed by apache. Perhaps it originally came from apache and we can use that version. Would it be acceptable to use the maven-shade-plugin to generate one or more jars with different package names containing the classes, and redistirbute these modified binaries from apache? We'd need a bit more code, but that might work if legally OK.
        Hide
        David Jencks added a comment -

        Fixed in rev 825791 by using ant 1.7.0 code instead of plexus.

        Show
        David Jencks added a comment - Fixed in rev 825791 by using ant 1.7.0 code instead of plexus.

          People

          • Assignee:
            Kevan Miller
            Reporter:
            David Jencks
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development