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


Revision as of 13:52, 15 April 2010 by David (Talk | contribs) (Provider Names)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)


There are a number of tests that are ran as unit tests, after a build, that do some general sanity checks of the build, and compliance to requirements. These can cause "failures" in the releng test (and hence build). The more detailed logs can be found at the top of JUnit Details page.

Bundle Layout

This refers to a collection of checks for required, common or expected files. Certain errors have higher priority than others. And, remember, "missing" may indicate a mistake in the file.

  • Missing about.html files are considered blocking defects (for a release).
  • Missing properties files indicates that strings are not externalized.
  • The test for class or jar files is meant as a sanity check that the build worked as expected. There are many cases, though, where it is expected to have no class or jar files, in which case the bundle needs to be added to an explicit list of exceptions.

Provider Names

Our "Provider Name" for our features and plugins should always be "Eclipse Web Tools Platform".

There are certainly priorities to what needs to be fixed.

  • Features are more important than bundles
  • Missing or "symbolic variable names" are very bad.
  • Company names are horrible!
  • '' is incorrect, as of Galileo release, but prior to Galileo that was the required provider name, so it should be considered "minor" bug, if in bundle (a bug, but could ship with that bug).

License Consistency

As of Helios, there is a strong "standard text" requirement.


Future: Checks to make sure there is a copyright associated with a bundle or feature. Long Term Maybe Future: Checks if each source file has a copyright at beginning.

Back to the top