Strict Standards: Non-static method utf_normalizer::nfc() should not be called statically in /www/htdocs/w006661d/anddev/includes/utf/utf_tools.php on line 1781[phpBB Debug] PHP Notice: in file /includes/session.php on line 1007: Cannot modify header information - headers already sent by (output started at /includes/utf/utf_tools.php:1781)[phpBB Debug] PHP Notice: in file /includes/session.php on line 1007: Cannot modify header information - headers already sent by (output started at /includes/utf/utf_tools.php:1781)[phpBB Debug] PHP Notice: in file /includes/session.php on line 1007: Cannot modify header information - headers already sent by (output started at /includes/utf/utf_tools.php:1781)

Strict Standards: Non-static method utf_normalizer::nfc() should not be called statically in /www/htdocs/w006661d/anddev/includes/utf/utf_tools.php on line 1781

Strict Standards: Non-static method utf_normalizer::nfc() should not be called statically in /www/htdocs/w006661d/anddev/includes/utf/utf_tools.php on line 1781

Strict Standards: Non-static method utf_normalizer::nfc() should not be called statically in /www/htdocs/w006661d/anddev/includes/utf/utf_tools.php on line 1781[phpBB Debug] PHP Notice: in file /includes/functions.php on line 4362: Cannot modify header information - headers already sent by (output started at /includes/utf/utf_tools.php:1781)[phpBB Debug] PHP Notice: in file /includes/functions.php on line 4364: Cannot modify header information - headers already sent by (output started at /includes/utf/utf_tools.php:1781)[phpBB Debug] PHP Notice: in file /includes/functions.php on line 4365: Cannot modify header information - headers already sent by (output started at /includes/utf/utf_tools.php:1781)[phpBB Debug] PHP Notice: in file /includes/functions.php on line 4366: Cannot modify header information - headers already sent by (output started at /includes/utf/utf_tools.php:1781)anddev.org • View topic - Subversion usage - best practices?

I'm looking for best practices to use Android projects with Subversion. Actually I'd like to prevent committing Eclipse specific files (gen and bin folder, .classpath and .settings, ...) to the repository. But if I try to do that, somehow my Eclipse messes up after checking out the project.

Is there a list of best practices to set up a Android Subversion repository? Or what is the best way to check out a project?

What I found works best is to add the project, then just delete the bin directory. I've tried to trim down what I commit before and it has always caused problems checking out the project. I'd be interested if you find a process that works better.

-Jason

Mardaneus wrote:I'm looking for best practices to use Android projects with Subversion. Actually I'd like to prevent committing Eclipse specific files (gen and bin folder, .classpath and .settings, ...) to the repository. But if I try to do that, somehow my Eclipse messes up after checking out the project.

Is there a list of best practices to set up a Android Subversion repository? Or what is the best way to check out a project?