[JBoss JIRA] (JBIDE-16298) Layout for BrowserSim/CordovaSim Preferences should look similar to JRE tab in Java Application Run Configuration
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16298?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov updated JBIDE-16298:
-------------------------------------------
Fix Version/s: 4.3.x
(was: 4.2.0.CR1)
> Layout for BrowserSim/CordovaSim Preferences should look similar to JRE tab in Java Application Run Configuration
> -----------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16298
> URL: https://issues.jboss.org/browse/JBIDE-16298
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.1.1.Final
> Reporter: Denis Golovin
> Assignee: Konstantin Marmalyukov
> Priority: Minor
> Fix For: 4.3.x
>
> Attachments: Selection_023.png, Selection_024.png
>
>
> BrowserSim/CordovaSim Preferences should look very close to Java Application Launcher JRE configuration in Run Configuration Dialog:
> !Selection_024.png!
> Now it looks like:
> !Selection_023.png!
> What should be changed:
> 1. Group label should be "JRE to run BrowserSim/CordovaSim"
> 2. First radio button should use lable "Workspace Default JRE (jre-name-from-installed)
> 3. Second radio should be labeled as "Alternate JRE:"
> 4. Combo box with available JRE's should be placed right after "Alternate JRE:' label
> 5. Description text "See 'Installed JREs' for JRE definitions" should be replaced with ''General settings for BrowserSim/CordovaSim."
> 6. Add 'Installed JREs...' after combo box
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-16575) Tests for BrowserSim
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16575?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov updated JBIDE-16575:
-------------------------------------------
Fix Version/s: 4.3.0.Alpha1
(was: 4.2.0.CR1)
> Tests for BrowserSim
> --------------------
>
> Key: JBIDE-16575
> URL: https://issues.jboss.org/browse/JBIDE-16575
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: browsersim
> Reporter: Alexey Kazakov
> Assignee: Konstantin Marmalyukov
> Priority: Critical
> Fix For: 4.3.0.Alpha1
>
>
> We should create JUnit tests which will run BrowserSim on both Java platforms: with JavaFX and w/o it. Those tests should check if webkit BS can be run on both platforms and if JavaFX BS can be run on the platform with JavaFX.
> It's probably imposible to have such tests without special Jenkins settings.
> So [~nickboldt]'s help is needed.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-17834) VPE toolbar is not shown in Eclipse toolbar
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17834?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov updated JBIDE-17834:
-------------------------------------------
Fix Version/s: 4.3.0.Alpha1
(was: 4.2.0.CR1)
> VPE toolbar is not shown in Eclipse toolbar
> -------------------------------------------
>
> Key: JBIDE-17834
> URL: https://issues.jboss.org/browse/JBIDE-17834
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.2.0.Beta3
> Environment: Linux KDE, Java Oracle 1.8
> JBDS 8.0.0.Beta3-v20140706-0939-B172
> Reporter: Vlado Pakan
> Assignee: Konstantin Marmalyukov
> Fix For: 4.3.0.Alpha1
>
>
> 1. Open some HTML page in VPE
> ASSERT: VPE toolbar is displayed along VPE
> 2. Open Window > Preferences > JBoss Tools > Web > Editors > Visual Page Editor
> 3. Uncheck check box Show Ttoolabr within the editor ... and click OK
> ASSERT: VPE toolbar is not displayed along VPE
> ERROR: VPE toolbar is not displayed within Eclipse toolbar
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-17253) Server download wizard: T&Cs failed to be accepted
by David Hladky (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17253?page=com.atlassian.jira.plugi... ]
David Hladky commented on JBIDE-17253:
--------------------------------------
A correction for gzip compression between our server and Akamai is in place (we ignore the header on our server). Can you, please, try again and let us know the exact time of the attempt, so we can find something in logs? Please, do not forget to mention the time zone.
> Server download wizard: T&Cs failed to be accepted
> --------------------------------------------------
>
> Key: JBIDE-17253
> URL: https://issues.jboss.org/browse/JBIDE-17253
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta1
> Reporter: Michelle Murray
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.2.0.CR1
>
> Attachments: Server_downloadT&C.png
>
>
> 1. In Download Runtimes wizard, on JBoss.org Terms and Conditions page.
> 2. Select 'Australia'.
> 3. Click 'Accept Now'.
> >> Error message= Unable to accept terms and conditions: Server returned HTTP response code: 400 for URL: https://www.jboss.org/download-manager/rest/tc-accept
> >> Screenshot attached
> Unable to proceed any further with download wizard.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-17596) Cannot run test on WELD EE 1.1
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17596?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-17596:
----------------------------------------
Fix Version/s: 4.2.0.CR1
(was: 4.2.0.Final)
> Cannot run test on WELD EE 1.1
> ------------------------------
>
> Key: JBIDE-17596
> URL: https://issues.jboss.org/browse/JBIDE-17596
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools, upstream
> Affects Versions: 4.2.0.Beta2
> Reporter: Lucia Jelinkova
> Assignee: Snjezana Peco
> Fix For: 4.2.0.CR1
>
>
> When I try to run simple test with WELD 1.1 maven profile the test fails with the following exception:
> {code}
> java.lang.NoClassDefFoundError: javax/ejb/Stateless
> at org.jboss.arquillian.container.weld.ee.embedded_1_1.mock.Ejbs.findEjbs(Ejbs.java:38)
> at org.jboss.arquillian.container.weld.ee.embedded_1_1.mock.Ejbs.createEjbDescriptors(Ejbs.java:25)
> at org.jboss.arquillian.container.weld.ee.embedded_1_1.mock.BeanDeploymentArchiveImpl.<init>(BeanDeploymentArchiveImpl.java:81)
> at org.jboss.arquillian.container.weld.ee.embedded_1_1.mock.TestContainer.<init>(TestContainer.java:228)
> at org.jboss.arquillian.container.weld.ee.embedded_1_1.WeldEEMockContainer.deploy(WeldEEMockContainer.java:99)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:161)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:128)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deploy(ContainerDeployController.java:127)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createDeploymentContext(ContainerDeploymentContextHandler.java:78)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.container.impl.client.container.DeploymentExceptionHandler.verifyExpectedExceptionDuringDeploy(DeploymentExceptionHandler.java:50)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$1.perform(ContainerDeployController.java:95)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$1.perform(ContainerDeployController.java:80)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachDeployment(ContainerDeployController.java:263)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachManagedDeployment(ContainerDeployController.java:239)
> at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deployManaged(ContainerDeployController.java:79)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
> at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:101)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:84)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:65)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeClass(EventTestRunnerAdaptor.java:80)
> at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:182)
> at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314)
> at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46)
> at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
> at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147)
> at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
> at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)
> Caused by: java.lang.ClassNotFoundException: javax.ejb.Stateless
> at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
> ... 92 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18133) mark as deployable no longer visible in project explorer, common navigator etc.
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18133?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-18133:
---------------------------------------------
having to add it to individual view types is a bandaid solution IMO, there are more ways iresources can be shown than in these specific views.
> mark as deployable no longer visible in project explorer, common navigator etc.
> -------------------------------------------------------------------------------
>
> Key: JBIDE-18133
> URL: https://issues.jboss.org/browse/JBIDE-18133
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.CR1
> Reporter: Max Rydahl Andersen
> Assignee: Daniel Azarov
> Priority: Critical
> Fix For: 4.2.0.CR1
>
>
> JBIDE-15678 limis mark as deployable to only be in Package Explorer.
> That is bad since Project Explorer that are the main view in JBoss / JavaEE perspectives will then no longer have this.
> This also affects *any* views that shows the context menu for resources.
> On these I would argue mark as deployable should be shown.
> It is not only for package explorer.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18133) mark as deployable no longer visible in project explorer, common navigator etc.
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18133?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-18133:
---------------------------------------------
[~dazarov] but how about "Validate" ? it also appeared twice.
And why can we not have mark as deployable show up with the other iresource relevant entries in he context menu now that you moved it to another type of handler ?
> mark as deployable no longer visible in project explorer, common navigator etc.
> -------------------------------------------------------------------------------
>
> Key: JBIDE-18133
> URL: https://issues.jboss.org/browse/JBIDE-18133
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.CR1
> Reporter: Max Rydahl Andersen
> Assignee: Daniel Azarov
> Priority: Critical
> Fix For: 4.2.0.CR1
>
>
> JBIDE-15678 limis mark as deployable to only be in Package Explorer.
> That is bad since Project Explorer that are the main view in JBoss / JavaEE perspectives will then no longer have this.
> This also affects *any* views that shows the context menu for resources.
> On these I would argue mark as deployable should be shown.
> It is not only for package explorer.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months