[JBoss JIRA] (JBIDE-16182) For JBIDE 4.1.1.Final: Code Freeze + Branch [Central Discovery]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-16182:
----------------------------------
Summary: For JBIDE 4.1.1.Final: Code Freeze + Branch [Central Discovery]
Key: JBIDE-16182
URL: https://issues.jboss.org/browse/JBIDE-16182
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: discovery
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.1.1.Final [Central Discovery]: Please perform the following tasks:
0. If nothing has changed in your component since the last milestone or GA release on this branch (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Final or 7.1.0.GA
1. *IN THE {color:blue}4.1.1.x{color} branch*, update your root pom to use parent pom version *4.1.1.Final-SNAPSHOT*
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.1.Final-SNAPSHOT</version>
</parent>
{code}
2. *IN THE {color:orange}4.1.x{color} branch*, update your root pom to use parent pom version *4.1.2.Alpha1-SNAPSHOT*
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.2.Alpha1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform versions
{code}
mvn clean verify -Dtpc.version=4.30.6.Final
mvn clean verify -Dtpc.version=4.31.1.Final
{code}
4. Close (do not resolve) this JIRA when done.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Central Discovery task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16183) For JBIDE 4.1.1.Final: Code Freeze + Branch [Server]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-16183:
----------------------------------
Summary: For JBIDE 4.1.1.Final: Code Freeze + Branch [Server]
Key: JBIDE-16183
URL: https://issues.jboss.org/browse/JBIDE-16183
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: server
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.1.1.Final [Server]: Please perform the following tasks:
0. If nothing has changed in your component since the last milestone or GA release on this branch (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Final or 7.1.0.GA
1. *IN THE {color:blue}4.1.1.x{color} branch*, update your root pom to use parent pom version *4.1.1.Final-SNAPSHOT*
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.1.Final-SNAPSHOT</version>
</parent>
{code}
2. *IN THE {color:orange}4.1.x{color} branch*, update your root pom to use parent pom version *4.1.2.Alpha1-SNAPSHOT*
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.2.Alpha1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform versions
{code}
mvn clean verify -Dtpc.version=4.30.6.Final
mvn clean verify -Dtpc.version=4.31.1.Final
{code}
4. Close (do not resolve) this JIRA when done.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Server task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16184) For JBIDE 4.1.1.Final: Code Freeze + Branch [Hibernate]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-16184:
----------------------------------
Summary: For JBIDE 4.1.1.Final: Code Freeze + Branch [Hibernate]
Key: JBIDE-16184
URL: https://issues.jboss.org/browse/JBIDE-16184
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: hibernate
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.1.1.Final [Hibernate]: Please perform the following tasks:
0. If nothing has changed in your component since the last milestone or GA release on this branch (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Final or 7.1.0.GA
1. *IN THE {color:blue}4.1.1.x{color} branch*, update your root pom to use parent pom version *4.1.1.Final-SNAPSHOT*
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.1.Final-SNAPSHOT</version>
</parent>
{code}
2. *IN THE {color:orange}4.1.x{color} branch*, update your root pom to use parent pom version *4.1.2.Alpha1-SNAPSHOT*
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.2.Alpha1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform versions
{code}
mvn clean verify -Dtpc.version=4.30.6.Final
mvn clean verify -Dtpc.version=4.31.1.Final
{code}
4. Close (do not resolve) this JIRA when done.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Hibernate task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16186) For JBIDE 4.1.1.Final: Code Freeze + Branch [OpenShift]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-16186:
----------------------------------
Summary: For JBIDE 4.1.1.Final: Code Freeze + Branch [OpenShift]
Key: JBIDE-16186
URL: https://issues.jboss.org/browse/JBIDE-16186
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: openshift
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.1.1.Final [OpenShift]: Please perform the following tasks:
0. If nothing has changed in your component since the last milestone or GA release on this branch (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Final or 7.1.0.GA
1. *IN THE {color:blue}4.1.1.x{color} branch*, update your root pom to use parent pom version *4.1.1.Final-SNAPSHOT*
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.1.Final-SNAPSHOT</version>
</parent>
{code}
2. *IN THE {color:orange}4.1.x{color} branch*, update your root pom to use parent pom version *4.1.2.Alpha1-SNAPSHOT*
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.2.Alpha1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform versions
{code}
mvn clean verify -Dtpc.version=4.30.6.Final
mvn clean verify -Dtpc.version=4.31.1.Final
{code}
4. Close (do not resolve) this JIRA when done.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for OpenShift task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16185) For JBIDE 4.1.1.Final: Code Freeze + Branch [Base]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-16185:
----------------------------------
Summary: For JBIDE 4.1.1.Final: Code Freeze + Branch [Base]
Key: JBIDE-16185
URL: https://issues.jboss.org/browse/JBIDE-16185
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: common/jst/core, usage
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.1.1.Final [Base]: Please perform the following tasks:
0. If nothing has changed in your component since the last milestone or GA release on this branch (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Final or 7.1.0.GA
1. *IN THE {color:blue}4.1.1.x{color} branch*, update your root pom to use parent pom version *4.1.1.Final-SNAPSHOT*
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.1.Final-SNAPSHOT</version>
</parent>
{code}
2. *IN THE {color:orange}4.1.x{color} branch*, update your root pom to use parent pom version *4.1.2.Alpha1-SNAPSHOT*
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.2.Alpha1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform versions
{code}
mvn clean verify -Dtpc.version=4.30.6.Final
mvn clean verify -Dtpc.version=4.31.1.Final
{code}
4. Close (do not resolve) this JIRA when done.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Base task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-16135) EL Content Assist in Java Editor: Make Content Assistant Additional Info window support URLs.
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16135?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-16135:
-----------------------------------
Summary: EL Content Assist in Java Editor: Make Content Assistant Additional Info window support URLs. (was: EL Content Assist in Java Editor: Make Content Assistant Additional Info window to support URLs.)
> EL Content Assist in Java Editor: Make Content Assistant Additional Info window support URLs.
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-16135
> URL: https://issues.jboss.org/browse/JBIDE-16135
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.1.0.Final
> Reporter: Victor Rubezhny
> Assignee: Victor Rubezhny
> Priority: Minor
> Labels: new_and_noteworthy
> Fix For: 4.2.x
>
> Attachments: el-ca-add-info-javaeditor.png, hover-javaeditor.png, hover-xhtmleditor.png, html.png, javadoc.png
>
>
> EL could be used in String values in Java classes, so the same Additional Info is to be shown for Content Assist in Java Editor as well as in Tooltips (Hovers).
> There are two kinds of links which we should support:
> 1. External HTML links (<a href="http://..."> or <a href="https://...">). Such links are supposed to be opened in the default web browser:
> !html.png|thumbnail!
> *Note:* we don't have such links in our content assist. This screenshot is just an example how it will look like if we add any <a> to a description message.
> 2. Internal links to JavaElement (used in JSF EL). It works in the same way as Eclipse JDT content assist does. Such links are supposed to be opened in SWT web browser (in the same description window):
> !javadoc.png|thumbnail!
> 3. Links and Java-like Additional Info in Java Editor (for ELs in Java Strings):
> !el-ca-add-info-javaeditor.png|thumbnail!
> 4. Same look and functionality for Tooltips (Hovers) in Java and JBossTools Editors:
> !hover-javaeditor.png|thumbnail! !hover-xhtmleditor.png|thumbnail!
> *Steps to test:*
> 1. Make sure JDK sources are available in Eclipse
> 2. Create a JSF 2 KickStart project.
> 3. Open greeting.xhtml
> 4. Type #\{user.name.l and press Ctrl+Space
> 5. Select length
> 6. There should be a description dialog with java element links to length() and CharSequence:
> !javadoc.png|thumbnail!
> EL Content Assist in Java Strings:
> 7. Use the project created at steps 1-2.
> 8. Open User.java.
> 9. Reveal String getName() method and add the following line before the return statement:
> {code}String x = "#{user.}";{code}
> 10. Set the text cursor after 'user.' and press Ctrl-Space
> 11. Select 'name'
> 12. There should be a description dialog with java element links to package 'demo', classes 'String' and 'User', and methods 'getName()' and 'setName()'
> !el-ca-add-info-javaeditor.png|thumbnail!
> Tooltips in Java Editor:
> 13. Apply the 'name' proposal.
> 14. Point the mouse cursor over 'name' in EL and wait for a second.
> 15. There should be a hover dialog opened with java element links to package 'demo', classes 'String' and 'User', and methods 'getName()' and 'setName()'.
> !hover-javaeditor.png|thumbnail!
> Tooltips in JBoss Editors:
> 16. Open inputname.xhtm
> 17. Reveal '#\{user.name\}' EL in editor.
> 14. Point the mouse cursor over 'name' in EL and wait for a second.
> 15. There should be a hover dialog opened with java element links to package 'demo', classes 'String' and 'User', and methods 'getName()' and 'setName()'.
> !hover-xhtmleditor.png|thumbnail!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-15505) exception in jaxrs at startup
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15505?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen resolved JBIDE-15505.
-----------------------------------------
Resolution: Done
[~rrabara] we don't have a reliable way to reproduce this issue. the NPE is fixed in the code so it wont happen again thus resolving as fixed again.
> exception in jaxrs at startup
> -----------------------------
>
> Key: JBIDE-15505
> URL: https://issues.jboss.org/browse/JBIDE-15505
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.1.0.Alpha1
> Reporter: Max Rydahl Andersen
> Assignee: Max Rydahl Andersen
> Fix For: 4.2.0.Alpha1, 4.1.1.Beta1
>
>
> Not sure how I got the error, but I just restarted a workspace after deleting some projects in previous session.
> At startup I got this error:
> java.lang.NullPointerException
> at org.jboss.tools.ws.jaxrs.ui.cnf.UriMappingsContentProvider.dispose(UriMappingsContentProvider.java:116)
> at org.eclipse.ui.internal.navigator.extensions.SafeDelegateTreeContentProvider$1.run(SafeDelegateTreeContentProvider.java:76)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.navigator.extensions.SafeDelegateTreeContentProvider.dispose(SafeDelegateTreeContentProvider.java:74)
> at org.eclipse.ui.internal.navigator.extensions.NavigatorContentExtension$3.run(NavigatorContentExtension.java:210)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.navigator.extensions.NavigatorContentExtension.dispose(NavigatorContentExtension.java:207)
> at org.eclipse.ui.internal.navigator.NavigatorContentService.dispose(NavigatorContentService.java:355)
> at org.eclipse.ui.navigator.CommonViewer.dispose(CommonViewer.java:251)
> at org.eclipse.ui.navigator.CommonViewer.handleDispose(CommonViewer.java:239)
> at org.eclipse.jface.viewers.ContentViewer$2.widgetDisposed(ContentViewer.java:214)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:123)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4166)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1489)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1470)
> at org.eclipse.swt.widgets.Widget.release(Widget.java:1308)
> at org.eclipse.swt.widgets.Control.release(Control.java:2861)
> at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:910)
> at org.eclipse.swt.widgets.Widget.release(Widget.java:1311)
> at org.eclipse.swt.widgets.Control.release(Control.java:2861)
> at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:910)
> at org.eclipse.swt.widgets.Widget.release(Widget.java:1311)
> at org.eclipse.swt.widgets.Control.release(Control.java:2861)
> at org.eclipse.swt.widgets.Widget.dispose(Widget.java:671)
> at org.eclipse.e4.ui.workbench.renderers.swt.SWTPartRenderer.disposeWidget(SWTPartRenderer.java:152)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.disposeWidget(ContributedPartRenderer.java:273)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeRemoveGui(PartRenderingEngine.java:899)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$3(PartRenderingEngine.java:828)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$8.run(PartRenderingEngine.java:823)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.removeGui(PartRenderingEngine.java:808)
> at org.eclipse.e4.ui.workbench.renderers.swt.ElementReferenceRenderer.disposeWidget(ElementReferenceRenderer.java:109)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeRemoveGui(PartRenderingEngine.java:899)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$3(PartRenderingEngine.java:828)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$8.run(PartRenderingEngine.java:823)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.removeGui(PartRenderingEngine.java:808)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeRemoveGui(PartRenderingEngine.java:853)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$3(PartRenderingEngine.java:828)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$8.run(PartRenderingEngine.java:823)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.removeGui(PartRenderingEngine.java:808)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeRemoveGui(PartRenderingEngine.java:853)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$3(PartRenderingEngine.java:828)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$8.run(PartRenderingEngine.java:823)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.removeGui(PartRenderingEngine.java:808)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeRemoveGui(PartRenderingEngine.java:860)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$3(PartRenderingEngine.java:828)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$8.run(PartRenderingEngine.java:823)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.removeGui(PartRenderingEngine.java:808)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeRemoveGui(PartRenderingEngine.java:853)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$3(PartRenderingEngine.java:828)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$8.run(PartRenderingEngine.java:823)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.removeGui(PartRenderingEngine.java:808)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeRemoveGui(PartRenderingEngine.java:860)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$3(PartRenderingEngine.java:828)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$8.run(PartRenderingEngine.java:823)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.removeGui(PartRenderingEngine.java:808)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeRemoveGui(PartRenderingEngine.java:860)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$3(PartRenderingEngine.java:828)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$8.run(PartRenderingEngine.java:823)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.removeGui(PartRenderingEngine.java:808)
> at org.eclipse.ui.internal.WorkbenchWindow.hardClose(WorkbenchWindow.java:1598)
> at org.eclipse.ui.internal.WorkbenchWindow.busyClose(WorkbenchWindow.java:1231)
> at org.eclipse.ui.internal.WorkbenchWindow.access$14(WorkbenchWindow.java:1198)
> at org.eclipse.ui.internal.WorkbenchWindow$10.run(WorkbenchWindow.java:1261)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.WorkbenchWindow.close(WorkbenchWindow.java:1259)
> at org.eclipse.ui.internal.Workbench$14.run(Workbench.java:1096)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.Workbench.busyClose(Workbench.java:1079)
> at org.eclipse.ui.internal.Workbench.access$19(Workbench.java:1024)
> at org.eclipse.ui.internal.Workbench$19.run(Workbench.java:1327)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.Workbench.close(Workbench.java:1325)
> at org.eclipse.ui.internal.Workbench.restart(Workbench.java:2480)
> at org.eclipse.ui.internal.handlers.RestartWorkbenchHandler.execute(RestartWorkbenchHandler.java:31)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> at sun.reflect.GeneratedMethodAccessor86.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:167)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:850)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:743)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:727)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:662)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4166)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1489)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1474)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4012)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3651)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBDS-2844) Management API Server Adapter
by Burr Sutter (JIRA)
Burr Sutter created JBDS-2844:
---------------------------------
Summary: Management API Server Adapter
Key: JBDS-2844
URL: https://issues.jboss.org/browse/JBDS-2844
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: server
Reporter: Burr Sutter
Assignee: Max Rydahl Andersen
Related to JBIDE-14073
The current EAP/JBossAS/Wildfly Server Adapter often interacts with the underlying file-system of the app server. Users have asked that the following scenarios be supported:
- Remote Server Start/Stop
- Remote Server Deployment/Undeployment
- Remote Server single file update (e.g. html, js, jsp, xhtml, etc) with hot-deployment (to be worked out with the Wildfly team)
- Remote Server Log Viewing
and while the focus here in on remote servers, it should work just as well with localhost-based servers.
Also related, not having the actual server code locally installed, being able to work wholly with a remote server (comes up in the Data Virt/Teiid world).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBDS-2843) AngularJS Usability
by Burr Sutter (JIRA)
Burr Sutter created JBDS-2843:
---------------------------------
Summary: AngularJS Usability
Key: JBDS-2843
URL: https://issues.jboss.org/browse/JBDS-2843
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Burr Sutter
Related to JBIDE-14597
Phase 1) Insure that no extraneous error messages are displayed for otherwise "valid" AngularJS constructs in the HTML
Phase 2) Forge scaffolding of AngularJS apps should produce no warnings/error messages in the IDE from the generated code
Phase 3) Code Assist (cntrl-space) in .html
Phase 4) Code Assist (cntrl-space) in .js
Phase 5) Widget Palette (like our jQuery Mobile palete)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBDS-2843) AngularJS Usability
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-2843?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-2843:
-----------------------------
CDW pm_ack: ?
CDW release: ?
> AngularJS Usability
> -------------------
>
> Key: JBDS-2843
> URL: https://issues.jboss.org/browse/JBDS-2843
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Burr Sutter
>
> Related to JBIDE-14597
> Phase 1) Insure that no extraneous error messages are displayed for otherwise "valid" AngularJS constructs in the HTML
> Phase 2) Forge scaffolding of AngularJS apps should produce no warnings/error messages in the IDE from the generated code
> Phase 3) Code Assist (cntrl-space) in .html
> Phase 4) Code Assist (cntrl-space) in .js
> Phase 5) Widget Palette (like our jQuery Mobile palete)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months