Slb ado merge

Initial code push,build and scanning looks good in the branch.

@divido Can you please review and provide feedback before we merge to master?

added 1 commit

• 26ea39a3 - Added FOSSA

Compare with previous version

added 1 commit

• 3b103d47 - Added FOSSA

Compare with previous version

added 3 commits

• 5eaead3d - Adding a FOSSA configuration file
• 7bf84c35 - Adding the FOSSA generate NOTICE file
• f70e8473 - Update project number to match the Partition project

Compare with previous version

added no-detached-pipeline label

assigned to @divido

Caught me in a good moment...

Mostly looks good -- thanks for handling the initial import and set up. Here's the few addition steps that I took:

1. I generated a FOSSA configuration and set up the project on FOSSA's site.
2. Our luck held strong, and the initial 8 flagged dependencies were all things I've seen before; so no new legal investigations were need.
3. The pom.xml files were configured to store the jars in project 44 (Storage). I suspect this was a copy-paste oversight and not intentional. I updated the pom files with URLs that point to this project (4 different pom.xml files were affected).
4. I configured the protected branches on this project -- reject pushes to master, add "trusted-" as a wildcard, and "v" as a protected tag
5. I made this a committer branch so that the FOSSA scans would run without needing the "trusted-" branch.

added 1 commit

• d6cb2cb1 - Updated NOTICE file

Compare with previous version

added 1 commit

• 73aeabf9 - Removing settings file that was used in a previous hosting environment

Compare with previous version

resolved all threads

added 1 commit

• 00acdae1 - Updated NOTICE file

Compare with previous version

approved this merge request

merged

mentioned in commit 6a37c366

changed milestone to %M1 - Release 0.1