| Can't find org.eclipse.swt.win32.win32.x86_3.1.2.jar during export [message #444387] |
Tue, 14 February 2006 17:48  |
Eclipse User |
|
|
|
Originally posted by: kwpeck.mersoft.com
I recently updated to Eclipse 3.1.2 and I installed all the new 3.1.2
files I could find off the download page. When I attempt to do an export
now it says it can't find the file:
org.eclipse.swt.win32.win32.x86_3.1.2.jar
That file is sitting in my C:\Eclipse\plugins directory.
It also states check the log file for more information but I have been
unable to find a log file with anything in it. I have some with 0 bytes
with todays date but that is less than helpful.
Has anyone else upgraded to 3.1.2 (via update under Eclipse / not a new
install) and had this issue? Is there some place I need to update a file
to point to the proper one?
|
|
|
|
|
|
| Re: Can't find org.eclipse.swt.win32.win32.x86_3.1.2.jar during [message #444403 is a reply to message #444402] |
Wed, 15 February 2006 10:13  |
| Eclipse User |
|
|
|
Originally posted by: kwpeck.mersoft.com
The weird part is this works great on another project we did so I know
it is possible. We do use the Delta Pack. I just wanted to recreate a
success. We do have a custom build so we can build on a shared resource
for nightly builds. We will add the logic there which we did not have to
have before. We find that quite a bit in Eclipse, you can get something
to work once but a second time... well good luck.
Alex Blewitt wrote:
> I can suggest that you look at a custom build file for your feature, and then in that do a specific copy to move all the files over. I don't think it handles fragments very well at present.
>
> Either that, if you use an automated build system to do the work, tag that on as a step after your plugin has been built ...
>
> It's probably easiest to have the custom build option; you'll need to have an ant file with some specific targets (documentation is almost certainly in the help somewhere or in the build, but it's things like build.jars and gather.parts etc.). In any case, a feature is mostly just an empty zip file with feature.xml in, so tagging the export at that stage probably doesn't hurt.
>
> There might be more specific advice for exporting a multi-platform RCP application in the RCP delta pack; for example, a dependency on the RCP Delta pack might export them for you. But I don't know; I use maven to build plugins, and that's pretty configurable to do what I want :-)
>
> Alex.
|
|
|
| Re: Can't find org.eclipse.swt.win32.win32.x86_3.1.2.jar during [message #444784 is a reply to message #444402] |
Mon, 20 February 2006 17:23 |
| Eclipse User |
|
|
|
Originally posted by: kwpeck.mersoft.com
Solved the issue by adding org.eclipse.rcp to the Included Features tab
of the main projects .feature file
Alex Blewitt wrote:
> I can suggest that you look at a custom build file for your feature, and then in that do a specific copy to move all the files over. I don't think it handles fragments very well at present.
>
> Either that, if you use an automated build system to do the work, tag that on as a step after your plugin has been built ...
>
> It's probably easiest to have the custom build option; you'll need to have an ant file with some specific targets (documentation is almost certainly in the help somewhere or in the build, but it's things like build.jars and gather.parts etc.). In any case, a feature is mostly just an empty zip file with feature.xml in, so tagging the export at that stage probably doesn't hurt.
>
> There might be more specific advice for exporting a multi-platform RCP application in the RCP delta pack; for example, a dependency on the RCP Delta pack might export them for you. But I don't know; I use maven to build plugins, and that's pretty configurable to do what I want :-)
>
> Alex.
|
|
|
Powered by
FUDForum. Page generated in 0.11902 seconds
Home