September 2011 - arquillian-issues

[JBoss JIRA] Created: (ARQAJO-82) Cross-site request problems for Ajocado

by Karel Piwko (JIRA)

Cross-site request problems for Ajocado --------------------------------------- Key: ARQAJO-82 URL: https://issues.jboss.org/browse/ARQAJO-82 Project: Arquillian Ajocado Issue Type: Feature Request Components: integration Affects Versions: 1.0.0.CR1 Reporter: Karel Piwko Assignee: Lukáš Fryč Evaluate if Ajocado is affected by ARQ-521 and if proprosed solution will work for it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

3
2
0 / 0

[JBoss JIRA] Created: (ARQ-576) The build script bits that downloads and configures 1 or more managed containers should be extracted to a maven plugin, so we don't need to copy paste that logic

by Geoffrey De Smet (JIRA)

The build script bits that downloads and configures 1 or more managed containers should be extracted to a maven plugin, so we don't need to copy paste that logic ----------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: ARQ-576 URL: https://issues.jboss.org/browse/ARQ-576 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Maven Plugin Reporter: Geoffrey De Smet Priority: Minor See ARQ-574. Now we have to copy paste something like this, per managed container: {code} <properties> <managed-appserver.download.dir>${project.basedir}/local/managed-appserver</managed-appserver.download.dir> <managed-appserver.tomcat6.version>6.0.33</managed-appserver.tomcat6.version> <managed-appserver.tomcat6.home>${project.build.directory}/apache-tomcat-${managed-appserver.tomcat6.version}</managed-appserver.tomcat6.home> </properties> ... <plugin> <artifactId>maven-antrun-plugin</artifactId> <inherited>false</inherited> <executions> <execution> <phase>generate-test-resources</phase> <configuration> <target> <mkdir dir="${managed-appserver.download.dir}"/> <get src="http://archive.apache.org/dist/tomcat/tomcat-6/v${managed-appserver.tomca..." dest="${managed-appserver.download.dir}" verbose="true" skipexisting="true"/> <unzip src="${managed-appserver.download.dir}/apache-tomcat-${managed-appserver.tomcat6.version}.zip" dest="${project.build.directory}"/> </target> </configuration> <goals> <goal>run</goal> </goals> </execution> </executions> </plugin> <plugin> <artifactId>maven-resources-plugin</artifactId> <executions> <execution> <id>copy-resources</id> <phase>process-test-resources</phase> <goals> <goal>copy-resources</goal> </goals> <configuration> <outputDirectory>${managed-appserver.tomcat6.home}/conf</outputDirectory> <overwrite>true</overwrite> <resources> <resource> <directory>${basedir}/src/test/conf/tomcat6</directory> </resource> </resources> </configuration> </execution> </executions> </plugin> <plugin> <artifactId>maven-surefire-plugin</artifactId> <configuration> <environmentVariables> <CATALINA_HOME>${managed-appserver.tomcat6.home}</CATALINA_HOME> </environmentVariables> </configuration> </plugin> {code} But this changes over time, and since we copy-paste it to our user projects, our copy becomes stale. If this could be extracted somehow (aslak is not in favor of adding this to the managed container runtimes, so probably a maven plugin), that would be nice. Extra optional requirements: - It should be easy to ask for multiple managed appservers (say jboss 7, tomcat 6, jetty 6 and jboss 6) - Prefer zips from the maven repo over "download" url's. At least if the maven repo is down we know that a clean build doesn't work. - What if multiple hudson jobs are testing with arq on the same hudson slave? They can't use the same port! - I prefer downloading to /local instead of /target, because the latter gets deleted during "mvn clean". Then again, if it comes from ~/.m2/repository, neither is needed. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

4
7
0 / 0

[JBoss JIRA] Created: (ARQ-337) Create a Context/Scope activation/deactivation abstraction for CDI

by Aslak Knutsen (JIRA)

Create a Context/Scope activation/deactivation abstraction for CDI ------------------------------------------------------------------- Key: ARQ-337 URL: https://jira.jboss.org/browse/ARQ-337 Project: Arquillian Issue Type: Feature Request Reporter: Aslak Knutsen We need to have a stable and reliable api exposed by arquillian over the different container types and CDI impls to control the activation and deactivation of different scopes -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

4
7
0 / 0

[JBoss JIRA] Created: (ARQ-520) ResolutionException for artifact org.jboss.arquillian.osgi:arquillian-osgi-bundle:jar

by Thomas Diesler (JIRA)

ResolutionException for artifact org.jboss.arquillian.osgi:arquillian-osgi-bundle:jar ------------------------------------------------------------------------------------- Key: ARQ-520 URL: https://issues.jboss.org/browse/ARQ-520 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: OSGi Containers Affects Versions: osgi_1.0.0.CR2 Reporter: Thomas Diesler Assignee: Thomas Diesler When the JBoss Nexus repo is not defined in ~/.m2/settings.xml we get org.jboss.shrinkwrap.resolver.api.ResolutionException: Unable to resolve an artifact at org.jboss.shrinkwrap.resolver.impl.maven.MavenBuilderImpl.resolveAsFiles(MavenBuilderImpl.java:324) at org.jboss.shrinkwrap.resolver.impl.maven.MavenBuilderImpl.resolveAsFiles(MavenBuilderImpl.java:70) at org.jboss.shrinkwrap.resolver.impl.maven.MavenBuilderImpl$MavenArtifactBuilderImpl.resolveAsFiles(MavenBuilderImpl.java:471) at org.jboss.shrinkwrap.resolver.impl.maven.MavenBuilderImpl$MavenArtifactBuilderImpl.resolveAsFiles(MavenBuilderImpl.java:405) at org.jboss.arquillian.container.osgi.embedded.EmbeddedDeployableContainer.installBundle(EmbeddedDeployableContainer.java:182) at org.jboss.arquillian.container.osgi.embedded.EmbeddedDeployableContainer.start(EmbeddedDeployableContainer.java:108) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
6
0 / 0

[JBoss JIRA] Created: (ARQ-338) All test case to specify a list of support bundles

by Thomas Diesler (JIRA)

All test case to specify a list of support bundles -------------------------------------------------- Key: ARQ-338 URL: https://jira.jboss.org/browse/ARQ-338 Project: Arquillian Issue Type: Task Reporter: Thomas Diesler Assignee: Thomas Diesler ARQ OSGi tests may have the need to install the arquillian-osgi-bundle before they can run -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (ARQ-301) Create a Spring framework integration (for non-standalone containers)

by Dan Allen (JIRA)

Create a Spring framework integration (for non-standalone containers) --------------------------------------------------------------------- Key: ARQ-301 URL: https://jira.jboss.org/browse/ARQ-301 Project: Arquillian Issue Type: Feature Request Affects Versions: 1.0.0.Alpha4 Reporter: Dan Allen Implement a Spring framework integration. We want to be able to execute Spring tests in non-standalone containers (e.g., Java EE, Servlet). These containers don't have the Spring framework programming model out of the box. So we need to ship it to the server along with the test. That's the purpose of an Arquillian framework integration, so it's an ideal solution. -- 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

12 years, 8 months

4
12
0 / 0

[JBoss JIRA] Created: (ARQ-454) Console log output in Arquillian and JBoss Container Managed 6

by Ove Ranheim (JIRA)

Console log output in Arquillian and JBoss Container Managed 6 -------------------------------------------------------------- Key: ARQ-454 URL: https://issues.jboss.org/browse/ARQ-454 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: JBoss Containers Affects Versions: 1.0.0.Alpha5 Reporter: Ove Ranheim It should be possible to configure console log output in in arquillian.xml, so the logger would redirected server.log to console output. This would require a change in ServiceController: http://anonsvn.jboss.org/repos/jbossas/projects/server-manager/tags/1.0.4... For Bamboo users; Bamboo Jobs are sniffing on the console log output and is sensitive about that, so to get proper integration tests running, this is a requirement. This issue should probably be raised with Ryan Campbell. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
2
0 / 0

[JBoss JIRA] Created: (ARQ-583) When missing a vital part of an ARQ test a meaningful exception should be thrown

by Jason Porter (JIRA)

When missing a vital part of an ARQ test a meaningful exception should be thrown -------------------------------------------------------------------------------- Key: ARQ-583 URL: https://issues.jboss.org/browse/ARQ-583 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 1.0.0.CR4 Reporter: Jason Porter For example if you're missing a @Deployment, an error stating as much should be thrown. There may be some others, but this one comes to the top. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (ARQ-585) Support for adding a beans.xml without discarding the original beans.xml with .mergeAsResource()

by Geoffrey De Smet (JIRA)

Support for adding a beans.xml without discarding the original beans.xml with .mergeAsResource() ------------------------------------------------------------------------------------------------ Key: ARQ-585 URL: https://issues.jboss.org/browse/ARQ-585 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Geoffrey De Smet Priority: Critical Presume these 2 beans.xml files: Production code: beans.xml: {code} <beans xmlns="http://java.sun.com/xml/ns/javaee" ...>  </beans> {code} Test addition: test-beans.xml: {code} <beans xmlns="http://java.sun.com/xml/ns/javaee" ...> <alternatives> <class>org.drools.guvnor.server.repository.TestRepositoryStartupService</class> </alternatives> </beans> {code} Now, for non-test runs (such as in the IDE or in production), only the beans.xml is activated through weld and the test-only alternative should not be activated. For test runs, the test-only alternative should be activated, yet the rest of the content from beans.xml should be in there too. So it should be merged to something like this: {code} <beans xmlns="http://java.sun.com/xml/ns/javaee" ...>  <alternatives> <class>org.drools.guvnor.server.repository.TestRepositoryStartupService</class> </alternatives> </beans> {code} It would be nice if we do something like mergeAsResource(), shown in this example: {code} public static WebArchive createDeployment() { WebArchive webArchive = ShrinkWrap.create(ExplodedImporter.class, "guvnor-webapp-5.3.0-SNAPSHOT.war") .importDirectory(new File("target/guvnor-webapp-5.3.0-SNAPSHOT/")) .as(WebArchive.class) .mergeAsResource(new File("target/test-classes/META-INF/test-beans.xml"), "META-INF/beans.xml") .addAsResource(new File("target/test-classes/"), ArchivePaths.create("")) .addAsLibraries( DependencyResolvers.use(MavenDependencyResolver.class) .includeDependenciesFromPom("pom.xml") .resolveAsFiles(new ScopeFilter("test"))); return webArchive; } {code} Because of maintenance, copying everything from beans.xml to test-beans.xml on every change to beans.xml is NOT an option. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

6
14
0 / 0

[JBoss JIRA] Created: (ARQ-415) Use Seam Solder instead of Weld Extensions

by Hendy Irawan (JIRA)

Use Seam Solder instead of Weld Extensions ------------------------------------------ Key: ARQ-415 URL: https://issues.jboss.org/browse/ARQ-415 Project: Arquillian Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Examples Affects Versions: 1.0.0.Alpha5 Reporter: Hendy Irawan Use Seam Solder instead of Weld Extensions -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues September 2011