jira-importer commented on issue #323:
URL: 
https://github.com/apache/maven-install-plugin/issues/323#issuecomment-2771868429

   **[Jimisola 
Laursen](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=JIRAUSER281352)**
 commented
   
   I think I found a solution for us using MAVEN_ARGS, but I'll have to test it 
so that MAVEN_ARGS can be used to point out a core extension with
   
   ```java
   MAVEN_ARGS="-Dmaven.ext.class.path=extension.jar"
   ```
   
   Yes, inhouse projects and we have a lot of them.
   
   We avoid configuration files in projects like the plague because it does not 
scale (easy to forget to add and/or update). 
   
   If we have to make a change then we have to do it in all those projects and 
it's configuration for lombok, maven, log4j, sonarqube and so on. Every single 
tool has the mindset that it's just "a configuration file more". It's sadly 
not. It needs to be maintained and version controlled. It was, e.g. only in 
[May this year that renovate got support for 
.mvn/extensions.xml](https://github.com/renovatebot/renovate/pull/28893).
   
   If it is something that should be applied to "all" our projects then we 
prefer to configure that globally and handle the outliers separately.
   
   **Globally** in this case is that the configuration can be set in a way that 
it applies to all projects being run/build on that machine for a user and 
ideally it can also be overridden on project level or similar.
   
   That is, it does not matter if it's an actual user on a machine or in CI/CD. 
The only difference in this case is that _Registered via CLI argument mvn 
-Dmaven.ext.class.path=extension.jar_ would be very simple to add and maintain 
in CI/CD ({_}and this is when I recalled seeing something about MAVEN_ARGS for 
Maven 3.9+{_}).
   
   E.g. for mypy we have a global configuration file in ~/.config/mypy/mypy.ini 
that can be overridden on project level if needed.
   
   I also had an idea of :
   
    
   
   ```java
   <profiles>
       <profile>
           <id>default-options</id>
           <properties>
               <maven.ext.class.path>extension.jar</maven.ext.class.path>
           </properties>
       </profile>
   </profiles> 
   ```
   
   but, I'm not sure that that is the same as providing it on the command line 
as -D<...> or if settings.xml is read too late when it comes to core 
extensions. Been looking for documentation on it and searching for execution 
diagrams without luck.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to