ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maarten Coene (JIRA)" <j...@apache.org>
Subject [jira] Commented: (IVY-717) ivy-resolve fails when a project has different dependencies in different branches
Date Tue, 05 Feb 2008 22:45:08 GMT

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


Mime
View raw message