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

Kim edited comment on IVYDE-283 at 6/8/11 9:11 AM:
---------------------------------------------------

Hi

I don't understand the question 

   What does the ivy.xml of the project checkout twice look like ?

I have added my ivy.xml and that is the one I have checked out twice in 2 
different eclipse projects. I don't belive that there is any recursive 
dependencies. Is there anyway to check this. Also this ivy.xml file works fine 
with latest ivyde release and eclipse galileo

      was (Author: hhb97b):
    Hi

I don't understand the question 

   What does the ivy.xml of the project checkout twice look like ?

I have added my ivy.xml and that is the one I have checked out twice in 2 
different eclipse projects.
  
> Helios and ivyDe resolve/startup  issue
> ---------------------------------------
>
>                 Key: IVYDE-283
>                 URL: https://issues.apache.org/jira/browse/IVYDE-283
>             Project: IvyDE
>          Issue Type: Bug
>          Components: workspace resolver
>    Affects Versions: trunk
>         Environment: apache-ivyde-2.2.0.201104250538-hudson-186
> ivy 2.2.0RC
> Helios sr2
> 2 computer
>            Reporter: Kim
>              Labels: helios, resolve
>         Attachments: ivy.xml
>
>
> I'm having problem with ivyDE and Eclipse Helios Sr2. The problem is that the 
> cpu is used 100% and the process is stuck, when resolved is runned. However I 
> also get the problem when starting up eclipse 
> It seems to happen when I have the same project checkout twice. I have looked 
> inside the log file in .metadata, but I couldn“t find any error messages.I 
> have all of the ivy-files inside the project. The setup is like the one in 
> defect ivyde-256
> I have also tried it on 2 different machines, where one of them was a single 
> core.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to