[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [pde-build-dev] Build a Plugin as a dircetory instead of a jarfile
|
From: "Barrie Treloar" <baerrach@xxxxxxxxx>
Reply-To: "Eclipse PDE Build developers list." <pde-build-dev@xxxxxxxxxxx>
To: "Eclipse PDE Build developers list." <pde-build-dev@xxxxxxxxxxx>
Subject: Re: [pde-build-dev] Build a Plugin as a dircetory instead of a
jarfile
Date: Wed, 18 Apr 2007 19:23:30 +0930
On 4/18/07, Xiaoying Gu <xgu@xxxxxxxxxxx> wrote:
I have the same problem when I tired to export RCP product by export
wizard.
I found some plugins were exported as single jars which should be
directory, while some are correct. I checked the build.properties of
these plugins and hadn't found any difference. So I was confused why
some are exported as directory but some are not.
Since our product configuration is based on plug-ins, I don't how to
control this when exporting RCP product.
Could you please give me some advice?
Convert to a feature based product build.
I think I worked out how to do this with a plugin build but I can't
remember.
Conversion is really easy as is the preferred way from what I have read.
Sorry for the really, really late reply, but I've seen this problem get
mentioned
before. In my experience, if you have a jar named "." the plug-in
will be built as a Jar when exported. If there is not Jar named ".", it
will be built as a directory plug-in. Look on the Build tab of the
MANIFEST.MF editor.
You want to make sure that the Runtime and Build tabs of the MANIFEST.MF
editor are in sync, so that all of the Jar's built on the Build tab end up
in
the Classpath section of the "Runtime" tab. I believe when you add a
plug-in to a feature it uses this to detect if the plug-in should be set
to unzip or not. If you have CNFE or other weird issues, when you
export, but it runs fine inside of Eclipse. In my experience, it is because
those two panes are out of sync.
Migrating to features has lots of nice benefits, but just in case someone
wants the answer, I believe that to be it.
As an aside, it's very painful when first starting with Eclipse that so many
settings have to be in sync and correct for things to work inside of
Eclipse,
and then have the plug-ins either fail to export or fail to run successfully
because "inside" vs. "outside" don't all keep themselves in sync. I've
learned
the magic and can quickly diagnose the problems now when others ask, but
wow it was frustrating learning all of that.
Kirby
_______________________________________________
pde-build-dev mailing list
pde-build-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-build-dev
_________________________________________________________________
Get a FREE Web site, company branded e-mail and more from Microsoft Office
Live! http://clk.atdmt.com/MRT/go/mcrssaub0050001411mrt/direct/01/
