April 2012 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-893) Should be able to work with EAR, WAR and JARs with rebel.xml files pr module

by Aslak Knutsen (JIRA)

Aslak Knutsen created ARQ-893: --------------------------------- Summary: Should be able to work with EAR, WAR and JARs with rebel.xml files pr module Key: ARQ-893 URL: https://issues.jboss.org/browse/ARQ-893 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - JRebel Reporter: Aslak Knutsen Assignee: Bernard Labno Fix For: jrebel_1.0.0.next For EAR and WAR modules that contain other modules or libraries, a rebel.xml pr module is required to describe the content of the module. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
7
0 / 0

[JBoss JIRA] (ARQ-894) Allow developer to provide their own rebel.xml

by Bernard Labno (JIRA)

Bernard Labno created ARQ-894: --------------------------------- Summary: Allow developer to provide their own rebel.xml Key: ARQ-894 URL: https://issues.jboss.org/browse/ARQ-894 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - JRebel Reporter: Bernard Labno Assignee: Bernard Labno Developers may need to customize rebel.xml so if they attach it to deployment the extension should skip generation of rebel.xml. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
4
0 / 0

[JBoss JIRA] (ARQ-902) Add README to portal extension project

by Ken Finnigan (JIRA)

Ken Finnigan created ARQ-902: -------------------------------- Summary: Add README to portal extension project Key: ARQ-902 URL: https://issues.jboss.org/browse/ARQ-902 Project: Arquillian Issue Type: Task Security Level: Public (Everyone can see) Components: Extension - Portal Reporter: Ken Finnigan Assignee: Ken Finnigan Fix For: portal_1.0.0.next Need to add README to repository of project to outline what it provides and how it can be used. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
3
0 / 0

[JBoss JIRA] (ARQ-903) Update pom.xml with missing information

by Ken Finnigan (JIRA)

Ken Finnigan created ARQ-903: -------------------------------- Summary: Update pom.xml with missing information Key: ARQ-903 URL: https://issues.jboss.org/browse/ARQ-903 Project: Arquillian Issue Type: Task Security Level: Public (Everyone can see) Components: Extension - Portal Reporter: Ken Finnigan Assignee: Ken Finnigan Fix For: portal_1.0.0.next Update the scm configuration for the new location, and ensure that all the settings in pom.xml are ok ready for a release -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
3
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, 1 month

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, 1 month

2
3
0 / 0

[JBoss JIRA] (ARQ-697) Exception "Could not deploy to container" should report the real exception why the managed server is failing

by Geoffrey De Smet (Created) (JIRA)

Exception "Could not deploy to container" should report the real exception why the managed server is failing ------------------------------------------------------------------------------------------------------------ Key: ARQ-697 URL: https://issues.jboss.org/browse/ARQ-697 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Geoffrey De Smet Priority: Critical Currently, when something goes wrong in a managed server, such as ARQ-660, you get a meaningless exception "Could not deploy to container". The real exception should be reported, for example "port in use". It's furthermore unclear, how far this "Could not deploy to container" stretches: if we have a bug in our CDI configuration (such as an Ambiguous dependency) in our war, will it also be reported as such or not? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

4
4
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, 1 month

6
14
0 / 0

[JBoss JIRA] Created: (ARQ-615) Arquillian must scale to a high number of full-layer integration tests

by Geoffrey De Smet (JIRA)

Arquillian must scale to a high number of full-layer integration tests ---------------------------------------------------------------------- Key: ARQ-615 URL: https://issues.jboss.org/browse/ARQ-615 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Geoffrey De Smet Priority: Critical A full-layer integration test is an arquillian test which deploys the entire war of a webapp (for example guvnor-webapp) and then runs a higher number of test classes and test methods on it. Currently arquillian doesn't scale out to that. For different reasons. The main reason is ARQ-197: every test case starts the container again and after a while tomcat6-managed goes out of memory. But there are other reasons. This should be tested. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

4
6
0 / 0

[JBoss JIRA] (ARQ-897) ArchiveDeploymentExporter should export both archive and testable archive (if applicable)

by Dan Allen (JIRA)

Dan Allen created ARQ-897: ----------------------------- Summary: ArchiveDeploymentExporter should export both archive and testable archive (if applicable) Key: ARQ-897 URL: https://issues.jboss.org/browse/ARQ-897 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Base Implementation Affects Versions: 1.0.0.Final Reporter: Dan Allen Priority: Minor The ArchiveDeploymentExporter should export both the archive and the testable archive (in the case they differ) for testable deployments. This enhancement simply makes it easier on the developer to a) see the progression of the archive and b) see the contents of the original archive easier. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues April 2012