| Which setting files should/must/shouldn't be under version control? [message #29155] |
Tue, 16 June 2009 18:28  |
 Yves Schumann
Messages: 40
Registered: July 2009 |
Member |
|
|
Hello
Some weeks ago I migrate a lot of projects from Ant build to Maven build
using m2e. Since then we got a lot of problems with the hidden files, i.
e. all the setting files on the projects especially with version control
of them. Which ones should/must/shouldn't be under version control? As I
wrote on another posting some days ago, some of the files are modified
some of them not but nobody here know's exactly, how to handle this
correct. Before m2e usage every of these .* files was under version
control. But now?
If using a SCM system which uses write protect files, this turnes out
into a problem, either with a lot of errors on Eclipse if not checked
out for usage or with highjacked files on the SCM if modifying them the
hard way.
Maybe there is another possible problem, because m2e doesn't tell the
SCM plugin correct what's going on. Just see [1][2].
[1] https://issues.sonatype.org/browse/MNGECLIPSE-1238
[2] https://issues.sonatype.org/browse/MNGECLIPSE-1359
Regards,
Yves
--
"Schlager sind Texte, die gesungen werden müssen, weil sie zu dumm sind,
um gesprochen zu werden." -- Gisela Uhlen
|
|
|
|
Powered by
FUDForum. Page generated in 0.01960 seconds
Search
Help
Register
Login
Home
