1 Reply Latest reply on Mar 21, 2008 6:02 PM by Adrian Brock

    License linking in poms

    Paul Gier Master

      Is it ok to put this URL to the lgpl in our poms?
      http://www.gnu.org/licenses/lgpl-2.1.txt

      Instead of the copy we currently use
      http://repository.jboss.org/licenses/lgpl.txt

      The maven convention is to point to the site of the license organization. If it's not ok, should we rename the file in our repository lgpl-2.1.txt so that it's not confused with 3.0.

        • 1. Re: License linking in poms
          Adrian Brock Master

           

          "pgier" wrote:
          Is it ok to put this URL to the lgpl in our poms?
          http://www.gnu.org/licenses/lgpl-2.1.txt

          Instead of the copy we currently use
          http://repository.jboss.org/licenses/lgpl.txt

          The maven convention is to point to the site of the license organization. If it's not ok, should we rename the file in our repository lgpl-2.1.txt so that it's not confused with 3.0.


          That's not a question for the forums, its a question for the lawyers. ;-)

          IANAL but, the relevant part is here:

          You may copy and distribute verbatim copies of the Library's
          complete source code as you receive it, in any medium, provided that
          ... and distribute a copy of this License along with the
          Library
          .


          So we should have our own copy of the license in the same place
          as where the library is distributed.

          Maven conventions are just that (design by exception).
          The conventions don't work in all circumstances. :-)

          Just copy it to lgpl-2.1. Don't rename it, otherwise you'll invalidate all the previous links.