February 2011 - arquillian-issues

[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, 2 months

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, 2 months

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, 2 months

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, 2 months

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, 2 months

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, 2 months

2
12
0 / 0

[JBoss JIRA] Created: (ARQ-273) Verify that all jbosgi in-container tests can be migrated to ARQ

by Thomas Diesler (JIRA)

Verify that all jbosgi in-container tests can be migrated to ARQ ----------------------------------------------------------------- Key: ARQ-273 URL: https://jira.jboss.org/browse/ARQ-273 Project: Arquillian Issue Type: Task Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 1.0.0.Alpha4 -- 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, 2 months

2
8
0 / 0

[JBoss JIRA] Created: (ARQ-295) OSGi testsuite depends on arquillian-protocol-local artifact in local mvn repo

by Thomas Diesler (JIRA)

OSGi testsuite depends on arquillian-protocol-local artifact in local mvn repo ------------------------------------------------------------------------------ Key: ARQ-295 URL: https://jira.jboss.org/browse/ARQ-295 Project: Arquillian Issue Type: Bug Components: OSGi Containers Reporter: Thomas Diesler Assignee: Thomas Diesler Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.532 sec <<< FAILURE! testArtifactFromRepository(org.jboss.arquillian.container.osgi.arq198.ARQ198TestCase) Time elapsed: 0.09 sec <<< FAILURE! java.lang.AssertionError: artifactURL not null: arquillian-protocol-local at org.junit.Assert.fail(Assert.java:91) at org.junit.Assert.assertTrue(Assert.java:43) at org.junit.Assert.assertNotNull(Assert.java:524) at org.jboss.arquillian.container.osgi.arq198.ARQ198TestCase.testArtifactFromRepository(ARQ198TestCase.java:72) -- 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, 2 months

2
6
0 / 0

[JBoss JIRA] Created: (ARQ-302) OSGi integration not usable with Equinox

by Thomas Diesler (JIRA)

OSGi integration not usable with Equinox ---------------------------------------- Key: ARQ-302 URL: https://jira.jboss.org/browse/ARQ-302 Project: Arquillian Issue Type: Bug Components: OSGi Containers Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 1.0.0.Beta1 testBundleContextInjection(org.jboss.test.osgi.framework.simple.SimpleArquillianTestCase) Time elapsed: 0.045 sec <<< ERROR! java.lang.ClassNotFoundException: org.jboss.test.osgi.framework.simple.SimpleArquillianTestCase at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:494) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:410) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:398) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:105) at java.lang.ClassLoader.loadClass(ClassLoader.java:248) at org.eclipse.osgi.internal.loader.BundleLoader.loadClass(BundleLoader.java:326) at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:231) at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundle.java:1193) at org.jboss.arquillian.osgi.internal.ArquillianBundleActivator$1.loadTestClass(ArquillianBundleActivator.java:62) at org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethodInternal(JMXTestRunner.java:133) It seems that Equinox does not resolve the test bundle as a result of a dynamic import -- 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, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (ARQ-272) Allow @Deployment to be optional

by Thomas Diesler (JIRA)

Allow @Deployment to be optional -------------------------------- Key: ARQ-272 URL: https://jira.jboss.org/browse/ARQ-272 Project: Arquillian Issue Type: Feature Request Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 1.0.0.Alpha4 OSGi test cases frequently generate non-trivial bundle deployments as part of their test methods. The bundle that contains the test case is automatically generated by ARQ. To be precise, the test class is always added to the @Deployment. The bundle manifest is generated or extended by the required Import/Export-Package statements. If @Deployment was missing, ARQ could generate an Archive that contains the test class, which would reduce the noise in ARQ OSGi tests considerably. -- 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, 2 months

2
14
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues February 2011