Jump to: navigation, search

Difference between revisions of "WTP/Releng/Tools"

< WTP
(= Known limitations)
(Known limitations)
Line 20: Line 20:
 
: webtools.releng/plugins/org.eclipse.wtp.releng.fixups
 
: webtools.releng/plugins/org.eclipse.wtp.releng.fixups
  
== Known limitations ==  
+
=== Known limitations ===
  
 
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.  
 
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.
 
The Eclipse preference for end-of-line (EOL) is not honored, and the PD EOL is used for simplicity.

Revision as of 23:04, 9 April 2010

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.


Installation Repository

You can install "WTP Releng Tools" from this repository.

http://download.eclipse.org/webtools/releng/repository

CVS location of source code

/cvsroot/webtools
webtools.releng/plugins/org.eclipse.wtp.releng.fixups

Known limitations

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.