|
||||||||
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] (MNBMODULE-218) Treat pom-dependenci... Inge Solvoll (JIRA)
- [mojo-dev] [jira] (MNBMODULE-218) Treat pom-depen... Milos Kleint (JIRA)
- [mojo-dev] [jira] (MNBMODULE-218) Treat pom-depen... Inge Solvoll (JIRA)
- [mojo-dev] [jira] (MNBMODULE-218) Treat pom-depen... Milos Kleint (JIRA)
- [mojo-dev] [jira] (MNBMODULE-218) Treat pom-depen... Milos Kleint (JIRA)
- [mojo-dev] [jira] (MNBMODULE-218) Treat pom-depen... Inge Solvoll (JIRA)
- [mojo-dev] [jira] (MNBMODULE-218) Treat pom-depen... Jesse Glick (JIRA)
- [mojo-dev] [jira] (MNBMODULE-218) Treat pom-depen... Inge Solvoll (JIRA)
- [mojo-dev] [jira] (MNBMODULE-218) Treat pom-depen... Inge Solvoll (JIRA)
implementation-wise we would have to replace artifact.getDependencyTrail().size() > 2 condition with something that is capable of climbing the dependency path and decide based on what's there (pom vs jar)