Hi Sebb, sebb wrote:
[snip] > However file-based activation does work OK - this would require > projects to define a dummy file somewhere, for example: > > src/site/resources/coverage.jacoco > or > src/site/resources/coverage.cobertura > > A component can thereby define the appropriate default coverage tool. > > This can be overridden on the command line, for example: > > -P!jacoco -Pcobertura if we start to get into the file-based profile activation, I strongly suggest to follow a common pattern and use a profile directory: =========== %< ============= pom.xml profiles/ cobertura =========== %< ============= Otherwise no-one knows in the end what file triggers an automated profile. - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
