[
https://issues.jboss.org/browse/FURNACE-43?page=com.atlassian.jira.plugin...
]
George Gastaldi edited comment on FURNACE-43 at 4/22/15 1:41 PM:
-----------------------------------------------------------------
This is what happens when you execute a test that has the simple container and the cdi
container added in test scope:
{code}
org.jboss.forge.furnace.exception.ContainerException: Expected only one
[org.jboss.forge.furnace.lifecycle.AddonLifecycleProvider] but found multiple. Remove all
but one redundant container implementations:
[[org.jboss.forge.furnace.container:simple,2.16.1-SNAPSHOT +STARTED ->
org.jboss.forge.furnace.container.simple.lifecycle.SimpleContainerImpl@2f0935cc],
[org.jboss.forge.furnace.container:cdi,2.16.1-SNAPSHOT +STARTED ->
org.jboss.forge.furnace.container.cdi.lifecycle.WeldAddonLifecycleProvider@752d404b]]
at
org.jboss.forge.furnace.impl.addons.AddonRunnable.detectLifecycleProviderDependencies(AddonRunnable.java:324)
at
org.jboss.forge.furnace.impl.addons.AddonRunnable.detectLifecycleProvider(AddonRunnable.java:208)
at org.jboss.forge.furnace.impl.addons.AddonRunnable.run(AddonRunnable.java:81)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
{code}
cdi should be the only one added as it's in test scope
was (Author: gastaldi):
This is what happens when you execute a test that has the simple container and the cdi
container added in test scope:
{code}
org.jboss.forge.furnace.exception.ContainerException: Expected only one
[org.jboss.forge.furnace.lifecycle.AddonLifecycleProvider] but found multiple. Remove all
but one redundant container implementations:
[[org.jboss.forge.furnace.container:simple,2.16.1-SNAPSHOT +STARTED ->
org.jboss.forge.furnace.container.simple.lifecycle.SimpleContainerImpl@2f0935cc],
[org.jboss.forge.furnace.container:cdi,2.16.1-SNAPSHOT +STARTED ->
org.jboss.forge.furnace.container.cdi.lifecycle.WeldAddonLifecycleProvider@752d404b]]
at
org.jboss.forge.furnace.impl.addons.AddonRunnable.detectLifecycleProviderDependencies(AddonRunnable.java:324)
at
org.jboss.forge.furnace.impl.addons.AddonRunnable.detectLifecycleProvider(AddonRunnable.java:208)
at org.jboss.forge.furnace.impl.addons.AddonRunnable.run(AddonRunnable.java:81)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
{code}
Support @AddonDependencies(automatic=true) to remove the need for
manual specification of Addon dependencies
------------------------------------------------------------------------------------------------------------
Key: FURNACE-43
URL:
https://issues.jboss.org/browse/FURNACE-43
Project: Forge: Furnace
Issue Type: Feature Request
Components: Test Harness
Affects Versions: 2.16.0.Final
Reporter: Lincoln Baxter III
Assignee: Lincoln Baxter III
Fix For: 2.16.1.Final
The following @AddonDependencies annotation would signal to the test harness that all
Addons from the current maven module should be imported to the test case deployment:
{code}
@Deployment
@AddonDependencies(automatic=true)
public static AddonArchive getDeployment()
{
final AddonArchive archive = ShrinkWrap.create(AddonArchive.class)
.addBeansXML());
return archive;
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)