[MRELEASE-1067] Recompile in release:preform phase due to different checkout path

**[kevin leo](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=crackme)** opened **[MRELEASE-1067](https://issues.apache.org/jira/browse/MRELEASE-1067?redirect=false)** and commented

In the phase of run-preparation-goals,  it will run clean & verify, which includes compile.

When it comes to release, the plugin will checkout the source code to a different path （target/checkout) , then deploy the jar.

Because of different source path and target，mvn cannot use the previous compiled classes.  It's ok for small project, but will be time-consuming for large project.

Although we can customize the checkout directory, but the plugin will delete the content if it already exists.

Is there any workaround from suffering compiling twice?

---

**Affects:** 2.2

Start by tracing the release:preform phase and its run-preparation-goals, paying attention to the target/checkout path described in the issue. Determine how the release plugin handles compiled classes across the initial checkout and release checkout. Done means the recompilation concern has a documented or implemented resolution without changing the release behavior unexpectedly.

Written by the indexing model from the issue text.