| FW: [mylar-dev] Depending on Mylar plugins |
|
Hi It sounds like a good idea for us to move
to the packaging you suggest in order to make it possible to use the Mylar
plug-ins as JAR libraries without relying on the OSGi plug-in mechanism.
Please submit a new bug report for this (it should be a quick fix once the dust
from 0.6 and Callisto has settled). Mik From:
mylar-dev-bounces@xxxxxxxxxxx [mailto:mylar-dev-bounces@xxxxxxxxxxx] On Behalf Of Hi (I'm using Eclipse 3.2RC7 with Mylar
0.5.3.) I have a plugin project that I have made
dependent on Mylar core (I added the org.eclipse.mylar.core dependency to the
plugin.xml/manifest). But when I try to access mylar code - e.g.
by calling MylarPlugin.getDefault() I get a compilation error because it can't find any of the Mylar
classes. I think the problem is because the
org.eclipse.mylar.core_0.5.3.jar file contains the nested jar file
mylar-core.jar (which contains the class files). This nesting of jar
files seems to prevent me from accessing the Mylar classes. I extracted
the contents of the org.eclipse.mylar.core_0.5.3.jar file into a directory
inside of my eclipse/plugins and removed the org.eclipse.mylar.core_0.5.3.jar
file and it works. Have you or anyone else seen this problem
before? Does anyone know what the Eclipse
convention is on packaging plugin jars? I looked at a few other well know
plugins - EMF, PEF, and UI, and they all directly contain the class files (they
don't have nested jar files). Thanks,
|