Bug 174626 - [api] All local implementation should be internal
Summary: [api] All local implementation should be internal
Status: CLOSED FIXED
Alias: None
Product: Target Management
Classification: Tools
Component: RSE (show other bugs)
Version: 1.0.1   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 2.0   Edit
Assignee: Martin Oberhuber CLA
QA Contact: Martin Oberhuber CLA
URL:
Whiteboard:
Keywords: api
Depends on:
Blocks: 170922
  Show dependency tree
 
Reported: 2007-02-19 09:31 EST by Martin Oberhuber CLA
Modified: 2008-08-13 13:16 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Oberhuber CLA 2007-02-19 09:31:56 EST
All packages of the local subsystem and service implementation should be
internal.
These are implementation details, it is sufficient for users to know the
generic RSE APIs.

services.local           -->  org.eclipse.rse.internal.services.local
services.local.files     -->  org.eclipse.rse.internal.services.local.files
services.local.processes -->  org.eclipse.rse.internal.services.local.processes
services.local.search    -->  org.eclipse.rse.internal.services.local.search
services.local.shell     -->  org.eclipse.rse.internal.services.local.shell
connectorservice.local   -->  org.eclipse.rse.internal.connectorservice.local
subsystems.files.local   -->  org.eclipse.rse.internal.subsystems.files.local
subsystems.processes.local->org.eclipse.rse.internal.subsystems.processes.local
subsystems.shells.local  -->  org.eclipse.rse.internal.subsystems.shells.local
Comment 1 Martin Oberhuber CLA 2007-02-19 09:37:28 EST
Checked in on 19-Feb-2007
Comment 2 Martin Oberhuber CLA 2007-02-21 10:25:05 EST
made SubSystemConfiguration implementation API again with following checkin:

21-Feb-2007
[174271][174263][174626] make SubSystemConfiguration implementations API again
for customization
Comment 3 Martin Oberhuber CLA 2007-02-28 08:32:19 EST
Verified with I20070223-0730
Comment 4 Martin Oberhuber CLA 2008-08-13 13:16:57 EDT
[target cleanup] 2.0 M5 was the original target milestone for this bug