On 27/10/2010 1:28 PM, Wayne Fay wrote:
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.
Yes, this is how m-e-p works. The .project file is overwritten by
m-e-p and so you will lose all settings that you set up in Eclipse
unless you also set them up in your pom via configuration:
http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html
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.
This is not m-e-p's problem. Stop renaming your projects if you want
to use m-e-p and use it to regenerate the .project files. Keep the
name as the artifactId, or change the artifactId in the pom to meet
your needs.
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?
In the last 180 days, there have been zero issues in MECLIPSE resolved.
At the same time, 40 have been updated and 20 were created.
http://jira.codehaus.org/browse/MECLIPSE
For all intents, m-e-p is dead. If you require this functionality,
feel free to hack the plugin to add it and donate your changes back to
be included in a future release -- but bear in mind there may never be
another release. The last release was Feb 23, 2010 and before that was
June 13, 2009.
I suggest upgrading to m2eclipse:
http://m2eclipse.sonatype.org/
Or just move to Eclipse/STS(free) and get everything, all included.
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
