Switching the processModules() method to fail if a module is included but has no associated artifact file. It looks like this might be related to the forked lifecycles, where a clone of the project instances are created...in which case, we may need a lifecycle overlay that will bridge the project artifact over for each one from executedProject to project when the package phase finished...see the CloverPlugin for a pseudo-example of this.

git-svn-id: https://svn.apache.org/repos/asf/maven/plugins/branches/MASSEMBLY-14@399542 13f79535-47bb-0310-9956-ffa450edef68
1 file changed
tree: 5878b5a43114a342ae63d96618e41a94a9f42dd6
  1. src/
  2. pom.xml