|
| Re: Which setting files should/must/shouldn't be under version control? [message #337011 is a reply to message #336989] |
Tue, 21 July 2009 02:26  |
Eclipse User |
|
|
|
Originally posted by: eclipse-news.rizzoweb.com
This recent discussion should help clarify things a little bit.
http://dev.eclipse.org/newslists/news.eclipse.newcomer/msg29 354.html
(make sure to read all of the follow-up responses).
But the use of ClearCase (or any pessimistic locking scheme that
requires explicit locking or checking-out of files) complicates matters
a little bit. Generally, the .project, .classpath, and .settings files
will only be touched if someone changes things in the Project
properties. I have seen an occasional situation where the .classpath was
updated as a result of just looking at the properties (not changing
anything) but I'm pretty sure that was in the context of a project that
was migrated from one Eclipse version to another. In other words, that
should not be happening in general and not very often.
Perhaps if you can describe an exact scenario that you are having
trouble with the .project, .classpath, and .settings being under SCM
control, then we could help find a resolution to that specific scenario...
Hope this helps,
Eric
Yves Schumann wrote:
> Hi
>
> I've posted this question on e.t.m2e some weeks ago but there was no
> response. So let me ask this here, maybe someone could tell me more
> about this.
>
> So here is the posting again:
> ---------------->8 schnipp 8<-----------------
> Some weeks ago I migrate a lot of projects from Ant build to Maven build
> using m2e. Since then we got a lot of problems with the hidden files, i.
> e. all the setting files on the projects especially with version control
> of them. Which ones should/must/shouldn't be under version control? As I
> wrote on another posting some days ago, some of the files are modified
> some of them not but nobody here know's exactly, how to handle this
> correct. Before m2e usage every of these .* files was under version
> control. But now?
>
> If using a SCM system which uses write protect files, this turnes out
> into a problem, either with a lot of errors on Eclipse if not checked
> out for usage or with highjacked files on the SCM if modifying them the
> hard way.
> ---------------->8 schnapp 8<-----------------
>
> We use ClearCase as SCM which works with write protected files and some
> of the setting files are modified just during opening a project. How
> should this be handled?
>
> Regards,
> Yves
|
|
|
Powered by
FUDForum. Page generated in 0.70437 seconds
] 
Search
Help
Register
Login
Home
