Experience report with IvyDE trunk and "Resolve dependencies in workspace"

[Barry Kaplan <gr...@memelet.com>]

This is really great feature -- when it works. For reasons I can't quite
determine, the behavior is quite flakey. Sometimes the dependent project
will be add to the container, sometimes it will not. (I'm working with only
two projects, so my setup is simple for now.) 

Could be that the exception below is a clue. But it is not always generated.
I can add/remove my project dependency from ivy.xml and get only the info
the message that the deps were resolved (with no change in the classpath
container.) Hopefully I'll figure out the sequence of events that causes the
project to be added (and not added).

----
org.eclipse.core.internal.resources.ResourceException: The resource tree is
locked for modifications.
at
org.eclipse.core.internal.resources.WorkManager.checkIn(WorkManager.java:115)
at
org.eclipse.core.internal.resources.Workspace.prepareOperation(Workspace.java:1747)
at
org.eclipse.core.internal.resources.Resource.deleteMarkers(Resource.java:744)
at
org.apache.ivyde.eclipse.cpcontainer.IvyClasspathContainerConfiguration.setResolveStatus(IvyClasspathContainerConfiguration.java:340)
at
org.apache.ivyde.eclipse.cpcontainer.IvyClasspathContainerConfiguration.setConfStatus(IvyClasspathContainerConfiguration.java:328)
at
org.apache.ivyde.eclipse.cpcontainer.IvyClasspathContainerConfiguration.getModuleDescriptor(IvyClasspathContainerConfiguration.java:611)
at
org.apache.ivyde.eclipse.cpcontainer.IvyResolveJob.<init>(IvyResolveJob.java:113)
at
org.apache.ivyde.eclipse.cpcontainer.IvyClasspathContainer.computeClasspathEntries(IvyClasspathContainer.java:143)
at
org.apache.ivyde.eclipse.cpcontainer.IvyClasspathContainer.launchResolve(IvyClasspathContainer.java:168)
at
org.apache.ivyde.eclipse.cpcontainer.IvyClasspathInitializer.initialize(IvyClasspathInitializer.java:71)
at
org.eclipse.jdt.internal.core.JavaModelManager.initializeContainer(JavaModelManager.java:2371)
at
org.eclipse.jdt.internal.core.JavaModelManager$13.run(JavaModelManager.java:2301)
at
org.eclipse.jdt.internal.core.JavaModelManager.initializeAllContainers(JavaModelManager.java:2315)
at
org.eclipse.jdt.internal.core.JavaModelManager.getClasspathContainer(JavaModelManager.java:1679)
at org.eclipse.jdt.core.JavaCore.getClasspathContainer(JavaCore.java:2554)
at
org.eclipse.jdt.internal.core.JavaProject.resolveClasspath(JavaProject.java:2562)
at
org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath(JavaProject.java:1829)
at
org.eclipse.jdt.internal.core.DeltaProcessingState.initializeRoots(DeltaProcessingState.java:229)
at
org.eclipse.jdt.internal.core.DeltaProcessor.processResourceDelta(DeltaProcessor.java:1741)
at
org.eclipse.jdt.internal.core.DeltaProcessor.resourceChanged(DeltaProcessor.java:1923)
at
org.eclipse.jdt.internal.core.DeltaProcessingState.resourceChanged(DeltaProcessingState.java:410)
at
org.eclipse.core.internal.events.NotificationManager$2.run(NotificationManager.java:288)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at
org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:282)
at
org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:148)
at
org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:313)
at
org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1022)
at
org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:45)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

-- 
View this message in context: http://www.nabble.com/Experience-report-with-IvyDE-trunk-and-%22Resolve-dependencies-in-workspace%22-tp19134941p19134941.html
Sent from the ivy-user mailing list archive at Nabble.com.

Re: Experience report with IvyDE trunk and "Resolve dependencies in workspace"

[Nicolas Lalevée <ni...@hibnet.org>]

Le 24 août 08 à 23:52, Barry Kaplan a écrit :

>
> Well, it did take too long.
>
> The problem seemed to be due to my using the *released* beta ivy  
> plugin and
> the *trunk* ivyde plugin. Once I built the ivy plugin from trunk and
> deployed it, not only did the classpath container flakeyness go  
> away, a
> bunch of other minor issues also went away. Now I am very happy!

great it makes you happy, but the stack trace I saw doesn't look good  
at all.
And this should not be related to Ivy released or Ivy trunk. I have  
created IVYDE-116

By the way, thanks for trying the trunk version of IvyDE and send  
reports !

Nicolas

Re: Experience report with IvyDE trunk and "Resolve dependencies in workspace"

[Barry Kaplan <gr...@memelet.com>]

Well, it did take too long. 

The problem seemed to be due to my using the *released* beta ivy plugin and
the *trunk* ivyde plugin. Once I built the ivy plugin from trunk and
deployed it, not only did the classpath container flakeyness go away, a
bunch of other minor issues also went away. Now I am very happy!

cheers
-- 
View this message in context: http://www.nabble.com/Experience-report-with-IvyDE-trunk-and-%22Resolve-dependencies-in-workspace%22-tp19134941p19135234.html
Sent from the ivy-user mailing list archive at Nabble.com.