Community
Participate
Working Groups
Build Identifier: 20110301-1815 There is no need to creat the MANIFEST.MF file when importing an existing project. This will be autogenerated by Maven anyway. Reproducible: Always Steps to Reproduce: 1. Import a project 2. wait for project config 3. you'll see that your project is marked as dirty because a MANIFEST.MF has been created
This one is related to: https://issues.sonatype.org/browse/MECLIPSEWTP-66
I don't see this problem with recent m2e 0.13 builds. Feel free to reopen if you can provide standalone sample project and steps to reproduce the problem using clean 0.13 install (i.e. "for java developers" eclipse distribution 3.7M6).
Just verified. Seems to be fixed in 0.13-SNAPSHOT. Is this is going to be provided for 3.6 too?
Yes, 0.13 will work with 3.6.2 and 3.7. You can install SNAPSHOT builds from subfolders of https://repository.sonatype.org/content/repositories/forge-sites/m2e/0.13.0/N/ (each build is published to a separate subfolder)
Moved to https://github.com/eclipse-m2e/m2e-core/issues/