Bug 14024 - [Team] Project properties not persisted by Team
Summary: [Team] Project properties not persisted by Team
Status: RESOLVED DUPLICATE of bug 36965
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 2.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-VCM-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-04-17 12:24 EDT by Josh Heidebrecht CLA
Modified: 2003-06-23 08:43 EDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Josh Heidebrecht CLA 2002-04-17 12:24:37 EDT
Important project properties are not shared in a team environment.

From a Project's properties, e.g. (right click on a project->properties)
-Debugger Source Lookup information
-javadoc location
-launch configuration type
-Launcher
-Runtime JRE

Since these options are specific to a project they should be shared along with 
the project in team. I suspect that there are other preferences found in Window-
>Preferences that should be shared as well.

These settings can be hand configured, but our customers are starting to see 
their workspace include dozens of projects & dozens of developers. 
Consequently, hand tuning projects is no longer an option.
Comment 1 DJ Houghton CLA 2002-04-17 15:48:29 EDT
Resource properties are not shared. Currently we only have the concepts of 
session and persistent properties, not server properties. In order for 
properties to be shared they would probably have to be stored in files in the 
project content area, depending on the specifics of the team provider.

Moving to Platform/VCM for comment on shared properties.
Comment 2 Josh Heidebrecht CLA 2002-04-17 16:11:03 EDT
The customer that raised this issue is also attempting to share workspace 
settings that aren't project specific. E.g. they want to enforce code 
formatting styles, so sharing those settings are important.

So, the customer is asking for something even more general than what I 
initially stated. This sounds almost like a '.solution' concept where a 
solution file is a project independent mechanism for sharing workspace 
settings. For project specific information that doesn't require its own .XXX 
file then it would make sense to roll those properties into the .project. 

I understand that the above suggestion is terribly oversimplifying reality, but 
it should give you a feel for the requirement.
Comment 3 Kevin McGuire CLA 2002-04-19 14:01:02 EDT
Agree, would be great, but we weren't able to solve for 2.0.

Bugzilla note: reporter can set severity (how it impacts you) but its the 
owner's job to set priority (when it should be done wrt other bugs 
outstanding).  Consequently I've put priority down to P3 since we can't do for 
2.0.
Comment 4 Michael Valenta CLA 2002-09-09 16:10:29 EDT
Reopening
Comment 5 Michael Valenta CLA 2003-06-23 08:43:02 EDT

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