You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Aleksey Solntsev (JIRA)" <ji...@codehaus.org> on 2007/12/12 16:23:58 UTC

[jira] Created: (MNG-3319) Reactor cannot detect artifact with exist in project and has test-jar type and test scope

Reactor cannot detect artifact with exist in project and has test-jar type and test scope
-----------------------------------------------------------------------------------------

                 Key: MNG-3319
                 URL: http://jira.codehaus.org/browse/MNG-3319
             Project: Maven 2
          Issue Type: Bug
          Components: Plugins and Lifecycle, Reactor and workspace
    Affects Versions: 2.0.8
            Reporter: Aleksey Solntsev


The fix  for MNG-2277 has resolved a lot of problems, first of all for release procedure.
But we will still has the problem with detecting artifact like this. 

        <dependency>
            <groupId>agillic.models</groupId>
            <artifactId>agillic-processmodel</artifactId>
            <version>${project.version}</version>
            <type>test-jar</type>
            <scope>test</scope>
        </dependency>


-- 
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] Closed: (MNG-3319) Reactor cannot detect artifact with exist in project and has test-jar type and test scope

Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-3319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason van Zyl closed MNG-3319.
------------------------------

       Resolution: Incomplete
    Fix Version/s:     (was: 2.2.x)

> Reactor cannot detect artifact with exist in project and has test-jar type and test scope
> -----------------------------------------------------------------------------------------
>
>                 Key: MNG-3319
>                 URL: http://jira.codehaus.org/browse/MNG-3319
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Plugins and Lifecycle, Reactor and workspace
>    Affects Versions: 2.0.8
>            Reporter: Aleksey Solntsev
>
> The fix  for MNG-2277 has resolved a lot of problems, first of all for release procedure.
> But we will still has the problem with detecting artifact like this. 
>         <dependency>
>             <groupId>agillic.models</groupId>
>             <artifactId>agillic-processmodel</artifactId>
>             <version>${project.version}</version>
>             <type>test-jar</type>
>             <scope>test</scope>
>         </dependency>

-- 
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-3319) Reactor cannot detect artifact with exist in project and has test-jar type and test scope

Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MNG-3319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=204578#action_204578 ] 

Jason van Zyl commented on MNG-3319:
------------------------------------

Provide more of an explanation, or sample project.

> Reactor cannot detect artifact with exist in project and has test-jar type and test scope
> -----------------------------------------------------------------------------------------
>
>                 Key: MNG-3319
>                 URL: http://jira.codehaus.org/browse/MNG-3319
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Plugins and Lifecycle, Reactor and workspace
>    Affects Versions: 2.0.8
>            Reporter: Aleksey Solntsev
>
> The fix  for MNG-2277 has resolved a lot of problems, first of all for release procedure.
> But we will still has the problem with detecting artifact like this. 
>         <dependency>
>             <groupId>agillic.models</groupId>
>             <artifactId>agillic-processmodel</artifactId>
>             <version>${project.version}</version>
>             <type>test-jar</type>
>             <scope>test</scope>
>         </dependency>

-- 
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] Updated: (MNG-3319) Reactor cannot detect artifact with exist in project and has test-jar type and test scope

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-3319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated MNG-3319:
------------------------------

    Fix Version/s: 2.0.x

> Reactor cannot detect artifact with exist in project and has test-jar type and test scope
> -----------------------------------------------------------------------------------------
>
>                 Key: MNG-3319
>                 URL: http://jira.codehaus.org/browse/MNG-3319
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Plugins and Lifecycle, Reactor and workspace
>    Affects Versions: 2.0.8
>            Reporter: Aleksey Solntsev
>             Fix For: 2.0.x
>
>
> The fix  for MNG-2277 has resolved a lot of problems, first of all for release procedure.
> But we will still has the problem with detecting artifact like this. 
>         <dependency>
>             <groupId>agillic.models</groupId>
>             <artifactId>agillic-processmodel</artifactId>
>             <version>${project.version}</version>
>             <type>test-jar</type>
>             <scope>test</scope>
>         </dependency>

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