The use of the repository produced by this effort is not limited to m2e,
so I think "m2e tools" will be misleading.
And, yes, naming is hard. ;-)
--
Regards,
Igor
On 11-03-18 03:50 PM, Aaron Digulla wrote:
Am 18.03.2011 17:45, schrieb Wayne Beaton:
I am concerned that naming your efforts "m4e" is potentially confusing
for the community as it seems awfully close to "m2e" [1]. "m2e" comes
from "Maven 2 Plug-in for Eclipse" and, apparently, some folks from the
Maven community are already asking about "m3e" for Maven 3.
Thoughts?
I agree but naming is hard. Some suggestions:
Eclipse Maven Tools - too long. Is that tools for Maven or Eclipse?
Since we translate Eclipse bundles into Maven artifacts: "translate" in
various languages:
Catalan: traduir
Croatian: prevesti
Dutch: vertalen
Filipino: isalin
French: traduire
Galician: traducir
Or we use "m2e tools" because I'm building tools to use make Eclipse
bundles usable in projects that use m2e to build.
Regards,
_______________________________________________
dash-dev mailing list
dash-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/dash-dev
