Page History
...
| Note | ||
|---|---|---|
| ||
These same steps are also covered in the Sonatype Maven Repository Usage Guide |
Double Check Contents of all README (and similar) files in GitHub
| Info | ||
|---|---|---|
| ||
On skimming these instructions, this might look like a small thing, but it is not. It is a big information management task. Ask for help in wrangling/verifying the license information, and, if at all possible, DO NOT leave this job for release day. |
Make sure that the contents of all README, LICENSE, LICENSES_THIRD_PARTY, NOTICE files are up-to-date in GitHub. These files reside in [dspace-src]. If anything is out-of-date, make sure to update it and commit the proper changes before continuing.
Regenerate the LICENSES_THIRD_PARTY file
The "LICENSES_THIRD_PARTY" file is now autogenerated via a Maven command (using the codehaus license-maven-plugin). Simply run the following from your local source directory to re-generate this file:
...
Overview
Content Tools