package to type mappings are predefined in maven-artifact's components.xml, however any plugin can provide it's own through the extensions mechanism, which I believe you were using in the other rar example. The first part of your email is completely correct in how it works.
Cheers, Brett Jian.Wu wrote: > Hi, > > I just tried to get a general understanding of Maven2 Runtime behavior. > Please correct me if I'm wrong. > > It looks like that Maven Plugin is associated with packaging and Maven2 > Runtime is invoking the associated Plugins for the packaging defined in > pom.xml. Is this correct? > > And, is the plugin-packaging-association bootstraped from components.xml > inside maven-core.jar? > > Meanwhile, the type is used to resolve the dependency, either module > dependency or library dependency. > > But, I could not find any clear definition on how a type will map to a > project > with packaging assuming Maven2 Runtime will not resolve the dependency > based on packaging since "packaging" is not a valid sub-element of > "dependency" element. > > Will this end up that we can only introduce new packaging at the > top-level project and this new packaging can not be used in any > non-top-level project as a sub-project since Maven2 Runtime don't > know how to resolve this dependency when it appears in the middle > of dependency graph? > > Thanks a lot for the help! > > Jian > > > > -- > View this message in context: > http://www.nabble.com/-m2-Is-Plugin-associated-with-Packaging-but-type-is-used-for-dependency--t1365954.html#a3662477 > Sent from the Maven - Dev forum at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
