1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Eclipse Build Drop</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<meta name="author" content="Eclipse Foundation, Inc." />
<meta name="keywords"
content="eclipse,project,plug-ins,plugins,java,ide,swt,refactoring,free java ide,tools,platform,open source,development environment,development,ide" />
<link rel="stylesheet" type="text/css"
href="../../../eclipse.org-common/stylesheets/visual.css" media="screen" />
<link rel="stylesheet" type="text/css"
href="../../../eclipse.org-common/stylesheets/layout.css" media="screen" />
<link rel="stylesheet" type="text/css"
href="../../../eclipse.org-common/stylesheets/print.css" media="print" />
<script type="text/javascript">
sfHover = function() {
var sfEls = document.getElementById("leftnav").getElementsByTagName(
"LI");
for (var i = 0; i < sfEls.length; i++) {
sfEls[i].onmouseover = function() {
this.className += " sfhover";
}
sfEls[i].onmouseout = function() {
this.className = this.className.replace(new RegExp(
" sfhover\\b"), "");
}
}
}
if (window.attachEvent)
window.attachEvent("onload", sfHover);
</script>
</head>
<body>
<div id="leftcol">
<ul id="leftnav">
<li><a href="#Repository">Eclipse p2 Repository</a></li>
<li><a href="#EclipseSDK">Eclipse SDK</a></li>
<li><a href="#JUnitPlugin">JUnit Plugin Tests and Automated
Testing Framework</a></li>
<li><a href="#ExamplePlugins">Example Plug-ins</a></li>
<li><a href="#RCPRuntime">RCP Runtime Binary</a></li>
<li><a href="#RCPSDK">RCP SDK</a></li>
<li><a href="#DeltaPack">Delta Pack</a></li>
<li><a href="#PlatformRuntime">Platform Runtime Binary</a></li>
<li><a href="#JDTRuntime">JDT Runtime Binary</a></li>
<li><a href="#JDTSDK">JDT SDK</a></li>
<li><a href="#JDTCORE">JDT Core Batch Compiler</a></li>
<li><a href="#PDERuntime">PDE Runtime Binary</a></li>
<li><a href="#PDESDK">PDE SDK</a></li>
<li><a href="#CVSRuntime">CVS Client Runtime Binary</a></li>
<li><a href="#CVSSDK">CVS Client SDK</a></li>
<li><a href="#SWT">SWT binary and Source</a></li>
<li><a href="#org.eclipse.releng">org.eclipse.releng.tools
plug-in</a></li>
</ul>
</div>
<div id="midcolumn">
<h2>Download Details</h2>
<div class="homeitem3col">
<ul class="midlist">
<li><a name="Repository"> <b>Eclipse Repository</b>
</a>
<ul>
<li>The Eclipse Repository includes all that is produced by the
Eclipse Project, including the Eclipse Platform, Java development
tools, and Plug-in Development Environment, Unit Tests, and even
some extra items from other projects required by Eclipse (such as
Equinox and a few bundles from EMF and Orbit). Please be aware
that repositories have different retention policies, and
restrictions on what types can be updated with what other types.
See the wiki's <a
href="http://wiki.eclipse.org/Eclipse_Project_Update_Sites">Update
Sites</a> document for details.
</li>
</ul></li>
<li><a name="EclipseSDK"> <b>Eclipse SDK</b>
</a>
<ul>
<li>The Eclipse SDK includes the Eclipse Platform, Java
development tools, and Plug-in Development Environment, including
source and both user and programmer documentation. If you aren't
sure which download you want... then you probably want this one.
You will need a <a
href="http://wiki.eclipse.org/Eclipse/Installation#Install_a_JVM">Java
runtime environment (JRE)</a> to use Eclipse (Java SE 6 or greater
is recommended).
</li>
</ul></li>
<li><a name="JUnitPlugin"> <b> JUnit Plugin Tests and
Automated Testing Framework </b>
</a>
<ul>
<li>These packages contain the Test Framework and JUnit test
plugins used to run JUnit plug-in tests from the command line. See
the Platform's <a
href="http://wiki.eclipse.org/Platform-releng/Automated_Testing">Automated
Testing</a> wiki page for more information and setup instructions.
Includes both source code and binary.
</li>
</ul></li>
<li><a name="ExamplePlugins"> <b> Example Plug-ins </b>
</a>
<ul>
<li>To install the examples, download the p2 repository zip
containing the examples into a directory on disk. Select <b>Help
-> Install New Software</b>. Select <b>Add</b> to add a new
software site. Select <b>Archive</b> and specify the location of
the examples p2 repository zip and <b>Okay</b>. You will be
prompted to restart Eclipse to enable the new bundles. For
information on what the examples do and how to run them, look in
the "Examples Guide" section of the "Platform
Plug-in Developer Guide", by selecting Help Contents from the
Help menu, and choosing "Platform Plug-in Developer
Guide" book from the combo box.
</li>
</ul></li>
<li><a name="RCPRuntime"> <b> RCP Runtime Binary </b>
</a>
<ul>
<li>This p2 repository contains the Eclipse Rich Client
Platform base bundles and do not contain source or programmer
documentation. These downloads are meant to be used as target
platforms when developing RCP applications, and are not
executable, stand-alone applications.</li>
</ul></li>
<li><a name="RCPSDK"> <b> RCP SDK </b>
</a>
<ul>
<li>This p2 repository consists of the Eclipse Rich Client
Platform base bundles and their source and the RCP delta pack.</li>
</ul></li>
<li><a name="DeltaPack"> <b> Delta Pack </b>
</a>
<ul>
<li>The delta pack contains all the platform specific resources
from the SDK and is used for cross-platform exports of RCP
applications.</li>
</ul></li>
<!--
<li><a name="com.ibm.icu"> <b> com.ibm.icu.base binary and
source Plug-ins </b>
</a>
<ul>
<li>ICU4J (bundle com.ibm.icu) provides advanced Unicode and
Globalization support for software applications. The full version
is included in Eclipse SDK. For those that do not need that
support but need a smaller footprint for their own products, there
is a subset of ICU4J, "com.ibm.icu.base" available from the <a
href="http://download.eclipse.org/tools/orbit/downloads/">Orbit
Download Page</a>.
</li>
</ul></li>
-->
<li><a name="PlatformRuntime"> <b> Platform Runtime Binary
</b>
</a>
<ul>
<li>These drops contain only the Eclipse Platform with user
documentation and no source and no programmer documentation. The
Java development tools and Plug-in Development Environment are NOT
included. You can use these drops to help you package your tool
plug-ins for redistribution when you don't want to ship the entire
SDK.</li>
</ul></li>
<li><a name="PlatformSDK"> <b> Platform SDK </b>
</a>
<ul>
<li>These drops contain the Eclipse Platform Runtime binary
with associated source and programmer documentation.</li>
</ul></li>
<li><a name="JDTRuntime"> <b> JDT Runtime Binary </b>
</a>
<ul>
<li>This p2 repository contains the Java development tools
bundles only, with user documentation and no source and no
programmer documentation. The Eclipse platform and Plug-in
development environment are NOT included. You can combine this
with the Platform Runtime Binary if your tools rely on the JDT
being present.</li>
</ul></li>
<li><a name="JDTSDK"> <b> JDT SDK </b>
</a>
<ul>
<li>This p2 repository contains the JDT Runtime binary with
associated source and programmer documentation.</li>
</ul></li>
<li><a name="JDTCORE"> <b> JDT Core Batch Compiler </b>
</a>
<ul>
<li>These drops contain the standalone batch java compiler, Ant
compiler adapter and associated source. The batch compiler and Ant
adapter (ecj.jar) are extracted from the org.eclipse.jdt.core
plug-in as a 1.2MB download. For examples of usage, please refer
to this help section: JDT Plug-in Developer Guide>Programmer's
Guide>JDT Core>Compiling Java code.</li>
</ul></li>
<li><a name="PDERuntime"> <b> PDE Runtime Binary </b>
</a>
<ul>
<li>This p2 repository contains the Plug-in Development
Enviroment bundles only, with user documentation. The Eclipse
platform and Java development tools are NOT included. You can
combine this with the Platform and JDT Runtime Binary or SDK if
your tools rely on the PDE being present.</li>
</ul></li>
<li><a name="PDEProducts"> <b> PDE Build Products </b>
</a>
<ul>
<li>The PDE Builders are self-contained, executable PDE Build
configurations that can be used to build OSGi and Eclipse-based
systems. They can also be used as the basis for more sophisticated
build systems that run tests, do API scans, publish builds etc.</li>
</ul></li>
<li><a name="PDESDK"> <b> PDE SDK </b>
</a>
<ul>
<li>These drops contain the PDE Runtime Binary with associated
source.</li>
</ul></li>
<li><a name="CVSRuntime"> <b> CVS Client Runtime Binary </b>
</a>
<ul>
<li>This p2 repository contains the CVS Client plug-ins only.
The Eclipse platform, Java development, and Plug-in Development
Environment tools are NOT included. You can combine this with the
Platform and JDT Runtime Binary or SDK if your tools rely on the
CVS client being present.</li>
</ul></li>
<li><a name="CVSSDK"> <b> CVS Client SDK </b>
</a>
<ul>
<li>This p2 repository contains the CVS Runtime Binary with
associated source.</li>
</ul></li>
<li><a name="SWT"> <b> SWT Binary and Source </b>
</a>
<ul>
<li><p>
These drops contain the SWT libraries and source for standalone
SWT application development. For examples of standalone SWT
applications refer to the <a
href=" http://www.eclipse.org/swt/snippets/">snippets</a>
section of the SWT Component page.
</p>
<p>To run a standalone SWT application, add the swt jar(s) to
the classpath and add the directory/folder for the SWT JNI
library to the java.library.path. For example, if you extract
the download below to C:\SWT you would launch the HelloWorld
application with the following command:</p>
<p>java -classpath C:\SWT\swt.jar;C:\MyApp\helloworld.jar
-Djava.library.path=C:\SWT HelloWorld</p>
<p>
<b>Note that if you are running on Eclipse 3.3 or later</b>, you
do not need to specify the library path, so you would launch the
HelloWorld application with the following command:
</p>
<p>java -classpath C:\SWT\swt.jar;C:\MyApp\helloworld.jar
HelloWorld</p>
<p>
To run the standalone SWT examples that are shipped with
Eclipse, download them from <a href="index.php#ExamplePlugins">here</a>.
Then copy the file
eclipse\plugins\org.eclipse.swt.examples_xxx\swtexamples.jar to
C:\SWT. Now you can run the examples that are described <a
href="http://www.eclipse.org/swt/examples.php">here</a>. For
example:
</p>
<p>
cd C:\SWT<br /> java -classpath swt.jar;swtexamples.jar
org.eclipse.swt.examples.controlexample.ControlExample
</p>
<p>On Linux systems, note that the classpath separator
character is a colon, so the equivalent command becomes:</p>
<p>java -classpath swt.jar:swtexamples.jar
org.eclipse.swt.examples.controlexample.ControlExample</p></li>
</ul></li>
<li><a name="org.eclipse.releng"> <b> Releng Tools
(org.eclipse.releng.tools)</b>
</a>
<p>This plug-in provides features that can help committers with
the Eclipse development process. It is not intended as a "tool to
extend", or provide API, etc. It is a simple utility. You can
install the tool from the usual Eclipse Project repositories, or the
zipped repo provided on the download page. Since it uses several
"internal" non-API methods, you may have to have one that "matches"
the version of your development environment.</p>
<p>Currently, the tool provides two important functions.</p>
<ol>
<li><b>Fix Copyrights</b>. In the Resource Perspective Projects
context menu. Select one or more projects in the Resource
Perspective. This action will sanity check the copyright notices
in all the *.java and *.properties files. It compares the "end
dates" with the last time the file was changed. It works with
either Git repositories, or CVS. Copyrights will be updated
automatically where the tool deems appropriate. A copyright.log
file will be written to the workspace directory noting odd
conflicts that need to be looked at and manually confirmed or
modified. You will need to commit any changes yourself.</li>
<li><b>Validate Versions Match</b>. Once turned on, in
preferences, the bundle version in the MANIFEST.MF file will be
compared with the artifact version in the pom.xml file. If they
"mismatch", then a marker is left in problems view, so the
incorrect version can be fixed before being committed for a build.
Mismatched versions can cause Tycho/Maven builds to fail and it is
easy to change the version on one spot and forget the other, so
all committers are encourage to use and turn on this tool.</li>
</ol>
<p>Older tools for use with CVS: The following tools are for using
with CVS map files, and while we have every expectation they still
work fine, they are not actively used by many committers now that
most have moved to use to Git, so in theory they might be less
stable. If you still have a use for them, that's great, and if you
find bugs, we'll accept them as valid, but will likely require a
high quality patch before much effort is spent on it, since they are
a low priority for the Eclipse Platform team.</p>
<ol>
<li><b>Release</b> to the Team menu. This action will Tag
selected projects with the specified version <b>and</b> update the
appropriate loaded *.map files with the version. The user must
have the *.map files loaded in their workspace and the use must
commit the map file changes to the repository when done.</li>
<li><b>Load Map Projects </b>to the Team menu. Select one or
more *.map file and this action will load the projects listed in
the *.map file into your workspace. Naturally the versions
specified in the *.map file will be loaded.</li>
<li><b>Tag Map Projects</b> to the Team menu. Select one or
more *Map files and this action will tag the projects listed in
the *Map files with a tag you specify.</li>
<li><b>Compare with Released</b> to the Compare menu. Compare
the selected projects with the versions referenced in the
currently loaded map files.</li>
<li><b>Replace with Released</b> to the Replace menu. Replace
the selected projects with the versions referenced in the
currently loaded map files.</li>
</ol></li>
</ul>
</div>
<hr class="clearer" />
</div>
</body>
</html>
|
