This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 44216 - [vcs-cache-review] Revise whether the VCS Cache API could be made private
Summary: [vcs-cache-review] Revise whether the VCS Cache API could be made private
Status: RESOLVED FIXED
Alias: None
Product: obsolete
Classification: Unclassified
Component: vcscore (show other bugs)
Version: 4.x
Hardware: All All
: P1 blocker (vote)
Assignee: issues@obsolete
URL:
Keywords:
Depends on:
Blocks: 32089 43637
  Show dependency tree
 
Reported: 2004-06-02 16:04 UTC by Miloslav Metelka
Modified: 2004-12-01 16:30 UTC (History)
0 users

See Also:
Issue Type: TASK
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Miloslav Metelka 2004-06-02 16:04:41 UTC 
It could be useful to make the Cache API to be
private (more flexible maintenance etc.) among the
vcs modules and have a simpler stable API for the
VCS profiles to make an update from the repository.
Comment 1 Miloslav Metelka 2004-06-02 16:17:23 UTC 
Please decide the VCS Cache API stability level according to
http://openide.netbeans.org/tutorial/api-design.html
and create arch.xml document (or update the existing one in vcscore).
Comment 2 _ pkuzel 2004-11-09 13:44:26 UTC 
Plan for simplified cache is to avoid any public API. Our profiles
will use friend contracts (implementation dependency).

Stable profile vendor's may reopen the issue a contribute to APIsing.
Comment 3 _ pkuzel 2004-12-01 16:30:30 UTC 
Currently CVS profile depends on FileAttributeProvider, FileProperties
and FolderProperties contracts. In future we can expect the same for
Subversion profile.

Note, it's revised (but not yet implemented).