[JBoss JIRA] (JBIDE-19194) FeedHenry requires minimal-json, but it was removed from TP
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19194?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19194:
------------------------------------
{quote}
(2015-02-10 15:16:33) maxandersen: nickboldt: so I do not see anything indicating why we should not be okey use 0.9.2 just in TP (no0.9.1) if that is what tern *requires*.
(2015-02-10 15:25:07) nickboldt: maxandersen: my point was to simply ask gercan to be sure that he'd tested in luna w/ 0.9.2, since that's what we put in the 4.42.x TP
(2015-02-10 15:25:08) maxandersen: nickboldt: it was you and mistria saying you would want both 0.9.1 and 0.9.2 in there. if that is no longer the case then all is good.
(2015-02-10 15:25:26) nickboldt: well, *I* thought we wanted 0.9.1 cuz that was what gercan had in his manifest file
(2015-02-10 15:26:18) maxandersen: yup and thats fine to check - it was the comment about suggesting to include both instead of fix it properly ;)
(2015-02-10 15:26:48) nickboldt: well, I couldn't get confirmation from dev that there was no problem moving from 0.9.1 to 0.9.2 so I figured plan b was include both
(2015-02-10 15:44:07) maxandersen: nickboldt: okey so now you got the confirmation from me ;)
(2015-02-10 15:44:39) maxandersen: nickboldt: and again if tern includes 0.9.2 it would never get to install 0.9.1 anway ;)
{quote}
> FeedHenry requires minimal-json, but it was removed from TP
> -----------------------------------------------------------
>
> Key: JBIDE-19194
> URL: https://issues.jboss.org/browse/JBIDE-19194
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid, target-platform
> Affects Versions: 4.2.3.Beta1, 4.3.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Gorkem Ercan
> Fix For: 4.2.3.Beta1, 4.3.0.Alpha1
>
>
> When moving Tern from the 4.42.x and 4.50.x target platforms into JST, we also moved minimal-json assuming nothing else required it.
> But turns out that Feedhenry (Aerogear) also needs minimal-json.
> So... we need to add that plugin back into the TPs, and make sure that the version we include works with both Aerogear/FeedHenry (0.9.2, same code base in both 4.2.3 and 4.3.0, currently) and JST/Tern (0.9.1 in JBT 4.2, 0.9.2 in JBT 4.3).
> [~maxandersen] [~gercan] [~dgolovin] [~akazakov]
> In JBT 4.2.0-2 we include Tern 0.6 and minimal-json 0.9.1.
> In JBT 4.2.3 we include Tern 0.7 and minimal-json 0.9.1.
> In JBT 4.3.0 we _currently_ include Tern 0.8 and minimal-json 0.9.2.
> Which version should we include in the target platforms for JBT 4.2.3 (4.42.0.Beta1) and JBT 4.3.0 (4.50.0.Alpha1) ?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19100) On RHEL7 (JBT and JBDS) tooltips appear as dark text on a dark background
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19100?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-19100:
----------------------------------
Fix Version/s: 4.3.0.Beta1
(was: 4.3.0.Alpha1)
> On RHEL7 (JBT and JBDS) tooltips appear as dark text on a dark background
> -------------------------------------------------------------------------
>
> Key: JBIDE-19100
> URL: https://issues.jboss.org/browse/JBIDE-19100
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cleanup
> Affects Versions: 4.2.2.Final
> Environment: RHEL7
> Reporter: Len DiMaggio
> Assignee: Snjezana Peco
> Fix For: 4.2.3.Beta1, 4.3.0.Beta1
>
> Attachments: JBDS8_RHEL7_vnc.png, RHEL7_devtoolset3_JBT422_QS_Tooltip.png
>
>
> On RHEL7, some tooltips - for example - the notice displayed when updates to Tools/JBDS are available and the information relating to quickstarts as displayed in Central are shown as dark text on a dark background. See attached screenshots.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-16071) Duplicate cheat sheet options in Project Examples Preferences
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16071?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-16071:
----------------------------------
Fix Version/s: 4.3.0.Beta1
(was: 4.3.0.Alpha1)
> Duplicate cheat sheet options in Project Examples Preferences
> -------------------------------------------------------------
>
> Key: JBIDE-16071
> URL: https://issues.jboss.org/browse/JBIDE-16071
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.1.1.CR1
> Reporter: Michelle Murray
> Assignee: Snjezana Peco
> Fix For: 4.3.0.Beta1
>
> Attachments: Central_cheatsheet.png
>
>
> Click Window > Preferences > JBoss Tools > Project Examples.
> The check box options include 'show readme/cheatsheet file' and then further down specifically for cheat sheets radio buttons for cheat sheet behavior.
> !Central_cheatsheet.png!
> I think the labelling of 'show readme/cheatsheet file' is left over from earlier. With the new cheat sheet functionality, I think that option should just read 'show readme file'. And then the radio button 'Always show' etc. deal with cheat sheets.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-18878) Eclipse livelock(?) at startup with hibernate builder in stacktrace
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18878?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-18878:
----------------------------------
Fix Version/s: 4.3.0.Beta1
(was: 4.3.0.Alpha1)
(was: 4.2.3.Beta1)
> Eclipse livelock(?) at startup with hibernate builder in stacktrace
> -------------------------------------------------------------------
>
> Key: JBIDE-18878
> URL: https://issues.jboss.org/browse/JBIDE-18878
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 4.2.0.Final
> Reporter: Denis Golovin
> Assignee: Snjezana Peco
> Fix For: 4.3.0.Beta1
>
> Attachments: jstack-output.txt
>
>
> See attached [^jstack-output.txt]
> Console out is:
> {code}sh ./jbt420final.sh
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
> org.eclipse.m2e.logback.configuration: The org.eclipse.m2e.logback.configuration bundle was activated before the state location was initialized. Will retry after the state location is initialized.
> org.eclipse.m2e.logback.configuration: Logback config file: /home/eskimo/workspace/420cr2-test1/.metadata/.plugins/org.eclipse.m2e.logback.configuration/logback.1.5.0.20140606-0033.xml
> org.eclipse.m2e.logback.configuration: Initializing logback
> java.lang.ClassCastException: org.eclipse.osgi.internal.framework.EquinoxConfiguration$1 cannot be cast to java.lang.String
> at org.eclipse.m2e.logback.configuration.LogHelper.logJavaProperties(LogHelper.java:26)
> at org.eclipse.m2e.logback.configuration.LogPlugin.loadConfiguration(LogPlugin.java:189)
> at org.eclipse.m2e.logback.configuration.LogPlugin.configureLogback(LogPlugin.java:144)
> at org.eclipse.m2e.logback.configuration.LogPlugin.access$2(LogPlugin.java:107)
> at org.eclipse.m2e.logback.configuration.LogPlugin$1.run(LogPlugin.java:62)
> at java.util.TimerThread.mainLoop(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
> Dec 05, 2014 3:41:58 PM org.hibernate.eclipse.HibernatePlugin start
> INFO: HibernatePlugin Started{code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[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.Beta1
(was: 4.3.0.Alpha1)
> 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.3.0.Beta1
>
>
> 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.11#6341)
11 years, 2 months
[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.3.0.Beta1
(was: 4.3.0.Alpha1)
> 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.3.0.Beta1
>
>
> 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.11#6341)
11 years, 2 months
[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.Beta1
(was: 4.3.0.Alpha1)
> 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: testing-tools
> Affects Versions: 4.2.1.CR1
> Reporter: Lucia Jelinkova
> Assignee: Snjezana Peco
> Fix For: 4.3.0.Beta1
>
>
> 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.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-13876) Decide what to do with the Maven Facet
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13876?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-13876:
--------------------------------
Fix Version/s: LATER
(was: 4.1.x)
> Decide what to do with the Maven Facet
> --------------------------------------
>
> Key: JBIDE-13876
> URL: https://issues.jboss.org/browse/JBIDE-13876
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: maven
> Affects Versions: 4.1.0.Alpha1
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Fix For: LATER
>
>
> The JBoss Maven Facet has been used to :
> - convert projects to Maven
> - add new dependencies to an existing Maven project (by acting as a Library provider)
> The conversion part has been superceded (mostly) by m2e's conversion API.
> The way the Maven facet acts (not on its own but in support of other Facets, Seam most notably) is pretty ugly (storing Facets models in a MavenPostInstallListener), potentially leading to memory leaks.
> The project conversion bit needs to be revisited, see how m2e's conversion API could be leveraged.
> All in all, I'm convinced the whole Maven Facet programming model need a facelift. This issue is opened to discuss what we need to do and how to implement that.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months