March 2014 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-1665) Update to Jacoco 0.6.3

by Aslak Knutsen (JIRA)

Aslak Knutsen created ARQ-1665: ---------------------------------- Summary: Update to Jacoco 0.6.3 Key: ARQ-1665 URL: https://issues.jboss.org/browse/ARQ-1665 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Jacoco Affects Versions: jacoco_1.0.0.Alpha5 Reporter: Aslak Knutsen Assignee: Aslak Knutsen Fix For: jacoco_1.0.0.Alpha6 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1665) Update to Jacoco 0.6.3

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1665?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen updated ARQ-1665: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/arquillian/arquillian-extension-jacoco/pull/12 > Update to Jacoco 0.6.3 > ---------------------- > > Key: ARQ-1665 > URL: https://issues.jboss.org/browse/ARQ-1665 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Jacoco > Affects Versions: jacoco_1.0.0.Alpha5 > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: jacoco_1.0.0.Alpha6 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1014) Packaging Processor phase is skipped when the deployment is not testable

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1014?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen updated ARQ-1014: ------------------------------- Summary: Packaging Processor phase is skipped when the deployment is not testable (was: Instrumentation is skipped when the deployment is not testable) > Packaging Processor phase is skipped when the deployment is not testable > ------------------------------------------------------------------------ > > Key: ARQ-1014 > URL: https://issues.jboss.org/browse/ARQ-1014 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Jacoco > Affects Versions: 1.0.0.Alpha3 > Reporter: Jan Papousek > Fix For: 2.0.0.Beta1 > > > Documentation of [Deployment|https://github.com/arquillian/arquillian-core/blob/master/cont... says: "Defines if this deployment should be wrapped up based on the protocol so the testcase can be executed incontainer.". However when it's set to false it also disables all [application archive processors|https://github.com/arquillian/arquillian-core/blob/master/cont...] (see [code|https://github.com/arquillian/arquillian-core/blob/master/container/...]), so Jacoco instrumentation is not processed. > I think this behaviour should be at least well documented, but it would be better to rename testable() or change behaviour of deployment generator. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1014) Packaging Processor phase is skipped when the deployment is not testable

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1014?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen updated ARQ-1014: ------------------------------- Component/s: Packaging Enricher SPI (was: Extension - Jacoco) > Packaging Processor phase is skipped when the deployment is not testable > ------------------------------------------------------------------------ > > Key: ARQ-1014 > URL: https://issues.jboss.org/browse/ARQ-1014 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Packaging Enricher SPI > Affects Versions: 1.0.0.Alpha3 > Reporter: Jan Papousek > Fix For: 2.0.0.Beta1 > > > Documentation of [Deployment|https://github.com/arquillian/arquillian-core/blob/master/cont... says: "Defines if this deployment should be wrapped up based on the protocol so the testcase can be executed incontainer.". However when it's set to false it also disables all [application archive processors|https://github.com/arquillian/arquillian-core/blob/master/cont...] (see [code|https://github.com/arquillian/arquillian-core/blob/master/container/...]), so Jacoco instrumentation is not processed. > I think this behaviour should be at least well documented, but it would be better to rename testable() or change behaviour of deployment generator. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1327) arquillian-jacoco: Wrong asm library (3.1.1) dependency

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1327?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen updated ARQ-1327: ------------------------------- Fix Version/s: jacoco_1.0.0.Alpha6 > arquillian-jacoco: Wrong asm library (3.1.1) dependency > ------------------------------------------------------- > > Key: ARQ-1327 > URL: https://issues.jboss.org/browse/ARQ-1327 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Jacoco > Affects Versions: jacoco_1.0.0.Alpha5 > Reporter: Tobias Seppenhauser > Fix For: jacoco_1.0.0.Alpha6 > > > In its pom.xml the _arquillian-jacoco_ extension is requiring the _asm_ library in version 3.1.1 > http://search.maven.org/remotecontent?filepath=org/jboss/arquillian/exten... > The _Jacoco_ libraries itself don't require a certain version of the _asm_ library. > http://search.maven.org/remotecontent?filepath=org/jacoco/org.jacoco.core... > But the problem is, that trying to run a coverage test with _arquillian-jacoco_ and using _asm_ in version 3.1.1 is leading to an {{IncompatibleClassChangeError}}. > The class {{org.jacoco.core.internal.flow.ClassProbesVisitor}} is extending {{org.objectweb.asm.ClassVisitor}}, which is an interface in 3.1.1 and an abstract class in the latest version (4.1). > {code} > public abstract class ClassProbesVisitor extends ClassVisitor { > ... > } > {code} > So, in my opion the asm-depencency should be changed to 4.1 to avoid this error. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1646) Add WildFly managed container

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-1646?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak resolved ARQ-1646. --------------------------------- Resolution: Done [Pushed upstream|https://github.com/arquillian/arquillian-extension-persistence/c...] > Add WildFly managed container > ----------------------------- > > Key: ARQ-1646 > URL: https://issues.jboss.org/browse/ARQ-1646 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha6 > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Priority: Trivial > Fix For: persistence_1.0.0.next > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1646) Add WildFly managed container

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-1646?page=com.atlassian.jira.plugin.s... ] Work on ARQ-1646 started by Bartosz Majsak. > Add WildFly managed container > ----------------------------- > > Key: ARQ-1646 > URL: https://issues.jboss.org/browse/ARQ-1646 > Project: Arquillian > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha6 > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Priority: Trivial > Fix For: persistence_1.0.0.next > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1572) Marry Persistence and JRebel extensions

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-1572?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak resolved ARQ-1572. --------------------------------- Resolution: Done [Pushed upstrem|https://github.com/arquillian/arquillian-extension-persistence/co...] > Marry Persistence and JRebel extensions > --------------------------------------- > > Key: ARQ-1572 > URL: https://issues.jboss.org/browse/ARQ-1572 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha6 > Reporter: Bernard Labno > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.next > > > JRebel extension currently does not pick up changes in datasets. > Here is how it works: > If there is no target/jrebel-temp/.../*.meta file for given deployment then it assumes user wants full redeploy. If such file is present then deployment is blocked and tests are run at once. > JRebel extension also checks if there is a rebel.xml file in the archive. If not then it generates such file based on exact content of the archive and explodes archive into target/jrebel-temp/*. > Now the problem is that if resource is not in the archive then it will not be included in generated rebel.xml and thus won't be picked up by JRebel. > Datasets are now automatically packed inside WEB-INF/lib/randomUUID.jar. JRebel will not substitute resources or classes from bundled libs. We could generate additional rebel.xml for that but I'd have to know what is the name of such archive and we would tightly couple both extensions. > It would be easiest if Persistence ext would pack datasets directly into WE-INF/classes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues March 2014