Martin Höller wrote:
No, it's not, it's a WTP 2.0 project. My plugin configuration is as follows:<plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-eclipse-plugin</artifactId> <version>2.5-SNAPSHOT</version> <configuration> <downloadSources>false</downloadSources> <downloadJavadocs>false</downloadJavadocs> <wtpversion>2.0</wtpversion> <wtpmanifest>true</wtpmanifest>
^^^^
</configuration>
</plugin>
What purpose does this serve?
Well, this file is not created by eclipse but by the m-eclipse-p. And I would say this plugin shouldn't write to src/main/...
The way Eclipse deals with manifest files is they are considered part of the source code, not a generated artifact.
As a result, if you want to synchronise Eclipse with anything in maven, you have to edit the existing files where Eclipse put them.
Remember that unlike in the maven world, where absolutely everything is in the pom, and all other files are generated from scratch, in the Eclipse world information is scattered across the various files in the source tree. Maven can only edit a subset of the information in these files, as maven doesn't have enough knowledge to regenerate the file from scratch.
Regards, Graham --
smime.p7s
Description: S/MIME Cryptographic Signature
