When running the eclipse goal, the project name that gets set in the project description may not be the project you will initially save it as.
For example, I create a project with some name. I configure a pom to have a different artifactId, groupId that do not relate to the project name I originally configured it with. When I run eclipse:eclipse the project name in the .project file will be the artifactId (by default) despite the eclipse project name being something different. Now lets say we have a new project that depends on the project we just created. We run the eclipse goal on the new project, and with useProjectReferences enabled, the classpath references the name of the project based on the artifactID. This causes a problem when eclipse tries to build new projects workspace because the eclipse workspace project is one thing and the .project's project is something completely different. How come the maven-eclipse-plugin will never resolve the workspace project name to the .project project name. Or even offer a flag like <useEclipseProjectName>true</useEclipseProjectName> to override the original functionality? -- View this message in context: http://maven.40175.n5.nabble.com/maven-eclipse-plugin-Does-not-resolve-workspace-project-name-tp3237890p3237890.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
