Although I more and more use Git for source control, I face Subversion still frequently in daily life. I follow the rule that I don’t want to check in what can be generated in a headless build, where I usually use Maven. Xtext projects have the source folders
xtend-gen, where generated sources go to. Further, you will usually have 3 projects: The grammar project, the UI project and a test project.
In this article I will show some guidelines that I follow when checking in Xtext projects into source control.
Handling the src-gen folder
The content of
src-gen can be produced during a build, so I do not check in the content of it. What needs to be considered is that is no good idea to ignore the folder completely, since it would be missing when fresh checking out the project. This leads to an incomplete build path, and the MWE2 workflow is not executable from Eclipse until the folder was created. This is because the .mwe2 file needs to be on the project’s classpath, which is not the folder
src, but the output folder,
target/classes. It will be copied automatically with default workspace settings only when the build path is complete. This behavior can be changed in the workspace / project settings in Java / Compiler / Building.
If you rate down build path problems to warning level or just disable build abortion on errors, the .mwe2 file will be copied anyway to the target folder. If using project specific settings you could even check in these settings and share it in the team.
I prefer to check in the
src-gen folder, but avoid that any content gets checked in. To do so, add the folder with
svn add, but none of its content! Best you do this immediately after the Xtext project was created. After the folder was scheduled for adding, you can set the
svn:ignore property to value “*”.
The xtend-gen folder
At the moment it is not possible to compile
.xtend files during a Maven build, so the content of
xtend-gen must be checked in and handled like handcrafted sources. To cut this story short: Xtend and Java files depend usually on each other. Xtend files cannot be compiled until Java sources from the same project were compiled, and some Java sources will depend on about-to-be-compiled Xtend sources. So the Java source compilation fails, aborting the build.
I hope to solve this problem soon.
Some ignore patterns
On the root of each of the 3 Xtext projects, set the property
svn:ignore to this value:
Configure Maven clean plugin
mvn clean on your project you would like to to clean up all derived resources. The
target folder will be removed by default, but this is not enough. The content of the
src-gen folders must be cleaned up as well. This can be done by configuring the maven-clean-plugin. One thing to consider is that Xtext has 3 projects. It is not correct to configure the clean plugin for all 3 projects due the lifecycle of a Maven build: The projects will be build after each other, executing all lifecycles per project. If you execute a “mvn clean install” this would have the effect that
- clean is called on the grammar project
- in phase generate-sources the Xtext implementation classes are produced to all 3 projects
- the sources for the grammar project are compiled
- now the build continues with the next module, e.g. the UI project
- the project will be cleaned, removing the previously generated sources
- compilation fails, since the generated sources are missing now
For this reason the clean plugin must be configured only in the grammar project, and it should clean up the sources from all 3 projects. Now comes again a detail related to source control: Since we want to have the
src-gen checked in, we have to avoid that the SCM related folders and files are removed. Otherwise this would confuse your SCM system. So these files must be excluded from deletion. This leads to the following configuration: