|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [mojo-dev] [jira] (MWEBSTART-233) Dependencies with tes... JIRA
- [mojo-dev] [jira] (MWEBSTART-233) Dependencies wit... JIRA
- [mojo-dev] [jira] (MWEBSTART-233) Dependencies wit... Tony Chemit (JIRA)
- [mojo-dev] [jira] (MWEBSTART-233) Dependencies wit... Tony Chemit (JIRA)
- [mojo-dev] [jira] (MWEBSTART-233) Dependencies wit... JIRA
- [mojo-dev] [jira] (MWEBSTART-233) Dependencies wit... Tony Chemit (JIRA)

Hi Christian,
I don't know what to do to solve your problem...
The dependency plugin use a complete different algorithm to get dependencies, I don't feel confident using it like as it.
What you can do as a workaround is to exclude the junit dependency in dep2 pom:
<dependency> <groupId>${project.groupId}</groupId> <artifactId>dep1</artifactId> <version>${project.version}</version> <exclusions> <exclusion> <groupId>junit</groupId> <artifactId>junit</artifactId> </exclusion> </exclusions> </dependency>