Re: Getting the plugin running in Eclipse PDE

Sorry, should have sent to the list :-)

---------- Forwarded message ----------
From: Jeppe Nejsum Madsen
Date: Wed, Jul 8, 2009 at 4:44 PM
Subject: Re: [scala-tools] Getting the plugin running in Eclipse PDE
To: Naftoli Gugenhem

On Wed, Jul 8, 2009 at 4:22 PM, Naftoli Gugenhem wrote:
> Yes, it needs to be enabled. Is the eclipse folder writeable?

Depends on what you mean be the Eclipse folder? I'm not sure if I
expressed this clearly, but I'm trying to run the Scala plugin hosted
in an Eclipse Plugin Development Environment (PDE) workbench, i.e.
being able to debug, modify etc. the Scala plugin (and other Eclipse
plugins).

So in this case the eclipse folder (i think, I haven't done PDE
development since Eclipse 2 :-) is somewhere within my workspace which
should definitely be writable.

I wonder if enabling JDT Weaving is stored in config.ini. It seems the
PDE creates a new one on each launch, which is why the Wiki page said
to change it but at the same time writes that this shouldn't be
necessary for 3.5??

/Jeppe

If the reason you are hesitant to work with 2.8 is because you use 2.7.x with lift, I would point out that the 2.7.x plugin was designed for eclipse 3.4, while 2.8 is for 3.5, so it would anyway be a separate eclipse instance.
P.S. Does anyone have 2.7.5 working well in eclipse 3.5?

-------------------------------------
Miles Sabin wrote:

On Wed, Jul 8, 2009 at 10:36 PM, Jeppe Nejsum Madsen wrote:
> The issue I was trying to solve was the inability of the Eclipse JUnit
> runner to launch specs test cases without weird workarounds. A brief
> debugging session (with 2.7.5) showed that with a declaration like
>
> class UserUnitTest extends JUnit4(UserSpec)
>
> It seems like Eclipse is unable to find the superclass of UserUnitTest
> and therefore figure out that JUnit4 has the RunWith annotation. I
> haven't digged deep into the Scala plugin, but was wondering if this
> is some bigger piece that's missing or just i mishap in this specific
> case?

This sounds like quite a plausible diagnosis ... the IDE isn't
constructing the corresponding JDT type hierarchy completely/correctly
at the moment, and very likely that's frustrating searches which
depend on the type hierarchy.

Patches (against trunk if at all possible) which address that would be
very much appreciated, but failing that, a ticket on Trac so that this
doesn't get forgotten would help too.

Cheers,

Miles

On Thu, Jul 9, 2009 at 4:18 PM, Naftoli Gugenhem wrote:
> P.S. Does anyone have 2.7.5 working well in eclipse 3.5?

It works just fine. I'd recommend 3.5 over 3.4.2 as it happens.

Cheers,

Miles

Arrgh again missed the list.

To list owner: Could the Reply-To please be set to the list??

/Jeppe

---------- Forwarded message ----------
From: Jeppe Nejsum Madsen
Date: Thu, Jul 9, 2009 at 5:30 PM
Subject: Re: [scala-tools] Getting the plugin running in Eclipse PDE
To: Naftoli Gugenhem

On Thu, Jul 9, 2009 at 5:18 PM, Naftoli Gugenhem wrote:
> If the reason you are hesitant to work with 2.8 is because you use 2.7.x with lift, I would point out that the 2.7.x plugin was designed for eclipse 3.4, while 2.8 is for 3.5, so it would anyway be a separate eclipse instance.
> P.S. Does anyone have 2.7.5 working well in eclipse 3.5?

Yes :-) Works fine

Eclipse is (in general) pretty good at maintaining backwards
compatibility for plugins

/Jeppe

Hmm. I didn't seem to work for me but I'll try again. Thank for the info.

-------------------------------------
Miles Sabin wrote:

On Thu, Jul 9, 2009 at 4:18 PM, Naftoli Gugenhem wrote:
> P.S. Does anyone have 2.7.5 working well in eclipse 3.5?

It works just fine. I'd recommend 3.5 over 3.4.2 as it happens.

Cheers,

Miles

Jeppe Nejsum Madsen wrote:
> Arrgh again missed the list.
>
> To list owner: Could the Reply-To please be set to the list??
>
> /Jeppe
>

This is a recurring request. Last time I asked to our sysadmin, this was
the response:

Fabien Salvi wrote:
> I don't agree :)
>
> There was already a thread on the scala mailing list some time ago about
> that :
> http://osdir.com/ml/lang.scala.user/2008-01/msg00136.html
> After discussions with Martin, we decided to let the setting like it is
> now because only half people were in favor of a reply-to-list...
>
> In my opinion, a reply-to-list is not a good solution, because it makes
> difficult to reply only to the sender. Eg: with my Thunderbird (I don't
> know about others email clients), when the list is configured with
> reply-to-list (eg LAMP list), a "Reply" or "Reply-All" only gives the
> mailing list address, not the sender address. If I want to reply only to
> the sender, I have to copy and paste his email, which is quite annoying...
> Anyway, it's not up to me to decide about that, but I think you should
> see with Martin and others because it was already discussed before.