Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [pde-build-dev] Unpacked versus packed plugins

Tom Huybrechts wrote:
Packed jars with embedded jars cannot be handled by the compiler.
You need to unpack those in your target platform.

That explains why the compilation fails. It does not explain why the self-hosting scenario fails when I have the plug-in imported into my workspace.

I'm trying to understand if the two problems (the compiler not handling embedded jars and the runtime not handling the imported plug-in) should be considered bugs in Eclipse or if the Subclipse team has misunderstood something. Also, for participation in Europa, http://wiki.eclipse.org/index.php?title=Europa_Simultaneous_Release, one of the "Should do" items is " "Projects should have jar'ed plug-ins because this is good Eclipse citizenship.". Would it be fair say that one of the requirements on Eclipse in that case must be that they are handled properly? At present, that doesn't seem to be the case.

Are there any plans to make the compiler handle embedded jars before the 3.3 final release? If not, I suggest adding "The exception is when the plug-ins contain embedded jars" to the said "Should do" item.

Regards,
Thomas Hallgren


On 2/21/07, Thomas Hallgren <thomas@xxxxxxx> wrote:
Hi,
I have some difficulties with plugins that are installed as jars and
that in themselves contains jar files. Here's my usecase.

I have a plugin that is dependent on packages that are exported from one
of the jars contained in the org.tigris.subversion.subclipse.core
plugin. Although this plugin is installed in my target platform, is
enabled and functional, my plugin doesn't compile. If I however import
the plugin into my workspace (using import projects with source
folders), then everything compiles without errors immediately.

If I now start a self-hosted Eclipse IDE from the one where I have an
imported subclipse.core, the hosted IDE again fails to find the classes
at runtime. In order to rectify this, I need to change my launch
configuration and uncheck the subclipse.core plugin from "Workspace
plugins" and instead check it the one found in "Target Platform".

The problem is the same in both Eclipse 3.2.x and 3.3M5

I've mentioned this to the Subclipse team. They claim that this is an
Eclipse bug. I haven't managed to find the bugzilla for it. Is there one
or should I enter one?

Regards,
Thomas Hallgren



_______________________________________________
pde-build-dev mailing list
pde-build-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-build-dev

_______________________________________________
pde-build-dev mailing list
pde-build-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-build-dev



Back to the top