[arquillian-issues] [JBoss JIRA] (ARQ-1986) Jacoco extesion creates empty manifest entries removing the ones present in the archive
Alexandros Trifyllis (JIRA)
issues at jboss.org
Mon Oct 12 03:16:01 EDT 2015
[ https://issues.jboss.org/browse/ARQ-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117251#comment-13117251 ]
Alexandros Trifyllis commented on ARQ-1986:
-------------------------------------------
I did not have time to try to recreate the issue with a simple project and pom. I suppose that the issue occurs because of some configuration in my pom. I am posting it here for reference:
{code:xml}
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>gr.dias</groupId>
<artifactId>mybank-parent</artifactId>
<version>0.0.1-SNAPSHOT</version>
<relativePath>../mybank-parent/pom.xml</relativePath>
</parent>
<artifactId>mybank-test</artifactId>
<name>mybank-test</name>
<dependencyManagement>
<dependencies>
<!-- This bom is used to resolve versions of shrinkwrap dependencies.
It must be declared BEFORE the arquillian-bom -->
<dependency>
<groupId>org.jboss.shrinkwrap.resolver</groupId>
<artifactId>shrinkwrap-resolver-bom</artifactId>
<version>2.2.0</version>
<type>pom</type>
<scope>import</scope>
</dependency>
<dependency>
<groupId>org.jboss.arquillian</groupId>
<artifactId>arquillian-bom</artifactId>
<version>1.1.8.Final</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>
<dependencies>
<!-- needed at compile time because the integration tests use directly
the DAOs which referece the EntityManager -->
<dependency>
<groupId>javax</groupId>
<artifactId>javaee-api</artifactId>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>gr.dias</groupId>
<artifactId>mybank-ws</artifactId>
<version>${project.version}</version>
<!-- this is how we get access to the classes of the war -->
<classifier>classes</classifier>
<scope>test</scope>
</dependency>
<!-- Arquillian integration with jUnit -->
<dependency>
<groupId>org.jboss.arquillian.junit</groupId>
<artifactId>arquillian-junit-container</artifactId>
<scope>test</scope>
</dependency>
<!--Shrinkwrap resolvers are used to resolve e.g. Maven dependencies from
pom file -->
<dependency>
<groupId>org.jboss.shrinkwrap.resolver</groupId>
<artifactId>shrinkwrap-resolver-depchain</artifactId>
<type>pom</type>
<scope>test</scope>
</dependency>
<!-- This is how to use a Wildfly that is already running to deploy the
war -->
<dependency>
<groupId>org.wildfly.arquillian</groupId>
<artifactId>wildfly-arquillian-container-remote</artifactId>
<version>1.0.0.CR1</version>
<scope>test</scope>
</dependency>
<!-- CXF dependencies needed for client to work -->
<dependency>
<groupId>org.apache.cxf</groupId>
<artifactId>cxf-rt-frontend-simple</artifactId>
</dependency>
<dependency>
<groupId>org.jboss.ws.cxf</groupId>
<artifactId>jbossws-cxf-client</artifactId>
<scope>test</scope>
<!-- ecxlusion needed because a newer version is referenced in wildfly-arquillian-container-remote -->
<exclusions>
<exclusion>
<artifactId>jboss-logging</artifactId>
<groupId>org.jboss.logging</groupId>
</exclusion>
<exclusion>
<artifactId>asm</artifactId>
<groupId>asm</groupId>
</exclusion>
</exclusions>
</dependency>
<!-- <dependency>
<groupId>org.jboss.arquillian.extension</groupId>
<artifactId>arquillian-jacoco</artifactId>
<version>1.0.0.Alpha8</version>
<scope>test</scope>
</dependency> -->
<dependency>
<groupId>org.jacoco</groupId>
<artifactId>org.jacoco.core</artifactId>
<version>0.7.4.201502262128</version>
<scope>test</scope>
</dependency>
</dependencies>
<build>
<plugins>
<!-- Specify maven war plugin version because previous versions do not
work well with arquillian -->
<plugin>
<artifactId>maven-war-plugin</artifactId>
<version>2.6</version>
</plugin>
</plugins>
<!-- One way of including META-INF directory of generated project (wsdls,
xsds, etc). This is needed for the ws clients to work. It is not the best
way to achieve that (see http://jlorenzen.blogspot.gr/2010/07/sharing-resources-in-maven.html) -->
<testResources>
<testResource>
<directory>../mybank-generated/src/main/resources</directory>
</testResource>
<!-- we must specify the default location because it is overriden -->
<testResource>
<directory>src/test/resources</directory>
</testResource>
</testResources>
</build>
</project>
{code}
> Jacoco extesion creates empty manifest entries removing the ones present in the archive
> ---------------------------------------------------------------------------------------
>
> Key: ARQ-1986
> URL: https://issues.jboss.org/browse/ARQ-1986
> Project: Arquillian
> Issue Type: Bug
> Components: Extension - Jacoco
> Affects Versions: jacoco_1.0.0.Alpha8
> Reporter: Alexandros Trifyllis
> Priority: Minor
>
> The ShrinkWrap generated war file contains an empty MANIFEST.MF instead of the one specified during archive creation
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the arquillian-issues
mailing list