Improper usage of groupId and artifactId

[main--]

We should use things the way they are meant to be used: All MV-plugins should have the same groupId, only their artifactId should differ, in my opinion. @Multiverse What do you think?

[main--]

(I know that this will result in some difficulties for people that are using MV-plugins as dependencies.)

[main--]

Now we only need to find a good groupId.

(Would be good if we could release 2.3 with this change...)

[fernferret]

@main-- I asked you about a proposed domain mvplugin.com or mvplugins.com thoughts?

[main--]

Hm, I don't know...

[dumptruckman]

Doesn't seem likely for 2.5. Scheduling for 2.6.

[benwoo1110]

Outdated issue

[nicegamer7]

Reopening as this is still relevant. MV 5 would be a good time to fix this.