Return-Path: X-Original-To: apmail-ant-notifications-archive@minotaur.apache.org Delivered-To: apmail-ant-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0231C44BA for ; Wed, 8 Jun 2011 09:38:22 +0000 (UTC) Received: (qmail 50067 invoked by uid 500); 8 Jun 2011 09:38:21 -0000 Delivered-To: apmail-ant-notifications-archive@ant.apache.org Received: (qmail 50038 invoked by uid 500); 8 Jun 2011 09:38:21 -0000 Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ant.apache.org Delivered-To: mailing list notifications@ant.apache.org Received: (qmail 50031 invoked by uid 99); 8 Jun 2011 09:38:21 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Jun 2011 09:38:21 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Jun 2011 09:38:19 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id C1CE81086A2 for ; Wed, 8 Jun 2011 09:37:58 +0000 (UTC) Date: Wed, 8 Jun 2011 09:37:58 +0000 (UTC) From: =?utf-8?Q?Nicolas_Lalev=C3=A9e_=28JIRA=29?= To: notifications@ant.apache.org Message-ID: <599025538.2737.1307525878775.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1330678699.181.1307449138854.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (IVYDE-283) Helios and ivyDe resolve/startup issue MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/IVYDE-283?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13045= 863#comment-13045863 ]=20 Nicolas Lalev=C3=A9e commented on IVYDE-283: --------------------------------------- You're probably right, no circular dependency seems to be involved. What do you see in the [Ivy console|http://ant.apache.org/ivy/ivyde/history= /latest-milestone/console.html] while the resolve is apparently stuck ? The stack of Eclipse would help knowing what is going on too. To do that, g= et the process id of Eclipse and run 'jstack PROCESSID' while you see the r= esolve taking 100% of the cpu. It would be great if you could attach here t= he output of that command. > 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. Ho= wever I also get the problem when starting up eclipse=20 > It seems to happen when I have the same project checkout twice. I have lo= oked inside the log file in .metadata, but I couldn=C2=B4t find any error m= essages.I have all of the ivy-files inside the project. The setup is like t= he one in defect ivyde-256 > I have also tried it on 2 different machines, where one of them was a sin= gle core. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira