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

Bug 361549

Summary:	process compile source roots even if the do not exist
Product:	z_Archived	Reporter:	Igor Fedorenko <igor>
Component:	m2e	Assignee:	Igor Fedorenko <igor>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Igor Fedorenko

2011-10-20 10:14:19 EDT

This is a follow up for bug 349586. Currently, m2e jdt project configurator ignores (test) compiler source roots if they do not exist in workspace during project import and/or configuration update. Additionally, all source folders created by m2e jdt project configurator from MavenProject are marked as required, which are automatically removed by eclipse during some workspace operations (see [1]).

Better approach would be always create source folders corresponding to MavenProject (test) compile source roots, regardless if they exist in workspace or not. Mark second and all the rest source folders as optional, so they are not removed. 

To be extra nice to less perfectly written maven plugins, do shallow refresh on source folders, so folders that exist on local filesystem appear in Package explorer even when workspace is not in sync with filesystem.


[1] http://dev.eclipse.org/mhonarc/lists/m2e-users/msg01709.html

Comment 1 Igor Fedorenko

2011-10-20 16:34:52 EDT

Done. Implementation marks all source classpath entries as optional.

http://git.eclipse.org/c/m2e/m2e-core.git/commit/?id=7eb939c1c3c46d5dc23b763abae0c532d734b51e
https://github.com/sonatype/m2e-core-tests/commit/990a4b7b7a504eea97ff48567edf94e0a7c3c469

Comment 2 Denis Roy

2021-04-19 13:25:10 EDT

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