Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Web Tools Project (WTP) » Problem updating from 3.2.0 to 3.2.1 using the WTP update site
Problem updating from 3.2.0 to 3.2.1 using the WTP update site [message #553367] Tue, 17 August 2010 09:28 Go to next message
Mauro Molinari is currently offline Mauro Molinari
Messages: 278
Registered: July 2009
Senior Member
Hi!
I'm using the WTP update site
(http://download.eclipse.org/webtools/repository/helios) to install WTP
3.2.1, however WTP is not working properly after that.

I feel there are some missing packages; for instance I can't find any
JST Server Adapters for 3.2.1 in the WTP update site; in the Helios
update site, instead, there are two packages with this name, however
they're marked as version 3.2.0; same thing for Eclipse Faceted Project
Framework JDT Enablement

The result is that, for isntance, there's no File | New | Web folder
category to create a Dynamic Web Project, no Java EE perspective and
other plugins that depend on WTP (Spring Tool Suite, for instance) do
not work properly (missing features in the UI).

How to solve that?

BTW: please consider that before trying to install 3.2.1 from the update
manager, I was using a manually-downloaded WTP pre-3.2.1-weekly build
using the dropins folder, because I needed an important performance fix.
However, before installing WTP with the update manager, I completely
removed WTP from the dropins folder...

Mauro.
Re: Problem updating from 3.2.0 to 3.2.1 using the WTP update site [message #553376 is a reply to message #553367] Tue, 17 August 2010 10:50 Go to previous messageGo to next message
Mauro Molinari is currently offline Mauro Molinari
Messages: 278
Registered: July 2009
Senior Member
Unfortunately, to solve the problem I reainstalled the whole Eclipse
from scratch, starting from a Eclipse Platform Runtime Binary and
installing only the plugins I needed.

I didn't install WTP 3.2.0, I immediately installed 3.2.1 from the WTP
update site. Now WTP works, but I suspect there still are problems.
First of all my Dynamic Web Projects show the following errors:

- Target runtime Apache Tomcat 5.5.28 is not defined.
- Implementation of project facet jst.web could not be found.
Functionality will be limited.
- Implementation of project facet wst.jsdt.web could not be found.
Functionality will be limited.

However, these projects, the Servers project and the server runtime are
properly configured in this workspace (this is the one I was using with
3.2.0 till yesterday).

Moreover, if I look at the Servers view, the web applications that
appear under the servers show an undefined red-rectangle icon, instead
of the icon of the server. My suspect is that this is caused by the lack
of the JST Server Adapters bundles in 3.2.1.
May I install the 3.2.0 versioned ones to solve this?

Mauro.
Re: Problem updating from 3.2.0 to 3.2.1 using the WTP update site [message #553398 is a reply to message #553376] Tue, 17 August 2010 12:12 Go to previous messageGo to next message
Mauro Molinari is currently offline Mauro Molinari
Messages: 278
Registered: July 2009
Senior Member
I solved installing the two JST Server Adapters and JST Server UI
version 3.2.0 from the Helios update site, on top of my installation of
WTP 3.2.1. On the other hand, JST Web UI 3.2.0 and Eclipse Faceted
Project Framework JDT Enablement 3.2.0 (also on Helios update site)
could not be installed on WTP 3.2.1 because of dependency problems.

So, that's quite confusing. My feeling is that the WTP 3.2.1 update has
been pushed to the WTP update site only to update an existing
installation of WTP 3.2.0 from the Helios update site.

By the way, please notice that what has been written on WTP website
(http://www.eclipse.org/webtools/) is wrong, because WTP 3.2.1 is NOT
available on the Helios update site.

HTH.
Mauro.
Re: Problem updating from 3.2.0 to 3.2.1 using the WTP update site [message #553406 is a reply to message #553398] Tue, 17 August 2010 13:06 Go to previous messageGo to next message
Mauro Molinari is currently offline Mauro Molinari
Messages: 278
Registered: July 2009
Senior Member
I still have problems: the WSDL editor is not available yet... :-(

Anybody can help?

Mauro.
Re: Problem updating from 3.2.0 to 3.2.1 using the WTP update site [message #553433 is a reply to message #553406] Tue, 17 August 2010 13:40 Go to previous messageGo to next message
Mauro Molinari is currently offline Mauro Molinari
Messages: 278
Registered: July 2009
Senior Member
Funny enough...

I did the following:
- through update manager, uninstalled all of the WTP 3.2.1 features I
had previously installed: some of them were not completely unistalled
because in use by other plugins
- reinstalled WTP 3.2.0 from the Helios website
- checked for updates

.... and now the update manager says that it finds JST Web UI 3.2.1,
Eclipse Faceted Project Framework JDT Enablement 3.2.1 and JST Server
Adapters 3.2.1!!!
So, these bundles seem to appear only when checking for updates, but not
when browsing the repository (either the Helios one or the WTP one).

HTH.
Mauro.
Re: Problem updating from 3.2.0 to 3.2.1 using the WTP update site [message #553434 is a reply to message #553433] Tue, 17 August 2010 13:49 Go to previous messageGo to next message
Mauro Molinari is currently offline Mauro Molinari
Messages: 278
Registered: July 2009
Senior Member
Another unexpected behaviour: if I try "Install new software" and select
the WTP update site, there is Eclipse XSL Developer Tools 1.1.1
available under WTP 3.2.1, while its icon says that it is actually an
update.
In fact, if I switch to the Helios update site, I find that Eclipse XSL
Developer Tools 1.1.0 is installed.

So, if I check the Eclipse XSL Editor 1.1.1 bundle from the WTP update
site in "Install" new software dialog, the update manager says that my
selections were changed because the Eclipse XSL Developer Tools is
already installed, so an update will be performed instead.

That's right, however the strange thing is that if I do a "check for
updates", the update manager does not find the Eclipse XSL Developer
Tools 1.1.1 update. Maybe the reason is that the Eclipse XSL Developer
Tools bundle has been installed as a dependency from any other bundle
and not by myself (so it is not listed in the Help | About Eclipse
Platform | Installation Details list)?

Mauro.
Re: Problem updating from 3.2.0 to 3.2.1 using the WTP update site [message #553435 is a reply to message #553406] Tue, 17 August 2010 14:05 Go to previous messageGo to next message
Larry Isaacs is currently offline Larry Isaacs
Messages: 1310
Registered: July 2009
Senior Member
On 8/17/2010 9:06 AM, Mauro Molinari wrote:
> I still have problems: the WSDL editor is not available yet... :-(
>
> Anybody can help?
>
> Mauro.

Try temporarily adding -debug and -clean to your Eclipse startup
arguments. The -clean should force Eclipse to "resolve" what plug-ins
will participate in the running Eclipse and -debug should record which
plug-ins fail to resolve due to missing dependencies. Check the Error
Log view to see which plug-ins are failing to resolve and why. It may
not be easy to figure out the root problem(s), but I'm not aware of any
other way to get clues when certain plug-ins are running for some
unknown reason.

Cheers,
Larry
Re: Problem updating from 3.2.0 to 3.2.1 using the WTP update site [message #553645 is a reply to message #553435] Wed, 18 August 2010 09:38 Go to previous messageGo to next message
Mauro Molinari is currently offline Mauro Molinari
Messages: 278
Registered: July 2009
Senior Member
Thank you Larry for your help.
Unfortunately, "-clean" did not help. To be honest, recently I worked
with a bunch of Eclipse installations/updates and "-clean" didn't help
in any case. In one case it even caused Eclipse to restart repeatedly
(the splash screen kept on showing, hiding, showing, hiding, etc.). So
it seems like -clean does not really clean all that it should.

Anyway, coming back to this problem: as I wrote in another message, the
final solution was to unistall WTP 3.2.1, install WTP 3.2.0 and then
update to WTP 3.2.1.

My feeling is that WTP 3.2.1 bundles are not set up properly for a
"from-scratch" installation via update manager, but are suited only to
update an existing 3.2.0 installation.

Secondly, I can't find WTP 3.2.1 in the Helios Repository, while the WTP
homepage says it is there, too. I can only find it in the WTP update
site repository.

Moreover, there are certainly some issues when mixing plugins installed
through update manager and other installed manually (in dropins),
especially when you then try to remove manually installed ones or to
update them using update manager. The problem is that it's hard to
diagnose the source of these problems and often the solution is to
re-install the whole platform from scratch :-(

Mauro.
Re: Problem updating from 3.2.0 to 3.2.1 using the WTP update site [message #553757 is a reply to message #553645] Wed, 18 August 2010 17:35 Go to previous messageGo to next message
Larry Isaacs is currently offline Larry Isaacs
Messages: 1310
Registered: July 2009
Senior Member
On 8/18/2010 5:38 AM, Mauro Molinari wrote:
> Thank you Larry for your help.
> Unfortunately, "-clean" did not help. To be honest, recently I worked
> with a bunch of Eclipse installations/updates and "-clean" didn't help
> in any case. In one case it even caused Eclipse to restart repeatedly
> (the splash screen kept on showing, hiding, showing, hiding, etc.). So
> it seems like -clean does not really clean all that it should.
>
> Anyway, coming back to this problem: as I wrote in another message, the
> final solution was to unistall WTP 3.2.1, install WTP 3.2.0 and then
> update to WTP 3.2.1.
>
> My feeling is that WTP 3.2.1 bundles are not set up properly for a
> "from-scratch" installation via update manager, but are suited only to
> update an existing 3.2.0 installation.
>
> Secondly, I can't find WTP 3.2.1 in the Helios Repository, while the WTP
> homepage says it is there, too. I can only find it in the WTP update
> site repository.
>
> Moreover, there are certainly some issues when mixing plugins installed
> through update manager and other installed manually (in dropins),
> especially when you then try to remove manually installed ones or to
> update them using update manager. The problem is that it's hard to
> diagnose the source of these problems and often the solution is to
> re-install the whole platform from scratch :-(
>
> Mauro.

Hi Mauro,

I'm glad you got it working. Note that -clean isn't intended to fix any
problems. The -clean will force a "resolution" to occur, which would
otherwise occur only once and won't occur again until Eclipse thinks
something has changed. The -clean in conjunction with -debug should
show you which plug-ins aren't loading and why in the Error Log. In the
future, if you are re-installing, you can just add the -debug and your
Error Log will show the resolution errors that occur during normal use.

I tried installing WTP 3.2.1 directly to a plain Eclipse 3.6 SDK and it
seemed to work fine for me. I've tended to keep my various Eclipse
installs either "manual only" or "update only", so I don't know what
issues might occur when they are mixed.

Cheers,
Larry
Re: Problem updating from 3.2.0 to 3.2.1 using the WTP update site [message #553842 is a reply to message #553757] Thu, 19 August 2010 07:22 Go to previous messageGo to next message
Mauro Molinari is currently offline Mauro Molinari
Messages: 278
Registered: July 2009
Senior Member
Il 18/08/2010 19.35, Larry Isaacs ha scritto:
> On 8/18/2010 5:38 AM, Mauro Molinari wrote:
> I'm glad you got it working. Note that -clean isn't intended to fix any
> problems. The -clean will force a "resolution" to occur, which would
> otherwise occur only once and won't occur again until Eclipse thinks
> something has changed. The -clean in conjunction with -debug should show

I see, but there are some cases I cannot understand. For instance:
- if I manually add something in "dropins", Eclipse realizes it has
changed or I must use -clean? I had positive experiences that it isn't
necessary
- if I manually delete something from "dropins", Eclipse realizes it has
changed or I must use -clean? I had negative experiences in which either
using -clean or not, the Eclipse installation did get messed up
- it happened at least a couple of times that having WTP version x
installed, then placing WTP version y (y>x) in dropins, either using
-clean or not, the resolution did not "realize" there was WTP version y
in dropins, or it did but only for some of its bundles (and not for all)

> you which plug-ins aren't loading and why in the Error Log. In the
> future, if you are re-installing, you can just add the -debug and your
> Error Log will show the resolution errors that occur during normal use.

I'll try the -debug option next time, thank you.

> I tried installing WTP 3.2.1 directly to a plain Eclipse 3.6 SDK and it
> seemed to work fine for me. I've tended to keep my various Eclipse
> installs either "manual only" or "update only", so I don't know what
> issues might occur when they are mixed.

It seemed to work fine for me, too, but it actually wasn't, as described
in the second message of this thread. And I think it was because some
bundles (like JST Server Adapters, JST Server UI/Web UI and Eclipse
Faceted Project Framework JDT Enablement) were not shown in the "Istall"
new software dialog inside the WTP update site repository for WTP 3.2.1
folder, while these were proposed when performing a "check for update"
over an existing 3.2.0 installation.

If you try again installing WTP 3.2.1 directly into a plain Eclipse 3.6
SDK through "Install new software", which available packages are shown
to you in both the Helios Update Site and WTP update site?

Mauro.
Re: Problem updating from 3.2.0 to 3.2.1 using the WTP update site [message #554024 is a reply to message #553842] Thu, 19 August 2010 18:04 Go to previous messageGo to next message
Larry Isaacs is currently offline Larry Isaacs
Messages: 1310
Registered: July 2009
Senior Member
On 8/19/2010 3:22 AM, Mauro Molinari wrote:
> Il 18/08/2010 19.35, Larry Isaacs ha scritto:
>> On 8/18/2010 5:38 AM, Mauro Molinari wrote:
>> I'm glad you got it working. Note that -clean isn't intended to fix any
>> problems. The -clean will force a "resolution" to occur, which would
>> otherwise occur only once and won't occur again until Eclipse thinks
>> something has changed. The -clean in conjunction with -debug should show
>
> I see, but there are some cases I cannot understand. For instance:
> - if I manually add something in "dropins", Eclipse realizes it has
> changed or I must use -clean? I had positive experiences that it isn't
> necessary

Adding something to "dropins" would trigger *one* "resolve", so use of
-clean wouldn't matter. A -clean could force the "resolve" to be done
again without any other changes so that in conjunction with -debug you
could see which plug-ins weren't running.

> - if I manually delete something from "dropins", Eclipse realizes it has
> changed or I must use -clean? I had negative experiences in which either
> using -clean or not, the Eclipse installation did get messed up

I'm not an expert on "p2", but I've never assumed doing this is valid.
I don't know how well "p2" deals with plug-ins disappearing.

> - it happened at least a couple of times that having WTP version x
> installed, then placing WTP version y (y>x) in dropins, either using
> -clean or not, the resolution did not "realize" there was WTP version y
> in dropins, or it did but only for some of its bundles (and not for all)

Again, I'm not an expert on what "p2" can handle. I've avoided mixing
the use of updating and dropins in the same Eclipse install.
>
>> you which plug-ins aren't loading and why in the Error Log. In the
>> future, if you are re-installing, you can just add the -debug and your
>> Error Log will show the resolution errors that occur during normal use.
>
> I'll try the -debug option next time, thank you.
>
>> I tried installing WTP 3.2.1 directly to a plain Eclipse 3.6 SDK and it
>> seemed to work fine for me. I've tended to keep my various Eclipse
>> installs either "manual only" or "update only", so I don't know what
>> issues might occur when they are mixed.
>
> It seemed to work fine for me, too, but it actually wasn't, as described
> in the second message of this thread. And I think it was because some
> bundles (like JST Server Adapters, JST Server UI/Web UI and Eclipse
> Faceted Project Framework JDT Enablement) were not shown in the "Istall"
> new software dialog inside the WTP update site repository for WTP 3.2.1
> folder, while these were proposed when performing a "check for update"
> over an existing 3.2.0 installation.
>
> If you try again installing WTP 3.2.1 directly into a plain Eclipse 3.6
> SDK through "Install new software", which available packages are shown
> to you in both the Helios Update Site and WTP update site?

Sorry, I spoke too soon. A little more checking shows that the JST
server features aren't coming down with the installation from
http://download.eclipse.org/webtools/repository/helios/ and installing
just the "Web Tools Platform (WTP) 3.2.0" or "Web Tools Platform (WTP)
3.2.1" categories. Though the JST server features aren't visible (I
believe this is by design), I had assumed they would still have been
installed since I thought they were part of the "Eclipse Java EE
Developer Tools" feature. This assumption appears to be incorrect.

To see the JST server features, you would have to uncheck "Group items
by Category". To include the JST server features in the install you
would need to check the "JST Server UI" and "JST Server Adapters
3.2.0.v201005241530-208Z7w31211419" (the preview server). For WTP 3.2.1
also check the "JST Server Adapters
3.2.1.v20100707-777HFGQCcNBDiBiHa4BA8" (the generic and Tomcat servers).
Checking "JST Server Adapters
3.2.0.v201005241530-777HFGPCcNBDiBgIc4BA8" instead would give you WTP 3.2.0.

I'll see about opening a bug for this. The -clean and -debug won't help
here since the plug-ins you need to run simply aren't there. Comparing
some "feature" directories, it would appear that to duplicate what you
get in the WTP zip, you would need to also install "JST Web UI" as well.
That appears to pull down the full set of WTP plug-ins.

Cheers,
Larry


>
> Mauro.
Re: Problem updating from 3.2.0 to 3.2.1 using the WTP update site [message #554106 is a reply to message #554024] Fri, 20 August 2010 08:05 Go to previous messageGo to next message
Mauro Molinari is currently offline Mauro Molinari
Messages: 278
Registered: July 2009
Senior Member
Il 19/08/2010 20.04, Larry Isaacs ha scritto:
> I'm not an expert on "p2", but I've never assumed doing this is valid. I
> don't know how well "p2" deals with plug-ins disappearing.

So, what is the correct way to uninstall a plugin previously manually
installed in dropins? It does not show in About Eclipse Platform |
Installation Details | Installed Software if installed this way...

> Again, I'm not an expert on what "p2" can handle. I've avoided mixing
> the use of updating and dropins in the same Eclipse install.

Right. However, what do I have to do if I need to install an unreleased
(e.g. weekly build) version of WTP on top of my existing Eclipse
production installation completely managed through Update Manager (in
case I need, for instance, to have a critical bug fix and I don't have
time to wait for the next released version, taking care of all the risks
implied by the use of an unreleased one)? Is there any WTP weekly builds
update site? Or should I better use the P2 repositories in zipped format
rather than the manual installation procedure in my case? Would they
work correctly then?

> I'll see about opening a bug for this. The -clean and -debug won't help

Thank you. I would appreciate if you could post here back the bug link
when you've done.

Mauro.
Re: Problem updating from 3.2.0 to 3.2.1 using the WTP update site [message #554256 is a reply to message #554106] Fri, 20 August 2010 19:23 Go to previous message
Larry Isaacs is currently offline Larry Isaacs
Messages: 1310
Registered: July 2009
Senior Member
On 8/20/2010 4:05 AM, Mauro Molinari wrote:
> Il 19/08/2010 20.04, Larry Isaacs ha scritto:
>> I'm not an expert on "p2", but I've never assumed doing this is valid. I
>> don't know how well "p2" deals with plug-ins disappearing.
>
> So, what is the correct way to uninstall a plugin previously manually
> installed in dropins? It does not show in About Eclipse Platform |
> Installation Details | Installed Software if installed this way...

I don't know as I never do this. I've not experimented with the
Uninstall button on the Installed Software page or the Revert button on
the Installation History page to see exactly what possible.
>
>> Again, I'm not an expert on what "p2" can handle. I've avoided mixing
>> the use of updating and dropins in the same Eclipse install.
>
> Right. However, what do I have to do if I need to install an unreleased
> (e.g. weekly build) version of WTP on top of my existing Eclipse
> production installation completely managed through Update Manager (in
> case I need, for instance, to have a critical bug fix and I don't have
> time to wait for the next released version, taking care of all the risks
> implied by the use of an unreleased one)? Is there any WTP weekly builds
> update site? Or should I better use the P2 repositories in zipped format
> rather than the manual installation procedure in my case? Would they
> work correctly then?
>

I'm afraid this isn't a use case I've had to work out. I do mostly
plug-in development, so my "development" Eclipse doesn't need to get
updated very often. The Eclipse's that include WTP are ones I'm using
for testing and I effectively build them from scratch each time I need
one that has something different or newer. For testing, I want to know
for sure what versions of stuff is running and don't want an
"installation history" to cloud up that aspect. As a result, I "manage"
the installed software using ".link" files in the "dropins" folder which
point to folders containing expanded zips. If some software doesn't
provide a zip, I'll toss down a fresh Eclipse, install the software, and
using date-time stamps, copy the new stuff in "features" and "plugins"
to a separate folder. This may be more trouble than you want to bother
with.

>> I'll see about opening a bug for this. The -clean and -debug won't help
>
> Thank you. I would appreciate if you could post here back the bug link
> when you've done.

See https://bugs.eclipse.org/bugs/show_bug.cgi?id=323245

Cheers,
Larry

>
> Mauro.
Previous Topic:WTP can be installed on top of HPUX eclipse SDK?
Next Topic:Apache Derby Core/UI Plugin
Goto Forum:
  


Current Time: Sat Oct 25 22:06:13 GMT 2014

Powered by FUDForum. Page generated in 0.12298 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software