+1 to this.
Want to add a JIRA to maven-site-plugin for 2.0 to upgrade velocity
component?
- Brett
Fabrizio Giustina wrote:
On 1/11/06, Brett Porter [EMAIL PROTECTED] wrote:
I think we'd all agree with the sentiment. I think the default needs to
be less noisy
Well, a good start for
Hi John,
I think we'd all agree with the sentiment. I think the default needs to
be less noisy, and -X should be targetted (debug artifact resolution,
debug pom, etc). We could name systems and log accordingly. This is all
in JIRA.
If you have any suggestions for implementation, please say so!
I have been a big fan of domained logging...where the logging api call
contains whatever is necessary to earmark that log message as belonging to a
particular domain (domain being whatever you want to define it as, the
class, the package, the logical functionality of something..)
I have done this
Jesse McConnell wrote:
I have been a big fan of domained logging...where the logging api call
contains whatever is necessary to earmark that log message as belonging to a
particular domain (domain being whatever you want to define it as, the
class, the package, the logical functionality of
On 1/11/06, Brett Porter [EMAIL PROTECTED] wrote:
I think we'd all agree with the sentiment. I think the default needs to
be less noisy
Well, a good start for removing LOTS of useless debug messages while
generating site or reports could be committing this patch to plexus:
Jason van Zyl wrote:
That would be cool! It would be far simpler for users to track down
specific problems and even if there are intersecting domains involved
you just turn on the logging for the appropriate domain. Very nice idea.
Agreed. So how do we go about this? We can probably match the
sure thing, might not get to it for a bit...kinda crushed under some other
things but definitely something interesting to look into.
I was just thinking, that perhaps instead of domaining by package, it might
be interesting to try and do it via artifact...I am not sure what kind of
overhead would
Thoughts on logging:-
I would like to see logging messages use relevant and meaningful identifiers
that are correlatable to provide users with a means of knowing what is going
on and what sequence of events has brought about the output. Currently huge
amounts of work goes on 'behind the
