Community
Participate
Working Groups
Simliar to how the console view has description text on which VM and launch configuration you do, we should do something for the log you're currently look at. I envision something like "[workspace log]" or "[launch configuration name] c:/locaationblahbalbha" Feel free to be creative :)
Created attachment 88518 [details] patch it actually sets title as: Workspace log file - for current workspace log file Launch Configuration [C:\long\long\Launch Configuration\workspace\.metadata\.log] C:\long\long\Launch Configuration\workspace\.metadata\.log - if log does not belong to any launch configuration the other way ("[Name] Path") didn't look good to me. You may play with it modifying messages.properties :)
yay!
thanks Jacek, I had to fix an issue with paths not being relativized, but other than that the patch was perfect! A thought hit me that in the future, we may consider an extension point for the logview instead of the current LogFilesManager approach... however, that's a low priority and until someone asks for it, let's not worry about it :)
Created attachment 88564 [details] mylyn/context/zip
(In reply to comment #3) > A thought hit me that in the future, we may consider an extension point for the > logview instead of the current LogFilesManager approach... however, that's a > low priority and until someone asks for it, let's not worry about it :) gosh! that'd be my first extension point in Eclipse... not sure if I could handle this! :P imagine different log providers for different launch configs (Java Apps, Web servers, ...)! Automatic log formats detection, hundrets of log patterns (Apache logs, log4j, ...) :) TPTP Logging people would kill us.
Verified on I20080204-0800
