Eclipse Community Forums: Eclipse Platform

Home » Eclipse Projects » Eclipse Platform » ignored plugins

Sun, 13 September 2009 12:47

Eclipse User

ls $ECLIPSEHOME/plugins | wc -l
gives me well over 2000 plugins, but so many of them seem to be ignored.
I just downloaded an XML plugin from EPIC and unzipped to the plugins
subdirectory. I launch Eclipse, but the plug-in doesn't show up -- not
even in the Plug-in Registry View. I see no errors in the log either.
This has been the problem ever since moving to version 3.5. It might be
possible that the plug-ins that are ignored are not compatible with
version 3.5, but how can I find that out for sure? And it would seem
disappointing that more than half (1000+) of the plug-ins in the plugins
subdirectory would be obsolete/incompatible.

Can someone please help me understand why so many plugins are ignored?

Mark

Re: ignored plugins [message #485562 is a reply to message #485561]

Sun, 13 September 2009 12:56

Eclipse User

On 13/09/2009 17:47, Mark wrote:
> ls $ECLIPSEHOME/plugins | wc -l
> gives me well over 2000 plugins, but so many of them seem to be ignored.
> I just downloaded an XML plugin from EPIC and unzipped to the plugins
> subdirectory. I launch Eclipse, but the plug-in doesn't show up -- not
> even in the Plug-in Registry View. I see no errors in the log either.
> This has been the problem ever since moving to version 3.5. It might be
> possible that the plug-ins that are ignored are not compatible with
> version 3.5, but how can I find that out for sure? And it would seem
> disappointing that more than half (1000+) of the plug-ins in the plugins
> subdirectory would be obsolete/incompatible.
>
> Can someone please help me understand why so many plugins are ignored?
>
> Mark
>
Plugins need to be installed. You can no longer just unzip into the
plugins directory. Use Help->Install new software.

--
Derek

Re: ignored plugins [message #485563 is a reply to message #485561]

Sun, 13 September 2009 13:00

Eclipse User

Mark wrote:
> ls $ECLIPSEHOME/plugins | wc -l
> gives me well over 2000 plugins, but so many of them seem to be
> ignored. I just downloaded an XML plugin from EPIC and unzipped to the
> plugins subdirectory. I launch Eclipse, but the plug-in doesn't show up
> -- not even in the Plug-in Registry View. I see no errors in the log
> either. This has been the problem ever since moving to version 3.5. It
> might be possible that the plug-ins that are ignored are not compatible
> with version 3.5, but how can I find that out for sure? And it would
> seem disappointing that more than half (1000+) of the plug-ins in the
> plugins subdirectory would be obsolete/incompatible.
>
> Can someone please help me understand why so many plugins are ignored?

You have to understand that an installed plug-in doesn't necessarily
mean an ACTIVE plug-in. Since Eclipse 3.4, Eclipse supports a more
sophisticated provisioning mechanism via Equinox p2:

http://wiki.eclipse.org/Equinox_p2_Getting_Started

You should be using the "dropins" directory method... or preferably...
the p2 update ui to install things.

If you're curious about p2, there will be a free webinar Tuesday:

http://eclipsesource.com/blogs/2009/09/09/eclipse-p2-and-gal ileo/

Hope this helps.

Cheers,

Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465
http://twitter.com/eclipsesource | http://twitter.com/caniszczyk

Re: ignored plugins [message #485569 is a reply to message #485563]

Sun, 13 September 2009 14:38

Eclipse User

Ah, very helpful and so I checked this out by moving the specific plugins
I added over to the dropins directory instead, and bounced eclipse. Still
no-shows! Nothing seems to be different from what I described in my
initial post.

Then I tried using "Install New Software" and added a new local site
repository (file:/usr/local/eclipse) and p2 recognized it as a valid
repository (good news so far!). (Aside -- My development box has no
Internet access, so I have to FTP all my plugins in through a gateway.)
But, the local repository showed no available updates, even though there
are plug-ins in my dropins directory.

So now what?

Mark

Re: ignored plugins [message #485574 is a reply to message #485569]

Sun, 13 September 2009 15:28

Eclipse User

Mark wrote:
> Ah, very helpful and so I checked this out by moving the specific
> plugins I added over to the dropins directory instead, and bounced
> eclipse. Still no-shows! Nothing seems to be different from what I
> described in my initial post.
> Then I tried using "Install New Software" and added a new local site
> repository (file:/usr/local/eclipse) and p2 recognized it as a valid
> repository (good news so far!). (Aside -- My development box has no
> Internet access, so I have to FTP all my plugins in through a gateway.)
> But, the local repository showed no available updates, even though there
> are plug-ins in my dropins directory.

If you install the plug-ins via dropins... and start Eclipse with
console... and type "ss" ... do you see your plug-ins there? If they are
there... type "diag <plugin id>" and paste it here. I'm guessing there
are some missing dependencies or bad dependencies. If you use drop-ins
instead of the p2 ui, p2 doesn't give you any debug information as
you're responsible for managing the plug-ins. That's the trade off if
you don't use the UI or command line director to install things.

Are these publicly available plug-ins btw? If they are, I can try them
out quickly.

Cheers,

Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465
http://twitter.com/eclipsesource | http://twitter.com/caniszczyk

Re: ignored plugins [message #485601 is a reply to message #485561]

Mon, 14 September 2009 01:19

Eclipse User

Mark wrote:
> ls $ECLIPSEHOME/plugins | wc -l
> gives me well over 2000 plugins, but so many of them seem to be
> ignored. I just downloaded an XML plugin from EPIC and unzipped to the
> plugins subdirectory. I launch Eclipse, but the plug-in doesn't show up
> -- not even in the Plug-in Registry View. I see no errors in the log
> either. This has been the problem ever since moving to version 3.5. It
> might be possible that the plug-ins that are ignored are not compatible
> with version 3.5, but how can I find that out for sure? And it would
> seem disappointing that more than half (1000+) of the plug-ins in the
> plugins subdirectory would be obsolete/incompatible.
>
> Can someone please help me understand why so many plugins are ignored?
>
> Mark
>

What JVM version are you running Eclipse under? Many plugins require 1.5, and
some require 1.6. If you're inadvertently running under Java 1.4, Eclipse will
run but you'll have a lot of ignored plugins.

You may want to specify a JVM in your eclipse.ini or your command line, rather
than leaving it to the vagaries of the system path.

Re: ignored plugins [message #485764 is a reply to message #485569]

Mon, 14 September 2009 17:06

Eclipse User

I have seen this behaviour before. What other plugins have you installed
before by just "unzipping" them into Eclipse directory? Delta pack by any
chance?

Re: ignored plugins [message #486118 is a reply to message #485574]

Wed, 16 September 2009 08:04

Eclipse User

Thanks, Chris. I did an "ss" from the osgi prompt and it listed a bunch
of plug-ins, but none of the ones from the ./dropins folder (which I think
we should expect because they are not managed with p2, right?) I cannot
manage them from p2 ("Add New Software..."), either, because the local
repository shows only 4 entries which are all Subversive entries. Perhaps
where I am going wrong is in the setup of my local repository. Currently,
I have one I defined called "Local" and pointed it to
"file:/usr/local/eclipse" Is this incorrect? (Remember, I cannot access
the Internet through my Eclipse box except to use FTP through a gateway...)

Just for kicks, though, after doing an "ss", I did a "diag <plugin>" where
<plugin> was a cut&paste of one of the plugins listed as ACTIVE, and got
an error "cannot find bundle <plugin>" So, am I doing something
syntactically incorrect here, too?

I appreciate the help!
Mark

Re: ignored plugins [message #486134 is a reply to message #485569]

Wed, 16 September 2009 09:36

Eclipse User

Originally posted by: richkulp.us.NO_SPAM.ibm.com

Did you put them under dropins as:

dropins
mystuff
eclipse
features
plugins

It took me awhile to figure out I needed this structure for them to be
picked up.

Mark wrote:
> Ah, very helpful and so I checked this out by moving the specific
> plugins I added over to the dropins directory instead, and bounced
> eclipse. Still no-shows! Nothing seems to be different from what I
> described in my initial post.
> Then I tried using "Install New Software" and added a new local site
> repository (file:/usr/local/eclipse) and p2 recognized it as a valid
> repository (good news so far!). (Aside -- My development box has no
> Internet access, so I have to FTP all my plugins in through a gateway.)
> But, the local repository showed no available updates, even though there
> are plug-ins in my dropins directory.
>
> So now what?
>
> Mark
>

--
Thanks,
Rich Kulp

Re: ignored plugins [message #486147 is a reply to message #485574]

Wed, 16 September 2009 10:08

Eclipse User

Chris Aniszczyk wrote:
> Are these publicly available plug-ins btw? If they are, I can try them
> out quickly.

Both of these are ignored by Eclipse; both are in EclipsePluginCentral...
com.nubean.xmlespresso_6.0.0/
cz.wz.milanl.colors_0.0.2.jar

Mark

Re: ignored plugins [message #486178 is a reply to message #486134]

Wed, 16 September 2009 11:58

Eclipse User

I don't think you necessarily need to have this structure (I have put
jar files directly into dropins and it has worked before). But you do
need to restart eclipse using the -clean command line option to make it
refresh its caches.

Steffen

Rich Kulp wrote:
> Did you put them under dropins as:
>
> dropins
> mystuff
> eclipse
> features
> plugins
>
>
> It took me awhile to figure out I needed this structure for them to be
> picked up.
>
> Mark wrote:
>> Ah, very helpful and so I checked this out by moving the specific
>> plugins I added over to the dropins directory instead, and bounced
>> eclipse. Still no-shows! Nothing seems to be different from what I
>> described in my initial post.
>> Then I tried using "Install New Software" and added a new local site
>> repository (file:/usr/local/eclipse) and p2 recognized it as a valid
>> repository (good news so far!). (Aside -- My development box has no
>> Internet access, so I have to FTP all my plugins in through a
>> gateway.) But, the local repository showed no available updates,
>> even though there are plug-ins in my dropins directory.
>>
>> So now what?
>>
>> Mark
>>
>

Re: ignored plugins [message #486193 is a reply to message #486147]

Wed, 16 September 2009 12:50

Eclipse User

Mark wrote on Wed, 16 September 2009 10:08

Both of these are ignored by Eclipse; both are in EclipsePluginCentral...
com.nubean.xmlespresso_6.0.0/
cz.wz.milanl.colors_0.0.2.jar

Mark

Mark, do you have delta pack installed?

Re: ignored plugins [message #486199 is a reply to message #486178]

Wed, 16 September 2009 13:23

Eclipse User

Originally posted by: richkulp.us.NO_SPAM.ibm.com

Hi,

You shouldn't need -clean if dropins is working correctly. That is the
purpose of dropins. It sees changes in dropins on startup. Clean is very
heavy and expensive and can wipe out some installation history.

--
Thanks,
Rich Kulp

Re: ignored plugins [message #486210 is a reply to message #486178]

Wed, 16 September 2009 14:22

Eclipse User

Yes, I tried -clean, but that made no difference in my case.
Mark

Re: ignored plugins [message #486211 is a reply to message #486193]

Wed, 16 September 2009 14:28

Eclipse User

I don't think so, because I have not heard of this. Is this a plug-in
(extended functionality), or a patch to Eclipse? I googled it and only
found people having issues with delta pack, but found nothing that pointed
me where to get it. What does it do?
Mark

Re: ignored plugins [message #486213 is a reply to message #486211]

Wed, 16 September 2009 14:44

Eclipse User

It allows you to deploy your application to supported platforms other than one you run your Eclipse on. It can be downloaded from http://download.eclipse.org/eclipse/downloads/drops/R-3.5-20 0906111540/index.php. But if you never heard about it it's unlikely that you have it installed.

In my experience, once you install delta pack by unzipping it into eclipse directory, you start getting symptoms that you have.

Re: ignored plugins [message #486224 is a reply to message #486213]

Wed, 16 September 2009 15:38

Eclipse User

Ok, so the question was asked (if I had the delta pack) which I
interpreted to suggest that I should go get it to (possibly) solve my
problem, but you're saying that it was probably asked as if that may be
causing my problem. I don't have it (knowingly) and I won't install it
unless it is seen as something that could potentially solve my problem...
Mark

Re: ignored plugins [message #486238 is a reply to message #485561]

Wed, 16 September 2009 16:33

Eclipse User

Hmmmm,

I have similar problems here. Placed org.apache.log4j from orbit (the
newer version of log4j) in dropins, and it's not installed during startup.

This happens under Galileo 3.5 on linux. I did the same test on Windows,
and there it's installed fine.

I cannot see any problems in the error log. Any other places to check
for errors?

Re: ignored plugins [message #486239 is a reply to message #486238]

Wed, 16 September 2009 16:41

Eclipse User

Felix Dorner wrote:
> Hmmmm,
>
> I have similar problems here. Placed org.apache.log4j from orbit (the
> newer version of log4j) in dropins, and it's not installed during startup.
>
> This happens under Galileo 3.5 on linux. I did the same test on Windows,
> and there it's installed fine.
>
>
> I cannot see any problems in the error log. Any other places to check
> for errors?
>
>

Just for curiosity i placed the bundle directly in the plugins folder,
and now I get errors in the log:

!ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-09-16 22:37:57.517
!MESSAGE The installable unit
org.eclipse.equinox.executable_root.win32.win32.ia64 is missing the
filename property.

!ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-09-16 22:37:57.522
!MESSAGE The installable unit
org.eclipse.equinox.executable_root.carbon.macosx.x86 is missing the
filename property.

!ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-09-16 22:37:57.522
!MESSAGE The installable unit
org.eclipse.equinox.executable_root.motif.hpux.ia64_32 is missing the
filename property.

!ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-09-16 22:37:57.522
!MESSAGE The installable unit
org.eclipse.equinox.executable_root.win32.win32.x86 is missing the
filename property.

!ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-09-16 22:37:57.522
!MESSAGE The installable unit
org.eclipse.equinox.executable_root.carbon.macosx.ppc is missing the
filename property.

!ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-09-16 22:37:57.523
!MESSAGE The installable unit
org.eclipse.equinox.executable_root.motif.linux.x86 is missing the
filename property.

!ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-09-16 22:37:57.523
!MESSAGE The installable unit
org.eclipse.equinox.executable_root.gtk.linux.x86_64 is missing the
filename property.

!ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-09-16 22:37:57.523
!MESSAGE The installable unit
org.eclipse.equinox.executable_root.motif.solaris.sparc is missing the
filename property.

!ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-09-16 22:37:57.523
!MESSAGE The installable unit
org.eclipse.equinox.executable_root.gtk.solaris.x86 is missing the
filename property.

!ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-09-16 22:37:57.523
!MESSAGE The installable unit
org.eclipse.equinox.executable_root.cocoa.macosx.x86 is missing the
filename property.

!ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-09-16 22:37:57.524
!MESSAGE The installable unit
org.eclipse.equinox.executable_root.wpf.win32.x86 is missing the
filename property.

!ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-09-16 22:37:57.524
!MESSAGE The installable unit
org.eclipse.equinox.executable_root.photon.qnx.x86 is missing the
filename property.

!ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-09-16 22:37:57.524
!MESSAGE The installable unit
org.eclipse.equinox.executable_root.gtk.solaris.sparc is missing the
filename property.

!ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-09-16 22:37:57.524
!MESSAGE The installable unit
org.eclipse.equinox.executable_root.gtk.linux.x86 is missing the
filename property.

!ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-09-16 22:37:57.524
!MESSAGE The installable unit
org.eclipse.equinox.executable_root.cocoa.macosx.ppc is missing the
filename property.

!ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-09-16 22:37:57.525
!MESSAGE The installable unit org.eclipse.equinox.executable_root is
missing the filename property.

!ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-09-16 22:37:57.525
!MESSAGE The installable unit
org.eclipse.equinox.executable_root.win32.win32.x86_64 is missing the
filename property.

!ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-09-16 22:37:57.525
!MESSAGE The installable unit
org.eclipse.equinox.executable_root.gtk.linux.ppc is missing the
filename property.

!ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-09-16 22:37:57.525
!MESSAGE The installable unit
org.eclipse.equinox.executable_root.cocoa.macosx.x86_64 is missing the
filename property.

!ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-09-16 22:37:57.525
!MESSAGE The installable unit
org.eclipse.equinox.executable_root.motif.hpux.PA_RISC is missing the
filename property.

!ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-09-16 22:37:57.526
!MESSAGE The installable unit
org.eclipse.equinox.executable_root.motif.aix.ppc is missing the
filename property.

!ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-09-16 22:37:58.660
!MESSAGE The installable unit
org.eclipse.equinox.executable_root.win32.win32.ia64 is missing the
filename property.

!ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-09-16 22:37:58.660
!MESSAGE The installable unit
org.eclipse.equinox.executable_root.carbon.macosx.x86 is missing the
filename property.

!ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-09-16 22:37:58.660
!MESSAGE The installable unit
org.eclipse.equinox.executable_root.motif.hpux.ia64_32 is missing the
filename property.

!ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-09-16 22:37:58.675
!MESSAGE The installable unit
org.eclipse.equinox.executable_root.win32.win32.x86 is missing the
filename property.

!ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-09-16 22:37:58.675
!MESSAGE The installable unit
org.eclipse.equinox.executable_root.carbon.macosx.ppc is missing the
filename property.

!ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-09-16 22:37:58.675
!MESSAGE The installable unit
org.eclipse.equinox.executable_root.motif.linux.x86 is missing the
filename property.

!ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-09-16 22:37:58.676
!MESSAGE The installable unit
org.eclipse.equinox.executable_root.gtk.linux.x86_64 is missing the
filename property.

!ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-09-16 22:37:58.676
!MESSAGE The installable unit
org.eclipse.equinox.executable_root.motif.solaris.sparc is missing the
filename property.

!ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-09-16 22:37:58.676
!MESSAGE The installable unit
org.eclipse.equinox.executable_root.gtk.solaris.x86 is missing the
filename property.

!ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-09-16 22:37:58.676
!MESSAGE The installable unit
org.eclipse.equinox.executable_root.cocoa.macosx.x86 is missing the
filename property.

!ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-09-16 22:37:58.677
!MESSAGE The installable unit
org.eclipse.equinox.executable_root.wpf.win32.x86 is missing the
filename property.

!ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-09-16 22:37:58.677
!MESSAGE The installable unit
org.eclipse.equinox.executable_root.photon.qnx.x86 is missing the
filename property.

!ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-09-16 22:37:58.677
!MESSAGE The installable unit
org.eclipse.equinox.executable_root.gtk.solaris.sparc is missing the
filename property.

!ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-09-16 22:37:58.677
!MESSAGE The installable unit
org.eclipse.equinox.executable_root.gtk.linux.x86 is missing the
filename property.

!ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-09-16 22:37:58.678
!MESSAGE The installable unit
org.eclipse.equinox.executable_root.cocoa.macosx.ppc is missing the
filename property.

!ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-09-16 22:37:58.678
!MESSAGE The installable unit org.eclipse.equinox.executable_root is
missing the filename property.

!ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-09-16 22:37:58.678
!MESSAGE The installable unit
org.eclipse.equinox.executable_root.gtk.linux.ppc is missing the
filename property.

!ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-09-16 22:37:58.678
!MESSAGE The installable unit
org.eclipse.equinox.executable_root.win32.win32.x86_64 is missing the
filename property.

!ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-09-16 22:37:58.678
!MESSAGE The installable unit
org.eclipse.equinox.executable_root.cocoa.macosx.x86_64 is missing the
filename property.

!ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-09-16 22:37:58.678
!MESSAGE The installable unit
org.eclipse.equinox.executable_root.motif.hpux.PA_RISC is missing the
filename property.

!ENTRY org.eclipse.equinox.p2.directorywatcher 4 0 2009-09-16 22:37:58.679
!MESSAGE The installable unit
org.eclipse.equinox.executable_root.motif.aix.ppc is missing the
filename property.

!ENTRY org.eclipse.equinox.p2.engine 4 4 2009-09-16 22:38:01.109
!MESSAGE An error occurred while installing the items
!SUBENTRY 1 org.eclipse.equinox.p2.engine 4 0 2009-09-16 22:38:01.109
!MESSAGE session context was:(profile=SDKProfile,
phase=org.eclipse.equinox.internal.provisional.p2.engine.pha ses.Install,
operand=null --> [R]org.eclipse.equinox.executable_root
3.3.200.v20090521-1800-7M-Fm-FI3UouOe61h3BYGC,
action=org.eclipse.equinox.internal.p2.touchpoint.natives.ac tions.UnzipAction).
!SUBENTRY 1 org.eclipse.equinox.p2.touchpoint.natives 4 0 2009-09-16
22:38:01.109
!MESSAGE The artifact for
binary,org.eclipse.equinox.executable_root,3.3.200.v20090521 -1800-7M-Fm-FI3UouOe61h3BYGC
is not available.

Re: ignored plugins [message #486241 is a reply to message #486239]

Wed, 16 September 2009 16:50

Eclipse User

Your error messages indicate that you have delta pack installed. That's why you don't see any new plugins that are not installed via p2. Once you "drop" delta pack no new "dropped" plugins are recognized after that.

Re: ignored plugins [message #486250 is a reply to message #486241]

Wed, 16 September 2009 16:54

Eclipse User

Predrag Stanar wrote:
> Your error messages indicate that you have delta pack installed. That's
> why you don't see any new plugins that are not installed via p2. Once
> you "drop" delta pack no new "dropped" plugins are recognized after that.

Okay thanks. Is this desired behavior?

Felix

Re: ignored plugins [message #486254 is a reply to message #486250]

Wed, 16 September 2009 17:30

Eclipse User

I don't think so. In Eclipse prior to v3.5 you were able to drop delta pack and work normally. In v3.5 you can't do that any more, because if you do, all new plugins that are not installed via "Install New Software" are not recognized.
It seems that only way to add delta pack in v3.5 is to put it somewhere where Eclipse does not look automatically and then add that location to target Platform in Window->Preferences.

Re: ignored plugins [message #487259 is a reply to message #486254]

Tue, 22 September 2009 11:38

Eclipse User

Well, I don't remember installing a delta pack because I didn't even know what it was until it was explained earlier in this thread. How can I tell? I did a "find" on "*delta*" and only 2 files appeared in relation to EMF.CDO.source, so I doubt I have it. Perhaps knowing how I can tell if it is installed or not I can find out for sure... I do have the same type of messages in the terminal window as Felix noted. So maybe the delta pack is installed.

Assuming I do (assuming someone tells me how I can know for sure), then how do I get rid of it so that normal behavior returns? Just simply remove the delta pack files from the plugins directory?

Mark

Re: ignored plugins [message #487261 is a reply to message #487259]

Tue, 22 September 2009 11:47

Eclipse User

If you have files like org.eclipse.swt.motif.hpux.PA_RISC_3.5.0.HEAD.jar and org.eclipse.swt.gtk.solaris.sparc_3.5.0.v3550b.jar and org.eclipse.swt.cocoa.macosx.x86_64_3.5.0.v3550b.jar in your plugins directory, then yes you installed delta pack over base eclipse install and symptoms you are having are typical.

Unfortunately, you can't just remove delta pack files and get normal behaviour back. In my case I had to reinstall eclipse from scratch.

Re: ignored plugins [message #487287 is a reply to message #487261]

Tue, 22 September 2009 12:33

Eclipse User

Thanks. But I don't not have any of these files (or anything even close) anywhere under /usr/local/eclipse/ so I guess I don't have the delta pack although I seem to have nearly identical symptoms. But, a check just now reveals that I no longer have any of the "missing filename property" errors Felix has listed earlier in the thread. Yet certain plugins are still ignored.

Even though my problem probably wasn't caused by installing the delta pack incorrectly, I may be relegated to wiping Eclipse clean and starting from scratch again. Is there a way (such as saving off a config file) to avoid losing all my configuration of perspectives and window dimensions, etc. Is there a way to preserve the existence of the couple dozen or so third-party plugins that I have installed (aside from archiving the plugins directory)??

Mark

Re: ignored plugins [message #487288 is a reply to message #485561]

Tue, 22 September 2009 12:38

Eclipse User

Perspective customizations and windows positions are stored under .metadata directory which is normally in your workspace, not in eclipse directory structure.

As for preserving 3rd party plugins there's nothing I know of other than archiving them and restoring them after one by one.

Previous Topic:	Re: A product form multiple platforms
Next Topic:	String variable expansion

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Jul 23 16:06:23 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter