Spring Roo
  1. Spring Roo
  2. ROO-1820

Replace search features in Shell and JDBC drivers with new RooBot-based search (plus remove now-disused OBR module)

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Complete
    • Affects Version/s: 1.1.0.RELEASE
    • Fix Version/s: 1.1.1.RELEASE
    • Component/s: @ CORE
    • Labels:
      None

      Description

      The old org.springframework.roo.obr module has been deprecated (see ROO-1817).

      The new RooBot Client add-on now offers a far more elaborate search mechanism as contained in ROO-1819. The add-on search discovery in the shell and JDBC driver manager should be replaced to use this.

      The JDBC driver manager should also be enhanced to allow newly-loaded bundles to provide a JDBC driver (in part enabled by ROO-1816).

        Issue Links

          Activity

          Hide
          Ben Alex added a comment -

          Shell searching now uses the fact roobot.xml explicitly contains shell commands.

          JDBC search relies on the description field. The format is:

           #jdbcdriver driverclass:some.class.name.of.the.Driver. Any other description desired.
          

          The hash code and driverclass: can appear anywhere in the description (these do not need to appear at the start or at any other specific location).

          A quick reminder, a normal add-on developer will edit the pom.xml for their add-on and update the description. This will in turn be included in the manifest when the JAR is built. The OBR system will parse the manifest and include it in the repository.xml. RooBot server will parse the OBR file and include it in roobot.xml.

          Git commit 088fa7df21d67c580a473e33a70bf4233db4065d

          Show
          Ben Alex added a comment - Shell searching now uses the fact roobot.xml explicitly contains shell commands. JDBC search relies on the description field. The format is: #jdbcdriver driverclass:some.class.name.of.the.Driver. Any other description desired. The hash code and driverclass: can appear anywhere in the description (these do not need to appear at the start or at any other specific location). A quick reminder, a normal add-on developer will edit the pom.xml for their add-on and update the description. This will in turn be included in the manifest when the JAR is built. The OBR system will parse the manifest and include it in the repository.xml. RooBot server will parse the OBR file and include it in roobot.xml. Git commit 088fa7df21d67c580a473e33a70bf4233db4065d

            People

            • Assignee:
              Ben Alex
              Reporter:
              Ben Alex
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: