Here is a good new for those who ever suffered reading ATL VM's stack traces: ATL3.0.0 provides console hyperlinks which allow to follow errors just by clicking, as you can see below.
Great work on the lastest ATL 3.0 version (about 10 to 20 times faster!). We're launching ATL transformations in OSGI mode, is there a way to deactivate the console ui logging, or a way to redirect the logging stream (using java code)?
Here is the place where the ATLLogger output is "catched": org.eclipse.m2m.atl.core.ui.ATLCoreUIPlugin.startConsole() in the org.eclipse.m2m.atl.core.ui plugin.
You can use the same way to redirect the logging stream (ATLLogger.getLogger().addHandler();).
This is nice. It has always been a pain to find the location of errors in ATL-scripts.
RépondreSupprimerGreat work on the lastest ATL 3.0 version (about 10 to 20 times faster!). We're launching ATL transformations in OSGI mode, is there a way to deactivate the console ui logging, or a way to redirect the logging stream (using java code)?
RépondreSupprimerHi Jean,
RépondreSupprimerHere is the place where the ATLLogger output is "catched": org.eclipse.m2m.atl.core.ui.ATLCoreUIPlugin.startConsole() in the org.eclipse.m2m.atl.core.ui plugin.
You can use the same way to redirect the logging stream (ATLLogger.getLogger().addHandler();).
Thank you William, I hooked it back into our logging system and its working great.
RépondreSupprimer