[
https://issues.jboss.org/browse/JBIDE-18258?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-18258:
-------------------------------------
Rob says he saw this kind of error before, when he was missing
plugin.xml,
To clarify, I meant I've seen this TYPE of issue (ie, this error output) during
dev-mode if my plugin.xml was missing some triggerpoints. Usually I've seen it when
adding new features or new structures to trees like project explorer or other, and I had
not fully implemented the solution.
Anyway, I also cannot replicate
"Cannot find navigator content extension" when starting a
local server after setting up a remote server
-------------------------------------------------------------------------------------------------------
Key: JBIDE-18258
URL:
https://issues.jboss.org/browse/JBIDE-18258
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jmx, server
Affects Versions: 4.2.0.CR1
Reporter: Martin Malina
Assignee: Rob Stryker
Priority: Critical
Fix For: 4.2.0.CR1
When I set up a local server, then a remote server and then I start the local server, I
get errors:
{code}
!ENTRY org.eclipse.ui.navigator 4 0 2014-09-04 11:46:26.700
!MESSAGE Cannot find navigator content extension (using triggerPoints) for object
"org.jboss.modules.Main [22362]" parent path: "R/". Check that you
have an expression for this object in a navigatorContent triggerPoints or enablement.
!ENTRY org.eclipse.ui.navigator 4 0 2014-09-04 11:46:26.703
!MESSAGE Cannot find navigator content extension (using triggerPoints) for object
"org.jboss.modules.Main [22362]" parent path: "R/". Check that you
have an expression for this object in a navigatorContent triggerPoints or enablement.
!ENTRY org.eclipse.ui.navigator 4 0 2014-09-04 11:46:26.895
!MESSAGE Cannot find navigator content extension (using triggerPoints) for object
"org.jboss.modules.Main [22362]" parent path: "R/". Check that you
have an expression for this object in a navigatorContent triggerPoints or enablement.
{code}
I'm not exactly sure how this works, but strangely, the errors are thrown even after
I remove the remote server. But they did not occur before I created the remote server. So
perhaps it has something to do with the existence of the remote system and not really the
remote server itself? I don't know.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)