The case systematic has been reorganized. Valid cases now have a number >= 10 ...

TC03a stood for 'Test-Driven Open Source Compliance Automation Test Case No. 3a: a Simple Hello World with JAVA and gradle'

The "Test-Driven Open Source Compliance Automation" is an initiative initiated by Deutsche Telekom AG and hosted and driven by the Open Chain Reference Tooling Work Group.

The project scope statement and further information of TDOSCA can be found at https://github.com/Open-Source-Compliance/tdosca.

This test case follows the general pattern of a TDOSCA test case:

• It has its own repository https://github.com/Open-Source-Compliance/tdosca-tc03a-simplhw
• and contains the following parts:
  • compliance-traps.md: describes the traps / challenges implemented by and in the test case [used to manually control whether a tested compliance tool really overcomes all difficulties]
  • input-sources: contains all sources to create the distributable (binary package) [used by the tested tool to create the compliance artifacts]
  • README.md: this file
  • reference-compliance-artifacts: the compliance compliance artifacts a tool (chain) must/should generate
    • bom.csv: a list of all differently licensed open source components of a package
    • oscf.md: the open source compliance file [fulfills the compliance requirements if combined with the distributed source- or binary package]
    • prerequisites.csv: a list of preinstalled tools and libs, required by the software but not delivered as part of the software package

The test data of this test case (the program sources in input-sources)

• can be compiled, installed and used by the respective gradle commands
• consist of three java files (Main.java, GreetingService.java and EnvService.java) and the respective gradle files to use them
• Main includes GreetingService includes EnvService. Each part says Hello
• The main project license is the MIT license, but EnvService.java is licensed under the BSD-2-Clause.
• The JUnit test are licensed as the classes the test.
• For specific challenges of this test case the compliance-traps.md

HINT:

1. Using gradle with all options (= gradle init) would evoke an immanent compliance trap, because (parts of) gradle would become part of the repository. These parts would be licensed under the Apache-V2 license. Hence distributing the repository (even by cloning / downloading it from GitHub) would require, that the respective gradle compliance artifacts would have also to be integrated into the repo.
2. For easing this 'merge', the test case 03a does not offer the complete gradle methods, but requires gradle to be installed on the development machine.

(c) 2020, Karsten Reincke, Deutsche Telekom AG

• The software delivered as content of the test case directory input-sources is licensed under the licenses the test case uses to challenge the compliance tools. Contributions take place under the same licenses.

• Unless otherwise specified, all other files are distributed under the terms of the CC-BY-4.0 license: If you share or adapti this tect case or (one of) the files, please add the attribution: "based on https://github.com/Open-Source-Compliance/tdosca-tc03a-simplhw initiated by Deutsche Telekom AG"