You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Bisser Peshev (JIRA)" <ji...@apache.org> on 2017/09/09 23:07:02 UTC

[jira] [Commented] (MJAR-138) jar:test-jar is skipped when maven.test.skip=true

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

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

We just encountered this issue in Maven 3.3.3. Our builds usually take over an hour, so, to save time, the sandbox builds always run with -Dmaven.test.skip=true. But because of this, the test-jar artifacts don't get created, yet each test-jar dependency is enforced (even though it's test-scoped, and even though maven.test.skip is true), so the build breaks.

I agree with the above comments that this is a bug and should be fixed. If -Dmaven.test.skip=true skips the creation of the test-jar artifact, it should also skip enforcing the dependencies on that tets-jar artifact.

> 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)