[Dave Stubbs]

Since upgrading to 3.8GA I can’t make anything to do with JSP files work any more.

Config.
Clean install of Eclipse 3.0 GA
Clean install of MyEclipse IDE 3.8GA
Clean install of Current version of oxygenxml 4.2

Here are a list of the problems I have seen so far.

JSP validation does not report any errors at all (Everything checked in preferences, not overriden in project) I deliberately introduced an error and nothing happened at all.

If I reformat (CTRL+SHIFT+F) a jsp I get an error telling me that the key I pressed failed. The code has been reformatted as follows.

Import attribute has wrapped and put ; on the end of each import statement.

The following header code

<%@ page language=”java” import=”com.convergys.cbsci.preperation.gl.*,com.convergys.cbsci.model.*,com.convergys.cbsci.constants.*,com.convergys.cbsci.model.datatype.*,com.convergys.cbsci.view.*,java.util.*,com.convergys.framework.international.*,com.convergys.interactive.controller.*” %>

Was replaced with

<%@ page language=”java”
import=”com.convergys.framework.international.*;
import com.convergys.interactive.controller.*;

public class Flow_servicesavailable extends HttpServlet
{
public void _jspService(HttpServletRequest request, HttpServletResponse response) throws IOException, Se”%>

which is half baked to say the least.

Lots of code has been marked with the red underlines and the right margin markers, but not with an error marker in the left margin or agains the JSP file or in the problem panel. All filters are checked to display all error messages.

Some long lines have been wrapped, other haven’t. I can’t find how to set the line width for splitting, only the print margin.

I can’t get any of the HTML errors to appear at all. No yellow flashes anywhere.

A clean and rebuild does not make any of the errors appear.

General performance seems slower as well. Lots of occassional hang ups etc.

I think I am going to have to go back to beta 2 until the GA gets fixed.

[ingesol]

I agree, this upgrade from beta2 to GA is the worst experience I’ve had with myeclipse so far. I’m really annoyed because it seems to me that the race for features seems to be a higher priority than stability. Without a minimum of stability, I find the software close to useless.

This 3.8GA version is completely useless to me, and I will switch back to beta2 too.

[Riyad Kalla]

Guys,
Believe it or not we tried to avoid a 3rd beta because we were overdue with a release by a month, and wanted to *hook you up* with some great new editors by including the WTP editors before we released. All internal testing we did pointed to “Good” which is just ironic now… I think its safe to say that we have learned our lesson over this and it will never happen again. We are actually completely adjusting our development methologies and will from now on introduce public milestone cycles before a release is tagged GA again.

We can’t do anymore than appologize and ask that you hang in there while we clean up this mess. After all we agree with you guys, you should be pissed off this was a bad choice we made and we’ll take the lumps for it.

On a side note all the problems you listed have been filed with high priority in our tracker. We are going to try and get a service release out by weeks end with some of the most annoying bugs fixed and keep cranking out service releases until GA is stable.

[Dave Stubbs]

Thanks for the update.

We’re all, probably to a man (and woman), software developers, and know exactly what things are like. Customers always have expectations and we as developers hope we managed to achieve them, but there is always something that slips through the net.

Don’t worry unnecessarily, ME users are pretty much a loyal bunch and are on the whole patient. Another week is OK with me.

I’m just glad I tested out the install fully before letting the rest of the development team loose on it.

I just have to rebuild everything now, so I have lost a days work over this, but that’s software for you.

[support-michael]

Lots of code has been marked with the red underlines and the right margin markers, but not with an error marker in the left margin or agains the JSP file or in the problem panel. All filters are checked to display all error messages.

Note the problems view is reserved for errors identified during a build process (i.e., validation/compilation). So transient syntax annotations that show up in the right-hand margin are not added to the problems view. This behavior is identical to that of the Java editor.

The new ME editor suite is patterned after the Java editor in may ways. For example the new editor suite performs real-time syntax check-as-you-type similar to the Java editor and presents these errors/warning in the right-hand overview/margin. Also just like the Java editor the ME real-time error annotations are not added to the problems view. Instead only compilation/validation errors are added to the problems view.

For example if you enable JSP Validation (see project properties),introduce an error into a JSP file, save that file with project auto-build enabled, the JSP validator will create a validation annotation that will appear in the left margin of the JSP editor as well as a problem’s view entry will have been created.

Hope this explains some of the new editor behavior.

[Author]

Posts