Yes, the mapping is there just to map to existing paths. So if this is a new dependency, I would prefer that you use the maven path and then you won't need any mapping configuration.
Eventually, I would like to remove all the mapping configs and simplify the pom, but in the short term I just didn't want to risk breaking the build.
Thanks; that's exactly what I figured your plan was. :-)
Seems forum doesn't like quotation marks in subject line.
BTW, anyone reading this thread, please ignore my example above. The thirdparty/pom.xml has a maven-buildmagic-thirdparty-plugin with a plugin config that uses a bunch "dependency" elements inside a "mappedDependencies" element. Don't put a lib without a "mapping" element there; it doesn't work. Scroll down and put it in the regular maven dependencies section.