History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: IDEA-17013
Type: Bug Bug
Status: Open Open
Assignee: Anton Makeev
Reporter: Jonathan Gilbert
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
IDEA: Feedback

Dependencies are incorrect when they use <exclude>

Created: 30 Jan 08 15:37   Updated: 31 Jan 08 13:03
Component/s: Maven Integration

Build: 7,656
Severity: Medium


 Description  « Hide
Using <exclude> appears to be ignored by IDEA.

If I have project A which has a dependency D, and B depends on A with an explicit exclusion of D, then IDEA still includes D as a dependency for B. In my case this causes a class clash in unit tests.

<dependency>
<artifactId>A</artifact>
<excludes>
<exclude>D</exclude>
</excludes>
</dependency>

Unfortunately I'm not sure if IDEA itself supports the runtime non-export of dependencies to other modules. (the 'export' option seems to only apply to build-time)



 All   Comments   Work Log   Change History      Sort Order:
Anton Makeev - 31 Jan 08 13:03
As the build-time dependencies, I've checked that and it seems to work as expected - the module D is excluded from the B dependencies. (If you still have the problem try the latest eap).

Regarding the runtime exclusion - how do you reckon that should work? All the classes would be loaded into memory notwithstanding the dependencies of the module B. I'm not sure if I understood you clearly.