zaplatynski / second-hand-log Goto Github PK

At the moment the console can only be used from FirstSpirit SiteArchitect. There should be a way to launch it somewhere out of the ServerManager.

To get a better understanding what is going on at the log messages there should be an automatic way of mark log messages by colour.

Error messages should be red, warnings should be written in orange while info messages can be displayed in blue or debug messages appear in dark grey.

As a place or for new additions like commands for change the number of lines which the console keeps or a command to copy the console to the system's clipboard etc.

To focus on the current development task it is useful to clear the log console before to keep only log messages which have to do the one's we are interested in.

If you are using more than one instance of SiteArchitect it could be confusing which log window belongs to which one. To be able to tell which log window belongs to which SiteArchitect instance there must be the name of the project inside the log window's title.

Migrate to the version of Maven FSM package type and make use of the distributed creation of the FirstSpirit deployment descriptor (module.xml) as preparation for future enhancements.

The Second-Hand Log should provide the possibility to disable it for certain FirstSpirit projects and user groups.

Add an menu action to configure Log4J to store all log messages to the user's directory for further investigation.

At the moment the Maven install goal does not work the way one would expect: it should install the FSM. Instead it installs the jar contained in the FSM. As long as nobody wants to add the FSM to the local Maven repository or a artifact repository like Nexus this is not critical.

This single Maven module project is far to rough to create a complex artifact like FSM. This must be solved with multi Maven module project to respect the way Maven works.

For reasons of storage efficiency the number of lines in the console must be limited. The number depends on how much memory is available to the main Java application.

At the moment the number is static and can not be changed during runtime. A menu action is needed to change the number of lines.

Add an menu action to copy all current log messages to the system's clipboard.