@zurbergram yes this is not possible in the moment out of the box.

However, there is a way for you to achieve what you are looking for with some internal customizations. We have an internal SPI ModelElementProcessor that adds the spring @Component annotation. The one for Spring is the SpringComponentProcessor.

What you can do is to define your own ModelElementProcessor that would be of a custom component model, provide your own marker annotation for the name of the component and you would be able to do what you are looking for.

Just keep in mind that this is an internal SPI, which means that we cannot guarantee backwards compatibility between versions. However, it is rarely changed.

Oups, sorry! I wasn't aware about the fact that changes in my forked mapstruct repo will directly be linked to this issue. Hopefully I haven't spammed you with too much notification mails.

@filiphr as my changes are now linked here maybe you could already take a look or should I create a PR? (this is my more or less first 'real' OS contribution; right now I am waiting that the built finishs locally including all tests)

I tried to add the possibility to have an extra annotation (@MapperSpringConfig / @MapperJsr330Config) to be able to have more component model specific configurations, e. g. if @Service or @Component should be used and - as requested in this ticket - to define an own bean name.

Maybe its better to extend the @Mapper configuration with a new property like componentName, but my idea was that there are maybe also other configuration things that only belongs to a special componentModel and having a special annotation for this could be helpful for those usecases.

@zurbergram yes this is not possible in the moment out of the box.

However, there is a way for you to achieve what you are looking for with some internal customizations. We have an internal SPI ModelElementProcessor that adds the spring @Component annotation. The one for Spring is the SpringComponentProcessor.

What you can do is to define your own ModelElementProcessor that would be of a custom component model, provide your own marker annotation for the name of the component and you would be able to do what you are looking for.

Just keep in mind that this is an internal SPI, which means that we cannot guarantee backwards compatibility between versions. However, it is rarely changed.

I've tried your suggestion, but the Processor is not picked up by org.mapstruct.ap.MappingProcessor in method getProcessors() (v1.3.1.Final):

/**
     * Retrieves all model element processors, ordered by their priority value
     * (with the method retrieval processor having the lowest priority value (1)
     * and the code generation processor the highest priority value.
     *
     * @return A list with all model element processors.
     */
    private Iterable<ModelElementProcessor<?, ?>> getProcessors() {
        // TODO Re-consider which class loader to use in case processors are
        // loaded from other modules, too
        @SuppressWarnings("rawtypes")
        Iterator<ModelElementProcessor> processorIterator = ServiceLoader.load(
            ModelElementProcessor.class,
            MappingProcessor.class.getClassLoader()
        )
            .iterator();
        List<ModelElementProcessor<?, ?>> processors = new ArrayList<>();

        while ( processorIterator.hasNext() ) {
            processors.add( processorIterator.next() );
        }

        Collections.sort( processors, new ProcessorComparator() );

        return processors;
    }

I assume it's because my ModelElementProcessor is not in the same classloader as MappingProcessor. Am I doing something wrong?

Just to share some info about how this can be done with some custom Spring @ComponentScan.

Let's say that we have the following:

package com.example.mapper.v1;

@Mapper
public interface CakeMapper {
}

package com.example.mapper.v2;

@Mapper
public interface CakeMapper {
}

Then your configuration can look like the following:

package com.example.mapper;

@Configuration
public class MapperConfig {

    @Configuration
    @ComponentScan(basePackages = "com.example.mapper.v1", nameGenerator = V1NameGenerator.class)
    public static class V1MapperConfig {
    
    }

    @Configuration
    @ComponentScan(basePackages = "com.example.mapper.v2", nameGenerator = V2NameGenerator.class)
    public static class V2MapperConfig {
    
    }

    protected static class V1NameGenerator extends PackageVersionNameGenerator {
        protected V1NameGenerator() {
            super("V1");
        }
    }

    protected static class V2NameGenerator extends PackageVersionNameGenerator {
        protected V2NameGenerator() {
            super("V2");
        }
    }

    protected static class PackageVersionNameGenerator extends AnnotationBeanNameGenerator {

        protected final String suffix;

        protected PackageVersionNameGenerator(String suffix) {
            this.suffix = suffix;
        }
            
        @Override
        protected String buildDefaultBeanName(BeanDefinition definition) {
            return super.buildDefaultBeanName(definition) + suffix;
        }
    }
}