Last year org.eclipse.jdt.internal.core.PackageFragmentRoot.getHandleMemento(StringBuffer)
was changed to include the extra classpath attributes into the handle identifier.
this requires org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath()
to be called (at least it is called for now)
although e.g. subclasses have org.eclipse.jdt.internal.core.JarPackageFragmentRoot.extraAttributes
this leads to the problem that getHandleIdentifier cannot be called if the caller does not have the workspace lock that is needed for resolveClasspath
is this side effect of the change intended?
can this be done in a better way?
should we mimic the behaviour of getHandleIdentifier to avoid the problem?