Home » Eclipse Projects » Rich Client Platform (RCP) » why does export wizard create BOTH .class files AND the plugin jar-file?
| why does export wizard create BOTH .class files AND the plugin jar-file? [message #449171] |
Wed, 10 May 2006 16:33  |
Eclipse User |
|
|
|
WinXP, R3.1.1
I've been exporting and delivering my RCP app just finr for some while now, when one of my clients
asked me -- "why does the app include a jar-file for each plug-in and ALSO all the .class files for
that plug-in?" Good question, and I have no clue.
According to http://www.eclipse.org/articles/Article-RCP-1/tutorial1.html the structure created
should look like this:
RcpTutorial1
| .eclipseproduct
| eclipse.exe
| startup.jar
+--- configuration
| config.ini
+--- plugins
org.eclipse.core.commands_3.1.0.jar
org.eclipse.core.expressions_3.1.0.jar
org.eclipse.core.runtime_3.1.2.jar
org.eclipse.help_3.1.0.jar
org.eclipse.jface_3.1.1.jar
org.eclipse.osgi_3.1.2.jar
org.eclipse.swt.win32.win32.x86_3.1.2.jar
org.eclipse.swt_3.1.0.jar
*org.eclipse.ui.tutorials.rcp.part1_1.0.0.jar*
org.eclipse.ui.workbench_3.1.2.jar
org.eclipse.ui_3.1.2.jar
But in my case, it actually looks like this:
MyLittleApp
| .eclipseproduct
| eclipse.exe
| startup.jar
+--- configuration
| config.ini
+--- features
| com.mun.ist.fea.cher1_0.1.1
| com.mun.ist.fea.cher2_0.1.1
| com.mun.ist.fea.cher3_0.1.1
| com.mun.ist.fea.cher4_0.1.1
| org.eclipse.rcp_3.1.1
+--- plugins
| com.mun.ist.plug.inA_0.1.1.jar
| org.eclipse.core.commands_3.1.0.jar
| org.eclipse.core.expressions_3.1.0.jar
| org.eclipse.core.runtime_3.1.1.jar
| org.eclipse.help_3.1.0.jar
| org.eclipse.jface_3.1.1.jar
| org.eclipse.osgi_3.1.1.jar
| org.eclipse.rcp_3.1.0.jar
| org.eclipse.swt.win32.win32.x86_3.1.2.jar
| org.eclipse.swt_3.1.0.jar
| org.eclipse.ui.forms_3.1.0.jar
| org.eclipse.ui.views_3.1.1.jar
| org.eclipse.ui.workbench_3.1.1.jar
| org.eclipse.ui_3.1.1.jar
| org.eclipse.update.configurator_3.1.0.jar
+----com.mun.ist.plug.inB_0.1.1
plug.inB.jar
bin/com/mun/ist/plug/inB/<dozens of .class files>
+----com.mun.ist.plug.inC_0.1.1
plug.inC.jar
bin/com/mun/ist/plug/inC/<dozens of .class files>
+----com.mun.ist.plug.inD_0.1.1
<third-party jars, as expected>
plug.inD.jar
bin/com/mun/ist/plug/inD/<dozens of .class files>
+----com.mun.ist.plug.inE_0.1.1
<third-party jars, as expected>
plug.inE.jar
bin/com/mun/ist/plug/inE/<dozens of .class files>
+----com.mun.ist.plug.inF_0.1.1
<third-party jars, as expected>
+----com.mun.ist.plug.inG_0.1.1
<third-party jars, as expected>
fea.cher1 = {plug.inA, plug.inB, plug.inC}
fea.cher2 = {plug.inD, plug.inE}
fea.cher3 = plug.inF
fea.cher4 = plug.inG
There are of course plenty of differences between the various MANIFEST.MF files, but I have no clue
which ones would be relevant. Any ideas to explain this apparently random behavior?
thanks,
Paul
|
|
|
| Re: why does export wizard create BOTH .class files AND the plugin jar-file? [message #449399 is a reply to message #449171] |
Thu, 11 May 2006 21:19  |
| Eclipse User |
|
|
|
What do you have checked to export in your build.properties file? If you
include the folders that eclipse uses to keep class files then you will get
all of those files included in your export. I don't know if this is what is
happening, but you should check what you are exporting in the binary build
from your build.properties file.
Chris
"Paul Keyser" <rolarenfan@earthlink.net> wrote in message
news:e3timm$gsh$1@utils.eclipse.org...
> WinXP, R3.1.1
>
> I've been exporting and delivering my RCP app just finr for some while
> now, when one of my clients asked me -- "why does the app include a
> jar-file for each plug-in and ALSO all the .class files for that plug-in?"
> Good question, and I have no clue.
>
> According to http://www.eclipse.org/articles/Article-RCP-1/tutorial1.html
> the structure created should look like this:
>
> RcpTutorial1
> | .eclipseproduct
> | eclipse.exe
> | startup.jar
> +--- configuration
> | config.ini
> +--- plugins
> org.eclipse.core.commands_3.1.0.jar
> org.eclipse.core.expressions_3.1.0.jar
> org.eclipse.core.runtime_3.1.2.jar
> org.eclipse.help_3.1.0.jar
> org.eclipse.jface_3.1.1.jar
> org.eclipse.osgi_3.1.2.jar
> org.eclipse.swt.win32.win32.x86_3.1.2.jar
> org.eclipse.swt_3.1.0.jar
> *org.eclipse.ui.tutorials.rcp.part1_1.0.0.jar*
> org.eclipse.ui.workbench_3.1.2.jar
> org.eclipse.ui_3.1.2.jar
>
> But in my case, it actually looks like this:
>
> MyLittleApp
> | .eclipseproduct
> | eclipse.exe
> | startup.jar
> +--- configuration
> | config.ini
> +--- features
> | com.mun.ist.fea.cher1_0.1.1
> | com.mun.ist.fea.cher2_0.1.1
> | com.mun.ist.fea.cher3_0.1.1
> | com.mun.ist.fea.cher4_0.1.1
> | org.eclipse.rcp_3.1.1
> +--- plugins
> | com.mun.ist.plug.inA_0.1.1.jar
> | org.eclipse.core.commands_3.1.0.jar
> | org.eclipse.core.expressions_3.1.0.jar
> | org.eclipse.core.runtime_3.1.1.jar
> | org.eclipse.help_3.1.0.jar
> | org.eclipse.jface_3.1.1.jar
> | org.eclipse.osgi_3.1.1.jar
> | org.eclipse.rcp_3.1.0.jar
> | org.eclipse.swt.win32.win32.x86_3.1.2.jar
> | org.eclipse.swt_3.1.0.jar
> | org.eclipse.ui.forms_3.1.0.jar
> | org.eclipse.ui.views_3.1.1.jar
> | org.eclipse.ui.workbench_3.1.1.jar
> | org.eclipse.ui_3.1.1.jar
> | org.eclipse.update.configurator_3.1.0.jar
> +----com.mun.ist.plug.inB_0.1.1
> plug.inB.jar
> bin/com/mun/ist/plug/inB/<dozens of .class files>
> +----com.mun.ist.plug.inC_0.1.1
> plug.inC.jar
> bin/com/mun/ist/plug/inC/<dozens of .class files>
> +----com.mun.ist.plug.inD_0.1.1
> <third-party jars, as expected>
> plug.inD.jar
> bin/com/mun/ist/plug/inD/<dozens of .class files>
> +----com.mun.ist.plug.inE_0.1.1
> <third-party jars, as expected>
> plug.inE.jar
> bin/com/mun/ist/plug/inE/<dozens of .class files>
> +----com.mun.ist.plug.inF_0.1.1
> <third-party jars, as expected>
> +----com.mun.ist.plug.inG_0.1.1
> <third-party jars, as expected>
>
> fea.cher1 = {plug.inA, plug.inB, plug.inC}
>
> fea.cher2 = {plug.inD, plug.inE}
>
> fea.cher3 = plug.inF
>
> fea.cher4 = plug.inG
>
> There are of course plenty of differences between the various MANIFEST.MF
> files, but I have no clue which ones would be relevant. Any ideas to
> explain this apparently random behavior?
>
> thanks,
> Paul
|
|
|
| Re: why does export wizard create BOTH .class files AND the plugin jar-file? [message #449400 is a reply to message #449171] |
Thu, 11 May 2006 21:20 |
| Eclipse User |
|
|
|
As a follow up...
From the looks of it it looks like you are exporting your bin folder with
everything else. This is not necessary. Eclipse will build your source
folder at export time and add that to the plugin jar.
(Sorry about the two separte posts.)
Chris
"Paul Keyser" <rolarenfan@earthlink.net> wrote in message
news:e3timm$gsh$1@utils.eclipse.org...
> WinXP, R3.1.1
>
> I've been exporting and delivering my RCP app just finr for some while
> now, when one of my clients asked me -- "why does the app include a
> jar-file for each plug-in and ALSO all the .class files for that plug-in?"
> Good question, and I have no clue.
>
> According to http://www.eclipse.org/articles/Article-RCP-1/tutorial1.html
> the structure created should look like this:
>
> RcpTutorial1
> | .eclipseproduct
> | eclipse.exe
> | startup.jar
> +--- configuration
> | config.ini
> +--- plugins
> org.eclipse.core.commands_3.1.0.jar
> org.eclipse.core.expressions_3.1.0.jar
> org.eclipse.core.runtime_3.1.2.jar
> org.eclipse.help_3.1.0.jar
> org.eclipse.jface_3.1.1.jar
> org.eclipse.osgi_3.1.2.jar
> org.eclipse.swt.win32.win32.x86_3.1.2.jar
> org.eclipse.swt_3.1.0.jar
> *org.eclipse.ui.tutorials.rcp.part1_1.0.0.jar*
> org.eclipse.ui.workbench_3.1.2.jar
> org.eclipse.ui_3.1.2.jar
>
> But in my case, it actually looks like this:
>
> MyLittleApp
> | .eclipseproduct
> | eclipse.exe
> | startup.jar
> +--- configuration
> | config.ini
> +--- features
> | com.mun.ist.fea.cher1_0.1.1
> | com.mun.ist.fea.cher2_0.1.1
> | com.mun.ist.fea.cher3_0.1.1
> | com.mun.ist.fea.cher4_0.1.1
> | org.eclipse.rcp_3.1.1
> +--- plugins
> | com.mun.ist.plug.inA_0.1.1.jar
> | org.eclipse.core.commands_3.1.0.jar
> | org.eclipse.core.expressions_3.1.0.jar
> | org.eclipse.core.runtime_3.1.1.jar
> | org.eclipse.help_3.1.0.jar
> | org.eclipse.jface_3.1.1.jar
> | org.eclipse.osgi_3.1.1.jar
> | org.eclipse.rcp_3.1.0.jar
> | org.eclipse.swt.win32.win32.x86_3.1.2.jar
> | org.eclipse.swt_3.1.0.jar
> | org.eclipse.ui.forms_3.1.0.jar
> | org.eclipse.ui.views_3.1.1.jar
> | org.eclipse.ui.workbench_3.1.1.jar
> | org.eclipse.ui_3.1.1.jar
> | org.eclipse.update.configurator_3.1.0.jar
> +----com.mun.ist.plug.inB_0.1.1
> plug.inB.jar
> bin/com/mun/ist/plug/inB/<dozens of .class files>
> +----com.mun.ist.plug.inC_0.1.1
> plug.inC.jar
> bin/com/mun/ist/plug/inC/<dozens of .class files>
> +----com.mun.ist.plug.inD_0.1.1
> <third-party jars, as expected>
> plug.inD.jar
> bin/com/mun/ist/plug/inD/<dozens of .class files>
> +----com.mun.ist.plug.inE_0.1.1
> <third-party jars, as expected>
> plug.inE.jar
> bin/com/mun/ist/plug/inE/<dozens of .class files>
> +----com.mun.ist.plug.inF_0.1.1
> <third-party jars, as expected>
> +----com.mun.ist.plug.inG_0.1.1
> <third-party jars, as expected>
>
> fea.cher1 = {plug.inA, plug.inB, plug.inC}
>
> fea.cher2 = {plug.inD, plug.inE}
>
> fea.cher3 = plug.inF
>
> fea.cher4 = plug.inG
>
> There are of course plenty of differences between the various MANIFEST.MF
> files, but I have no clue which ones would be relevant. Any ideas to
> explain this apparently random behavior?
>
> thanks,
> Paul
|
|
| | | |
| Re: why does export wizard create BOTH .class files AND the plugin jar-file? [message #449426 is a reply to message #449423] |
Fri, 12 May 2006 19:12 |
| Eclipse User |
|
|
|
Um, I think I was doing "both", but am not sure, since the way to specify these things is, um,
confusing. I had "bin" checked in the "Build" tab of the plugin.xml/MANIFEST.MF editor; but
elsewhere in that editor, some complex compound of settings was also exporting jar files, i.e., the
jar of the given plugin's class-files (plus any 3rd-party jars in that plugin). I actually *want* to
export the jars and *not* the bin directory.
Just a little while ago I finished climbing the dependency-tree and removing one "bin" at a time,
and now all is well.
(In the process I discovered that I can omit the ".settings" directory and all seems well; but I
must include the plugin.xml, iff it is not empty, and any "schema" directory.)
There are still some oddities in the exported "plugins" directory: the jar of one of my plugins
winds up by itself (i.e., as a sibling to the org.eclipse jars), whereas all the others wind up in a
directory called com.mun.ist.plu.gin_0.1.1 (0.1.1 is indeed the version-# I am using). Admittedly,
that lone exception is the only plugin that provides no icons directory, no plugin.xml, and no
3rd-party jars, so maybe that explains it.
I am still exporting all the MANIFEST.MF files (though in the case of the lone naked plugin.jar, it
does not appear); I wonder if I can skip that?
thanks,
Paul
|
|
|
Goto Forum:
Current Time: Sat Aug 30 16:10:55 EDT 2025
Powered by FUDForum. Page generated in 0.03189 seconds |
Home