[JBoss JIRA] (JBIDE-17597) Changing package presentation on Arquillia cruiser view does not work
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17597?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-17597:
---------------------------------------
Package presentation works only in the Java part of the view. It doesn't work for a deployment archive. A deployment archive isn't a project, but a simple zip file and is always hierarchically displayed.
You have to create more Arquillian tests in different packages in order to see different presentations. Behaviour is the same as in the Package Explorer.
> Changing package presentation on Arquillia cruiser view does not work
> ----------------------------------------------------------------------
>
> Key: JBIDE-17597
> URL: https://issues.jboss.org/browse/JBIDE-17597
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Affects Versions: 4.2.0.Beta2
> Reporter: Lucia Jelinkova
> Assignee: Snjezana Peco
> Fix For: 4.2.0.CR1
>
> Attachments: arquillia.ogv
>
>
> Changing the Package presentation option in Arquillia cruiser does not change the way the packages are displayed
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18179) Forge Console is limited to 80 chars and throws exception if line surpasses the limit
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18179?page=com.atlassian.jira.plugi... ]
George Gastaldi reassigned JBIDE-18179:
---------------------------------------
Assignee: George Gastaldi
> Forge Console is limited to 80 chars and throws exception if line surpasses the limit
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-18179
> URL: https://issues.jboss.org/browse/JBIDE-18179
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Reporter: George Gastaldi
> Assignee: George Gastaldi
> Priority: Blocker
> Fix For: 4.2.0.CR1
>
>
> {code}
> org.eclipse.jface.text.BadLocationException
> at org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1179)
> at org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1210)
> at org.jboss.tools.aesh.ui.internal.document.DocumentImpl$3.run(DocumentImpl.java:103)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3806)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3444)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18252) "Mark as Deployable" does not work in Package Explorer and is not visible in Editor context menu
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18252?page=com.atlassian.jira.plugi... ]
Daniel Azarov edited comment on JBIDE-18252 at 9/3/14 4:41 PM:
---------------------------------------------------------------
Max, you were right, these actions did work on editor context menu.
[~maxandersen], [~rob.stryker] please review my PRs
was (Author: dazarov):
Max, you were right these actions did work on editor context menu.
[~maxandersen], [~rob.stryker] please review my PRs
> "Mark as Deployable" does not work in Package Explorer and is not visible in Editor context menu
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18252
> URL: https://issues.jboss.org/browse/JBIDE-18252
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.CR1
> Reporter: Daniel Azarov
> Fix For: 4.2.0.CR1, 4.3.0.Alpha1
>
> Attachments: CannotPublishToServer.png
>
>
> There is a regression from JBIDE-15678 and JBIDE-18133
> Actions "Mark/Unmark as Deployable" do not working in Package Explorer with follow error:
> !CannotPublishToServer.png!
> Also these actions are not visible in editor context menu
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18252) "Mark as Deployable" does not work in Package Explorer and is not visible in Editor context menu
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18252?page=com.atlassian.jira.plugi... ]
Daniel Azarov edited comment on JBIDE-18252 at 9/3/14 4:41 PM:
---------------------------------------------------------------
Max, you were right these actions did work on editor context menu.
[~maxandersen], [~rob.stryker] please review my PRs
was (Author: dazarov):
[~maxandersen], [~rob.stryker] please review my PRs
> "Mark as Deployable" does not work in Package Explorer and is not visible in Editor context menu
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18252
> URL: https://issues.jboss.org/browse/JBIDE-18252
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.CR1
> Reporter: Daniel Azarov
> Fix For: 4.2.0.CR1, 4.3.0.Alpha1
>
> Attachments: CannotPublishToServer.png
>
>
> There is a regression from JBIDE-15678 and JBIDE-18133
> Actions "Mark/Unmark as Deployable" do not working in Package Explorer with follow error:
> !CannotPublishToServer.png!
> Also these actions are not visible in editor context menu
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months