1<?xml version="1.0"?>
2
3<!DOCTYPE topLevel [
4  <!ELEMENT topLevel (zipTypes,logFiles)>
5  
6  <!ELEMENT zipTypes (zipType+)>
7  
8  <!ELEMENT zipType (platform)>
9  <!ATTLIST zipType
10  		name	CDATA #REQUIRED
11  >
12   
13  <!ELEMENT platform EMPTY>
14  <!ATTLIST platform
15  		id		ID #REQUIRED
16  		name	CDATA #REQUIRED
17  		fileName CDATA #REQUIRED
18  >
19  		
20  <!ELEMENT logFiles (logFile+)>
21  
22  <!ELEMENT logFile  (effectedFile+)>
23    <!ATTLIST 	zipType
24  		name	CDATA #REQUIRED
25  	>
26  		
27  <!ELEMENT effectedFile EMPTY>
28    <!ATTLIST effectedFile
29  		id		CDATA #REQUIRED
30  >
31]>
32
33<!--
34The element and attribute definitions are as follows:
35
36<zipTypes> - listing of binary distributable categories, ie. SDK, examples, tests.
37
38<zipType> - a category of binary distributable.
39	name - name of binary distributable category.
40
41<platform> - description of a platform-specific or non-platform specific binary distributable.
42	id - unique identifier for the platform relevant to the zip file referenced in fileName attribute.  Used to map compile logs and test logs listed in the manifest to a specific platform of a zipType.
43	name - text that should appear on download page to describe where the binary can be installed, ie. "ALL" or "Windows 98/ME/2000/XP".
44	fileName - html source inserted on download index page to produce link to the distributable.
45
46<logFiles> - listing of JUnit test result files and compile logs and their mappings to <platform> elements.
47	
48<logFile>
49	name - the path to a file relative to value used for 
50
51<effectedFile> - references the value of the id attribute for a platform element.  Used to mark a <platform> with a status depending on the log content.
52
53-->
54
55<topLevel>
56<zipTypes>
57	<!--example
58	
59	<zipType name="zipTypeName">
60		<platform id="ID" name="applicable platforms" fileName='&lt;a href="file.zip">file.zip&lt;/a>'></platform>
61	</zipType>
62	
63	-->
64</zipTypes>
65
66<logFiles>
67	<!--list JUnit test results-->
68	<!--example:  if there are JUnit test failures found in this log, the file identified with id "ID" should be marked with a red x.
69	
70	<logFile name="junittestresult.xml">
71		<effectedFile id="ID"></effectedFile>
72	</logFile>
73	
74	-->
75	
76	<!--list compile logs-->
77	<!--example:  if there are compile errors found in this log, the file identified with id "ID" should be marked with a red x.
78	<logFile name="pluginname/myjar.bin.log">
79		<effectedFile id="ID"></effectedFile>
80	</logFile>
81	-->
82</logFiles>
83</topLevel>
84
85