1
0
Fork 0
mirror of https://github.com/eclipse-cdt/cdt synced 2025-07-06 00:25:25 +02:00

[doc] Fix unnecessary broken links and redirects found by Linksleuth

This commit is contained in:
Martin Oberhuber 2007-02-28 17:45:36 +00:00
parent 9f75eb674c
commit 9f9115b625
10 changed files with 101 additions and 101 deletions

View file

@ -111,7 +111,7 @@ support in the future into internal packages.</p>
API changes on the RSE 1.0 maintenance stream (1.0.x), but we need to
change the API for TM 2.0 in a not backward compatible way.<br/>
All such API changes are voted on
by committers on the <a href="http://dev.eclipse.org/mailman/listinfo/dsdp-tm-dev">
by committers on the <a href="https://dev.eclipse.org/mailman/listinfo/dsdp-tm-dev">
dsdp-tm-dev</a> developer mailing list, and documented in a migration guide
for future releases.</p>
<p>Currently, we see the following areas for more potential API changes:

View file

@ -20,7 +20,7 @@ feedback and help further improving the APIs. Therefore,</p>
<p>This means, that we reserve the right to change any API after RSE 1.0
in a not backward compatible way. All such API changes will be voted on
by committers on the <a href="http://dev.eclipse.org/mailman/listinfo/dsdp-tm-dev">
by committers on the <a href="https://dev.eclipse.org/mailman/listinfo/dsdp-tm-dev">
dsdp-tm-dev</a> developer mailing list, and documented in a migration guide
for future releases. We expect that with Community Feedback, we'll reach a
stable, hardened API for RSE 2.0. Please give your feedback on

View file

@ -27,7 +27,7 @@ feedback and help further improving the APIs. Therefore,</p>
<p>This means, that we reserve the right to change any API after RSE 1.0
in a not backward compatible way. All such API changes will be voted on
by committers on the <a href="http://dev.eclipse.org/mailman/listinfo/dsdp-tm-dev">
by committers on the <a href="https://dev.eclipse.org/mailman/listinfo/dsdp-tm-dev">
dsdp-tm-dev</a> developer mailing list, and documented in a migration guide
for future releases. We expect that with Community Feedback, we'll reach a
stable, hardened API for RSE 2.0. Please give your feedback on

View file

@ -36,7 +36,7 @@ feedback and help further improving the APIs. Therefore,</p>
<p>This means, that we reserve the right to change any API after RSE 1.0
in a not backward compatible way. All such API changes will be voted on
by committers on the <a href="http://dev.eclipse.org/mailman/listinfo/dsdp-tm-dev">
by committers on the <a href="https://dev.eclipse.org/mailman/listinfo/dsdp-tm-dev">
dsdp-tm-dev</a> developer mailing list, and documented in a migration guide
for future releases. We expect that with Community Feedback, we'll reach a
stable, hardened API for RSE 2.0. Please give your feedback on

View file

@ -16,11 +16,11 @@
<ul>
<li><A href="#Services">Service Layer</A></li>
<li><A href="#Subsystems">Subsystem Layer</A></li>
<li><A href="#UIs">UI Layer</A></li>
<li><A href="#UI">UI Layer</A></li>
</ul>
<h2><A name="Services">RSE Service Layer</A></h2>
<A name="Services"></A><h2>RSE Service Layer</h2>
<p>
This is the headless, barebones API layer that is used to interact with different protocols to
provide remote services that can be integrated into RSE. By default, RSE defines the following
@ -38,7 +38,7 @@ different protocols. For example, the IFileService could be implemented locally
other protocol. Similarly, the IShellService could be implemented locally via DataStore, telnet, SSH or something
else.
</p>
<h2><A name="SubSystems">RSE Subsystem Layer</A></h2>
<A name="Subsystems"></A><h2>RSE Subsystem Layer</h2>
<p>
RSE subsystems integrate the services of the service layer with connection information, model artifacts and persistence.
Each subsystem is associated with a single service type. For example, the file service subsystem is associated with the
@ -67,7 +67,7 @@ specify a criteria for which to query a set of data. In addition to filters, th
associated with a subsystem, each of which can be saved and restored across sessions.
</p>
<h2><A name="UI">RSE UI Layer</A></h2>
<A name="UI"></A><h2>RSE UI Layer</h2>
<p>
The Remote System Explorer perspective provides views that render the subsystems and associated artifacts. Users can create
new connections, which can be expanded to reveal subsystems and the information the subsystems reveal about a system.

View file

@ -1,11 +1,11 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
<html>
<head>
<meta name="copyright" content="Copyright (c) IBM Corporation and others 2005, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
<meta name="copyright" content="Copyright (c) IBM Corporation and others 2005, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<meta http-equiv="Content-Style-Type" content="text/css">
<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
<title>RSE Hosts</title>
<title>RSE Filters</title>
<link rel="stylesheet" type="text/css" href="../book.css">
</head>
<body>

View file

@ -18,7 +18,7 @@ extend the RSE:
<li><a href="tutorial/subsystem.html">Creating a subsystem configuration</a> for working with remote resources, using the <a href="plugin/subsystem.html">org.eclipse.rse.core.subsystemConfigurations</a> extension point.
</ul>
<p>The source code for all tutorials is available in the RSE-examples package, which
can be obtained from the DSDP <a href="http://download.eclipse.org/dsdp/tm/downloads">
can be obtained from the DSDP <a href="http://download.eclipse.org/dsdp/tm/downloads/">
Target Management download site</a> or directly from the RSE <b>Update Site</b>. In fact,
the simplest way to get the examples is to choose <I>Help &gt; Software Updates &gt;
Find and Install</I> from the Workbench, get the Examples installed, and then choose

View file

@ -42,7 +42,7 @@ feedback and help further improving the APIs. Therefore,</p>
<p>This means, that we reserve the right to change any API after RSE 1.0
in a not backward compatible way. All such API changes will be voted on
by committers on the <a href="http://dev.eclipse.org/mailman/listinfo/dsdp-tm-dev">
by committers on the <a href="https://dev.eclipse.org/mailman/listinfo/dsdp-tm-dev">
dsdp-tm-dev</a> developer mailing list, and documented in a migration guide
for future releases. We expect that with Community Feedback, we'll reach a
stable, hardened API for RSE 2.0. Please give your feedback on

View file

@ -52,7 +52,7 @@
-bottom "Copyright (c) IBM Corporation and others 2000, 2006. All Rights Reserved."
-group "RSE Core Plug-in Packages" "org.eclipse.rse.core;org.eclipse.rse.core.*"
-group "RSE UI Plug-in Packages" "org.eclipse.rse.ui;org.eclipse.rse.ui.*"
-link http://java.sun.com/j2se/1.5/docs/api
-link http://java.sun.com/j2se/1.4.2/docs/api
-linkoffline ./../../../org.eclipse.platform.doc.isv/reference/api @javadoc.link.location@/platform/reference/api/
-linkoffline ./../../../org.eclipse.dstore.doc.isv/reference/api ../org.eclipse.dstore.doc.isv/reference/api
-link http://bundles.osgi.org/javadoc/r4

View file

@ -20,7 +20,7 @@ feedback and help further improving the APIs. Therefore,</p>
<p>This means, that we reserve the right to change any API after RSE 1.0
in a not backward compatible way. All such API changes will be voted on
by committers on the <a href="http://dev.eclipse.org/mailman/listinfo/dsdp-tm-dev">
by committers on the <a href="https://dev.eclipse.org/mailman/listinfo/dsdp-tm-dev">
dsdp-tm-dev</a> developer mailing list, and documented in a migration guide
for future releases. We expect that with Community Feedback, we'll reach a
stable, hardened API for RSE 2.0. Please give your feedback on