|[CDO] Workspace metadata filling up with CDO Javadocs [message #1402231]
||Wed, 16 July 2014 18:22
|| Christian W. Damus
Registered: July 2009
I don't know whether this is a problem in the CDO SDK or PDE or what,
but I'm only seeing it with CDO, so I'm asking here whether anyone else
has observed this phenomenon and knows what I can do to prevent it.
In the workspace metadata area, amongst so much else, PDE keeps caches
of stuff for launch configurations, including (it would seem) the
Javadoc resources (HTML, CSS, and images) for APIs included in the
JUnit launch configurations. Every one of my JUnit launch
configurations caches a copy of the CDO Javadocs in various hidden
".cp" folders in the org.eclipse.osgi cache area. For example, there
are 42 distinct occurrences of UserPassword.html, e.g.
As far as I can tell, I am only getting this with CDO (perhaps because
CDO is the only project that includes Javadocs in its doc plug-ins?).
I have the CDO SDK installed in my PDE target in the usual way; it is
not checked out in source projects in the workspace, so the problem is
not that I am somehow generating these Javadocs. They are being copied
by PDE out of the CDO doc plug-in JARs.
Oddly, this doesn't happen with launch configurations of workbench
type, only JUnit, even though my workbench launch configs also include
the org.eclipse.emf.cdo.doc plug-in.
So, how to resolve this useless bloat of my workspace metadata
directory? Is there something I need to do to tell PDE not to copy
these resources into its OSGi classpath cache? Or should the CDO doc
plug-ins not include the Javadocs in the JARs that it distributes? I
can delete all of these files, but they are just copied again the next
time I launch a test suite ...
I'm using everything at Luna SR0 version: my development Eclipse
workbench and CDO in my PDE target.
Powered by FUDForum
. Page generated in 0.01909 seconds