Under the intended use-case, the consumers of the artefacts published using
this lifecycle extension will also be using the same lifecycle extension,
and importing/resolving those properties based on business rules/conditions
beyond the scope of this specific problem.
Unfortunately, the flatten pl
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 exten
Hey all,
Bit of a crazy, mad, deep-in-bowels-of-maven question for you all.
In our locally published artifacts we've been declaring dependency versions in
a property within our poms:
```xml
1.2.3
...
test
test
${test.version}
```
and that all works fine. When we build projects that
