You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Antoine Levy-Lambert (JIRA)" <ji...@apache.org> on 2008/02/05 23:33:08 UTC

[jira] Created: (IVY-717) ivy-resolve fails when a project has different dependencies in different branches

ivy-resolve fails when a project has different dependencies in different branches
---------------------------------------------------------------------------------

                 Key: IVY-717
                 URL: https://issues.apache.org/jira/browse/IVY-717
             Project: Ivy
          Issue Type: Bug
          Components: Ant
         Environment: Solaris, JDK 1.5
            Reporter: Antoine Levy-Lambert
             Fix For: 2.0.0-alpha-2


The scenario is the following :

we build on the same server the project foo or the organization wombat in two branches called 1 and 2

in branch 2 foo is dependent upon bar which is also from the organization wombat

in branch 1 foo has no dependencies

if we do a build in the branch 2, then attempt to build in branch 1 without cleaning the cache, we are getting an unresolved dependency to bar, which does not exist in the branch 1.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (IVY-717) ivy-resolve fails when a project has different dependencies in different branches

Posted by "Xavier Hanin (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/IVY-717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Xavier Hanin updated IVY-717:
-----------------------------

    Fix Version/s: 2.0

> ivy-resolve fails when a project has different dependencies in different branches
> ---------------------------------------------------------------------------------
>
>                 Key: IVY-717
>                 URL: https://issues.apache.org/jira/browse/IVY-717
>             Project: Ivy
>          Issue Type: Bug
>          Components: Ant
>    Affects Versions: 2.0.0-alpha-2
>         Environment: Solaris, JDK 1.5
>            Reporter: Antoine Levy-Lambert
>             Fix For: 2.0
>
>
> The scenario is the following :
> we build on the same server the project foo or the organization wombat in two branches called 1 and 2
> in branch 2 foo is dependent upon bar which is also from the organization wombat
> in branch 1 foo has no dependencies
> if we do a build in the branch 2, then attempt to build in branch 1 without cleaning the cache, we are getting an unresolved dependency to bar, which does not exist in the branch 1.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (IVY-717) ivy-resolve fails when a project has different dependencies in different branches

Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/IVY-717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12566383#action_12566383 ] 

Maarten Coene commented on IVY-717:
-----------------------------------

You can using the cacheIvyPattern and cacheArtifactPattern attributes in you settings file.
More information can be found here: http://ant.apache.org/ivy/history/latest-milestone/configuration/conf.html

> ivy-resolve fails when a project has different dependencies in different branches
> ---------------------------------------------------------------------------------
>
>                 Key: IVY-717
>                 URL: https://issues.apache.org/jira/browse/IVY-717
>             Project: Ivy
>          Issue Type: Bug
>          Components: Ant
>    Affects Versions: 2.0.0-alpha-2
>         Environment: Solaris, JDK 1.5
>            Reporter: Antoine Levy-Lambert
>
> The scenario is the following :
> we build on the same server the project foo or the organization wombat in two branches called 1 and 2
> in branch 2 foo is dependent upon bar which is also from the organization wombat
> in branch 1 foo has no dependencies
> if we do a build in the branch 2, then attempt to build in branch 1 without cleaning the cache, we are getting an unresolved dependency to bar, which does not exist in the branch 1.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (IVY-717) ivy-resolve fails when a project has different dependencies in different branches

Posted by "Antoine Levy-Lambert (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/IVY-717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565941#action_12565941 ] 

Antoine Levy-Lambert commented on IVY-717:
------------------------------------------

Hello Maarten, 

how do I specify my cache patterns ?

Also, I found out that we have published in the branch 1 something which mentions a dependency to a module which is new in branch 2. This is the root cause of what I am explaining above. Cleaning the cache in this case does not help unfortunately.

Regards,

Antoine

> ivy-resolve fails when a project has different dependencies in different branches
> ---------------------------------------------------------------------------------
>
>                 Key: IVY-717
>                 URL: https://issues.apache.org/jira/browse/IVY-717
>             Project: Ivy
>          Issue Type: Bug
>          Components: Ant
>         Environment: Solaris, JDK 1.5
>            Reporter: Antoine Levy-Lambert
>             Fix For: 2.0.0-alpha-2
>
>
> The scenario is the following :
> we build on the same server the project foo or the organization wombat in two branches called 1 and 2
> in branch 2 foo is dependent upon bar which is also from the organization wombat
> in branch 1 foo has no dependencies
> if we do a build in the branch 2, then attempt to build in branch 1 without cleaning the cache, we are getting an unresolved dependency to bar, which does not exist in the branch 1.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Assigned: (IVY-717) ivy-resolve fails when a project has different dependencies in different branches

Posted by "Xavier Hanin (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/IVY-717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Xavier Hanin reassigned IVY-717:
--------------------------------

    Assignee: Xavier Hanin

> ivy-resolve fails when a project has different dependencies in different branches
> ---------------------------------------------------------------------------------
>
>                 Key: IVY-717
>                 URL: https://issues.apache.org/jira/browse/IVY-717
>             Project: Ivy
>          Issue Type: Bug
>          Components: Ant
>    Affects Versions: 2.0.0-alpha-2
>         Environment: Solaris, JDK 1.5
>            Reporter: Antoine Levy-Lambert
>            Assignee: Xavier Hanin
>             Fix For: 2.0
>
>
> The scenario is the following :
> we build on the same server the project foo or the organization wombat in two branches called 1 and 2
> in branch 2 foo is dependent upon bar which is also from the organization wombat
> in branch 1 foo has no dependencies
> if we do a build in the branch 2, then attempt to build in branch 1 without cleaning the cache, we are getting an unresolved dependency to bar, which does not exist in the branch 1.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (IVY-717) ivy-resolve fails when a project has different dependencies in different branches

Posted by "Xavier Hanin (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/IVY-717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Xavier Hanin resolved IVY-717.
------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 2.0)
                   2.0-RC1

I've added a unit test, changed the default cache patterns, which fixed the problem. 

> ivy-resolve fails when a project has different dependencies in different branches
> ---------------------------------------------------------------------------------
>
>                 Key: IVY-717
>                 URL: https://issues.apache.org/jira/browse/IVY-717
>             Project: Ivy
>          Issue Type: Bug
>          Components: Ant
>    Affects Versions: 2.0.0-alpha-2
>         Environment: Solaris, JDK 1.5
>            Reporter: Antoine Levy-Lambert
>            Assignee: Xavier Hanin
>             Fix For: 2.0-RC1
>
>
> The scenario is the following :
> we build on the same server the project foo or the organization wombat in two branches called 1 and 2
> in branch 2 foo is dependent upon bar which is also from the organization wombat
> in branch 1 foo has no dependencies
> if we do a build in the branch 2, then attempt to build in branch 1 without cleaning the cache, we are getting an unresolved dependency to bar, which does not exist in the branch 1.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (IVY-717) ivy-resolve fails when a project has different dependencies in different branches

Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/IVY-717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565922#action_12565922 ] 

Maarten Coene commented on IVY-717:
-----------------------------------

I don't know if it will make a difference, but my first guess is that you need to include [branch] in your cache patterns for Ivy files and artifacts to workaround this problem.

> ivy-resolve fails when a project has different dependencies in different branches
> ---------------------------------------------------------------------------------
>
>                 Key: IVY-717
>                 URL: https://issues.apache.org/jira/browse/IVY-717
>             Project: Ivy
>          Issue Type: Bug
>          Components: Ant
>         Environment: Solaris, JDK 1.5
>            Reporter: Antoine Levy-Lambert
>             Fix For: 2.0.0-alpha-2
>
>
> The scenario is the following :
> we build on the same server the project foo or the organization wombat in two branches called 1 and 2
> in branch 2 foo is dependent upon bar which is also from the organization wombat
> in branch 1 foo has no dependencies
> if we do a build in the branch 2, then attempt to build in branch 1 without cleaning the cache, we are getting an unresolved dependency to bar, which does not exist in the branch 1.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (IVY-717) ivy-resolve fails when a project has different dependencies in different branches

Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/IVY-717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maarten Coene updated IVY-717:
------------------------------

    Affects Version/s: 2.0.0-alpha-2
        Fix Version/s:     (was: 2.0.0-alpha-2)

> ivy-resolve fails when a project has different dependencies in different branches
> ---------------------------------------------------------------------------------
>
>                 Key: IVY-717
>                 URL: https://issues.apache.org/jira/browse/IVY-717
>             Project: Ivy
>          Issue Type: Bug
>          Components: Ant
>    Affects Versions: 2.0.0-alpha-2
>         Environment: Solaris, JDK 1.5
>            Reporter: Antoine Levy-Lambert
>
> The scenario is the following :
> we build on the same server the project foo or the organization wombat in two branches called 1 and 2
> in branch 2 foo is dependent upon bar which is also from the organization wombat
> in branch 1 foo has no dependencies
> if we do a build in the branch 2, then attempt to build in branch 1 without cleaning the cache, we are getting an unresolved dependency to bar, which does not exist in the branch 1.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.