Possibly will be renamed, but basically the mechanism used by other bundles to report information about their activities - whether errors, warnings, info, debug, etc.
The logger could be similar to the ValidationManager, and provide management of a number of logger implementations, or could simply be a single component that can be switched out to provide the most appropriate implementation for the environment.
One potential issue - in the command line approach, if just using the straight command line, then output to stdout/err is fine. However if issuing the commands from other apps, then they may expect access to the reported errors. Possibly a false returned from the command, indicating a fatal error, would be adequate.
Logger implementations now available for command line and Eclipse environment. Tests also provide their own local (test based) logger implementation - so does not really need to be an OSGi component.
Possibly will be renamed, but basically the mechanism used by other bundles to report information about their activities - whether errors, warnings, info, debug, etc.
The logger could be similar to the ValidationManager, and provide management of a number of logger implementations, or could simply be a single component that can be switched out to provide the most appropriate implementation for the environment.
One potential issue - in the command line approach, if just using the straight command line, then output to stdout/err is fine. However if issuing the commands from other apps, then they may expect access to the reported errors. Possibly a false returned from the command, indicating a fatal error, would be adequate.