You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Aaron Anderson <ni...@yahoo.com> on 2006/05/05 21:52:04 UTC
overriding maven-core default implementations of components
The maven-core artifact has a META-INF/plexus/components.xml that defines the default implementations for all the components. One can create a plugin that has it's own component.xml override and if a POM has this plugin configured with extention->true then the override will occur.
I would like to take this a step further and somehow configure the default maven installation to use a custom component.xml file with custom implementations. For example, in the absence of a POM I would like the archetype plugin to use my implementation of the Archetype interface instead of the default one.
Is there a way to modify the default super POM that all POM's extend from to use a custom plugin that defines new implementations for components? Is modifying and creating a custom maven-core artifact the only way to change the default implementations for components?
Re: overriding maven-core default implementations of components
Posted by Alexandre Poitras <al...@gmail.com>.
I don't think it quite doable at the moment but there are some discussions
for 2.1 :
http://docs.codehaus.org/display/MAVEN/Substitution+of+Custom+Maven+Components
On 5/5/06, Aaron Anderson <ni...@yahoo.com> wrote:
>
> The maven-core artifact has a META-INF/plexus/components.xml that defines
> the default implementations for all the components. One can create a plugin
> that has it's own component.xml override and if a POM has this plugin
> configured with extention->true then the override will occur.
>
> I would like to take this a step further and somehow configure the default
> maven installation to use a custom component.xml file with custom
> implementations. For example, in the absence of a POM I would like the
> archetype plugin to use my implementation of the Archetype interface instead
> of the default one.
>
> Is there a way to modify the default super POM that all POM's extend from
> to use a custom plugin that defines new implementations for components? Is
> modifying and creating a custom maven-core artifact the only way to change
> the default implementations for components?
>
>