Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Components Page Conventions"

(Table Templates)
 
(39 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{#eclipseproject:technology.higgins}}
+
This page describes the definitions and table formatting conventions used on these pages: [[Components]].
=== Navigation === 
+
* All information, interfaces, doc, etc. about any Component should be reachable by clicking on the component name in the column above.
+
=== Table Templates ===
+
* The tables on this page should use these templates:
+
** [[Template:HigCompTblHead2]]
+
** [[Template:HigCompTblSec2]]
+
** [[Template:HigCompTblRow2]]
+
  
* Older versions of templates
+
== Definitions ==
** [[Template:HigCompTblHead]]
+
* See [[Diagram Key]]
** [[Template:HigCompTblSec]]
+
** [[Template:HigCompRow]]
+
  
===Column Names === 
+
== Three kinds of tables  ==
* Left-most Column (may be indented)
+
** Component-level rows: '''Component name''' plus:
+
*** (Bugzilla component name) if Bugzilla name is different
+
** Sub-component-level rows (Token Service and IdAS only): '''Sub-Component name'''
+
** Project-level rows: '''Project name''' plus:
+
*** [SVN module name]
+
*** {branches} --list of branch names for this component
+
* '''Dep.''' (Dependencies) 
+
** '''dep''' - wiki page of non-Higgins libraries (e.g. JARs) that this component depends on to build and run 
+
* '''Repository'''
+
** '''svn''' - link to the SVN source files
+
*** Use either the https link given, or substitute svn+ssh for https as the svn URL in order to access the code for a project
+
* '''Downloads''' 
+
** '''downloads''' - link to the mostly recently generated nightly on build.eclipse.org [Soon: this page will also include all stable builds]
+
*'''Test Status''' 
+
**For each of the java sub-projects of each Component listed in all of these tables there exists a second project a sister ".test" project exists containing unit tests. These tests are [well, will soon be] automatically run during the nightly build process. This cell should contain a status word related to these tests: 
+
*** '''none''' - no sister ".test" project exists
+
*** '''minimal''' - a few unit tests exist in the ".test" project 
+
*** '''good''' - reasonable coverage of functionality exists in the ".test" project   
+
* '''First check-in''' [MANDATORY]
+
** The first branch that contained this project or file. E.g. if the table or release build that contained this project/file was "B-1-0-0" then this column entry would read "B-1-0-0".
+
* '''Most recent''' [MANDATORY]
+
** The most recent branch that contains this project or file. E.g. if the most recent stable or release build were "B-1-0-0" then if this project/file were a part of this build then this column entry would read "B-1-0-0".
+
* '''Owner''' 
+
** '''<email>''' - email of the owner of this component
+
  
 +
There are three kind of tables on these [[Components]] pages:
  
== Currently Disabled ==
+
;Single project
* '''Build Status''' (LED)
+
:tables that describe a single Component and implement it with a single Project (row). [[Components 1.X#I-Card_Service_Web_App|Example]].
** '''green''' - last night's build succeeded
+
;Alternatives
** '''red''' - last night's build failed
+
:tables that describe a single Component but contain multiple alternative implementation Projects (rows). [[Components 1.X#IdAS_Context_Provider|Example]].
** '''clear/off''' - not yet part of nightly build
+
;Package
 +
:tables that describe a set of rows each of which is a Component. [[Components_1.X#IdAS | Example]].
  
== Proposed Improvements to the tables on this page ==
+
== Table Format ==
This section is a place to capture new ideas, suggestions, requirements for improvements to the templates used to generate these tables:
+
The tables on the [[Components]] page uses these templates:
# Make the LED's clickable so when one is red, it can be clicked which results in the user being taken to the build log or something that explains why the build broke. I'm not sure how to do this in a way that doesn't display the ugly wiki "external link" graphic. I do know how to do it nicely if we're linking to a wiki.eclipse.org page (jimse)
+
* [[Template:HigCompTblHead2SingleRow]] - table header for '''single project''' component (excepting test, config, etc. supporting projects) that implements the component service description (see definitions above)
 +
* [[Template:HigCompTblHead2]] - table header for '''alternatives table''' (see above)
 +
* [[Template:HigCompTblHead2Package]] - table header for a '''package table''' (see above)
 +
* [[Template:HigCompTblSec2]] - grey table section rows
 +
* [[Template:HigCompTblRow2]] - Eclipse project row
 +
** [[Template:HigCompTblRow2Wiki]] - Eclipse project row with regular wiki page <-- preferred over *2Note
 +
** [[Template:HigCompTblRow2Note]] - Eclipse project row with "note" wiki page <-- alternate to *2Wiki [deprecated]
 +
 
 +
===Table Header ===  
 +
Left-most column
 +
* <Component Name> - wiki page describing this Component. Should follow [[Component Description Template]]
 +
* bugzilla shortcuts - create, open, closed
 +
 
 +
===Table Section Row ===
 +
Left-most column
 +
* Indicates the runtime environment supported by the project-rows in this section (e.g. Java 1.4 or Adobe Flex, etc.)
 +
 
 +
=== Project Rows ===
 +
 
 +
Each regular row of the table is a project.
 +
 
 +
*'''type''' of project
 +
**''Interface'' - this project defines the interface for the component separately from its implementation
 +
**''Impl.'' - implementation
 +
**''Alt. Impl'' - one of N alternative implementations of the component interface
 +
**''Test'' - unit test project
 +
**''Misc'' - misc supporting implementation project
 +
*'''project name''' (Second-from-left-most column)
 +
**If the project is shared with other components the word "(shared)" will appear after the project name
 +
*'''Repository''' - '''svn''' link to the SVN source files and '''viewsvn''' link. Note
 +
 
 +
:Use either the https link given, or substitute svn+ssh for https as the svn URL in order to access the code for a project
 +
 
 +
*'''Downloads''' - link to the mostly recently generated nightly on build.eclipse.org [Some day: this page will also include all stable builds]. If the project can't be autobuilt (i.e. there are not downloads) then add a downloadurl param with value "no" (this appears as "[no downloads]" in the HTML
 +
*'''Test''' - For each of the java sub-projects of each Component listed in all of these tables there exists a second project a sister ".test" project exists containing unit tests. These tests are [well, will soon be] automatically run during the nightly build process. This cell should contain a status word related to these tests:
 +
**'''none''' - no sister ".test" project exists
 +
**'''minimal''' - a few unit tests exist in the ".test" project
 +
**'''good''' - reasonable coverage of functionality exists in the ".test" project
 +
*'''H1.0''' [MANDATORY] - green LED if this component is part of 1.0 (red otherwise)<br>
 +
*'''H1.1''' [MANDATORY] - green LED if this component is part of 1.1 (red otherwise)<br>
 +
*'''Owner''' - email of the owner of this component
 +
 
 +
== Old Template ==
 +
* [[Old Components Page Conventions]] using older templates

Latest revision as of 15:28, 15 August 2014

This page describes the definitions and table formatting conventions used on these pages: Components.

Definitions

Three kinds of tables

There are three kind of tables on these Components pages:

Single project
tables that describe a single Component and implement it with a single Project (row). Example.
Alternatives
tables that describe a single Component but contain multiple alternative implementation Projects (rows). Example.
Package
tables that describe a set of rows each of which is a Component. Example.

Table Format

The tables on the Components page uses these templates:

Table Header

Left-most column

Table Section Row

Left-most column

  • Indicates the runtime environment supported by the project-rows in this section (e.g. Java 1.4 or Adobe Flex, etc.)

Project Rows

Each regular row of the table is a project.

  • type of project
    • Interface - this project defines the interface for the component separately from its implementation
    • Impl. - implementation
    • Alt. Impl - one of N alternative implementations of the component interface
    • Test - unit test project
    • Misc - misc supporting implementation project
  • project name (Second-from-left-most column)
    • If the project is shared with other components the word "(shared)" will appear after the project name
  • Repository - svn link to the SVN source files and viewsvn link. Note
Use either the https link given, or substitute svn+ssh for https as the svn URL in order to access the code for a project
  • Downloads - link to the mostly recently generated nightly on build.eclipse.org [Some day: this page will also include all stable builds]. If the project can't be autobuilt (i.e. there are not downloads) then add a downloadurl param with value "no" (this appears as "[no downloads]" in the HTML
  • Test - For each of the java sub-projects of each Component listed in all of these tables there exists a second project a sister ".test" project exists containing unit tests. These tests are [well, will soon be] automatically run during the nightly build process. This cell should contain a status word related to these tests:
    • none - no sister ".test" project exists
    • minimal - a few unit tests exist in the ".test" project
    • good - reasonable coverage of functionality exists in the ".test" project
  • H1.0 [MANDATORY] - green LED if this component is part of 1.0 (red otherwise)
  • H1.1 [MANDATORY] - green LED if this component is part of 1.1 (red otherwise)
  • Owner - email of the owner of this component

Old Template

Back to the top