[android-developers] ADT painstakingly remove my exclusion setting for android library
I have a common library android project being used by several other
projects. And I use svn to manage my source code.
So I have to exclude svn files from compiling process otherwise
eclipse will generate errors saying something already exists bla
bla...
This setting works very well until recently I switched to mac os (and
upgrade to newest version of ADT, I don't know which is really the
cause of this problem).
Now every time I re-open eclipse, the .classpath file of my project is
re-written and the exclusion setting is lost. I have to either
manually revert to previous version or re-set the exclusion again. It
is really annoying.
I would like to ask if this behaviour of ADT can be shut down?
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
0 Comments:
Post a Comment
Subscribe to Post Comments [Atom]
<< Home