No "Run utPLSQL test" context menu in Connections window

[PhilippSalvisberg]

Problem

Sometimes after the installation or reinstallation of the utPLSQL extensions the context menu is missing in Connections window. It does look similar to this:

The SQL Developer About dialog shows that the extension is not fully loaded.

Opening the context menu in the Connections window (database navigator) does not trigger the load of the extension. This is a bug. The extensions should be fully loaded as soon as a context menu with a "Run utPLSQL test" option is opened (or the assigned keyboard shortcut is pressed). However, triggering works in the PL/SQL editor or in the Worksheet but not in the Connections window. This is a bug.

Workaround

As a workaround the context menu in the PL/SQL editor or the Worksheet can be opened. After a restart of SQL Developer the extension is fully loaded and fully functional.

[PhilippSalvisberg]

Based on feedback from dtabase in Slack, it is necessary to execute "Run utPLSQL test" to fully load the extension. After that the option appears in the Connection window without a restart of SQL Developer

[PhilippSalvisberg]

Looks like a custom rule-type cannot be applied as long as the extension is not loaded. And the rule-type definition:

		<rules>
			<rule-type class="org.utplsql.sqldev.menu.UtplsqlNavigatorRule"
				id="utplsql-navigator-rule">
				<supported-parameters />
			</rule-type>
			<rule id="dbnode-is-utplsql-ready" type="utplsql-navigator-rule" />
		</rules>

does not cause the extension to be loaded. A kind of chicken-egg-issue. I see two options:

1. Add the utPLSQL menu on every node in the tree, unconditionally (rule="always-enabled" instead of rule="dbnode-is-utplsql-ready")

2. Use rule-types defined in the extension oracle.jdeveloper.java.core, they are already loaded and therefore can be used. However, rules have to be build using a composite-rule in the extension.xml, which is a bit verbose and less precise than the current implementation in UtplsqlNavigatorRule.xtend.

Option 2 is the way to go.