title: How should Eclipse RCP target platforms be configured for multiple products?
body: <p>In our Eclipse RCP (Kepler with Tycho/Nexus) project we create a custom application with two sub parts. These parts are organized in the features <strong>Planning</strong> and <strong>Production</strong>. They are delivered as three different products: standalone <strong>Planning</strong>, standalone <strong>Production</strong> and a combination of <strong>Planning</strong>-*<em>Production</em>*.</p>
  
  <p>The question is now how the target platform for the builds should look like?
  Should the TP be set up per build? Meaning we have four TP for:</p>
  
  <ul>
  <li>Build TP for creating plugins</li>
  <li>Planning Release TP </li>
  <li>Production Release TP</li>
  <li>Planning-Production Release TP</li>
  </ul>
  
  <p>Or should the TP be looked at like a repository? Meaning there is just one for the whole project and depending on the context the build will get dependencies either from the TP or the local source code.</p>
  
  <p>(To be honest we have the first solution at the moment and my gut tells me it is a bad idea. Although my gut is good enough for me, solution architects tend to ignore such input. I am looking therefore as well for arguments why one or the other solution is better or worse.)</p>