DZone Forums
Go Back   DZone Forums > Community > Tools & IDEs > Eclipse
Reload this Page Eclipse Plugin export fails
Notices
Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  (#1 (permalink)) Old
Member
 
Posts: 5
Thanks: 0
Thanked 0 Times in 0 Posts
Join Date: Nov 2009
Question Eclipse Plugin export fails - 01-27-2010, 02:23 AM

Hi,
A few weeks ago I changed my os from vista 32-bit to win 7 64-bit. I
copied my whole eclipse directory and restored it to the freshly
installed computer. With development everything works fine. But when I
try to export the plugin I always get an error message like this:

Problems during export
D:\workspaces\workspace_springdm_divsdd\.metadata\ .plugins
\org.eclipse.pde.core\temp\org.eclipse.pde.contain er.feature\build.xml:
34: The following error occurred while executing this line:
D:\workspaces\workspace_springdm_divsdd\.metadata\ .plugins
\org.eclipse.pde.core\temp\org.eclipse.pde.contain er.feature\build.xml:
10: The following error occurred while executing this line:
D:\workspaces\workspace_springdm_divsdd\divsdd.spr ingdm\build.xml:222:
The following error occurred while executing this line:
D:\workspaces\workspace_springdm_divsdd\divsdd.spr ingdm\build.xml:157:
IO error scanning directory 'C:\Config.Msi'

Running eclipse with admin rights pushed me over the config.msi
directory, but the next issue with the identical error message was
with the directory "c:\documents and settings" which exists only as
link in win7.

I tried to set up a complete fresh product configuration, but the same
error occurred.

Anyone got a clue, what is happening there? I even don't understand
what eclipse is scanning during the build in these directories, anyone
who knows something about that? What is going on in the
'internals'????

Any help would be greatly appreciated,
Dagmar
Reply With Quote
  (#2 (permalink)) Old
Member
 
Posts: 5
Thanks: 0
Thanked 0 Times in 0 Posts
Join Date: Nov 2009
Talking Problem solved... - 01-29-2010, 03:05 AM

Hi,
the problem was not dependent from os or so, it was just a mistake in the build configuration. I had the following lines in my build.properties:
Code:
source.. = src/,\
           ****-INF/spring/
and eclipse showed me a warning there. Quick fix changed this to:
Code:
source.. = src/,\
           ****-INF/spring/,\
           /
and this caused the build to copy the entire volume, which comes clear, if you take a closer look to the added line! So: Silly mistake, but costs me a lot of time searching. Be careful with quick fix.....
Regards,
Dagmar
Reply With Quote
Reply

Tags
deployment, eclipse plugin, export

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Eclipse Dev. Studio fails to start after Plug-in update rambilas Eclipse 0 08-10-2009 04:25 AM
Export Eclipse project to HTML sarv6 Eclipse 0 12-01-2008 11:39 PM
ImportOperation fails in Eclipse plugin ysion Eclipse 0 11-24-2008 03:33 PM
Help request: Eclipse PDE Export problem meekrosoft Eclipse 3 04-17-2008 03:36 AM
Eclipse suddenly fails to launch on OS X nexum Eclipse 1 04-07-2008 04:04 PM


Copyright 1997-2009, DZone, Inc.
vBulletin Skin developed by: vBStyles.com