| Cvs and .classpath .project files [message #84963] |
Sun, 29 June 2003 22:01  |
Eclipse User |
|
|
|
Originally posted by: paul.noemail.thankyou.com
Hi all,
How can I remove the .classpath and .project files from cvs sharing? I've
added them to the ignored resources list which hasn't made any difference -
they are still showing up in the synchronise window.
Any advice ?
|
|
|
|
|
| Re: Cvs and .classpath .project files [message #91597 is a reply to message #85832] |
Fri, 11 July 2003 03:03  |
| Eclipse User |
|
|
|
Why can't the JDT automatically detect .classpath files that have a
platform dependent suffix ?
John Arthorne wrote:
> The SWT plugin has the same problem. It gets around this by checking in
> all the .classpath files with the OS as the suffix: .classpath_win32,
> .classpath_motif, etc. This requires an extra step on checkout: rename
> the appropriate .classpath_xxx file to be .classpath. This way it's the
> same steps on all platforms.
>
> As Peter says, the approach taken by other platform plugins is to put OS
> -specific code in a plugin fragment (org.eclipse.core.resources.win32,
> for example, is the windows-specific fragment of the resources plugin).
> --
>
>
> Graham Perks wrote:
>
>> The problem is, I develop on both Windows and Linux. I would like the
>> .classpath files to be in CVS. However each platform will have a
>> different
>> classpath. So I decide, well let's check in ONE version at least, say the
>> Windows one. Now on Linux I get nagged every time I sync and one day will
>> accidentally check in the Linux version. Then when I next sync on
>> Windows,
>> it will pull down the Linux version and my Windows installation is hosed.
>>
>> What a pain!
>>
>>
>> "Richard L. Kulp" <richkulp@NOSPAM.us.ibm.com> wrote in message
>> news:bef8ss$e4k$1@eclipse.org...
>>
>>> However, do you really want to delete them?
>>>
>>> It makes sharing the project very difficult. Those files contain all of
>>> the information necessary to check out a project as a Java Project AND
>>> have the correct build path already setup. Otherwise everytime the
>>> project is checked out, it would need to be explicitly checked out as a
>>> Java project and then by hand the build path needs to be setup.
>>>
>>> --
>>> Thanks, Rich Kulp
>>>
>>>
>>
>>
>>
>
|
|
|
Powered by
FUDForum. Page generated in 0.04069 seconds
Home