jira-importer commented on issue #323: URL: https://github.com/apache/maven-install-plugin/issues/323#issuecomment-2771868421
**[Jimisola Laursen](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jimisola)** commented We always want to be able use Maven in the same manner locally as in our CI/CD. Sometimes we use profiles (e.g. time consuming goals) that aren't activated locally but one can always opt-in. I'm suspecting that there is a challenge in how the one can configure the loading of an extension as per https://maven.apache.org/guides/mini/guide-using-extensions.html#core-extension: 1. Registered via extension jar in `{}${maven.home}/lib/ext{`}: clutters Maven installations and/or potentially requires rebuild of container with pre-installed Maven (seems tedious to make it work with Maven Wrapper) 2. Registered via CLI argument `mvn -Dmaven.ext.class.path=extension.jar: not a good option for something permanent` 3. Registered via [`.mvn/extensions.xml` file:](https://maven.apache.org/configure.html#mvn-extensions-xml-file)per project only It seems as if none of these options are a good fit for our use-case (unless I misunderstood them): * should work with both maven and maven wrapper * should work globally (i.e. not on project level) * should work both locally and in ci/cd, some extensions not be active per default but available for opt-in I noticed that there are a few (old) issues here that would meet our use-case, namely settings.xml and profiles: * https://issues.apache.org/jira/browse/MNG-6903 * https://issues.apache.org/jira/browse/MNG-5820 * https://issues.apache.org/jira/browse/MNG-6961 -- 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
