Gary O'Neall

One other note - there is a newer version of the compare tool at https://github.com/spdx/tools-java which unfortunately has the same issue.

I also noticed that the license text isn't filled in for any of the LicenseRef's. They all contain text `See details at https://github.com/nexB/scancode-toolkit/blob/develop/src/licensedcode/data/licenses/`... The license compare algorithm does a license...

> The root issue is that SPDX should be supported by standard libraries for all of the main programming languages, while the only comprehensive support is available only for Java,...

@silverhook It is a reasonable amount of work - I would guess on the order of magnitude 40 hours. We work from the issues list in terms of TODO. I'll...

The code that needs to be updated is in the [merge package](https://github.com/spdx/tools/tree/master/src/org/spdx/merge) and the [merge main class](https://github.com/spdx/tools/blob/master/src/org/spdx/tools/MergeSpdxDocs.java).

@gling07 Do you have any time to update?

@farislam Can you be a bit more specific on the issue? If there needs to be a new SPDX listed license or a new SPDX listed license exception, you can...

> Should we raise a request or create a LicenseRef within the SPDX document with the complete text of the license? Since it takes some time to get a license...

@nam-np There is a newer version of the SPDX tools you might want to try: [tools-java](https://github.com/spdx/tools-java). There are 2 libraries the newer version uses - [SPDX Java Library](https://github.com/spdx/Spdx-Java-Library) and [spdx-java-tagvalue-store](https://github.com/spdx/spdx-java-tagvalue-store)....

The SPDX tools currently accept expressions for PackageLicenseInforFromFiles.