Bug 528186 - Replace usage of Platform#getJobManager by
Job#getJobManager
Signed-off-by: Karsten Thoms <karsten.thoms@itemis.de>
diff --git a/bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs.htm b/bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs.htm
index 92026e2..f22ef3e 100644
--- a/bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs.htm
+++ b/bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs.htm
@@ -177,8 +177,8 @@
work with the job infrastructure can use <b><a href="../reference/api/org/eclipse/core/runtime/jobs/IJobManager.html">IJobManager</a></b>
to perform tasks such as suspending all jobs in the system, finding out which job is running, or receiving progress
feedback about a particular job. The platform's job manager can be obtained using
-<b><a href="../reference/api/org/eclipse/core/runtime/Platform.html">Platform</a></b> API:</p>
-<pre> IJobManager jobMan = Platform.getJobManager();
+<b><a href="../reference/api/org/eclipse/core/runtime/jobs/Job.html">Job</a></b> API:</p>
+<pre> IJobManager jobMan = Job.getJobManager();
</pre>
<p>Plug-ins interested in the state of all jobs in the system can register a job change listener on the job manager rather
than registering listeners on many individual jobs.
@@ -201,7 +201,7 @@
<b><a href="../reference/api/org/eclipse/core/runtime/jobs/IJobManager.html">IJobManager</a></b>
protocol can be used to cancel, join, sleep, or find all jobs in a family:
<pre>
- IJobManager jobMan = Platform.getJobManager();
+ IJobManager jobMan = Job.getJobManager();
jobMan.cancel(MY_FAMILY);
jobMan.join(MY_FAMILY, null);
</pre>
diff --git a/bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs_locks.htm b/bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs_locks.htm
index c304435..f211fe9 100644
--- a/bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs_locks.htm
+++ b/bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs_locks.htm
@@ -26,7 +26,7 @@
</p>
<pre> ...
myObject = initializeImportantObject();
- IJobManager jobMan = Platform.getJobManager();
+ IJobManager jobMan = Job.getJobManager();
<b>myLock = jobMan.newLock();</b>
...
</pre>
diff --git a/bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs_progress.htm b/bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs_progress.htm
index 2576c03..af62c75 100644
--- a/bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs_progress.htm
+++ b/bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs_progress.htm
@@ -135,7 +135,7 @@
and associate it with a job.
</p>
<pre> ...
- IJobManager jobMan = Platform.getJobManager();
+ IJobManager jobMan = Job.getJobManager();
myGroup = jobMan.createProgressGroup();
job.setProgressGroup(myGroup, 600); // specify the units of work the job needs to show.
job.schedule()
diff --git a/bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs_rules.htm b/bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs_rules.htm
index 56df046..1e4de3d 100644
--- a/bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs_rules.htm
+++ b/bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs_rules.htm
@@ -123,7 +123,7 @@
The following example acquires a rule within a try/finally block, preventing other
threads and jobs from running with that rule for the duration between
invocations of <tt>beginRule</tt> and <tt>endRule</tt>.</p>
-<pre> IJobManager manager = Platform.getJobManager();
+<pre> IJobManager manager = Job.getJobManager();
try {
manager.beginRule(rule, monitor);
... do some work ...
