On 9/28/05, Orjan Austvold [EMAIL PROTECTED] wrote:
Instead of having lots of debug statements in your Mojo, you could
simply connect a debugger to Maven.
I'm doing this with IDEA simply by running maven with
MAVEN_OPTS=-Xdebug -Xnoagent -Djava.compiler=NONE
When writting a Mojo, what are the standard convention to trace/log [debug]
messages ?
Gilles Scokart
_
Protégez votre boîte de réception: Phishing : comment l'identifier, le
signaler et l'empêcher
On Wed, 2005-09-28 at 12:24 +0200, Gilles Scokart wrote:
When writting a Mojo, what are the standard convention to trace/log [debug]
messages ?
getLog().info( Hey yo! );
--
Trygve
-
To unsubscribe, e-mail: [EMAIL
Instead of having lots of debug statements in your Mojo, you could
simply connect a debugger to Maven.
I'm doing this with IDEA simply by running maven with
MAVEN_OPTS=-Xdebug -Xnoagent -Djava.compiler=NONE
-Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005 m2 install
Ørjan
Thanks, but what are the guidelines on when to log at which level ? I guess
it's a good idea that all plugins follow the same guidelines. What is the
best practice for that ?
And what if our mojo call external code that is not (and should not be)
aware of running into a maven plugin ?
On 9/29/05, Gilles Scokart [EMAIL PROTECTED] wrote:
Thanks, but what are the guidelines on when to log at which level ? I guess
it's a good idea that all plugins follow the same guidelines. What is the
best practice for that ?
This should all be information for the user: ERROR for things
