Le 2025-03-17 à 17 h 03, Matthias Bünger a écrit :

I'm not an IDE developer, but Maven user and mixing those two, for me independend things, will make it more confusing than simpler.
The usage of <type> introduced in Maven 4 is already implicitly mixing the scope. The proposal to replace:

   <type>modular-processor</type>

by

   <type>modular-jar</type>
   <scope>processor</scope>

is an attempt to make that clearer, therefore hopefully clearer for Maven users. It integrates with the current Maven usage, where <scope> is already used for saying that a JAR shall be used at compilation time, or testing time, etc. Saying that a JAR shall be used at annotation processing time, or javadoc time, is a natural extension. Wouldn't it be clearer for Maven users than having a "processor" scope implied by the "processor" suffix of the "modular-processor" type?

    Martin


Reply via email to