April 2011 - arquillian-issues - Jboss List Archives

[JBoss JIRA] Created: (ARQ-109) RunMode Local should support TestEnrichment

by Aslak Knutsen (JIRA)

RunMode Local should support TestEnrichment ------------------------------------------- Key: ARQ-109 URL: https://jira.jboss.org/jira/browse/ARQ-109 Project: Arquillian Issue Type: Task Components: Runtime Enricher SPI Reporter: Aslak Knutsen Currently when in RunMode local no enrichment is done. We can still enrich: @Resources for remote exposed object @EJB with Remote interface -- 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, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (ARQ-321) Test enrichers should provide a ready-made deployment appender dependency

by Dan Allen (JIRA)

Test enrichers should provide a ready-made deployment appender dependency ------------------------------------------------------------------------- Key: ARQ-321 URL: https://jira.jboss.org/browse/ARQ-321 Project: Arquillian Issue Type: Feature Request Components: Packaging Enricher SPI, Runtime Enricher SPI Affects Versions: 1.0.0.Alpha4 Reporter: Dan Allen Priority: Minor Fix For: 1.0.0.CR1 Each test enrichers implementation should provide a dependency that packages the test enricher as an auxiliary archive. Currently, a container adapter will assemble an auxiliary archive of the test enrichers that are supported by that container. But there are cases when the container may have been enhanced with additional capabilities that allow it to support an additional enricher. At this point, it's up to the developer to package the enricher. We could alleviate this requirement by providing ready-made test enrichers that include the auxiliary archive packaging. This supplementary dependency could be named using an additional classifier on the test enricher artifact, as such: <groupId>org.jboss.arquillian.testenricher</groupId> <artifactId>arquillian-testenricher-cdi</artifactId> <classifier>auxiliary-archive</classifier> <version>...</version> This will give you not only the test enricher, but also enlistment as an auxiliary archive. The containers will still do their own packaging...this is for standalone usage. -- 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, 1 month

2
6
0 / 0

[JBoss JIRA] Created: (ARQ-357) Create a single extension point

by Aslak Knutsen (JIRA)

Create a single extension point ------------------------------- Key: ARQ-357 URL: https://issues.jboss.org/browse/ARQ-357 Project: Arquillian Issue Type: Feature Request Affects Versions: 1.0.0.Alpha4 Reporter: Aslak Knutsen To simplify the creation of extensions, we should move all SPI loading into a single java SPI loadable location, and do Service registry from there. http://arquillian.pastebin.com/bcrup1UD -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (ARQ-386) Extract Configuration as a separate module

by Aslak Knutsen (JIRA)

Extract Configuration as a separate module ------------------------------------------ Key: ARQ-386 URL: https://issues.jboss.org/browse/ARQ-386 Project: Arquillian Issue Type: Feature Request Components: Base Implementation Affects Versions: 1.0.0.Alpha5 Reporter: Aslak Knutsen Fix For: 1.0.0.Beta1 Configuration is currently located in impl-base, should be extracted as a separate module so it can be reused by e.g. Forge -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (ARQ-297) create an essential build profile to make build more approachable

by Dan Allen (JIRA)

create an essential build profile to make build more approachable ----------------------------------------------------------------- Key: ARQ-297 URL: https://jira.jboss.org/browse/ARQ-297 Project: Arquillian Issue Type: Feature Request Components: Build Infrastructure Affects Versions: 1.0.0.Alpha4 Reporter: Dan Allen Fix For: 1.0.0.Beta1 Newcomers are struggling to build Arquillian for the first time because the default profile steps into all the container modules. This results in massive downloads (JBoss AS embedded, GlassFish embedded, etc), slow build processes and frequent failures. A newcomer to Arquillian shouldn't have to go through this whole parade. They really just want to build the essential bits of Arquillian, then hand pick the container module they want to study or hack. To cut down on the default build, we should introduce a new profile in the aggregator pom that is activated by default. (Hudson can be set to run with -Pall) <profile> <id>essential</id> <activation> <activeByDefault>true</activeByDefault> </activation> <modules> <module>build</module> <module>api</module> <module>spi</module> <module>impl-base</module> <module>junit</module> <module>testng</module> <module>testenrichers</module> <module>protocols</module> </modules> </profile> (I should note that Thomas already did a similar thing to isolate the Arquillian essentials to work on OSGi, but that build profile could be replaced with this one, give or take a module or two). -- 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, 1 month

3
12
0 / 0

[JBoss JIRA] Created: (ARQ-235) OSGi Framework does not get stopped

by Thomas Diesler (JIRA)

OSGi Framework does not get stopped ----------------------------------- Key: ARQ-235 URL: https://jira.jboss.org/browse/ARQ-235 Project: Arquillian Issue Type: Bug Reporter: Thomas Diesler The framework should be started as part of @BeforeClass and taken down in @AfterClass -- 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, 1 month

2
14
0 / 0

[JBoss JIRA] Created: (ARQ-294) Shrinkwrap has a dependency on ThreadContext ClassLoader

by Thomas Diesler (JIRA)

Shrinkwrap has a dependency on ThreadContext ClassLoader -------------------------------------------------------- Key: ARQ-294 URL: https://jira.jboss.org/browse/ARQ-294 Project: Arquillian Issue Type: Bug Reporter: Thomas Diesler The Shrinkrap API provided by the arquillian-osgi-bundle has a dependency on TCCL See AbstractOSGiContainer public Bundle installBundle(Archive<?> archive) throws BundleException { InputStream inputStream; ClassLoader ctxLoader = Thread.currentThread().getContextClassLoader(); try { // Read the archive in the context of the arquillian-osgi-bundle Thread.currentThread().setContextClassLoader(getClass().getClassLoader()); ZipExporter exporter = archive.as(ZipExporter.class); ByteArrayOutputStream baos = new ByteArrayOutputStream(); exporter.exportZip(baos); inputStream = new ByteArrayInputStream(baos.toByteArray()); } finally { Thread.currentThread().setContextClassLoader(ctxLoader); } return context.installBundle(archive.getName(), inputStream); } As long as this internal code needs to set the TCCL, user code that works on the Archive will also need to do that. The likely resolution is, to remove TCCL dependency iin shrinkwrap. -- 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, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (ARQ-199) Add support to controll multiple framework instances

by Thomas Diesler (JIRA)

Add support to controll multiple framework instances ---------------------------------------------------- Key: ARQ-199 URL: https://jira.jboss.org/browse/ARQ-199 Project: Arquillian Issue Type: Feature Request Components: OSGi Containers Reporter: Thomas Diesler It would also be nice if it could support controlling multiple framework instances. As mentioned before, an OSGi Framework can be controlled using a standard interface: org.osgi.framework.launch.Framework extends Bundle. In some test scenarios (especially ones involving Distributed OSGi) you'd want to bring up multiple frameworks and run tests bundles in both of them. The unit test would then essentially orchestrate the whole thing and make assertions on behaviour in these two frameworks which can be obtained through the bundle context of either. -- 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, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (ARQ-190) Remote OSGi bundle testing

by Thomas Diesler (JIRA)

Remote OSGi bundle testing -------------------------- Key: ARQ-190 URL: https://jira.jboss.org/browse/ARQ-190 Project: Arquillian Issue Type: Task Components: OSGi Integration Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 1.0.0.Alpha3 Add remoteness to the jmx protocoll -- 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, 1 month

2
12
0 / 0

[JBoss JIRA] Closed: (ARQ-303) NPE when uninstalling support bundles with Equinox

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-303?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen closed ARQ-303. ----------------------------- > NPE when uninstalling support bundles with Equinox > -------------------------------------------------- > > Key: ARQ-303 > URL: https://issues.jboss.org/browse/ARQ-303 > Project: Arquillian > Issue Type: Bug > Components: OSGi Containers > Reporter: Thomas Diesler > Assignee: Thomas Diesler > > Caused by: java.lang.NullPointerException > at org.jboss.arquillian.container.osgi.embedded.EmbeddedDeployableContainer.getBundle(EmbeddedDeployableContainer.java:214) > at org.jboss.arquillian.container.osgi.embedded.EmbeddedDeployableContainer.getBundleState(EmbeddedDeployableContainer.java:181) > at org.jboss.arquillian.osgi.internal.AbstractDeployableContainer.uninstallBundleList(AbstractDeployableContainer.java:145) > at org.jboss.arquillian.osgi.internal.AbstractDeployableContainer.uninstallSupportBundles(AbstractDeployableContainer.java:97) > at org.jboss.arquillian.container.osgi.embedded.EmbeddedDeployableContainer.undeploy(EmbeddedDeployableContainer.java:122) > at org.jboss.arquillian.impl.handler.ContainerUndeployer.callback(ContainerUndeployer.java:61) > at org.jboss.arquillian.impl.handler.ContainerUndeployer.callback(ContainerUndeployer.java:47) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues April 2011