Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 341590

Summary:	When import a project a useless META-INF/MANIFEST.MF ist created
Product:	z_Archived	Reporter:	Michael Osipov <1983-01-06>
Component:	m2e	Assignee:	Project Inbox <m2e.core-inbox>
Status:	CLOSED WORKSFORME	QA Contact:
Severity:	normal
Priority:	P3	CC:	igor
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Michael Osipov

2011-04-01 05:13:24 EDT

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

Comment 1 Michael Osipov

2011-04-01 05:16:37 EDT

This one is related to: https://issues.sonatype.org/browse/MECLIPSEWTP-66

Comment 2 Igor Fedorenko

2011-04-01 09:05:27 EDT

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).

Comment 3 Michael Osipov

2011-04-01 11:08:53 EDT

Just verified. Seems to be fixed in 0.13-SNAPSHOT. Is this is going to be provided for 3.6 too?

Comment 4 Igor Fedorenko

2011-04-01 11:11:04 EDT

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)

Comment 5 Denis Roy

2021-04-19 13:25:36 EDT

Moved to https://github.com/eclipse-m2e/m2e-core/issues/