You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Parag Srivastava (JIRA)" <ji...@codehaus.org> on 2009/05/04 17:55:44 UTC
[jira] Issue Comment Edited: (MNG-2975) test scope does not work
with pom dependency
[ http://jira.codehaus.org/browse/MNG-2975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=175044#action_175044 ]
Parag Srivastava edited comment on MNG-2975 at 5/4/09 10:53 AM:
----------------------------------------------------------------
I am also facing the same problem. It will be good if the dependency poms worked with test scope as well because we'll be able to have a common definition of the test dependency groups as well.
I understand that the tests are private to the artifact but it is also about consistency and avoiding repetition.
In my projects, I need a set of 3-4 Glassfish appserver dependencies to run test cases. Having the developers add them in each project is not very practical, especially when we have seen the advantages of dependency groups with compile scope and need the same set used consistently everywhere for running the tests.
Can this bug be opened again for fixing?
was (Author: paragsrivastava):
I am also facing the same problem. It will be good if the dependency poms worked with test scope as well because we'll be able to have a common definition of the test dependency groups as well.
I understand that the tests are private to the artifact but is also about consistency and avoiding repetition.
In my projects, I need a set of 3-4 Glassfish appserver dependencies to run test cases. Having the developers add them in each project is not very practical, especially when we have seen the advantages of dependency groups with compile scope and need the same set used consistently everywhere for running the tests.
Can this bug be opened again for fixing?
> test scope does not work with pom dependency
> --------------------------------------------
>
> Key: MNG-2975
> URL: http://jira.codehaus.org/browse/MNG-2975
> Project: Maven 2
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 2.0.4
> Environment: jdk1.5
> Reporter: Franck HUGOT
> Assignee: Brett Porter
>
> I have a project A with pom packaging (<packaging>pom</packaging>) that use this dependency :
> <dependency>
> <groupId>org.springframework</groupId>
> <artifactId>spring-mock</artifactId>
> <version>2.0</version>
> <scope>test</scope>
> </dependency>
> In project B , I try to use the project A like a dependency like this :
> <dependency>
> <groupId>xxx</groupId>
> <artifactId>SOFFWK_LIBS</artifactId>
> <version>1.0</version>
> <type>pom</type>
> </dependency>
> I don't get the spring-mock transitive dependency when I compile or test project B.
> Is it because it has a test scope?
--
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