Eclipse Community Forums: ServerTools (WTP) » Status of M9 and opportunity for early testers: M9 planned for 11/23

Home » Language IDEs » ServerTools (WTP) » Status of M9 and opportunity for early testers: M9 planned for 11/23

Status of M9 and opportunity for early testers: M9 planned for 11/23 [message #147539]

Thu, 17 November 2005 12:22

Eclipse User

As some of you have noticed, we have produced an I-build, I200511162235,=

that we think is suitable for some "in depth" testing, as we prepare to =
declare M9
next week.

If any (more) of you in the community are able and willing to take a loo=
k at this
build,

http://download.eclipse.org/webtools/downloads/drops/I-I2005 11162235-200=
511162235/

that would be helpful in knowing if we have any "show stopping" defects =
that need
to be fixed before declaring M9.

BTW, I don't think we've announce here, or updated website yet, but our =
official
planned date for M9 release was moved from Friday the 18th, to Wednesday=
the 23rd.
(So we in the US will *really* have something to be thankful for! :)
This was simply due to some "last minute" improvements we felt critical,=
but
we wanted to have at least of weeks's worth of stability testing.

So, if any of you can contribute by some testing over the next few days,=
that'd be great.

Re: Status of M9 and opportunity for early testers: M9 planned for 11/23 [message #147559 is a reply to message #147539]

Thu, 17 November 2005 14:20

Eclipse User

I'm not sure yet if this is just my configuration or something, but the
validator for Dynamic Web Projects seems *way* slower than in previous
builds for me. I'll try to investigate this further. Other than that, it
seems a lot more bug-free to me than previous recent I-builds. A lot of
things seem more logical and just work better on this one. Nice job guys!

David Williams wrote:
>
> As some of you have noticed, we have produced an I-build, I200511162235,
> that we think is suitable for some "in depth" testing, as we prepare to
> declare M9
> next week.
>
> If any (more) of you in the community are able and willing to take a
> look at this
> build,
>
> http://download.eclipse.org/webtools/downloads/drops/I-I2005 11162235-200511162235/
>
>
> that would be helpful in knowing if we have any "show stopping" defects
> that need
> to be fixed before declaring M9.
>
> BTW, I don't think we've announce here, or updated website yet, but our
> official
> planned date for M9 release was moved from Friday the 18th, to Wednesday
> the 23rd.
> (So we in the US will *really* have something to be thankful for! :)
> This was simply due to some "last minute" improvements we felt critical,
> but
> we wanted to have at least of weeks's worth of stability testing.
>
> So, if any of you can contribute by some testing over the next few days,
> that'd be great.

Re: Status of M9 and opportunity for early testers: M9 planned for 11/23 [message #147672 is a reply to message #147539]

Fri, 18 November 2005 05:09

Eclipse User

I still seem to have the problem that I reported a few days ago with the last 'I' build - I cannot edit JSP
files, I get the following exception thrown:

java.lang.NoClassDefFoundError: org/eclipse/wst/html/ui/StructuredTextViewerConfigurationHTM L
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Unknown Source)
at java.lang.Class.getConstructor0(Unknown Source)
at java.lang.Class.newInstance0(Unknown Source)
at java.lang.Class.newInstance(Unknown Source)
at org.eclipse.core.internal.registry.ConfigurationElement.crea teExecutableExtension(ConfigurationElement.java:162)
at org.eclipse.core.internal.registry.ConfigurationElement.crea teExecutableExtension(ConfigurationElement.java:142)
at org.eclipse.core.internal.registry.ConfigurationElement.crea teExecutableExtension(ConfigurationElement.java:129)
at
org.eclipse.core.internal.registry.ConfigurationElementHandl e.createExecutableExtension(ConfigurationElementHandle.java: 48)
at
org.eclipse.wst.sse.ui.internal.ExtendedConfigurationBuilder .createExtension(ExtendedConfigurationBuilder.java:89)
at
org.eclipse.wst.sse.ui.internal.ExtendedConfigurationBuilder .createConfigurations(ExtendedConfigurationBuilder.java:134)
at
org.eclipse.wst.sse.ui.internal.ExtendedConfigurationBuilder .getConfigurations(ExtendedConfigurationBuilder.java:203)
at
org.eclipse.wst.sse.ui.internal.ExtendedConfigurationBuilder .getConfiguration(ExtendedConfigurationBuilder.java:175)
at org.eclipse.wst.sse.ui.StructuredTextEditor.createSourceView erConfiguration(StructuredTextEditor.java:1438)
at org.eclipse.wst.sse.ui.StructuredTextEditor.updateSourceView erConfiguration(StructuredTextEditor.java:2768)
at org.eclipse.wst.sse.ui.StructuredTextEditor.update(Structure dTextEditor.java:2440)
at org.eclipse.wst.sse.ui.StructuredTextEditor.setModel(Structu redTextEditor.java:2374)
at org.eclipse.wst.sse.ui.StructuredTextEditor.doSetInput(Struc turedTextEditor.java:1674)
at org.eclipse.ui.texteditor.AbstractTextEditor$16.run(Abstract TextEditor.java:2360)
at org.eclipse.jface.operation.ModalContext.runInCurrentThread( ModalContext.java:346)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.ja va:291)
at org.eclipse.jface.window.ApplicationWindow$1.run(Application Window.java:624)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:69)
at org.eclipse.jface.window.ApplicationWindow.run(ApplicationWi ndow.java:621)
at org.eclipse.ui.internal.WorkbenchWindow.run(WorkbenchWindow. java:2134)
at org.eclipse.ui.texteditor.AbstractTextEditor.internalInit(Ab stractTextEditor.java:2378)
at org.eclipse.ui.texteditor.AbstractTextEditor.init(AbstractTe xtEditor.java:2405)
at org.eclipse.wst.sse.ui.StructuredTextEditor.init(StructuredT extEditor.java:2049)
at org.eclipse.ui.internal.EditorManager.createSite(EditorManag er.java:778)
at org.eclipse.ui.internal.EditorReference.createPartHelper(Edi torReference.java:596)
at org.eclipse.ui.internal.EditorReference.createPart(EditorRef erence.java:384)
at org.eclipse.ui.internal.WorkbenchPartReference.getPart(Workb enchPartReference.java:552)
at org.eclipse.ui.internal.EditorReference.getEditor(EditorRefe rence.java:223)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched( WorkbenchPage.java:2362)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(Workben chPage.java:2295)
at org.eclipse.ui.internal.WorkbenchPage.access$9(WorkbenchPage .java:2287)
at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.ja va:2273)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:69)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPa ge.java:2268)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPa ge.java:2249)
at org.eclipse.ui.ide.IDE.openEditor(IDE.java:371)
at org.eclipse.ui.ide.IDE.openEditor(IDE.java:334)
at org.eclipse.ui.internal.ide.EditorAreaDropAdapter.openNonExt ernalEditor(EditorAreaDropAdapter.java:137)
at org.eclipse.ui.internal.ide.EditorAreaDropAdapter.asyncDrop( EditorAreaDropAdapter.java:110)
at org.eclipse.ui.internal.ide.EditorAreaDropAdapter.access$0(E ditorAreaDropAdapter.java:75)
at org.eclipse.ui.internal.ide.EditorAreaDropAdapter$1.run(Edit orAreaDropAdapter.java:69)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:123)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:3057)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2716)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:1699)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:367)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:143)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplicatio n.java:103)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivator.java:226)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:376)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:163)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334 )
at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
at org.eclipse.core.launcher.Main.run(Main.java:973)
at org.eclipse.core.launcher.Main.main(Main.java:948)

David Williams wrote:
>
> As some of you have noticed, we have produced an I-build, I200511162235,
> that we think is suitable for some "in depth" testing, as we prepare to
> declare M9
> next week.
>

<-- snip -->

Re: Status of M9 and opportunity for early testers: M9 planned for 11/23 [message #147680 is a reply to message #147539]

Fri, 18 November 2005 05:14

Eclipse User

My J2EE perspective seems to be broken - the screen is not repainting correctly - or rather the bottom 80-odd
pixels are not repainting correctly. This is on WinXP, and the non-repainting area seems to correspond to where
my auto-hide task bar resides. I can post a picture and elaborate further if reqd.

David Williams wrote:
>
> As some of you have noticed, we have produced an I-build, I200511162235,
> that we think is suitable for some "in depth" testing, as we prepare to
> declare M9
> next week.
>

<-- snip -->

Re: Status of M9 and opportunity for early testers: M9 planned for 11/23 [message #147754 is a reply to message #147539]

Fri, 18 November 2005 11:08

Eclipse User

It would really be good to keep the Milestone Overview site up to date.

As you mentioned, it still says M9 is tonday 11/18. I'm here looking for
M9. It is sloppy to have the site say it's coming, then to dig around and
find out it's a week later....

http://www.eclipse.org/webtools/plans/1.0/reports/report-mil estone-overview.html

-bob

Re: Status of M9 and opportunity for early testers: M9 planned for 11/23 [message #147785 is a reply to message #147672]

Fri, 18 November 2005 16:58

Eclipse User

Russell Dodd wrote:
> I still seem to have the problem that I reported a few days ago with the
> last 'I' build - I cannot edit JSP files, I get the following exception
> thrown:
>
> java.lang.NoClassDefFoundError:
> org/eclipse/wst/html/ui/StructuredTextViewerConfigurationHTM L

One thing you might want to do is install only EITHER the WST or WTP
build. We don't do any testing to ensure you can mix the two since
the WTP build should include all of the functionality in the
corresponding WST build. You should also make sure that any plugins
from prior WST/WTP builds have been removed before manually adding
the contents of a new build to your install, and that you restart
with -clean afterwards. Errors like this are almost always the
result of a problem with the install.

WTP = WST + JST (and eventually + JSF)

--
- Nitin

Re: Status of M9 and opportunity for early testers: M9 planned for 11/23 [message #147956 is a reply to message #147785]

Mon, 21 November 2005 05:34

Eclipse User

Nitin Dahyabhai wrote:
>
> One thing you might want to do is install only EITHER the WST or WTP
> build. We don't do any testing to ensure you can mix the two since the
> WTP build should include all of the functionality in the corresponding
> WST build. You should also make sure that any plugins from prior
> WST/WTP builds have been removed before manually adding the contents of
> a new build to your install, and that you restart with -clean
> afterwards. Errors like this are almost always the result of a problem
> with the install.
>
> WTP = WST + JST (and eventually + JSF)
>

Ahh - ok thanks for that. I will try out what you say.

Re: Status of M9 and opportunity for early testers: M9 planned for 11/23 [message #148245 is a reply to message #147539]

Tue, 22 November 2005 11:02

Eclipse User

Originally posted by: stefan.baramov.trx.com

I've set up the I200511162235 build with Eclipse SDK 3.1.0 and it works
great except one minor glitch. The JSP page does not get "auto reload".

Here is my configuration:
JDK 1.5
Eclipse SDK 3.1.0
WTP I200511162235
Tomcat 5.0.30

1. Create an empty web project. All jsp's are stored in web directory
(instead of WebContent).

2. Create a simple JSP.

3. Run the tomcat server and deploy the application

4. Load the JSP in a browser

5. Edit the JSP and refresh the browser. The new version does not show
up. The server still serves the old version of the JSP.

The same scenario works just fine on WTP 0.7

- Stefan Baramov

Re: Status of M9 and opportunity for early testers: M9 planned for 11/23 [message #148675 is a reply to message #148245]

Wed, 23 November 2005 14:21

Eclipse User

On Tue, 22 Nov 2005 11:02:46 -0500, Stefan Baramov <stefan.baramov@trx.c=
om> wrote:

> I've set up the I200511162235 build with Eclipse SDK 3.1.0 and it work=
s
> great except one minor glitch. The JSP page does not get "auto reload"=
..
>

I believe this is same as
https://bugs.eclipse.org/bugs/show_bug.cgi?id=3D112363
you might "watch" that bug to see when fixed.

Previous Topic:	Why two classes?
Next Topic:	formatting a jsp but skipping the undo stack

Goto Forum:

-=] Back to Top [=-

Current Time: Wed May 07 04:23:57 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter