Forrest
  1. Forrest
  2. FOR-857

append license files to the top-level LICENSE.txt

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 0.10-dev
    • Component/s: Project administration
    • Labels:
      None
    • Urgency:
      Blocker

      Description

      The license files for accompanying external products needs to be appended after the Apache License in the top-level $FORREST_HOME/LICENSE.txt file.

      Perhaps the current discussion on the legal-discuss mailing list will clarify
      http://www.apache.org/foundation/mailinglists.html#foundation-legal

        Issue Links

          Activity

          Hide
          David Crossley added a comment - - edited
          For the 0.8 release we added a listing of pathnames for all licenses for supporting products, into the top-level LICENSE.txt file.

          That was reasonably easy with 'find' because we tried to maintain a file naming convention following the {packageName}.license.txt pattern. Careful, some are uppercase.

          That was double-checked by searching for all jar etc packages and ensure that they had a matching license file.

          That process needs to be repeated each at release until we get a better way.
          Show
          David Crossley added a comment - - edited For the 0.8 release we added a listing of pathnames for all licenses for supporting products, into the top-level LICENSE.txt file. That was reasonably easy with 'find' because we tried to maintain a file naming convention following the {packageName}.license.txt pattern. Careful, some are uppercase. That was double-checked by searching for all jar etc packages and ensure that they had a matching license file. That process needs to be repeated each at release until we get a better way.
          Hide
          Tim Williams added a comment -
          If you know of a good, reasonably reliable find command, pls share it. Otherwise, I'll try to write something in ruby to do this.

          On the other hand, this got me wondering, is RAT not verifying this for us?
          Show
          Tim Williams added a comment - If you know of a good, reasonably reliable find command, pls share it. Otherwise, I'll try to write something in ruby to do this. On the other hand, this got me wondering, is RAT not verifying this for us?
          Hide
          David Crossley added a comment -
          No, RAT does other things (basically helping with part B of FOR-855).

          Yes i do have a Perl script that i am using to assist me with this FOR-857 and with some of part A of FOR-855.

          I will keep doing this task, while other people get on with the other release-related issues. As i tidy up the program, i will add a version here.

          Show
          David Crossley added a comment - No, RAT does other things (basically helping with part B of FOR-855 ). Yes i do have a Perl script that i am using to assist me with this FOR-857 and with some of part A of FOR-855 . I will keep doing this task, while other people get on with the other release-related issues. As i tidy up the program, i will add a version here.
          Hide
          David Crossley added a comment -
          Attached Perl script to assist with matching license files with artefacts.
          See licer-20100825.pl.gz
          Show
          David Crossley added a comment - Attached Perl script to assist with matching license files with artefacts. See licer-20100825.pl.gz
          Hide
          David Crossley added a comment -
          I have decided to only list the license files in the top-level LICENSE.txt file. This is still a vast improvement on what we did for the 0.8 release.

          Appending each license file is just too huge a job. Better to eventually use Ivy for our supporting products, as suggested in FOR-1123.
          Show
          David Crossley added a comment - I have decided to only list the license files in the top-level LICENSE.txt file. This is still a vast improvement on what we did for the 0.8 release. Appending each license file is just too huge a job. Better to eventually use Ivy for our supporting products, as suggested in FOR-1123 .
          Hide
          David Crossley added a comment -
          Done as much as i can.

          The main one needing investigation is lib/core/concurrent-1.3.4.jar.license.txt
          Does upgrading help?
          Show
          David Crossley added a comment - Done as much as i can. The main one needing investigation is lib/core/concurrent-1.3.4.jar.license.txt Does upgrading help?
          Hide
          David Crossley added a comment -
          For Concurrent, see FOR-1206
          Show
          David Crossley added a comment - For Concurrent, see FOR-1206
          Hide
          David Crossley added a comment -
          Moving this to our next release cycle.
          Show
          David Crossley added a comment - Moving this to our next release cycle.

            People

            • Assignee:
              Unassigned
              Reporter:
              David Crossley
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:

                Development