Hi Mark, > Is there anyway in current maven (3.3.9) that I can replace the > |DefaultDependencyCollector| with one of my own, that can use > maven-filtering and demangle the versions as appropriate? Can I register > a replacement in my |META-INF/plexus/components.xml| file for my > lifecycle extension at all?
even if there is (I've no clue), what about all the consumers of your artifacts? They will fetch you POMs from a Maven repository and have no idea where to get the dependencies from, as *they* use the DefaultDependencyCollector. But maybe the flatten-maven-plugin can help in such cases, so that you use you "magic" properties only during the build but the published POMs have all properties replaced. Best wishes, Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
