maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bisser Peshev (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MJAR-138) jar:test-jar is skipped when maven.test.skip=true
Date Sun, 10 Sep 2017 16:25:02 GMT

    [ https://issues.apache.org/jira/browse/MJAR-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16160394#comment-16160394
] 

Bisser Peshev commented on MJAR-138:
------------------------------------

Well, there's a workaround with Maven profiles. The test-jar dependencies will be declared
only if maven.test.skip is not true:

{code:xml}
      <profile>
         <activation>
            <property>
               <name>maven.test.skip</name>
               <value>!true</value>
            </property>
         </activation>
         <dependencies>
            <dependency>
               <groupId>com.acme.project</groupId>
               <artifactId>my-artifact</artifactId>
               <type>test-jar</type>
               <version>${project.version}</version>
               <scope>test</scope>
            </dependency>
         </dependencies>
      </profile>
{code}

Ugly, but at least works.


> jar:test-jar is skipped when maven.test.skip=true
> -------------------------------------------------
>
>                 Key: MJAR-138
>                 URL: https://issues.apache.org/jira/browse/MJAR-138
>             Project: Maven JAR Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.3.1
>         Environment: jar:test-jar
>            Reporter: Andrew Hughes
>             Fix For: more-investigation
>
>         Attachments: MJAR-138-maven-jar-plugin.patch
>
>
> Not sure if this is a bug or improvement...
> Example:
> * ./pom.xml
> * ./moduleA/pom.xml
> * ./moduleB/pom.xml
> Situation:
> * moduleA produces moduleA-1.2.3-test.jar with the jar:test-jar goal
> * moduleB consumes moduleA-1.2.3-test.jar as a <dependency>...<scope>test</scope><dependency>
> Problem:
> * When -Dmaven.test.skip=true the moduleA-1.2.3-test.jar is never built.
> * Then when moduleB tries to build, it's moduleA-1.2.3-test.jar dependency is unresolved.
FAIL! Even with -Dmaven.test.skip=true this will fail.
> You might argue that this is a bug with dependency resolution with -Dmaven.test.skip=true
- should a missing dependency @ test scope really fail the build??? It probably should - which
is why the bug is submitted here :)
> I've no idea what could be done to fix this either?
> ---
> p.s. for anyone with this bug the only workaround I can suggest is running another module...
> ./moduleA-test/pom.xml
> and have <dependency>...<artifactId>moduleA-test<artifactId>...<scope>test</scope></dependency>



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message