I can confirm that this problem exists.
How to reproduce this:
1 Create an android project and set it as an Android library.
2 Create another android project that uses the previous library.
3 Commit these source code into a svn repository.
4 Change something in your library project, then commit it.
5 An error will occur in the project that uses the library. The
message says the project can't compile because bin/[path to your
source code]/.svn/entries file already exists.

This is obvious because when importing library source code, the .svn
folder is also included and copied to bin folder when project
compiles.
That is not a big problem because you can set to exclude .svn folder
and its contents in Eclipse.
But my real problem is that the current ADT always tries to remove the
exclusion setting for my projects.

My ADT version is 0.9.9.v201009221407-60953

On Nov 3, 10:45 pm, Marcin Orlowski <[email protected]> wrote:
> On 3 November 2010 14:11,mianwo<[email protected]> wrote:
>
> > 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...
>
> I never had to exclude any SVN folders here nor seen Eclipse
> complaining about these folders. That would be silly as Eclipse
> got nothing to say here. I also got lot of other folders in
> project tree and it's not a problem at all.

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to