Sources and patches are always unpacked even if the source archive has been expanded

Just need to do an up-to-date check on the expansion target dir vs. the archive for newest-timestamp, and make a decision accordingly.

fixed, and an IT was added to the project-sources plugin. An IT for the patch-maven-plugin is quite a bit more complex, since it never has a local archive to test against...it will require two "resolve" steps in a build, where the first will resolve/unpack, then something would remove the result of that unpacking, then the second resolve step would avoid unpacking. That's going to be necessary in order to have the patch artifact's lastMod date remain unchanged...

This optimization step is causing problems in cases where a patch is applied to the unpacked sources. In this case, Maven will try to reapply the patch on the same sources (which have already been patched) and fail.

I'm going to set the optimizations flag to false by default to work around this until we reach a more final solution.

Patches are tracked, and will not be reapplied if optimizations are turned on (as they are by default), and the patch-tracking file is in place. This file will be wiped out along with everything else in target when `mvn clean` is issued.