@Nicolas-Boltz: I've added

<location includeAllPlatforms="false" includeConfigurePhase="true" includeMode="planner" includeSource="false" type="InstallableUnit">
  <unit id="org.dataflowanalysis.analysis" version="0.0.0"/>
  <unit id="org.dataflowanalysis.analysis.pcm" version="0.0.0"/>
  <unit id="org.dataflowanalysis.analysis.dfd" version="0.0.0"/>
  <repository location="https://dataflowanalysis.github.io/updatesite/nightly/dataflowanalysis/"/>
 </location>	

to the targetplatform. Now it works, but it is incredibly ugly, because we may need to build stuff twice when certain changes arrise.

Why does this happen?
If we take a look at the dependencies, the issue is plain:
org.dataflowanalysis.analysis.tests (DataFlowAnalysis) --depends-->org.dataflowanalysis.examplemodels (ExampleModels) and org.dataflowanalysis.analysis,org.dataflowanalysis.analysis.pcm and org.dataflowanalysis.analysis.dfd (DataFlowAnalysis)

but also:

org.dataflowanalysis.examplemodels (ExampleModels) --depends-->org.dataflowanalysis.analysis,org.dataflowanalysis.analysis.pcm and org.dataflowanalysis.analysis.dfd (DataFlowAnalysis)

Before merging, lets have a short discussion how to resolve this properly. I have thought about several solutions, but none are really "clean" the way our organization is set up.

• Easiest solution would be to put the unit tests from DFA in the example models repo... For us this means that the example models repo would have to be renamed and functionality spread over multiple repos...
• Merging DFA, ExampleModels and Converter in one repo could be a solution that also makes dependency management easier...

@Nicolas-Boltz
Thinking about it some more, I come with the following proposal:

The Example Models should not require the analysis as a bundle, instead it should try to import the bundle if it exists. That also results in being able to use the Example Models without the analysis (and without the expected results, as they are analysis specific) or with the analysis and the results.
This would break the dependency cycle and therefore our issues

What do you think about that idea?

As of the discussion in the meeting yesterday, we will initially add the Analysis to its own target site as dependency.
After the release of version 4.1.0 we will create a monorepo of DataFlowAnalysis, Converter and ExampleModels, which not only resolves the dependency issues (as only Analysis Tests require the ExampleModels and ExampleModels requires the Analysis core), but also lower the overall efforts of maintenance and keeping things consistent to each other.
Further efforts will be taken to maybe move away from Tycho to "plain" Maven.