|
| Re: Any issues accessing a common project (via cvs) with 3.4 and 3.3? [message #330328 is a reply to message #330292] |
Fri, 25 July 2008 14:16   |
Eclipse User |
|
|
|
Originally posted by: eclipse-news.rizzoweb.com
Michael Giroux wrote:
> We have a large development project. Most team members are using Eclipse
> 3.3. We would like to evaluate Eclipse 3.4, but before we do that, we want
> to know if there will be issues with any of the files.
>
> We know that if an individual developer upgrades a workspace to 3.4 it may
> not be backward compatable with 3.3. But there does not seem to be much
> documentation describing issues with sharing a project.
>
> We are concerned that if a developer begins to use Ganymede and commits
> something to CVS, the project may become unusable for Eclipse 3.3 users.
> For example, is there any chance that 3.4 will make entries in the
> .classpath that are not recognized by 3.3? What about shared launch
> configurations?
>
> The files that seem to be of interest include:
> .classpath
> .project
> *.launch
> .cdtproject
> .cproject
>
> Are there any issues with these?
I can't speak about the CDT files (not a CDT user) but I can tell you
that I've been the sole 3.4 user on my team for a couple of months,
without any significant problems. Because we are building plugins and an
RCP app, there's a couple of things I can't do easily in 3.4, but the
only "general purpose" (ie, non-RCP-related) issue is that 3.4 changes
the .launch files a little. I haven't taken the time to analyze the
details, but I just avoid checking in .launch files until the rest of
the team moves up to 3.4
Eric
|
|
|
|
Powered by
FUDForum. Page generated in 0.03178 seconds
] 
Search
Help
Register
Login
Home
