Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 361549 - process compile source roots even if the do not exist
Summary: process compile source roots even if the do not exist
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: m2e (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Igor Fedorenko CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-20 10:14 EDT by Igor Fedorenko CLA
Modified: 2021-04-19 13:25 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Igor Fedorenko CLA 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 2 Denis Roy CLA 2021-04-19 13:25:10 EDT
Moved to https://github.com/eclipse-m2e/m2e-core/issues/