ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Becheanu (JIRA)" <j...@apache.org>
Subject [jira] Commented: (IVYDE-148) Turning on retrieve after resolve with a disabled configuration causes IvyDE to begin throwing exceptions during resolve.
Date Fri, 02 Jan 2009 20:25:44 GMT

    [ https://issues.apache.org/jira/browse/IVYDE-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660381#action_12660381
] 

Daniel Becheanu commented on IVYDE-148:
---------------------------------------

I think this is solved in 

http://issues.apache.org/jira/browse/IVYDE-140

Try building from trunk and see if you still see the problem. 

> Turning on retrieve after resolve with a disabled configuration causes IvyDE to begin
throwing exceptions during resolve.
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: IVYDE-148
>                 URL: https://issues.apache.org/jira/browse/IVYDE-148
>             Project: IvyDE
>          Issue Type: Bug
>    Affects Versions: 2.0.0.beta1
>            Reporter: Adam Karl
>
> I have a project with several enabled configurations and a few disabled configurations,
meaning that I do not want those artifacts downloaded by IvyDE (they are purely for packaging
and developers in Eclipse don't need them).  If I have retrieve after resolve turned on IvyDE
starts throwing exceptions such as the text below.
> Error while resolving dependencies for ivy.xml
> problem during retrieve of organization#myprojectname: java.lang.IllegalStateException:
Report file 'C:\Documents and Settings\username\.ivy2\cache\organization-myprojectname-disabledconfigname.xml'
does not exist.
> problem during retrieve of organization#myprojectname: java.lang.IllegalStateException:
Report file 'C:\Documents and Settings\username\.ivy2\cache\organization- myprojectname-disabledconfigname.xml'
does not exist.
> - NOTE: I do not think this bug was evident in 2.0.0alpha 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