Theoretically if you will look at the maven xsd https://maven.apache.org/xsd/maven-4.0.0.xsd it does not apply any restriction on the group id, just ask for string.
Internally it will validate using the regex "[A-Za-z0-9_\-.]+" see here
thanks tunaki
<xs:element minOccurs="0" name="groupId" type="xs:string">
<xs:annotation>
<xs:documentation source="version">3.0.0+</xs:documentation>
<xs:documentation source="description">
A universally unique identifier for a project. It is normal to use a fully-qualified package name to distinguish it from other projects with a similar name (eg. <code>org.apache.maven</code>).
</xs:documentation>
</xs:annotation>
</xs:element>
But the description specify that (and the common use case) to usea fully-qualified package name witch should not end with "."
But remember that maven use the group id to create the directory path where it store the artifact locally. Maybe some OS found it problematic so m2eclipse prefer to avoid it.
In windows 7.0 if you will try to compile such project from command line it will work fine.
Anyway I think that it is recommenced to avoid the "." in the end of the groupid