February 2011 - arquillian-issues

[JBoss JIRA] Created: (ARQAJO-26) Distribute source artifacts as well

by Karel Piwko (JIRA)

Distribute source artifacts as well ----------------------------------- Key: ARQAJO-26 URL: https://issues.jboss.org/browse/ARQAJO-26 Project: Arquillian Ajocado Issue Type: Feature Request Affects Versions: 1.0.0.Alpha1 Reporter: Karel Piwko Assignee: Lukas Fryc Deploy source artifacts into repository as well. This will greatly improve user experience when building tests in an IDE. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (ARQAJO-19) Move initial version from 1.5.3 to 1.0.0

by Lukas Fryc (JIRA)

Move initial version from 1.5.3 to 1.0.0 ---------------------------------------- Key: ARQAJO-19 URL: https://issues.jboss.org/browse/ARQAJO-19 Project: Arquillian Ajocado Issue Type: Task Reporter: Lukas Fryc Assignee: Lukas Fryc Priority: Blocker Fix For: 1.0.0.Alpha1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (ARQAJO-7) Create TestNG listener instead of an abstract class

by Karel Piwko (JIRA)

Create TestNG listener instead of an abstract class --------------------------------------------------- Key: ARQAJO-7 URL: https://issues.jboss.org/browse/ARQAJO-7 Project: Arquillian Ajocado Issue Type: Feature Request Affects Versions: 1.5.3 Reporter: Karel Piwko Using an abstract class to get the Ajocado functionality is a limitation. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (ARQAJO-6) Move TestNG dependency to TestNG module

by Karel Piwko (JIRA)

Move TestNG dependency to TestNG module --------------------------------------- Key: ARQAJO-6 URL: https://issues.jboss.org/browse/ARQAJO-6 Project: Arquillian Ajocado Issue Type: Bug Affects Versions: 1.5.3 Reporter: Karel Piwko TestNG is listed as dependency in API, however it has a dedicated package at the moment. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (ARQ-187) Create a integration format for Tools

by Aslak Knutsen (JIRA)

Create a integration format for Tools ------------------------------------- Key: ARQ-187 URL: https://jira.jboss.org/browse/ARQ-187 Project: Arquillian Issue Type: Task Reporter: Aslak Knutsen Assignee: Aslak Knutsen To integrate without binary dep with tooling by creating a XML format for Deployment Archive. Tooling can use this to read in the deployment and find the related resource in the project and show a Archive view. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (ARQ-364) Spurious (?) warnings about "More then one reference to the same implementation was found for org.jboss.arquillian.spi.ApplicationArchiveGenerator, please verify you classpath"

by Bob McWhirter (JIRA)

Spurious (?) warnings about "More then one reference to the same implementation was found for org.jboss.arquillian.spi.ApplicationArchiveGenerator, please verify you classpath" -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: ARQ-364 URL: https://issues.jboss.org/browse/ARQ-364 Project: Arquillian Issue Type: Bug Reporter: Bob McWhirter Priority: Trivial In our Arquillian+RSpec (JRuby) integration, everything works, but we repeatedly get this warning: {noformat} [WARNING] Feb 8, 2011 10:46:57 AM org.jboss.arquillian.impl.DynamicServiceLoader verifySameImplementation [WARNING] WARNING: More then one reference to the same implementation was found for org.jboss.arquillian.spi.ApplicationArchiveGenerator, please verify you classpath {noformat} Would be lovely to have one of: * Instructions on how to solve the root cause (which classpath? I think we have 3: maven's, jruby's and AS's...) * Instructions on how to mute the warning -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (ARQ-343) Allow user defined test context properties to propagate to the server side

by Thomas Diesler (JIRA)

Allow user defined test context properties to propagate to the server side -------------------------------------------------------------------------- Key: ARQ-343 URL: https://jira.jboss.org/browse/ARQ-343 Project: Arquillian Issue Type: Feature Request Reporter: Thomas Diesler There are currently quite a number of ThreadLocal hacks that transport data from the receiving side of the protocol (i.e. JMXTestRunner) to the TestEnrichers and other places. This request is about defining a TextContext factory API that allows the receiving side of the protocol to create and populate the Context that is seen by the various server side components. The ServiceLoader associated with the Context is part of that. Currently the DynamicServiceLoader, which is impl detail leaks into the JMXTestRunner. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (ARQ-335) Weld SE container does not properly load extension classes at boot

by Lincoln Baxter III (JIRA)

Weld SE container does not properly load extension classes at boot ------------------------------------------------------------------ Key: ARQ-335 URL: https://jira.jboss.org/browse/ARQ-335 Project: Arquillian Issue Type: Bug Components: Weld Containers Affects Versions: 1.0.0.Alpha4 Environment: Weld 1.1.0.Beta1 Reporter: Lincoln Baxter III ServiceLoader needs to be used to load the extensions and add then to the Deployment: package org.jboss.arquillian.container.weld.se.embedded_1; import java.util.ArrayList; import java.util.Arrays; import java.util.Collection; import java.util.List; import javax.enterprise.inject.spi.Extension; import org.jboss.arquillian.container.weld.se.embedded_1.shrinkwrap.ShrinkwrapBeanDeploymentArchive; import org.jboss.arquillian.protocol.local.LocalMethodExecutor; import org.jboss.arquillian.spi.Configuration; import org.jboss.arquillian.spi.ContainerMethodExecutor; import org.jboss.arquillian.spi.Context; import org.jboss.arquillian.spi.DeployableContainer; import org.jboss.arquillian.spi.DeploymentException; import org.jboss.arquillian.spi.LifecycleException; import org.jboss.shrinkwrap.api.Archive; import org.jboss.weld.bootstrap.WeldBootstrap; import org.jboss.weld.bootstrap.api.Environments; import org.jboss.weld.bootstrap.api.ServiceRegistry; import org.jboss.weld.bootstrap.spi.BeanDeploymentArchive; import org.jboss.weld.bootstrap.spi.Deployment; import org.jboss.weld.bootstrap.spi.Metadata; import org.jboss.weld.context.api.helpers.ConcurrentHashMapBeanStore; import org.jboss.weld.extensions.util.service.ServiceLoader; import org.jboss.weld.manager.api.WeldManager; /** * WeldSEContainer * * @author <a href="mailto:aslak@conduct.no">Aslak Knutsen</a> * @version $Revision: $ */ public class WeldSEContainer implements DeployableContainer { /* * (non-Javadoc) * * @see org.jboss.arquillian.spi.DeployableContainer#setup(org.jboss.arquillian.spi.Context, * org.jboss.arquillian.spi.Configuration) */ public void setup(final Context context, final Configuration configuration) { } /* * (non-Javadoc) * * @see org.jboss.arquillian.spi.DeployableContainer#start(org.jboss.arquillian.spi.Context) */ public void start(final Context context) throws LifecycleException { } /* * (non-Javadoc) * * @see org.jboss.arquillian.spi.DeployableContainer#stop(org.jboss.arquillian.spi.Context) */ public void stop(final Context context) throws LifecycleException { } /* * (non-Javadoc) * * @see org.jboss.arquillian.spi.DeployableContainer#deploy(org.jboss.arquillian.spi.Context, * org.jboss.shrinkwrap.api.Archive) */ public ContainerMethodExecutor deploy(final Context context, final Archive<?> archive) throws DeploymentException { final ShrinkwrapBeanDeploymentArchive beanArchive = archive.as(ShrinkwrapBeanDeploymentArchive.class); final Deployment deployment = new Deployment() { public Collection<BeanDeploymentArchive> getBeanDeploymentArchives() { return Arrays.asList((BeanDeploymentArchive) beanArchive); } public ServiceRegistry getServices() { return beanArchive.getServices(); } public BeanDeploymentArchive loadBeanDeploymentArchive( final Class<?> beanClass) { return beanArchive; } /* * (non-Javadoc) * * @see org.jboss.weld.bootstrap.spi.Deployment#getExtensions() */ public Iterable<Metadata<Extension>> getExtensions() { return transform(ServiceLoader.load(Extension.class, beanArchive.getClassLoader())); } }; ContextClassLoaderManager classLoaderManager = new ContextClassLoaderManager(beanArchive.getClassLoader()); classLoaderManager.enable(); context.add(ContextClassLoaderManager.class, classLoaderManager); WeldBootstrap bootstrap = new WeldBootstrap(); beanArchive.setBootstrap(bootstrap); bootstrap.startContainer(Environments.SE, deployment, new ConcurrentHashMapBeanStore()) .startInitialization() .deployBeans() .validateBeans() .endInitialization(); WeldManager manager = bootstrap.getManager(beanArchive); context.add(WeldBootstrap.class, bootstrap); context.add(WeldManager.class, manager); return new LocalMethodExecutor(); } /* * (non-Javadoc) * * @see org.jboss.arquillian.spi.DeployableContainer#undeploy(org.jboss.arquillian.spi.Context, * org.jboss.shrinkwrap.api.Archive) */ public void undeploy(final Context context, final Archive<?> archive) throws DeploymentException { WeldBootstrap bootstrap = context.get(WeldBootstrap.class); if (bootstrap != null) { bootstrap.shutdown(); } ContextClassLoaderManager classLoaderManager = context.get(ContextClassLoaderManager.class); classLoaderManager.disable(); } public static Iterable<Metadata<Extension>> transform(final ServiceLoader<Extension> serviceLoader) { List<Metadata<Extension>> result = new ArrayList<Metadata<Extension>>(); for (final Extension extension : serviceLoader) { result.add(new Metadata<Extension>() { public String getLocation() { return "unknown"; } public Extension getValue() { return extension; } }); } return result; } } -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

3
2
0 / 0

[JBoss JIRA] Created: (ARQ-55) TestNG @Test(dependsOnMethods="") does not work when running inside the container

by Aslak Knutsen (JIRA)

TestNG @Test(dependsOnMethods="") does not work when running inside the container --------------------------------------------------------------------------------- Key: ARQ-55 URL: https://jira.jboss.org/jira/browse/ARQ-55 Project: Arquillian Issue Type: Bug Components: TestNG Reporter: Aslak Knutsen "methodX is not allowed to depend on methodY" The way Arquillian invokes the remote container it creates a new 'suite' pr TestCase pr test method. Since only one test method is invoked pr suite, TestNGs dependsOnMethods fail. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (ARQ-167) Support @EJB.mappedName for TestClass injection

by Aslak Knutsen (JIRA)

Support @EJB.mappedName for TestClass injection ----------------------------------------------- Key: ARQ-167 URL: https://jira.jboss.org/browse/ARQ-167 Project: Arquillian Issue Type: Feature Request Components: Runtime Enricher SPI Affects Versions: 1.0.0.Alpha2 Reporter: Aslak Knutsen We should support letting the user set the mappedName on the injection in the test case to avoid having to follow our naming standards. (until we can do it more reliable, https://jira.jboss.org/browse/ARQ-77) Needs to document the potential jndi naming changes between Embedded EJB containers and Remote Containers(packaging).. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

4
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues February 2011