July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16645) Seam Portlet deployed on EPP 5.2 is in error

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16645?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-16645: ---------------------------------- Fix Version/s: 4.2.0.CR1 (was: 4.2.0.Beta3) > Seam Portlet deployed on EPP 5.2 is in error > -------------------------------------------- > > Key: JBIDE-16645 > URL: https://issues.jboss.org/browse/JBIDE-16645 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: portal-gatein > Affects Versions: 4.2.0.Alpha2 > Environment: EPP-5.2.2.GA with Seam 2.2.5.EAP5 > Reporter: Radoslav Rábara > Assignee: Radoslav Rábara > Fix For: 4.2.0.CR1 > > Attachments: epp52-server-log > > > Seam portal project deployed on EPP 5.2 is in error. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17799) Compile error in arquillian

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17799?page=com.atlassian.jira.plugi... ] Denis Golovin closed JBIDE-17799. --------------------------------- verified in local build > Compile error in arquillian > --------------------------- > > Key: JBIDE-17799 > URL: https://issues.jboss.org/browse/JBIDE-17799 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, testing-tools > Affects Versions: 4.2.0.Beta3 > Reporter: Snjezana Peco > Assignee: Denis Golovin > Priority: Blocker > Fix For: 4.2.0.Beta3 > > > The project examples API has been changed by JBIDE-17713 (https://github.com/jbosstools/jbosstools-central/commit/4e59ddf3e41474aca...) > Since it is a public API (org.jboss.tools.project.examples.model.ProjectExample), it shouldn't be changed. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17728) HTML5 Palette: Ionic components

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17728?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-17728: ---------------------------------- Attachment: ListWizBan.png List.png > HTML5 Palette: Ionic components > ------------------------------- > > Key: JBIDE-17728 > URL: https://issues.jboss.org/browse/JBIDE-17728 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Labels: new_and_noteworthy > Fix For: 4.2.0.CR1 > > Attachments: Content.png, ContentWizBan.png, List.png, ListWizBan.png, Scroll.png, ScrollWizBan.png > > > http://ionicframework.com/docs/ -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17625) Checking an installed/up-to-date feature enables update anyway

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17625?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-17625: ---------------------------------------- I updated this PR and it seems to fix the issue you noticed. > Checking an installed/up-to-date feature enables update anyway > -------------------------------------------------------------- > > Key: JBIDE-17625 > URL: https://issues.jboss.org/browse/JBIDE-17625 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.0.Beta2 > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.2.0.Beta3 > > > When selecting a connector that is already installed and up to date, this one shouldn't increment the number of item to install or update. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17596) Cannot run test on WELD EE 1.1

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17596?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-17596: ---------------------------------- Fix Version/s: 4.2.0.CR1 (was: 4.2.0.Beta3) > 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.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16225) Let the user select the version of the arquillian container adapter

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16225?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-16225: ---------------------------------- Fix Version/s: 4.2.0.CR1 (was: 4.2.0.Beta3) > Let the user select the version of the arquillian container adapter > --------------------------------------------------------------------- > > Key: JBIDE-16225 > URL: https://issues.jboss.org/browse/JBIDE-16225 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: testing-tools > Affects Versions: 4.1.1.CR1 > Reporter: Xavier Coulon > Assignee: Snjezana Peco > Fix For: 4.2.0.CR1 > > > The Arquillian wizard provides users with a list of containers (eg: JBOSS_AS_REMOTE_7.X) that can be used but it misses the version selection (eg: 7.1.1.Final, 7.2.0.Final, etc.). > I think it's important to let the user choose the version of the 'driver' she needs to use, because it needs to match against the actual version of the container. > for example, using org.jboss.as:jboss-as-arquillian-container-remote:7.2.0.Final against JBoss AS 7.1.1 will not work. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16990) arquillian editor has no info/docs explaining what the various elements/pages are doing - just whitespace

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16990?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-16990: ---------------------------------- Fix Version/s: 4.2.0.CR1 (was: 4.2.0.Beta3) > arquillian editor has no info/docs explaining what the various elements/pages are doing - just whitespace > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-16990 > URL: https://issues.jboss.org/browse/JBIDE-16990 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing-tools > Reporter: Max Rydahl Andersen > Assignee: Snjezana Peco > Fix For: 4.2.0.CR1 > > > arquillian editor looks great but its not providing much value besides an empty pure source editor at this moment. > We should get some docs into the various elements/hints explaining what the elements are. > for example - "qualifier" for tests. what does that field mean ? is there a naming convention ? could it be defaulted ? > There is a button to click to get a list of names but no explanation what they mean besides guessing -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16992) filters in arquillian editor is case sensitive and start of string

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16992?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-16992: ---------------------------------- Fix Version/s: 4.2.0.CR1 (was: 4.2.0.Beta3) > filters in arquillian editor is case sensitive and start of string > ------------------------------------------------------------------ > > Key: JBIDE-16992 > URL: https://issues.jboss.org/browse/JBIDE-16992 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing-tools, upstream > Reporter: Max Rydahl Andersen > Assignee: Snjezana Peco > Fix For: 4.2.0.CR1 > > > EXECUTE: open qualifier list and type "remote" > ASSERT: qualifiers containing the string remote should show up > currently it does not - I have to type WILDFLY_REMOTE. > it should be a case insensitive in string search instead of case sensitive beginning of string search. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16948) Project facet group group.birt.chart.runtime has not been defined.

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16948?page=com.atlassian.jira.plugi... ] Snjezana Peco reassigned JBIDE-16948: ------------------------------------- Assignee: Snjezana Peco > Project facet group group.birt.chart.runtime has not been defined. > ------------------------------------------------------------------ > > Key: JBIDE-16948 > URL: https://issues.jboss.org/browse/JBIDE-16948 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: birt > Affects Versions: 4.2.0.Beta1 > Reporter: Pavol Srna > Assignee: Snjezana Peco > Fix For: 4.2.0.Beta3 > > > Project facet group group.birt.chart.runtime has not been defined. It is used in plugin org.eclipse.birt.integration.wtp.ui. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17092) arquillian.xml file creation is confusing

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17092?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-17092: ---------------------------------- Fix Version/s: 4.2.0.CR1 (was: 4.2.0.Beta3) > arquillian.xml file creation is confusing > ----------------------------------------- > > Key: JBIDE-17092 > URL: https://issues.jboss.org/browse/JBIDE-17092 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: testing-tools > Affects Versions: 4.2.0.Beta1 > Reporter: Lucia Jelinkova > Assignee: Snjezana Peco > Fix For: 4.2.0.CR1 > > > The creation of arquillian.xml file is a little bit confusing since it is not generated when the Arquiilian support is added to the project. When is it actually generated? > The other think is that you need to refresh the project manually in Eclipse to see the generated file - could you do it automatically? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2014