FD & Galileo (Eclipse 3.5) Compatible?

[DG]

I am having issues with my CFEclipse breakpoints firing on Eclipse 3.3
(ran great on 3.2). RDS and Fusion Debug still runs great.

A clean install of Galileo (eclipse 3.5) has breakpoints firing well,
so am wondering if 3.3 has issues.

Any known campibility issues between FD 2.0.1 and Eclipse 3.5? Do I
need a clean install to get it all going again?

[charlie arehart]

This is a little confusing, DG. First, you mention "CFEclipse breakpoints"
but of course there is no debugger in CFEclipse, per se. Did you mean
"FusionDebug breakpoints"?

But then you say it's working in 3.5, then you ask if there are "any known
compatibility issues between FD 2.0.1 and Eclipse 3.5". Did you mean "and
Eclipse 3.3"?

Anyway, I ran FD on Eclipse 3.3 in the past and it worked fine.

You say you did a clean install of 3.5. Have you tried doing a clean install
of 3.3? By that I mean either installing Eclipse into a new directory and
installing the plug in into that? And/or have you tried using a new
workspace even with a new install? That can help sometimes.

Finally, you may also benefit from the -clean option when launching Eclipse,
which helps remove cached entries for various things. Here's one resource
that talks about how to do that, as it's often a challenge for those not
used to working with the Windows command line:

http://wiki.eclipse.org/Graphical_Eclipse_FAQs#I_have_just_installed_a_plug-
in_but_I_do_not_see_any_indication_of_it_in_my_workspace._What_do_I_do.3F

Let us know if any of these help.

/charlie

[HHWD]

I am sorry for not being clear... My eclipse has both CFeclipse, CF8
debuggerplugin, RDS plugin and FD plugin. The breakpoints fire when FD
debugger is running. I have always "blended" Cfeclipse and CF8
debugger terminology. I did a clean install of Eclipse 3.5 w/
coldfusion debugger but no FD and all runs fine (different computer).
So I checked my FD documentation and the pdfs (a tad old) recommended
Eclipse 3.2 version. If 3.3 was buggy (which I cannot find any
documentation it is), then I would just upgrade the eclipse on my
computer I use FD on to 3.5.

So, I suppose, my question really was... since 3.5 is fairly new...
and I don't see any documentation w/ FD having issues with it, but
none "blessing" it either, I was checking to see if an upgrade was
safe. Since I use the FD 99% of the time (better speed), I don't want
to muck up my development area.

Before I do anything however, I will try to clean option. IF that
doesn't work, I may do a clean install and reinstall FD as well.

Thanks Charlie... sorry for being obtuse :) Tami

When I was on 3.2

On Jul 27, 9:53 pm, "charlie arehart" <charlie_li...@carehart.org>
wrote:

> This is a little confusing, DG. First, you mention "CFEclipse breakpoints"
> but of course there is no debugger in CFEclipse, per se. Did you mean
> "FusionDebug breakpoints"?
>
> But then you say it's working in 3.5, then you ask if there are "any known
> compatibility issues between FD 2.0.1 and Eclipse 3.5". Did you mean "and
> Eclipse 3.3"?
>
> Anyway, I ran FD on Eclipse 3.3 in the past and it worked fine.
>
> You say you did a clean install of 3.5. Have you tried doing a clean install
> of 3.3? By that I mean either installing Eclipse into a new directory and
> installing the plug in into that? And/or have you tried using a new
> workspace even with a new install? That can help sometimes.
>
> Finally, you may also benefit from the -clean option when launching Eclipse,
> which helps remove cached entries for various things. Here's one resource
> that talks about how to do that, as it's often a challenge for those not
> used to working with the Windows command line:
>

> http://wiki.eclipse.org/Graphical_Eclipse_FAQs#I_have_just_installed_...

[Peter Bailey [FusionDebug Team]]

Hi HHWD,

I thought we should add some details FYI, thanks as usual Charlie for
the quick support responses.

2.0.1 has some compatibility issues with Eclipse 3.4 Ganymede; these
will no doubt be the same in 3.5. The up and coming FusionDebug 3.0 is
compatible with 3.5 Galileo as well as 3.4.

With regards to the breakpoints not firing issue, 3.3 does not have
any issues like this I am aware of, and FD 2.0.1has been heavily used
and developed on 3.3 in the past. But with the set up you have
mentioned perhaps mappings/lookups are getting mixed.

One thing to mention is which breakpoints are being used/set. If you
have more then one Debugger installed, you will have multiple types of
breakpoints, FD will accept other types such as the CF8 ones, but the
FD breakpoints will not be accepted by CF8 in turn. If you are trying
to hit FD breakpoints with a CF8 debug connection, this could cause
breakpoints you expect not to fire. CFEclipse will set breakpoints of
differing types, depending on what you have installed.

If the problem persists please give as much detail on what connections/
breakpoints etc you are using and we shall look into it.

Regards,
Peter Bailey
[FusionDebug Team]