Collaborate working with Ecore and Sirius

My collegues and I explored the possibility to use for our next project a model-driven architecture (MDA) approach. Therfor we designed our Model in Eclipse Ecore and used for testing and visualisation issues Eclipse Sirius. To work together we decided to use GIT and had the issue, that by default the GIT Repository was filled with to much build data. Every comit ran into a conflict. To solve this issue we includet the following GIT Ignore file and everything was fine. ### Eclipse ### .metadata bin/ tmp/ *.tmp *.bak *.swp *~.nib local.properties .settings/ .loadpath .recommenders # External tool builders .externalToolBuilders/ # Locally stored "Eclipse launch configurations" *.launch !lab2/at.ac.tuwien.big.roverml.xtext/ME Lab2 Runtime Eclipse.launch # PyDev specific (Python IDE for Eclipse) *.pydevproject # CDT-specific (C/C++ Development Tooling) .cproject # CDT- autotools .autotools # Java annotation processor (APT) .factorypath # PDT-specific (PHP Development Tools) .buildpath # sbteclipse plugin .target # Tern plugin .tern-project # TeXlipse plugin .texlipse # STS (Spring Tool Suite) .springBeans # Code Recommenders .recommenders/ # Annotation Processing .apt_generated/ # Scala IDE specific (Scala & Java development for Eclipse) .cache-main .scala_dependencies .worksheet ### Eclipse Patch ### # Eclipse Core .project # JDT-specific (Eclipse Java Development Tools) .classpath # Annotation Processing .apt_generated .sts4-cache/
1 answer

gitignore is very important in many aspects, we also put in some local config files which pointed to some needed data files for the application (linux vs windows have different path seperators for example) to avoid rewriting after every pull the gitignore can be very helpful as long as you remember to forcefully commit a real change

Taggings: