This reminds me one of issues I was working some time ago - version
range resolution. It is also an element provided by core.
If problem is related to proper handling of repository layout (not model
parsing) it might be that you have only "default" repository layout
provider which wins everything. It happens when SPI lookup finds no
better candidates, and candidate lookup is sometimes done very early in
the cycle.
Mind that some of core extensions require additional care to replace
Maven core components - my issue was solved through this finding:
https://stackoverflow.com/a/41970497/
TLDR; In general devil sits in details - you must use plexus annotations
and declare in META-INF/maven/extension.xml export package with
plexus-components.xml, otherwise it will not work.
Best,
Łukasz
On 23.02.2022 18:04, Christoph Läubrich wrote:
I could of course write a custom layout there, but it is always changed
to "default" if I put a breakpoint at the code.
Am 23.02.22 um 16:40 schrieb Michael Osipov:
Am 2022-02-22 um 19:36 schrieb Christoph Läubrich:
I'm currently investigate a plugin that uses the
distributionManagement > repository
but it seems only default/legacy is allowed her and no custom type.
As tycho provides a custom artifact repository type 'p2' I wonder if
it would make sense here to support custom repository types in the
distributionManagement section?
Did you actually check whether the value is evaluated within Maven Core?
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
