- This topic has 3 replies, 2 voices, and was last updated 15 years, 9 months ago by
.
-
Posts
-
I’ve updated to 7.0.1 (using the offline installer to upgrade an existing install), and now have the dropins folder. So I copied a .link file (that used to work in 6.x) pointing to a vendor plugin installation, and started MyEclipse. The Eclipse doc http://wiki.eclipse.org/Equinox_p2_Getting_Started says this should work, so hopefully I did it correctly. As far as I can tell the .link file is being ignored, there’s no evidence of the extension/plugin referenced by the link file. I checked the Genuitec\Common\logs directory but see no indication of errors, etc. I also don’t see on the help menu any equivalent of the old Manage Configuration ability to see what non-MyEclipse plugins eclipse sees and which ones are broken
So, what’s the process in 7.0.1 for diagnosing why an addition to the dropins folder doesn’t work?
More info – I found this call stack in the workspace .metadata\.log file. It evidently doesn’t like my link file:
!ENTRY org.eclipse.equinox.p2.reconciler.dropins 4 0 2009-02-17 08:58:19.607
!MESSAGE Error occurred while building repository location from file: C:\MyEclipse7.0\dropins\com.mks.integrations.eclipse.src.link
!STACK 0
java.io.IOException: The filename, directory name, or volume label syntax is incorrect
at java.io.WinNTFileSystem.canonicalize0(Native Method)
at java.io.Win32FileSystem.canonicalize(Unknown Source)
at java.io.File.getCanonicalPath(Unknown Source)
at java.io.File.getCanonicalFile(Unknown Source)
at org.eclipse.equinox.internal.p2.reconciler.dropins.DropinsRepositoryListener.getLinkRepository(Unknown Source)
at org.eclipse.equinox.internal.p2.reconciler.dropins.DropinsRepositoryListener.createRepositoryURL(Unknown Source)
at org.eclipse.equinox.internal.p2.reconciler.dropins.DropinsRepositoryListener.added(Unknown Source)
at org.eclipse.equinox.internal.provisional.p2.directorywatcher.DirectoryWatcher.processFile(Unknown Source)
at org.eclipse.equinox.internal.provisional.p2.directorywatcher.DirectoryWatcher.scanDirectories(Unknown Source)
at org.eclipse.equinox.internal.provisional.p2.directorywatcher.DirectoryWatcher.poll(Unknown Source)
at org.eclipse.equinox.internal.p2.reconciler.dropins.Activator.watchDropins(Unknown Source)
at org.eclipse.equinox.internal.p2.reconciler.dropins.Activator.start(Unknown Source)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:1009)
at java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:1003)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:984)
at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:346)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:355)
at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1074)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:616)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:508)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:299)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:489)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:211)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:321)The contents of the link file looks correct – it’s just a one line text file with “path=C:\Program Files\MKS\IntegrityClient\integrations\IBM\eclipse_3” which is the correct path for the desired extension. At this location there is an eclipse supdirectory, containing a .eclipseextension text file, a features subdirectory, and a plugins subdirectory. So I’m a little farther, but what next?
Any suggestions for next steps would be appreciated, thanks in advance.
Ok, I found the problem, you can ignore the above question. Turns out that Eclipse 3.3 accepted the above link file path just fine. Eclipse 3.4 evidently requires that all the file separators be forward slashes – all I did was change the content of the link file to hace forward slashes instead of backslashes, and it started working.
