#166: consider all clean-lifecylce phases and add release-notes entry

[HannesWell]

This PR adds an release-notes entry for issue #166 and extends the first solution for that issue by additionally considering the other two phases of the clean life-cycle.

What makes me wonder is that maven usually talks about phases when referring to the different 'steps' of a lifecycle.
But the session (and its request) only provides a List of goals. Are specified phases considered as goals in Maven?
The content of the goals list seems to be as expected when I attached a debugger and I did not find the word 'phase' in the MavenSession or MavenExecutionRequest class.

[laeubi]

Its confusing but maybe this helps a bit?
https://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html#a-build-phase-is-made-up-of-plugin-goals

A plugin goal represents a specific task (finer than a build phase) which contributes to the building and managing of a project. It may be bound to zero or more build phases. A goal not bound to any build phase could be executed outside of the build lifecycle by direct invocation.

[HannesWell]

If this is fine, please squash and merge the commits. I think there is no value in keeping the changes as single commits.

[HannesWell]

If this is fine, you can squash in merge the commits. I think there is no value in keeping the changes as single commits.

Its confusing but maybe this helps a bit?
https://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html#a-build-phase-is-made-up-of-plugin-goals

A plugin goal represents a specific task (finer than a build phase) which contributes to the building and managing of a project. It may be bound to zero or more build phases. A goal not bound to any build phase could be executed outside of the build lifecycle by direct invocation.

Thanks for the link, but this only confirms my understanding of goals and phases.
For example clean, verify, package etc. are phases (of the two life-cycles clean and default), while e.g. maven-compiler-plugin:compile is a goal (by default bound to the lifecycle phase compile).
But when I call mvn clean verify the code MavenSession.getGoals() returns a List composed of "clean" and "verify".
From this I expect for a command like mvn clean maven-compiler-plugin:compile verify
that getGoals() returns ["clean", "maven-compiler-plugin:compile", "verify"].

But I actually expected something like MavenSession.getPhases(), that would return ["clean", "verify"] and getGoals() that returns ["maven-compiler-plugin:compile"].

From the example in your link I think the solution of this theoretical problem is likely that the order of goals and phases specified in a Maven command needs to be maintained, even if they are mixed. And this is only possible if you store them together in one list in the model. Therefore I assume that Maven treats phases specified in a command as goals too?

But this theoretical problem is actually not relevant for this PR and the code should work anyways.

[laeubi]

clean is a "life-cycle" see https://maven.apache.org/ref/3.8.1/maven-core/lifecycles.html

In the context of tycho, we define for a packaging-type a custom mapping of Life-cycle Phases depending on the packaging type.