I can hypothecate a use case, but I can't point to an example. Consider a plugin that sits on top of something large and complex, and which logs, and which takes complete responsibility for its logging. It might, for example, have plugin parameters that control the logging and the destination.
The users of that plugin will not be happy if a change to maven x.y results in all this information being re-routed into Maven's Own Log, instead of landing where their configuration tells it to land. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
