[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [tycho-user] It is safer for eclipse.org projects to remove .classpath and .project from git when using tycho ?
- From: Aaron Digulla <digulla@xxxxxxxx>
- Date: Sat, 16 Jun 2012 00:13:27 +0200
- Delivered-to: email@example.com
- User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120421 Thunderbird/12.0
Am 15.06.2012 00:54, schrieb Cristiano Gavião:
> Many Eclipse project are being converted to Tycho.
> But I'm seeing some resistance of some teams to remove .classpath and
> .project from source control even knowing that .classpath and .project
> are generated by m2e plugin.
> Could Tycho developers give me some words about this?
I hate it when teams cripple their projects in this way. These are
*Eclipse* projects. After downloading/cloning them, I should be able to
open them in my workspace without any additional work.
Also, m2e doesn't always create correct files (or it didn't in the
past). Does m2e support special builders in the .project file? So this
is dangerous, too.
And lastly, when the people doing that aren't careful about their
gitignore settings, the next developer either gets missing files or
project that are always in a modified state.
The only argument which is in favor of deleting these files is that you
shouldn't commit generated files. While this might make sense at first
glance, it can (and does) create lots of problems that are hard to track
down (the "I didn't change anything" kind).
If these were huge files, I might be game but not for something that is
so small and vital and error prone.
Aaron "Optimizer" Digulla a.k.a. Philmann Dark
"It's not the universe that's limited, it's our imagination.
Follow me and I'll show you something beyond the limits."