Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: for the plan.

Jump to: navigation, search

WTP Release 1.5 Patches

Revision as of 00:10, 23 September 2007 by Unnamed Poltroon (Talk) (added dreprecated note)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Deprecated. This page has been superseded by WTP Release 1.5.5 Patches

What is an "official patch"?

Under some circumstance the WTP project may find it desirable to produce a "feature patch" which typically includes exactly one jar, that has a fix for exactly one bug. These are done for bugs which happen to be considered extremely severe or blocking -- but may not even apply to all installs, or all users. (So, as a general rule, they are not to be installed by everyone ... but any bugs fixed by patches will be fixed in the next maintenance release ... though the exact fix might be different).

While few, it is important to create and apply these in a controlled, repeatable process in order to maintain product level professional quality. For example, it is important to compile with exactly the same compiler, and exactly the same "pre-reqs" that was used to create the original build.

Technical Notes

Normally, only the "releng team" (ok ... me and Naci :) need to mess with patches. There should be very few, very special purpose, handled and produced on a case-by-case bases.

There is a special stream to that contains code related to these patches:


There is a special component


in the releng.wtpbuilder cvs project that along with special distribution targets

that produce patch features that contains a special feature to "host" the plugin. See Eclipse Help for details, but remember, the patch feature must say "requires" the feature that it is patching, including all 4 fields of the version -- the 'qualifier' field is not computed automatically.

The end-result is

  • a compressed archive on
  • a feature and plugin suitable for an update site. These update jars are actually in the same directory as the zip download, but normally not visible from the web.

If it desired to be generally available to all WTP users (by them simply use the Eclipse update feature to get updates to existing installed features), then the update features and plugins have to be copied to the downloads/webtools/updates directory. Also, remember to

  1. update the site.xml
  2. recreate the digest
  3. run pack200

Updates required in wtpBuilder

Currently, the wtpBuilder project needs to be modified to build the patch feature:

  1. In the wtp-patches component, the has a field, patchFeature that needs to be updated for the particular patch feature that is being created. Additionally, there is one target name in customTargest.xml file that needs to be updated. It is the one that starts with assemble (who knew ant target's can not contain variables?).


Feel free to ask questions on if there are questions.

Back to WTP Build Process and Procedures
Back to Web Tools Wiki Home

Back to the top