[jira] Created: (MNG-4192) When using maven.test.skip it does verify the test dependency...

["Martin Poitras (JIRA)" <ji...@codehaus.org>]

When using maven.test.skip it does verify the test dependency...
----------------------------------------------------------------

                 Key: MNG-4192
                 URL: http://jira.codehaus.org/browse/MNG-4192
             Project: Maven 2
          Issue Type: Improvement
          Components: Dependencies
    Affects Versions: 2.0.9
         Environment: Windows
            Reporter: Martin Poitras
            Priority: Minor


I use a common jar for my test environment. This jar is build during test phase. Some module need it and include it dependency and specify:
<type>test-jar</type>
<scope>test</scope>

Initially, in a fresh environment, if I do "mvn install -Dmaven.test.skip=true" the module that depends on this test-jar will complain about the missing dependency.
But since I don't want the test to run I think it should not complain. It should compile package and install..?

Thanks



-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (MNG-4192) When using maven.test.skip it does verify the test dependency...

["Benjamin Bentmann (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MNG-4192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=179701#action_179701 ] 

Benjamin Bentmann commented on MNG-4192:
----------------------------------------

This is in part a major design issue. The Maven core doesn't not know about skipping plugins, it are the plugin themselves that evalute properties like "maven.test.skip" and simply quit immediately. However, the resolution of dependencies for these plugins happens by the core and since the core doesn't know about skipping, it always resolves dependencies.

"mvn install -D skipTests" should serve as a workaround. It still skips test execution, but causes the tests to be compiled and packaged into the test JAR.

> When using maven.test.skip it does verify the test dependency...
> ----------------------------------------------------------------
>
>                 Key: MNG-4192
>                 URL: http://jira.codehaus.org/browse/MNG-4192
>             Project: Maven 2
>          Issue Type: Improvement
>          Components: Dependencies
>    Affects Versions: 2.0.9
>         Environment: Windows
>            Reporter: Martin Poitras
>            Priority: Minor
>
> I use a common jar for my test environment. This jar is build during test phase. Some module need it and include it dependency and specify:
> <type>test-jar</type>
> <scope>test</scope>
> Initially, in a fresh environment, if I do "mvn install -Dmaven.test.skip=true" the module that depends on this test-jar will complain about the missing dependency.
> But since I don't want the test to run I think it should not complain. It should compile package and install..?
> Thanks

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira