Hi, maybe a bit out of context but some work was done to make it possible to define options within the pom, why wouldn't it fit better than a hacky file which is actually just an internal trick of some maven plugins but not all? It would be like dependencies for a JVM. Assuming to assign them a "scope" (literal meaning not <dependency> one) you can then gather the options from any plugin and use it properly and reuse them accross plugins. Would mean surefire, failsafe, exec, etc could get a <jvmArgsIdentifier> (List<String>) and gather some options from there. Indeed, since we are about conventions, we would define some default "groups" (identifiers/scopes) but nothing crazy in our land.
Doesn't it sound better than a file which looks like a java thing but is not (content), has no editor support (extension), will need to be supported by all plugins and still requires its location to be configurable since you can need to run surefire with multiple configurations to test different cases (different group sets in my proposal). Hope it makes some sense. Romain Manni-Bucau @rmannibucau <https://x.com/rmannibucau> | .NET Blog <https://dotnetbirdie.github.io/> | Blog <https://rmannibucau.github.io/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/en-us/product/java-ee-8-high-performance-9781788473064> Le lun. 14 avr. 2025 à 12:54, Martin Desruisseaux < martin.desruisse...@geomatys.com> a écrit : > Le 2025-04-14 à 12 h 49, Gary Gregory a écrit : > > > "The ".txt" extension is because this file is not standard Java > > (proposals for better extension are welcome)." > > How about ".mvn" or ".maven" to make it clear that this file exists > > for Maven's purpose and is not documentation, which is what ".txt" > > feels like to me. > > Yes, I also though about ".mvn" or ".maven". This is certainly a good > candidate. > > Martin > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
