RE: [Subclipse-users] "Add to version control" problem in Subclise 1.1.10

Hi Mark,

        But this does not change the problem that subclipse should put whatever file I say under SVN control version. It is not up to the SVN client decide this right? Therefore I still have the problem and I don't know how to solve it... and it also doesn't explains why some .class has the icon (under version control) and some others don't.

PS: I am creating a Javacard compilation tool that needs the .class to generate the .cap and that is the why I need the .class under the version control. I explain why I must put the .class files in SVN just to clarify the reason to you although the point is: Subclipse cannot decide for me what will be in the server or not.

============
Olavo Lira
________________________________________
From: Mark Phippard [mailto:markphip@gmail.com]
Sent: Thursday, February 01, 2007 8:02 PM
To: users@subclipse.tigris.org
Subject: Re: [Subclipse-users] "Add to version control" problem in Subclise 1.1.10

Eclipse has a concept of derived files.  Bring up the Eclipse Resource Properties dialog on one of these files and you will see the Derived check box is checked.  Team providers are supposed to automatically ignore derived files.  .class files compiled by Eclipse will be marked derived.

Subclipse does not decorate these items because 99% of the time they should not be versioned and it would kill performance for us to ask Subversion the status of these files when almost always we know they should be ignored.

I cannot think of any situation where storing .class files in Subversion is a good idea.

I also do not think we have made any changes in Subclipse that would effect the decoration of these files.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/ 
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org