On 23 May 2013 08:34, Jörg Schaible <joerg.schai...@scalaris.com> wrote: > 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.
I choose src/site/resources because the profiles affect the site build and I did not want to create a new folder. But of course other locations are possible. Or we could use "profile.jacoco" instead of "coverage.jacoco" under src/site/resources I have committed the change as originally proposed. We can change the trigger files (and associated comments) before releasing CP30 Meanwhile please try out the new profiles. > - Jörg > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
