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 scenes' that results in lots of messages being produced long before there's any mention of what phase or plugin goal has caused the messages or where the user is in the flow of things. One of the biggest draw backs with using maven 2, beyond the lack of tutorials and indepth technical documentation, is its difficulty in problem identifcation and resolution - even to the hex headed, when something breaks/doesnt work (as expected) the only option is to spend a week (or 2) hacking away at the mighty collection of projects, code, apis and utils (i.e. custom everything) trying to get to grips with whats going on uner the scenes. In my humble opinion, a build system, with its critical posiitoning within the engineering process, has gotta be simple (or at least appear to be without obscuring pertinent details), accessible and above all easy to fix and administer and currently the lack of consistent, user oriented logging and tracing gets in the way of this. Regarding m2s adoption in large scale enterprise dev env projects: yes I need a build fwk that supports/promotes depedency mgmt, standardisation, reporting, network delivery, deployment control, agile SDM techniques and architeral governance but more importantly, i need one that is easy to support, train, administer, adapt, extend and fix. Better messages and message tracing and some proper technical docs will help this i think.

Observations:-

- Too much noise that is only really meaningful to experts
- Unable to distinguish what action has caused a message, part of a wider issue with not being able to associate what is being said, by who, and why (users pov)
- No ability to extend message generation/delivery with adapters etc.


John Allen.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to