ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Ondrejko (JIRA)" <j...@apache.org>
Subject [jira] [Created] (IVYDE-317) IvyDE classpath containers become empty on eclipse/MyEclipse startup
Date Tue, 14 Aug 2012 21:42:38 GMT
Michael Ondrejko created IVYDE-317:
--------------------------------------

             Summary: 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 Workspace" for the IvyDE
classpath containers, we consistently see that containers become empty in our projects. When
this occurs, it may be as simple as performing an Ivy -> Refresh (or combination of Ivy->Refresh,
Ivy->Resolve, and file Refresh). However, it may also require removing and re-adding the
classpath container manually.
  
While attempting to setup a test-case to demonstrate the problem, for some time, I was not
able to consistently reproduce any of the issues that I encountered. Some of the issues that
I did see along the way include
•         when changing ivy.xml directly, upon save only one (of two in my case) classpatch
containers would be updated to reflect the changes
•         when importing a project, sometimes one or more/all classpath containers would
not be created. A manual Ivy->refresh was required
•         losing the export setting on one of the Ivy classpath containers
•         random disappearing IvyDE classpath containers
  
What I eventually found is that in our application project environment, we have Eclipse set
to refresh files on startup. When I set this in my test environment, I consistently see the
behavior described where IvyDE classpath containers disappear on eclipse startup. Note that
I have Ivy set to “Do Nothing” and “Refresh” and both have consistently resulted in
the issue.
  
I have attached the sample projects from my investigation. Unfortunately, I was unable to
include the eclipse workspace itself due to file size limitations. I believe the only significant
change in the eclipse environment is to set Refresh on startup in General->Startup and
Shutdown. Let me know if you have any other questions.
  
Thanks and I hope this helps you resolve the issue more quickly.

---

We've found it gets worse with "Resolve in Workspace" active. Michael 
is actively working on a test case that doesn't require us to send you 
our entire codebase. :)

---

It appears that when I shut down and restart Eclipse the Ivy Classpath Container 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 Resolve when I bring up Eclipse.

What we'd like to see is that the Ivy Classpath Container actually persist its contents, even
between Eclipse restarts. So that when Eclipse comes up, no resolve is necessary. And at times,
I really don't want to do a resolve, 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 Launch, or do a manual
resolve. This usually also causes an entire rebuild of 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 either deleted from the workspace, or another
resolve is done?

It is supposed to work. But like you I have noticed that sometimes it looses its content too,
which is boring me too. I have never took time to investigate though.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message