Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [egit-dev] Strange behavior on committed .class files

2012/9/5 Thomas Hallgren <thomas@xxxxxxx>
We have a file named MockOutput.class checked in to one of our repositories. This is very deliberate since one of our tests actually runs this file. When using egit to switch branches, I often (but seemlingly not always), encounters problems with this file. Egit seems to think that it must be committed before the switch is made. A commit however, comes up empty. The repository is clean.

I have no problems switching branches using the command line git tool.

I don't have a global gitignore file nor any other .gitignore on the path that affects .class files and the team preference setting for ignored files doesn't contain .class either. So why does this happen in Egit? Does anyone have a clue? I'm using the Juno release of EGit/JGit.

Are you using core.autocrlf = true or input on Windows ? Since JGit doesn't yet have support for gitattributes
it's using a heuristic check in order to prevent corruption of binary files by line break conversion (it assumes that
text files don't contain null bytes), maybe this causes your problem.

Or maybe the compiler touches the file and this way affects its meta data ?

Did you try the latest nightly build version of EGit ?

--
Matthias

Back to the top