how will 2007 support work?

[dingfelder]

I am anticipating purchase of either 2007 developer or 2007 enterprise, and I am wondering how support will be handled.

I anticipate that a number of issues could be "Eclipse" issues, since 2007 is an extension upon the Eclipse 3.2 framework.

If I do run into an eclipse bug, how will it get resolved?

After spending thousands for JBuilder, the last thing I want to be told is: "That is an eclipse bug. Please ask about it on the eclipse bug system". (My experience with eclipse is that things don't get quickly addressed very often, whereas I have been happy in the past with Borland fixing issues with a patch when issues have arisen.

I realize this is a tricky issue for CodeGear, as supporting Eclipse could open big can of worms, but I really need to know what I am getting my self into before I lay out a bunch of $ for an IDE and a support contract.

[Lori M Olson [TeamB]]

Post by dingfelder
I am anticipating purchase of either 2007 developer or 2007
enterprise, and I am wondering how support will be handled.
I anticipate that a number of issues could be "Eclipse" issues, since
2007 is an extension upon the Eclipse 3.2 framework.
If I do run into an eclipse bug, how will it get resolved?
After spending thousands for JBuilder, the last thing I want to be
told is: "That is an eclipse bug. Please ask about it on the
eclipse bug system". (My experience with eclipse is that things
don't get quickly addressed very often, whereas I have been happy in
the past with Borland fixing issues with a patch when issues have
arisen.
I realize this is a tricky issue for CodeGear, as supporting Eclipse
could open big can of worms, but I really need to know what I am
getting my self into before I lay out a bunch of $ for an IDE and a
support contract.

Keeping in mind that this is just my opinion...

Identifying and fixing Eclipse bugs that cause problems to
support-paying JB2007 customers HAS to be part and parcel of the whole
JB2007 package. If it isn't, they won't last long enough to produce a
JB2008.
--
Regards,

Lori Olson [TeamB]

------------

Save yourself, and everyone else, some time and search the
newsgroups and the FAQ-O-Matic before posting your next
question.

Google Advanced Newsgroup Search
http://www.google.ca/advanced_group_search
Other Newsgroup Searches:
http://www.borland.com/newsgroups/ngsearch.html
Joi Ellis's FAQ-O-Matic:
http://www.visi.com/~gyles19/fom-serve/cache/1.html

[Gillmer J. Derge [TeamB]]

Post by dingfelder
If I do run into an eclipse bug, how will it get resolved?

Repeating Lori's caveat, this is just my opinion. It's not the official
policy statement that you probably want. Having said that ...

In a way, this isn't really anything new. In older versions of
JBuilder, a bug might have been a JDK bug, an ICE browser bug (the
browser used for web view and the help system), some other third party
bug, or a Borland bug. It wasn't up to the user to deal with that. If
JBuilder 2006 doesn't work, then I don't care why or whose fault it is.
I just want it fixed. The same should be true with JB2007.

My recommendation would be that if you find a problem, report it in
QualityCentral. If it's important enough to you, vote on it in
QualityCentral. At that point, if it turns out to be something in
Eclipse code, that's CodeGear's problem, not yours.

If enough customers are complaining about the problem and voting on it
in QC and/or if it causes significant enough problems in the IDE, then I
imagine CodeGear would spend some of their developers' time to fix it.
If it's a minor problem where only one or two people have reported it or
there's an obvious workaround, then I imagine they might let it go until
Eclipse people get around to dealing with it.