[JBoss JIRA] (JBIDE-24552) Jsp parser gives Syntax error, insert ")" to complete Expression
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24552?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24552:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Jsp parser gives Syntax error, insert ")" to complete Expression
> -----------------------------------------------------------------
>
> Key: JBIDE-24552
> URL: https://issues.jboss.org/browse/JBIDE-24552
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html-source-editing
> Environment: Environment is Eclipse MARS 2
> Reporter: Edoardo Barolo
> Assignee: Jeff MAURY
> Priority: Minor
> Fix For: 4.6.x
>
>
> While I write a jsp i obtain the error "Syntax error, insert ")" to complete Expression"
> in a coda like this
> %> <option value="<%=item.getCode() %>"><%=item.getDescription() %></option> <%
> as you can see the ) is present... I think this is an ancient error that is present everywhere in eclipse I continue to see it
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-22929) NullPointerException in VpePreviewDomBuilder.createNode
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22929?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22929:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> NullPointerException in VpePreviewDomBuilder.createNode
> -------------------------------------------------------
>
> Key: JBIDE-22929
> URL: https://issues.jboss.org/browse/JBIDE-22929
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Reporter: Automated Error Reporting Bot
> Assignee: Ilya Buziuk
> Fix For: 4.6.x
>
>
> The following problem was reported via the automated error reporting:
> Message: Unhandled event loop exception
> {noformat}
> java.lang.NullPointerException: null
> at org.jboss.tools.vpe.editor.VpePreviewDomBuilder.createNode(VpePreviewDomBuilder.java:92)
> at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255)
> at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:543)
> at org.jboss.tools.vpe.editor.VpePreviewDomBuilder.createNode(VpePreviewDomBuilder.java:100)
> at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255)
> at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:543)
> at org.jboss.tools.vpe.editor.VpePreviewDomBuilder.createNode(VpePreviewDomBuilder.java:100)
> at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255)
> at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:543)
> at org.jboss.tools.vpe.editor.VpePreviewDomBuilder.createNode(VpePreviewDomBuilder.java:100)
> at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255)
> at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:543)
> at org.jboss.tools.vpe.editor.VpePreviewDomBuilder.createNode(VpePreviewDomBuilder.java:100)
> at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255)
> at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.buildDom(VpeVisualDomBuilder.java:192)
> at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.rebuildDom(VpeVisualDomBuilder.java:224)
> at org.jboss.tools.vpe.editor.mozilla.MozillaPreview.rebuildDom(MozillaPreview.java:111)
> at org.jboss.tools.vpe.editor.VpeEditorPart.setVisualMode(VpeEditorPart.java:315)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.JSPMultiPageEditor.pageChange(JSPMultiPageEditor.java:337)
> at org.eclipse.ui.part.MultiPageEditorPart$2.widgetSelected(MultiPageEditorPart.java:295)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> {noformat}
> Bundles:
> | org.eclipse.swt | 3.104.2.v20160212-1350 | 3.105.0.v20160603-0902 |
> | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.108.0.v20160518-1929 |
> | org.jboss.tools.jst.web.ui | 3.7.1.Final-v20160331-0256-B96 | 3.8.0.Final-v20160609-2146-B2 |
> | org.jboss.tools.vpe | 3.7.1.Final-v20160331-0327-B91 | 3.8.0.Final-v20160609-2229-B3 |
> Operating Systems:
> | Linux | 3.8.0 | 3.8.0 |
> | Windows | 6.1.0 | 6.1.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/57447dcde4b0138d62...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-20730) Displaying of a project in OpenShift Explorer view is not consistent
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20730?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-20730:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Displaying of a project in OpenShift Explorer view is not consistent
> --------------------------------------------------------------------
>
> Key: JBIDE-20730
> URL: https://issues.jboss.org/browse/JBIDE-20730
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Marián Labuda
> Priority: Minor
> Labels: explorer, openshift_v3
> Fix For: 4.6.x
>
>
> OpenShift 3 project is displayed a bit tricky in OpenShift Explorer view. If project has only project name, then project name is shown as normal text in OpenShift Explorer view under an OpenShift 3 connection. But if a project has set also an optional attribute displayName, then this name is used as a normal text under an OpenShift 3 connection and it's name is used only as a decorated text in parenthesis. Example:
> Project 01 has name: project01
> Project 02 has name: project02 and displayName: projectName02
> In OpenShift Explorer view are those projects shown as
> project01
> projectName02 (project02)
> One could think that project01 and projectName02 are the same attribute of a project, but it's not. I think we could and should show projects like this:
> project01 (project01)
> projectName02 (project02)
> because default value for a displayName is attribute name. In that case it would be consistent and user would not be confused.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months