Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 357873 - when <build><resources> and build-helper conflict, resources wins, in mvn command line, it works
Summary: when <build><resources> and build-helper conflict, resources wins, in mvn com...
Status: CLOSED DUPLICATE of bug 349586
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: m2e (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-15 15:55 EDT by Jeff CLA
Modified: 2021-04-19 13:27 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jeff CLA 2011-09-15 15:55:57 EDT 
Build Identifier:  20110615-0604

when I specify a directory <resources><resource>

and also  add that same directory with the build-helper plugin, in eclipse that directory is marked as excluded ** so those files aren't compiled, but in maven command line they are. 

Reproducible: Always

Steps to Reproduce:
1.add an additional source directory with the build-helper plugin
2.also make it a <resource> 
3.the top level folder will show as a source folder, but in the build path it is marked as excluded **
Comment 1 Igor Fedorenko CLA 2011-09-22 11:40:37 EDT 
MavenProject instance is not properly updated with additional sources/resources folders contributed by build-helper plugin

*** This bug has been marked as a duplicate of bug 349586 ***
Comment 2 Denis Roy CLA 2021-04-19 13:27:09 EDT 
Moved to https://github.com/eclipse-m2e/m2e-core/issues/