Want explain on Dependencies Scope

I am newbie to Maven, and now want to write a custom plugin. But I get confuse on maven's transitive dependency handling. My poms' dependencies setting is something like: Project A ... saxpath saxpath 1.0-FCS ${compile} jaxen jaxen

Re: Want explain on Dependencies Scope

I just want to know how can my [plugin] project use [jaxen], [saxpath] properly with only set dependency on [CommonLib]. Or more general, if there is artifact C, B, A, X-Z - artifact A has a function dynamic load (Class.forName) some of the class appeared in project X-Z - artifact B wrap

Re: Want explain on Dependencies Scope

Thanks. I have read it yet. But the samples do not suit my case. What I want is how to let project A use project B's wrapper function of project C, in which the function use Class.forName or more specific that how can my [plugin] project use [CommonLib]'s wrapper of [JDom's XPath]'s function

Re: Want explain on Dependencies Scope

Yes, it's what i want -- View this message in context: http://www.nabble.com/Want-explain-on-Dependencies-Scope-tf1979614.html#a5442789 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL

Problem on java plugin development (fail to use dependency classpath)

Hi, I am new to Maven and currently want to write a custom java plugin, my workspace is something like below: template:common --- a project to store utility class and method template:maven-buildarchetype-plugin --- Test writing java mojo plugin , where their file structure is something