[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[lepido-dev] Re: Install problem
|
Date: Mon, 08 Aug 2005 09:29:24 +0100
From: Ross Gardler <rgardler@xxxxxxxxxx>
Subject: Re: [lepido-dev] Install problem
To: "Lepido, Tools for Apache Cocoon developer discussions"
<lepido-dev@xxxxxxxxxxx>
Message-ID: <42F717E4.9030804@xxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Scott Yeadon wrote:
Hi,
Following the install instructions I have expanded the zip files, but
trying to install the actual Lepido update I get
Lepido, Tools for Apache Cocoon (0.1.0) requires plug-in
"org.eclipse.wst.sse.core".
on the software manager update. However this does exist in the plug-in
directory at org.eclipse.wst.sse.core_0.7.0.jar after expanding
wt-0.7.zip. Any idea why eclipse can't see it?
Just because a plugin is present does not necessariy mean it is loaded
and working.
Try "eclipse -clean" as suggested by David elsewhere in this thread.
This dforces Eclipse to reload all plugins.
If that fails go to Help -> Software Update -> Manage Configuration
Ensure the "Show Disabled Features" button is pressed (the one with the
little red "no entry" sign)
Tried all that before I mailed the list (sorry, should have said!), no results. I also reinstalled Eclipse from scratch as well just to make sure no other plugins I had downloaded had mucked it up. I ran out of ideas as to what could be wrong - oh well, back to HTML forms I guess.
Expand the nodes until you can see the list of installed features. Do
any of them have a "no entry" sign on them? This indicates they are not
enabled. If any are not enabled click on them and select "Show
Properties" then "Status". This will tell you way the feature is not
enabled.
Web Tools doesn't even show up, regardless of what I do. Anything from an update site is fine (EMF, GEF, etc) but unzipping and restarting just doesn't seem to register anything - I get no errors in the log about dependencies. All the other plugins appear enabled.
It is likely that a dependency for Web Tools is not enabled, thus web
tools itself cannot work.
Ross
