Check and fix-up licenses tool
This tool is a very simple aide to make license properties and files consistent in features. See bug 306627 for some history and details. In short, in addition to the Eclipse requirement of having the right SUAs, etc., in features, beginning with the Helios release, we want them to be perfectly consistent, to improve ease-of-use of the Installation UI and make the license acceptance more meaningful.
It works on (only) workspace files. It finds all projects that are features, by looking for those that contain a "feature.xml" file. Then it looks for a "feature.properties" file. If so, it checks for a "license" property om that file, and compares its value with the value of the standard version. If different, it will update the feature.properties file with the new, correct and consistent license text. It leaves other parts of the file untouched (such as, it leaves in existing comments and white space, and just replaces the license part.
If it finds it needs to update the 'license' property, then it will blindly replace the existing license.html file with one that has the standard HTML Content.
To operate, click Releng (on menu bar) and then click "Check Licenses". At that point, it does its work, maybe modify some, not others, but it does write a log of what it did in the console.
Be sure to compare and look closely that the tool didn't mess something up and make things worse before you commit to head and release for a build.
You can install "WTP Releng Tools" from this repository.
CVS location of source code
- Some key data is hard code. For example, the license key must be, literally, "license". There's no reason it has to be, but in my experience, they all are named "license". If someone used something else, like "licenseStr" then the program would been to be made better.
- The Eclipse preference for end-of-line (EOL) is not honored, and the PD EOL is used for simplicity.