Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 48 - Make sure can future store other project reference types (1GDF7C0)
Summary: Make sure can future store other project reference types (1GDF7C0)
Status: RESOLVED DUPLICATE of bug 22
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 2.0   Edit
Hardware: All Windows NT
: P5 normal (vote)
Target Milestone: ---   Edit
Assignee: Kevin McGuire CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 20
Blocks:
  Show dependency tree
 
Reported: 2001-10-10 21:35 EDT by Kevin McGuire CLA
Modified: 2002-04-08 14:41 EDT (History)
1 user (show)

See Also:

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 Kevin McGuire CLA 2001-10-10 21:35:34 EDT 
Project references come in three flavours:

1. project name
2. project name + version (+ repo)
3.  project name + stream (+ repo)

We currently store #1.  While noone makes use of form 2 or 3, we should ensure that being able to store them at some
future time will not require changing our .vcm_meta file format.

This could be solved, for example, by having distinct xml tags for each of these forms.

NOTES:

BB (5/14/2001 4:13:08 PM)
	Right now, project references of type 1 are stored as: <project-reference name="..."/>
	If we use different tag names for 2. and 3. we should be fine. For example:
<project-version-reference name="projectname" versionname="v1" repository=":pserver:user@cvslnx:/home/cvs/vcmrepo"/>
	Moving to Active-TimePermitting as a reminder to add project references of type 2 and 3.
Comment 1 DJ Houghton CLA 2001-10-23 23:40:53 EDT 
PRODUCT VERSION:

104a
Comment 2 Kevin Haaland CLA 2002-04-08 14:41:59 EDT 
Closing as duplicate

*** This bug has been marked as a duplicate of 22 ***