hi, i am having problem with transitive dependency resolving, in one of our projects it did not work correctly. in both m2eclipse plugin (for development time) and maven assembly plugin (for release time). i filed this already under issue http://jira.codehaus.org/browse/MASSEMBLY-242). since short weird thing is that it occurs in m2eclipse plugin too, so i guess something is wrong with maven 2.1 transitive dependency resolving. to dig a bit deeper and to maybe provide a unit test instead of a black box pom.xml test, i would like to see the code which potentially raises transitive resolving issue.
so my questions are: 1) error occurs in m2eclipse, is it correct that m2eclipse is using maven 2.1 behind the wall? that means, is the maven 2.1 trunk the right way to look for? 2) transitive resolving issue occurs in maven-assembly plugin (see bug report), does this plugin completely delegate the transitive resolving to maven core or is it doing some bits itself? this information would influence my approach to find the bug (main maven vs. assembly plugin sources). 3) which module/package of maven 2.1 is responsible for transitive dependency resolving? i had a rough look under several modules and packages but wasn't successfull to find the correct class or subsystem. thanks for information. -- View this message in context: http://www.nabble.com/which-module-to-dig-for-dependency-resolving--tf4694001s177.html#a13417195 Sent from the Maven Developers mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]