To complete the list of Hervé, I was thinking of:
maven [ .$groupId ] .${artifactId} [ [ .${executionId} ] .${goal} ]
Next it would be very nice that if there's an exception during the
process, we could add a line like for instance:
Execute "mvn verify -Lmaven.g.a.e.g=debug" to get extra information of
the failing goal.
Next feature would be to let Maven detect for a goal if it has been
specified with a custom logging level, so it can mark that block by
beginning and ending it with a line of "===" or other character range.
This way users don't have to send complete logs and we don't have to
search for the failing part. For over 90% of the testcases this is enough
info to pinpoint the issue.
-Robert
Op Fri, 16 Nov 2012 07:39:50 +0100 schreef Hervé BOUTEMY
<[email protected]>:
+1 for the idea
other complementary ideas:
- groupId is not really useful, plugins's artifactId is in general
sufficient
- I'd add goal name
- dot separator, since this is the classical separator in every java
logging
implementations (due to the classical class name as logger pattern)
- add prefix with something like "maven.", to separate maven logs from
logs
from other tools (probably organized by full class name)
then my preference would go to
maven.${artifactId}.${goal}
which is a "domain specific" pattern, not the classical full class name
(FYI, that' not the first time I use such "domain specific" logger name
pattern,
and I never had problems with such decision: yes, that's a bit not
conventional but respects logging frameworks and is easy to understand)
Regards,
Hervé
Le jeudi 15 novembre 2012 14:18:46 Olivier Lamy a écrit :
Hi,
Currently logger for all mojos is the DefaultPluginManager logger.
So it's a bit hard to have filtering per plugin (i.e. only compiler in
debug etc..)
So I'd like to change that to be able to customize mojo logging.
My first is idea is mojo with logger name ${groupId}:${artifactId} (ie
org.apache.maven.plugins:maven-clean-plugin) so if you only want debug
for compiler put logger org.apache.maven.plugins:maven-compiler-plugin
to debug.
Makes sense ?
The code to change is here:
https://github.com/olamy/maven-3/blob/log4j2/maven-core/src/main/java/org/ap
ache/maven/plugin/internal/DefaultMavenPluginManager.java#L445
WDYT ?
Thanks
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
