More restrictive dependencies for maven

[maybeec]

Maybe there is a need for including all maven-core, but I couldn't find it in my use case utilizing mmm java maven.
Possibly it's worth thinking about replacing maven-core with maven-model dependency if the rest of maven-core is not needed.

[hohwille]

@maybeec thanks for the PR. Minimizing dependencies is always a good thing. I can still extend them later when needed. I am trying to setup CI to verify PRs ind this repo and just added the action to master.

[hohwille]

CI issue: #32

[hohwille]

So adding CI prior to merging was a good step as it reveals that you did not test this change and it breaks the build.

So either we can close this PR or you can rework it so the build is green.

[maybeec]

should be fixed now

[hohwille]

seems fine. CI hangs. Trying to restart...

[hohwille]

@maybeec thanks again for your PR 👍
I would love to merge this.
I can neither edit nor update this feature-branch.
Did you somehow lock your fork of mmm-code?
As the diff is very small, I can also commit the change myself and close this PR, but I would like to understand what is happening in this PR on github for future PRs. All I want is the build to be triggered and see if this change does not break it.

[maybeec]

I see it's even not a branch on my fork but on this repository.

[hohwille]

Ah, now I get it:

maybeec wants to merge 5 commits into m-m-m:master from maybeec:patch-2

This PR was created from a fork that does not exist anymore. In the early days of Github this broke the PR. Nowadays when a PR is created Github creates an internal branch to keep the diff persistent for the repo.
OK, then I will simply redo the change myself. Sorry that I did not pickup this PR for 1,5 years - what a pity...