[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [virgo-dev] PDE2Virgo Plugin

Hi GianMaria,
 
+1 for the renaming of this flags label to "Tail deploy events into Console view".
Otherwise it is really misleading for users, and me ;) Many thanks for your investigation efforts.
 
Regards,
Dani
Gesendet: Sonntag, 07. Februar 2016 um 18:45 Uhr
Von: Giamma <gm.romanato@xxxxxxxxx>
An: "Virgo Project" <virgo-dev@xxxxxxxxxxx>
Betreff: Re: [virgo-dev] PDE2Virgo Plugin
Dani,

I confim that the only part of the IDE that is affected by the tail flag is the JMX deployer command that deploys workspace bundles to the Virgo runtime once the user region is ready.
Should we rename the option to "Tail deploy events into Console view" ?
 
GIanMaria.
 
On Thu, Jan 21, 2016 at 1:26 PM Giamma <gm.romanato@xxxxxxxxx> wrote:
On Wed, Jan 20, 2016 at 3:19 PM Daniel Marthaler <DMarthaler@xxxxxxx> wrote:
 
| Similarly, the tail parameter seem to be properly managed.
 
But what is the expected effect when selecting this option in the server dialog? I expect to see the application trace log in the Eclipse Console View when I select this option, but I can only see the event logs as before I selected this option. Or do I misunderstand this feature?
 

Initially I had the same expectation as you, but in my practical experience, that flag influences only the event logs (in fact, it's the JMX deployer command that checks the value of the flag and produces the event logs in case it's set to true).  I'll investiage a bit more, but in my working experience with the tools, I usually tweak the serviceability.xml file and change appenders to re-route log more to the Eclipse console.

 
_______________________________________________ virgo-dev mailing list virgo-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/virgo-dev