Using -Declipse.projectNameTemplate is broken on multi module projects

Oops, the classpathentry in moduleA/.classpath was wrong. Should have been "/moduleB".

Workaround: projectNameTemplate must be specified in the root pom.

 
	<build>
		<pluginManagement>
			<plugins>
				<plugin>
					<groupId>org.apache.maven.plugins</groupId>
					<artifactId>maven-eclipse-plugin</artifactId>
					<configuration>
						<!--
							projectNameTemplate must be specified here as it's broken on the command line:
							http://jira.codehaus.org/browse/MECLIPSE-586
						-->
						<projectNameTemplate>[artifactId]-[version]</projectNameTemplate>
					</configuration>
				</plugin>
			</plugins>
		</pluginManagement>
	</build>

I tried this workaround but it doesn't work for me. Tried to put <projectNameTemplate> element in the parent POM, parent and child and child only and project names in .classpath are still generated without the version number.

I'm also having problems with getting the child projects to reference the correct project name when the eclipse project files are generated. The unchanged artifactId is referenced, not the custom artifact id where we like to have groupId and version added. It would be great if this could be fixed so that my team can set up many branches of the same project in the same Eclipse workspace without all the hassle of manually fixing the dependencies.

For now our manual fix is to change two things with the sub (child) project's files:

1) In the .project file, update the listed project name from "core" to the proper project, e.g.:
<projects>
<project>com.mycompany.core-1.0</project>
</projects>

2) In the .classpath file, make similar change, changing core as per below:
<classpathentry kind="src" path="/com.mycompany.core-1.0"/>

It is hard to write a programmatic fix for this because it would basically have to replicate everything the eclipse plugin does by reading the POM, and of course it's better to fix it at the root cause.

Any progress/update on this issue? Is anyone implemented a patch that makes the plugin do the right thing here?

Adjusting description according to first comment.

Just wanted to add:

• This is occurring with 2.8 and current (mid-September 2011) 2.9-SNAPSHOT builds
• The workaround (changing the configuration of the plugin) does work.

This regression was introduced in r727620.

To fix, just delete the code which does the wrong thing from EclipsePlugin.java:

MavenProject reactorProject = getReactorProject( artifact );
if ( reactorProject != null )