On 11/01/13 17:27, Richard Eckart de Castilho wrote: > Am 11.01.2013 um 14:12 schrieb Thilo Goetz <[email protected]>: > >> I don't, but that still doesn't make it a good idea. Have you tested >> what happens when you check this out on a different machine, with >> different settings, OS, etc? > > No, I didn't explicitly test that. > >> The .settings stuff is not meant to >> be shared with other people, period. I have seen this cause annoying >> errors too many times. > > I have seen issues to, that is why I am very careful in what I check in. > If you don't mind too much, I'll leave it in for now and wait until people > report actual problems. Although, I have to admit that mostly the issue > was a dirty .settings directory upon checkout.
You do what you think is best. I really don't care, I was just trying to be helpful. > > The alternative would be to implement a Maven and/or Eclipse plugin to > fix that. Some googling revealed that people have done that already, but > there seem to be no publicly available implementations. > > It could be considered to implement a Maven plugin which reads the JDT > settings, overrides certain keys and saves it again. Possibly this even > works without a special m2e plugin. If not, the jcasgen m2e plugin from > Steven might serve as a template. If possible, for me a m2e plugin should > be avoided, because those tend to require regular maintenance updates. > > Cheers, > > -- Richard >
