Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-9892

JUnit Failures: org.jboss.tools.jsf.vpe.jsf.test.jbide.JBIDE788Test.testCAforSourceCodeTemplatesProposals()

    Details

      Gliffy Diagrams

        Issue Links

          Activity

          Hide
          dmaliarevich Denis Maliarevich added a comment -

          Because on Jenkins this test is passed – changing fix version to Beta1.

          Show
          dmaliarevich Denis Maliarevich added a comment - Because on Jenkins this test is passed – changing fix version to Beta1.
          Hide
          dmaliarevich Denis Maliarevich added a comment -

          There are no proposals because XHTMLTemplateContentAssistComputer hasn't been created yet.
          After you open Window->Preferences->JBoss Tools->Editors->VPE->Code Templates to check that temlates are defined – and then after returning back to the page CA will show templates' proposals.

          Show
          dmaliarevich Denis Maliarevich added a comment - There are no proposals because XHTMLTemplateContentAssistComputer hasn't been created yet. After you open Window->Preferences->JBoss Tools->Editors->VPE->Code Templates to check that temlates are defined – and then after returning back to the page CA will show templates' proposals.
          Hide
          dmaliarevich Denis Maliarevich added a comment - - edited

          The reason is that org.jboss.tools.jst.web.ui plugin is not loaded yet. Thus extension point "org.eclipse.wst.sse.ui.completionProposal" hasn't been initiated yet -> no completion proposals are shown.

          Show
          dmaliarevich Denis Maliarevich added a comment - - edited The reason is that org.jboss.tools.jst.web.ui plugin is not loaded yet. Thus extension point "org.eclipse.wst.sse.ui.completionProposal" hasn't been initiated yet -> no completion proposals are shown.
          Hide
          dmaliarevich Denis Maliarevich added a comment -

          Such a behavior is a rule in Eclipse UI:

          "A plug-in gets started when the user needs it. In UI design, an often cited rule is that the screen belongs to the user. A program should not make changes on the screen that the user didn’t somehow initiate." (c)

          It explains the situation that after looking into "Code Templates" CA starts working
          (or you can select "New JSF Wizard" -> CA will appear as well).

          Show
          dmaliarevich Denis Maliarevich added a comment - Such a behavior is a rule in Eclipse UI: "A plug-in gets started when the user needs it. In UI design, an often cited rule is that the screen belongs to the user. A program should not make changes on the screen that the user didn’t somehow initiate." (c) It explains the situation that after looking into "Code Templates" CA starts working (or you can select "New JSF Wizard" -> CA will appear as well).
          Hide
          dmaliarevich Denis Maliarevich added a comment - - edited

          JUnit on Jenkins is not failing because before running this test org.jboss.tools.jst.web.ui plugin has been already accessed.
          But localy there is a failure.

          Show
          dmaliarevich Denis Maliarevich added a comment - - edited JUnit on Jenkins is not failing because before running this test org.jboss.tools.jst.web.ui plugin has been already accessed. But localy there is a failure.
          Hide
          dmaliarevich Denis Maliarevich added a comment -

          But there is a question why the extension point is not loaded from plugin.xml file (declarative section). The full plugin initialization is not required to use plugin.xml.

          Show
          dmaliarevich Denis Maliarevich added a comment - But there is a question why the extension point is not loaded from plugin.xml file (declarative section). The full plugin initialization is not required to use plugin.xml.
          Hide
          dmaliarevich Denis Maliarevich added a comment -

          Actually there is an attribute "activate" in <proposalComputer> declaration which will force the plug-in to be loaded on content assist invocation.

          Show
          dmaliarevich Denis Maliarevich added a comment - Actually there is an attribute "activate" in <proposalComputer> declaration which will force the plug-in to be loaded on content assist invocation.
          Hide
          dmaliarevich Denis Maliarevich added a comment -

          Resolved.

          Show
          dmaliarevich Denis Maliarevich added a comment - Resolved.

            People

            • Assignee:
              dmaliarevich Denis Maliarevich
              Reporter:
              yradtsevich Yahor Radtsevich
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development