forrest-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bhatia Praveen, HCLT-Japan" <>
Subject RE: Forrest Coocon eclipse?
Date Mon, 23 May 2005 04:21:07 GMT
     Tried further with the installation of the Forrest plugin. By changing
the workspace to a new workspace, downloading org.burrokeet.serveletEngine
and WTP progressed further but then got stuck at the following
classes/methods being not found in

Perhaps these are from older WTP of IBM (not sure). Anyway, how do I get
them or circumvent them.

The relevant code snippet where the error comes in is as
                    url = new URL("http://localhost:8888");
                    IWorkbenchBrowserSupport browserSupport =
                    IWebBrowser browser = browserSupport.createBrowser(
                            null, null, null);



-----Original Message-----
From: Ross Gardler
Sent: 2005/05/19 19:37
Subject: Re: Forrest Coocon eclipse?

Ross Gardler wrote:
> Bhatia Praveen, HCLT-Japan wrote:
>> Hello,
>>       Thanks for the instructions. Most of it is fine but for some 
>> problems
>> for WTP.......
>>       Tried the steps given in the readme for forrest plugin for
>> Got stuck in the following as the location of .zip doesn't exist any 
>> longer.
> Hmmm... The WTP package has gone way passed that early release now and
> have yet to update the plugin to work with the latest milestone
> I'll do those conversions now as it needs to be done and someone on 
> Burrokeet hit the same problem earlier today.
> I'll notify via this list when the update is done.

I've now updated the plugin to work with WTP1.0M4. The readme has been 
updated, it's the same apart from we now work with Eclipse 3.1M* and 

Since you stared installing on the 3.0 version of Eclipse you should be 
OK sticking with that (although it is untested here).

If you start from the same place you were up to in the install 
instructions it should work, although you may need to update the 
dependant packages for the WTP using Eclipses update manageer.

Please let us know if this works as you will be the first to test this 
new configuration.


View raw message