Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 353312 - @requiresDependencyResolution is not honoured
Summary: @requiresDependencyResolution is not honoured
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-07-28 08:14 EDT by Igor Fedorenko CLA
Modified: 2021-04-19 13:23 EDT (History)
0 users

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 Igor Fedorenko CLA 2011-07-28 08:14:59 EDT 
m2e does not honour @requiresDependencyResolution mojo descriptor attribute and always passes test project dependencies to the mojo. This results in subtle and often hard to diagnose problems cased by presence of unexpected dependencies.

Implementation-wise, MavenImpl.execute needs to set appropriate artifact filter on the MavenProject instance and make sure to restore restore project artifacts back back to test scope because some clients, like DefaultClasspathManagerDelegate.addClasspathEntries, assume to see test dependencies.
Comment 2 Denis Roy CLA 2021-04-19 13:23:09 EDT 
Moved to https://github.com/eclipse-m2e/m2e-core/issues/