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 11953D2F0 for ; Sat, 18 Aug 2012 13:02:38 +0000 (UTC) Received: (qmail 49893 invoked by uid 500); 18 Aug 2012 13:02:38 -0000 Delivered-To: apmail-ant-notifications-archive@ant.apache.org Received: (qmail 49843 invoked by uid 500); 18 Aug 2012 13:02:38 -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 49832 invoked by uid 99); 18 Aug 2012 13:02:38 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 18 Aug 2012 13:02:38 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 007892C5BE1 for ; Sat, 18 Aug 2012 13:02:37 +0000 (UTC) Date: Sun, 19 Aug 2012 00:02:37 +1100 (NCT) From: =?utf-8?Q?Nicolas_Lalev=C3=A9e_=28JIRA=29?= To: notifications@ant.apache.org Message-ID: <55709110.26652.1345294958002.JavaMail.jiratomcat@arcas> In-Reply-To: <1002282262.9968.1344980558136.JavaMail.jiratomcat@arcas> Subject: [jira] [Commented] (IVYDE-317) IvyDE classpath containers become empty on eclipse/MyEclipse startup MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/IVYDE-317?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13437= 316#comment-13437316 ]=20 Nicolas Lalev=C3=A9e commented on IVYDE-317: --------------------------------------- As far I could see the state a classpath container is maintained by Eclipse= itself. But for some reason, project open/close messes with it. I have ope= n an issue: https://bugs.eclipse.org/bugs/show_bug.cgi?id=3D387535 There is a workaround implementable in IvyDE, which is already done in the = Maven plugin for instance: make the plugin persist itself the containers co= ntents rather than relying on Eclipse's API. =20 > IvyDE classpath containers become empty on eclipse/MyEclipse startup > --------------------------------------------------------------------- > > Key: IVYDE-317 > URL: https://issues.apache.org/jira/browse/IVYDE-317 > Project: IvyDE > Issue Type: Bug > Components: classpath container > Affects Versions: 2.2.0.beta1 > Reporter: Michael Ondrejko > Priority: Blocker > > As J.C. mentioned, we have found that when we enable "Resolve in Workspac= e" for the IvyDE classpath containers, we consistently see that containers = become empty in our projects. When this occurs, it may be as simple as perf= orming an Ivy -> Refresh (or combination of Ivy->Refresh, Ivy->Resolve, and= file Refresh). However, it may also require removing and re-adding the cla= sspath container manually. > =20 > While attempting to setup a test-case to demonstrate the problem, for som= e time, I was not able to consistently reproduce any of the issues that I e= ncountered. Some of the issues that I did see along the way include > =E2=80=A2 when changing ivy.xml directly, upon save only one (of = two in my case) classpatch containers would be updated to reflect the chang= es > =E2=80=A2 when importing a project, sometimes one or more/all cla= sspath containers would not be created. A manual Ivy->refresh was required > =E2=80=A2 losing the export setting on one of the Ivy classpath c= ontainers > =E2=80=A2 random disappearing IvyDE classpath containers > =20 > What I eventually found is that in our application project environment, w= e have Eclipse set to refresh files on startup. When I set this in my test = environment, I consistently see the behavior described where IvyDE classpat= h containers disappear on eclipse startup. Note that I have Ivy set to =E2= =80=9CDo Nothing=E2=80=9D and =E2=80=9CRefresh=E2=80=9D and both have consi= stently resulted in the issue. > =20 > I have attached the sample projects from my investigation. Unfortunately,= I was unable to include the eclipse workspace itself due to file size limi= tations. I believe the only significant change in the eclipse environment i= s to set Refresh on startup in General->Startup and Shutdown. Let me know i= f you have any other questions. > =20 > Thanks and I hope this helps you resolve the issue more quickly. > --- > We've found it gets worse with "Resolve in Workspace" active. Michael=20 > is actively working on a test case that doesn't require us to send you=20 > our entire codebase. :) > --- > It appears that when I shut down and restart Eclipse the Ivy Classpath Co= ntainer loses its contents. I could swear sometimes it doesn't, but almost = always when I restart Eclipse, it is empty until it does an automatic Resol= ve when I bring up Eclipse. > What we'd like to see is that the Ivy Classpath Container actually persis= t its contents, even between Eclipse restarts. So that when Eclipse comes u= p, no resolve is necessary. And at times, I really don't want to do a resol= ve, because it will trigger download of stuff I really am not ready for yet= . I'd like to control when I resolve and get new stuff downloaded, so right= now the only choice I have is to either check the checkbox to Resolve on L= aunch, or do a manual resolve. This usually also causes an entire rebuild o= f the projects, which sucks, because that can take 10-40 minutes depending = on how good the hardware is. > So, is there a way to make the Classpath Container remember its contents,= even between Eclipse restarts, and never lose it until the project is eith= er deleted from the workspace, or another resolve is done? > It is supposed to work. But like you I have noticed that sometimes it loo= ses its content too, which is boring me too. I have never took time to inve= stigate though. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrato= rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp= a For more information on JIRA, see: http://www.atlassian.com/software/jira