Mark Phippard wrote:
>> Can you please commit Eclipse settings for all Subclibse modules?
>>
>>
>Wasn't this just done? Was there a specific module that it was not done
>for that you are referring to?
>
>
Mark, it is not about .project and .classpat files, but about bunch of
settings in .settings directory in each project
None of svnClientAdapter, org.tigris.subversion.subclipse.ui or
org.tigris.subversion.subclipse.core has project-specific settings. This
feature is used by Eclipse 3.1 (since one of the Mx builds) and
currently there is only some settings for templates committed but
nothing for compiler and code style.
>> I also think that current project names for eclipse plugins are rather short and don't give enough context as opposed to commonly used long
>>project names on eclipse.org. What do you think?
>>
>>
>I do not have an opinion one way or the other. I have about 20 different
>workspaces and shortcuts I use. Subclipse is its own workspace so it
>doesn't bother me.
>
>
Right. I have completely opposite situation. My workspace has
everything related to Eclipse plugins (over 30 projects and some of of
them are closed). So, I had to rename Subclipse projects on checkout to
make names more context-specific...
regards,
Eugene
Received on Mon Aug 22 11:31:00 2005