Description of problem: The move to typeless gears and the new location of the log files has broken the tail feature in JBDS because they had the location hardcoded. The proposed resolution is to make a soft link from the old location to the new location Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. create app 2. attempt to tail log files from JBDS 3. Actual results: tail fails Expected results: tail succeeds Additional info:
JBoss Tools for OpenShift had this issue filed at https://issues.jboss.org/browse/JBIDE-13069. I would have added a sync to this bugzilla if I had been able ;)
The highest prio for us at JBoss Tools is to allow users of existing JBDS version to look at the application logs. So we'd be very grateful if you could provide a fix that would keep compatibility to existing JBDS releases. On the long run we can of course provide changes on our side but this would not help existing users.
We're looking at adding the log location to the rest api. Once that's done I'll add it to the java client and future versions of JBDS can use that. For now it looks like this is a regression bug we're going to have to live with as we can't create a link from the old log location to the new one.
Rajat to get into restAPI 16Nov2012. Team to review outcome and determine if this will go into this Sprint.
. looks like there is a way for the java client to find the env for the log file location and thus the log file. Bill working on that now. Not a blocker.
What's the state of this?
Ultimately we want to add the log file location to the rest api. Right now we can just get the log file location env filename. This is now exposed through the java client.
Will move to a user story.
*** This bug has been marked as a duplicate of bug 864653 ***