-
Notifications
You must be signed in to change notification settings - Fork 20
Incomplete License Descriptors in sample license.xml #58
Comments
In general, the configuration provided in org.aposin.licensescout.configuration.sample is an example. It is not intended to be used in real-world projects. For real projects a project specific configuration neds to be maintained anyway. One reason for this is that different projects use different licenses and they considere different licenses as acceptable or not acceptable, need special name or URL mappings, have different vendor IDs for exclusion of own artifacts, and need different excptions configured. So maintaining a configuration for a certain project is highly project specific. Therefore; I consider this out of scope of the open source project LicenseScout. Also, providing license texts may have legal implications. If we miss an important sentence from a license text, and somebody relies on this text copied into the resulting report, the LicenseScout developers may be sued, which we want to avoid under all circumstances. Regarding configuration, it is already possible to configure the license text as empty or leave out the tag ' Under this circumstances I consider it a reasonable choice to have a 'TODO' in a sample configuration - as a reminder for the maintainer of a project specific configuration that there is something to do. Raising an error on incomplete configuration may be considered as an additional feature. So I do not consider these issues as a "bug", but rather as a feature request. |
org.aposin.licensescout.configuration.sample/src/main/resources/licenses.xml contains numerous TODO entries for
licenseText
configurations.Bug report
TODO is copied literally into the generated license.txt report, resulting in an invalid license.txt while the maven build of the license report still completes with
Expected Behavior - What where you expecting to happen?
Current Behavior - What happens?
The text was updated successfully, but these errors were encountered: