I've added this to the code in trunk. It should be available in the next dev build. For the future, in order to track where change been originated from, it would be great if you submit enhancement requests to jira, at http://jira.codehaus.org/browse/MNGECLIPSE
On a side note, groupId is usually quite redundant if you named modules in an unique way. For example, here is how Maven project hierarchy is imported into Eclipse using simple [artifactId] template:
maven maven-compat maven-core maven-distribution maven-embedder etc... regards, Eugene Stian Soiland-Reyes wrote:
Is it possible to include [groupId].[artifactId] in the list of name template defaults in the drop down list? I found this to be the best solution, as the version number changes after a release and it's tricky to rename projects in Eclipse. The reason for this is that we have many nested modules that are typically grouped by their groupID, so it means I can almost replicate the hierarchy of "sub-projects" that I can then group in one working set "master project". (See http://soiland-reyes.com/stian/scrap/subprojects.png for example) So for this I wonder why [groupId].[artifactId] is not in the list of "Name templates" when creating/importing new projects.
--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
