May 2015 - jbosstools-issues - Jboss List Archives

[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.3.0.Beta2 (was: 4.3.0.Beta1) > 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: arquillian > Affects Versions: 4.1.1.CR1 > Reporter: Xavier Coulon > Assignee: Snjezana Peco > Fix For: 4.3.0.Beta2 > > > 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.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18832) Cannot run Arquillian test on WELD SE 1.1

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18832?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-18832: ---------------------------------- Fix Version/s: 4.3.0.Beta2 (was: 4.3.0.Beta1) > Cannot run Arquillian test on WELD SE 1.1 > ----------------------------------------- > > Key: JBIDE-18832 > URL: https://issues.jboss.org/browse/JBIDE-18832 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: arquillian > Affects Versions: 4.2.1.CR1 > Reporter: Lucia Jelinkova > Assignee: Snjezana Peco > Fix For: 4.3.0.Beta2 > > > When I try to run simple Arquillian test on WELD SE 1.1, it crashes with the following exception: > {code} > java.lang.NoSuchMethodError: org.jboss.weld.context.SingletonContext.invalidate()V > at org.jboss.weld.bootstrap.WeldRuntime.shutdown(WeldRuntime.java:55) > at org.jboss.weld.bootstrap.WeldBootstrap.shutdown(WeldBootstrap.java:113) > at org.jboss.arquillian.container.weld.se.embedded_1_1.WeldSEContainer.undeploy(WeldSEContainer.java:156) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:205) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$4.call(ContainerDeployController.java:185) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.undeploy(ContainerDeployController.java:184) > 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.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$2.perform(ContainerDeployController.java:119) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$2.perform(ContainerDeployController.java:110) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachDeployment(ContainerDeployController.java:263) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachDeployedDeployment(ContainerDeployController.java:249) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.undeployManaged(ContainerDeployController.java:109) > 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:108) > 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.afterClass(EventTestRunnerAdaptor.java:87) > at org.jboss.arquillian.junit.Arquillian$3$1.evaluate(Arquillian.java:204) > 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) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19349) Fix ShrinkWrap Archive file location validation issues

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19349?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-19349: ---------------------------------- Fix Version/s: 4.3.0.Beta2 (was: 4.3.0.Beta1) > Fix ShrinkWrap Archive file location validation issues > ------------------------------------------------------ > > Key: JBIDE-19349 > URL: https://issues.jboss.org/browse/JBIDE-19349 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: arquillian > Affects Versions: 4.3.0.Alpha1 > Reporter: Lucia Jelinkova > Assignee: Snjezana Peco > Fix For: 4.3.0.Beta2 > > > In JBIDE-14782, the validation was solved only partially. These issues still remain: > - EAR - no validation for application.xml > - WAR > -- validation for beans.xml and web.xml going to WEB-INF > --- addAsManifestResource - OK > --- addAsWebResource - NOK > -- validation for persistence.xml and ejb-jar.xml > --- addAsWebInfResource - OK > --- addAsWebResource - NOK -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19707) Remove direct use of the core Hibernate classes and/or Hibernate Proxy classes

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19707?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-19707: ---------------------------------- Fix Version/s: 4.3.x (was: 4.3.0.Beta1) > Remove direct use of the core Hibernate classes and/or Hibernate Proxy classes > ------------------------------------------------------------------------------ > > Key: JBIDE-19707 > URL: https://issues.jboss.org/browse/JBIDE-19707 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: birt, hibernate, seam2 > Affects Versions: 4.3.0.Alpha2 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.3.x > > > These uses should ideally be replaced by uses of the Hibernate SPI interfaces. It may be needed to create new SPI interfaces. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19864) Arquillian New and Noteworthy for 4.3.0.Beta1

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19864?page=com.atlassian.jira.plugi... ] Snjezana Peco resolved JBIDE-19864. ----------------------------------- Resolution: Rejected No changes for N&N. > Arquillian New and Noteworthy for 4.3.0.Beta1 > --------------------------------------------- > > Key: JBIDE-19864 > URL: https://issues.jboss.org/browse/JBIDE-19864 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: arquillian > Reporter: Max Rydahl Andersen > Priority: Critical > Fix For: 4.3.0.Beta1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Arquillian is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Arquillian by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19864) Arquillian New and Noteworthy for 4.3.0.Beta1

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19864?page=com.atlassian.jira.plugi... ] Snjezana Peco closed JBIDE-19864. --------------------------------- Assignee: Snjezana Peco > Arquillian New and Noteworthy for 4.3.0.Beta1 > --------------------------------------------- > > Key: JBIDE-19864 > URL: https://issues.jboss.org/browse/JBIDE-19864 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: arquillian > Reporter: Max Rydahl Andersen > Assignee: Snjezana Peco > Priority: Critical > Fix For: 4.3.0.Beta1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Arquillian is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Arquillian by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19814) sources zip should include local sources too (jbosstools-build-sites or jbdevstudio-product)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19814?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19814: ------------------------------------ PR pushed. New PR to make builds fail if no values found for projectName or projectSHA, and to use regular java.util.zip.ZipFile instead of zip4j -- hopefully this will work better w/ memory allocation / closing / flushing of files so that we won't OOM in Jenkins: https://github.com/jbosstools/jbosstools-maven-plugins/pull/45 > sources zip should include local sources too (jbosstools-build-sites or jbdevstudio-product) > -------------------------------------------------------------------------------------------- > > Key: JBIDE-19814 > URL: https://issues.jboss.org/browse/JBIDE-19814 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > > If we change the way the jbosstools-src.zip is produced, such that in addition to upstream projects it ALSO includes the contents of jbosstools-build-sites too, then we can reuse that mojo for the jbdevstudio-product src.zip too, as it will ALSO include the 17 upstream JBT zips (from Github) and also the local JBDS sources. > This would mean a large chunk of ant code in jbdevstudio-product/sources/build.xml (if not all of it) could go away. Hooray for 1 solution spanning both projects and product! :D > Max also suggested that we use a clean copy of the sources just in case the build process makes them dirty: > {code} > git clone --depth=1 . clean-sources-dir && rm -rf clean-sources-dir/.git{code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19500) warn/inform users running on non-compatilbe JVMs they are loosing out on features

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19500?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19500: --------------------------------------------- how about org.jboss.tools.foundation.checkup (to add things like this and in future other checkups of your installation) > warn/inform users running on non-compatilbe JVMs they are loosing out on features > --------------------------------------------------------------------------------- > > Key: JBIDE-19500 > URL: https://issues.jboss.org/browse/JBIDE-19500 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core > Reporter: Max Rydahl Andersen > Assignee: Daniel Azarov > Fix For: 4.3.0.Beta1 > > Attachments: JVMProblemDetector.png, JVMProblemDetector2.png > > > while reading https://developer.jboss.org/message/922318?et=watches.email.thread#922318 I got the idea that we could have a startup plugin that detects if the error log has lines matching: > {code} > org.osgi.framework.BundleException: Could not resolve module: org.fusesource.ide.preferences [1447] > Unresolved requirement: Require-Capability: osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=1.7))" > {code} > and there by tell them that they need to run JavaSE 1.7 to get this to work. > This dialog should show up and have "don't disturb me again" for the specific bundle/feature that is filtered out. > This is to warn those users that run ecipse with default javavm that still is java 6 on many installs. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19875) server New and Noteworthy for 4.3.0.Beta1

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19875?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19875: ------------------------------------- Only have 1 new feature... written about in blog https://github.com/jbosstools/jbosstools-website/pull/397 Waiting to hear on that blog post to see how I cover it in n&n. n&n would ideally link to the blog post if blog post is published. > server New and Noteworthy for 4.3.0.Beta1 > ----------------------------------------- > > Key: JBIDE-19875 > URL: https://issues.jboss.org/browse/JBIDE-19875 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: archives, jmx, server > Reporter: Max Rydahl Andersen > Priority: Critical > Fix For: 4.3.0.Beta1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If server is not listed here check if there are issues that should be added and add them. > Document the ones relevant for server by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19500) warn/inform users running on non-compatilbe JVMs they are loosing out on features

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19500?page=com.atlassian.jira.plugi... ] Daniel Azarov commented on JBIDE-19500: --------------------------------------- [~maxandersen], how about name for new plug-in? org.jboss.tools.foundation.environment org.jboss.tools.foundation.jvm.analyzer org.jboss.tools.foundation.jvm.checker org.jboss.tools.foundation.environment.analyzer org.jboss.tools.foundation.environment.checker > warn/inform users running on non-compatilbe JVMs they are loosing out on features > --------------------------------------------------------------------------------- > > Key: JBIDE-19500 > URL: https://issues.jboss.org/browse/JBIDE-19500 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core > Reporter: Max Rydahl Andersen > Assignee: Daniel Azarov > Fix For: 4.3.0.Beta1 > > Attachments: JVMProblemDetector.png, JVMProblemDetector2.png > > > while reading https://developer.jboss.org/message/922318?et=watches.email.thread#922318 I got the idea that we could have a startup plugin that detects if the error log has lines matching: > {code} > org.osgi.framework.BundleException: Could not resolve module: org.fusesource.ide.preferences [1447] > Unresolved requirement: Require-Capability: osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=1.7))" > {code} > and there by tell them that they need to run JavaSE 1.7 to get this to work. > This dialog should show up and have "don't disturb me again" for the specific bundle/feature that is filtered out. > This is to warn those users that run ecipse with default javavm that still is java 6 on many installs. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 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 May 2015