title: Maven modules which no longer exist in a reactor project appear in the Jenkins build report as "didn't run"
body: <p>I have a multi-module maven project which contains nested some other reactor submodules. As result I have a 3 level hierarchy of modules.</p>
  
  <p>In the past I refactored the hierachy, moving some nested modules from one  to another. I modified as well the names of some of the modules.</p>
  
  <p>On Jenkins, the old modules - now unexistent - appear in the build report as "didn't run". When I do locally a maven install these modules don't appear in the reactor summary.</p>
  
  <p>Is this behavior somehow expected?
  I mean, are there any setting in jenkins which makes the reactor runner remember old sub-modules?</p>
  
  <p>The "Delete workspace before build starts" option is enabled.</p>