[MNG-8113] Inconsistent way of overriding core components from extensions

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: Core
• Assignee: Unassigned
• Reporter: Tamas Cservenak
• Created: 01/May/24 10:14
• Updated: 01/May/24 10:14

Description

Problem: "let's have a (core) extension that is overriding some component X in Maven Core".

Doing this is very inconsistent, and depends HOW core component is defined in the first place.

IF core component is JSR330, then is simple: just define an own JSR330 component (w/ some higher than zero Priority) and done. This can be loaded from .mvn/extensions.xml just fine.

IF core component is Plexus, then is not simple:

• using JSR330 – could not do it
• using Plexus annotation + XML – does not works when JAR is in .mvn/extensions.xml !
• using Plexus annotation + XML – works only when using -Dmaven.ext.class.path w/ JAR enlisted here.