[JBoss JIRA] (JBIDE-18409) OpenShift Adapter: Add choice to show application in external device/browser
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18409?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-18409:
------------------------------------------
[~jpviragine] can you please explain what is "External Device"? I'm not aware of such an option in our server adapters, but I most likely miss that somehow.
> OpenShift Adapter: Add choice to show application in external device/browser
> ----------------------------------------------------------------------------
>
> Key: JBIDE-18409
> URL: https://issues.jboss.org/browse/JBIDE-18409
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.2.0.CR1
> Reporter: Joao Viragine
> Assignee: Max Rydahl Andersen
> Labels: server_adapter
> Fix For: 4.3.x
>
>
> It would be nice if we had the option: Show In/Web Browser on External Device for OpenShift Server as we have for JBoss EAP Server. (Servers/(Application)/Show In/Add Web Browser on External Device)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years
[JBoss JIRA] (JBIDE-16225) Let the user select the version of the arquillian container adapter
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16225?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-16225:
----------------------------------------
Fix Version/s: 4.2.1.Final
4.3.0.Alpha1
(was: 4.2.0.CR2)
> 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.1.Final, 4.3.0.Alpha1
>
>
> 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.3.1#6329)
11 years
[JBoss JIRA] (JBIDE-16695) Add marker/quick fix if test contains non static deployment method
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16695?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-16695:
----------------------------------------
Fix Version/s: 4.3.0.Alpha1
(was: 4.2.0.CR2)
> Add marker/quick fix if test contains non static deployment method
> ------------------------------------------------------------------
>
> Key: JBIDE-16695
> URL: https://issues.jboss.org/browse/JBIDE-16695
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Affects Versions: 4.1.1.Final
> Reporter: Rich DiCroce
> Assignee: Snjezana Peco
> Fix For: 4.3.0.Alpha1
>
>
> In an Arquillian test class, any method marked @Deployment that returns something other than Archive is not being detected. For example, this method is not detected by the tooling, despite the fact that WebArchive extends Archive:
> {code}
> @Deployment
> public static WebArchive createDeployment() {
> ...code to create deployment here...
> }
> {code}
> As a result, the deployment validation features do not work, and the Arquillian Cruiser view does not allow the archive to be browsed. Curiously, however, there is no warning about a missing @Deployment method.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years
[JBoss JIRA] (JBIDE-17696) Enabling Maven Dependency Management job waits forever
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17696?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-17696:
----------------------------------------
Fix Version/s: 4.2.1.Final
4.3.0.Alpha1
(was: 4.2.0.CR2)
> Enabling Maven Dependency Management job waits forever
> ------------------------------------------------------
>
> Key: JBIDE-17696
> URL: https://issues.jboss.org/browse/JBIDE-17696
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.2.0.Beta2
> Environment: OpenJDK 1.7, 64b
> Ubuntu 12.04, 64b
> Reporter: Rastislav Wagner
> Assignee: Denis Golovin
> Fix For: 4.2.1.Final, 4.3.0.Alpha1
>
> Attachments: .options, jstack1.out, jstack2.out, jstack_mvn.out, mvn.png, wait1.png, wait2.png
>
>
> I dont have exact steps to reproduce because this usually occurs after longer work. I'm testing various configurators (CDI/Seam/JAXRS..) using this scenario:
> 1. Create Dynamic Web Project
> 2. Convert to maven project (using Configure -> Convert to maven..)
> 3. Add some dependency
> 4. check if proper facet was enabled
> 5. delete project and repeat
> After trying this 10-15 times (sometimes more, sometimes less), during step 2 "Enabling Maven Dependency Management" job is waiting and never ends - see screenshot - there's always "Setting classpath containers".
> JVM thread dump attached.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years
[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.1.Final
4.3.0.Alpha1
(was: 4.2.0.CR2)
> 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.1.Final, 4.3.0.Alpha1
>
>
> 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
[JBoss JIRA] (JBIDE-18383) forge command rely on english description label to lookup commands - fragile!
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18383?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-18383:
----------------------------------------
Assignee: Koen Aers (was: George Gastaldi)
> forge command rely on english description label to lookup commands - fragile!
> -----------------------------------------------------------------------------
>
> Key: JBIDE-18383
> URL: https://issues.jboss.org/browse/JBIDE-18383
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Reporter: Max Rydahl Andersen
> Assignee: Koen Aers
> Priority: Critical
> Fix For: 4.2.0.CR2
>
>
> it seems this is the way forge commands are looked up:
> org.jboss.tools.forge.ui.runForgeCommand(org.jboss.tools.forge.ui.runForgeCommand.commandName=REST: Generate Endpoints From Entities)"
> meaning if description changes the cheatsheet breaks.
> should this not us a unique id or at least the cli command name so we have *one* API to obey to ?
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years
[JBoss JIRA] (JBIDE-17940) JPA Details view doesn't work for entities in autodiscovery mode when they are not explicitely listed
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17940?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-17940:
----------------------------------------
Fix Version/s: 4.2.1.Final
(was: 4.2.0.CR2)
> JPA Details view doesn't work for entities in autodiscovery mode when they are not explicitely listed
> -----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-17940
> URL: https://issues.jboss.org/browse/JBIDE-17940
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate, upstream
> Affects Versions: 4.2.0.Beta3
> Environment: JBDS 8.0.0.Beta3, GNU/Linux 64
> Reporter: Jiri Peterka
> Assignee: Koen Aers
> Priority: Critical
> Fix For: 4.2.1.Final
>
>
> JPA Details view is not working for entities in autodiscovery mode. It only works when entities are added into Managed Classes entities list. It's expected when JPA project is configured with "Discover annotated classes automatically" it should without manual listing entities in persistence.xml.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years