Bug 69268

Summary:	project-names shouldn't be references by .classpath files
Product:	[Eclipse Project] JDT	Reporter:	Sven Köhler <sven.koehler>
Component:	Core	Assignee:	JDT-Core-Inbox <jdt-core-inbox>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P3
Version:	3.0
Target Milestone:	3.0
Hardware:	All
OS:	All
Whiteboard:

Description Sven Köhler

2004-07-04 19:53:52 EDT

It is problematic, that the project-names are referenced in .classpath files.
I'd like random IDs better, since that way project-dependencies could be shared
with other people in a team.
The way it is now, all people in a team have to have the same project-names to
be abled to do that.

Comment 1 Philipe Mulet

2004-07-05 12:43:23 EDT

What would this random ID be then and how could it be shared amongst 
developpers ?

Comment 2 Sven Köhler

2004-07-05 15:28:50 EDT

The Project-ID could be an addition property of a project. It than must be
stored in the .project file and referenced by the .classpath files instead of
the project names.

The Project-ID would be a 32-bit (or longer) integer value, and it would be
chosen by random if a project is created. Even among diffenrent computers, there
shouldn't be much collisions.

Comment 3 Sven Köhler

2004-07-05 15:35:10 EDT

BTW: i assume that the .project file is shared among the developers.
I also filed Bug 69267 since the project-name isn't really honoured when a
project is checked out. So the project-names are pretty much the badest thing to
use for a file like .classpath which is shared among many developers in a team.

Comment 4 Philipe Mulet

2004-07-05 15:56:53 EDT

Then, once you checked out a project. It references subsequent projects, and 
only tells you about unbound IDs. How can you figure the missing ones, do you 
check them all out ? Having the name show up is likely a very good hint for 
your teammates, and you simply agree that people should change the name on 
checkout (unless they want to fixup all dependent project classpaths).

Comment 5 Sven Köhler

2004-07-05 16:21:21 EDT

OK, but than Bug 69267 should be "fixed". Either make Eclipse keeping the name
of the project and the project-name in the .project-file consistent, or don't
store the project-name in the .project file, since it isn't necessarily used by
Eclipse.

Comment 6 Philipe Mulet

2004-07-05 18:02:24 EDT

Comment#4 should have been reading: "[...] you simply agree that people should 
NOT change the name on checkout [...]".

Bug 69267 looks like a real inconsistency, which is misleading I believe.

Closing this one, since no action is planned on the build path.