Scala's Eclipse plugin under control of AspectJ development build?

On Thu, Jan 28, 2010 at 11:58 AM, Walla, Marcus wrote:
> Hi Scala Eclipse developers,
>
> I have a more stupid question about the use of the Scala plugin (I used
> version 2.7.7.final) of the newest Eclipse 3.5.1 IDE which I installed
> last week under my Linux laptop. By starting eclipse from a console
> window there is a lot of AspectJ output and one line which confuses me
> and makes me little bit nervous. Is it right that you use the
> DEVELOPMENT build of AspectJ instead of a stable one? I am speaking of
> the following output line (you find the overall output in the attached
> file):

The Scala IDE for 2.7.7.final shipped with the version of the weaver
that matched the then most current version of Equinox Aspects and JDT
Weaving, all of which should be considered somewhat experimental. The
IDE for 2.8 will ship with a later version.

> Moreover I am wondering why you use the AspectJ stuff to contribute the
> Scala plugin. Do you have an advice where to find more infos about that
> (URL's of web pages will be ok).

You can get some background from my presentation at the JVM languages
summit here,

http://www.chuusai.com/documents/2009-09/jvmlangsummit-20090916.pdf

Cheers,

Miles

AspectJ is needed for the JDT weavingThat, in turn, is used to inject behaviour into existing eclipse Java functionality, so it can be extended (though monkey-patching) to support java-like languages.Originally conceived for use by AspectJ, it turned out to be pretty convenient for Scala as well.

2010/1/28 Walla, Marcus <marcus.walla@desy.de>

Hi Scala Eclipse developers,

I have a more stupid question about the use of the Scala plugin (I used
version 2.7.7.final) of the newest Eclipse 3.5.1 IDE which I installed
last week under my Linux laptop. By starting eclipse from a console
window there is a lot of AspectJ output and one line which confuses me
and makes me little bit nervous. Is it right that you use the
DEVELOPMENT build of AspectJ instead of a stable one? I am speaking of
the following output line (you find the overall output in the attached
file):

...
[org.eclipse.jdt.ui] info AspectJ Weaver Version DEVELOPMENT built on
Wednesday Mar 4, 2009 at 17:23:55 GMT
...

Moreover I am wondering why you use the AspectJ stuff to contribute the
Scala plugin. Do you have an advice where to find more infos about that
(URL's of web pages will be ok).

Cheers,
Marcus Walla

------------------------------------------------------------------------
Marcus Walla                       Deutsches Elektronen-Synchrotron MCS1
phone:  +49-40-8998-2628                                    Notkestr. 85
fax:    +49-40-8994-4303                                   22607 Hamburg
e-mail: marcus.walla@desy.de                                     Germany
------------------------------------------------------------------------

--
Kevin Wright

mail/google talk: kev.lee.wright@googlemail.com
wave: kev.lee.wright@googlewave.com
skype: kev.lee.wright
twitter: @thecoda

Hi Miles,

thank you for your fast response. I will read the slides you mentioned
in your mail.

Cheers, Marcus

------------------------------------------------------------------------
Marcus Walla Deutsches Elektronen-Synchrotron MCS1
phone: +49-40-8998-2628 Notkestr. 85
fax: +49-40-8994-4303 22607 Hamburg
e-mail: marcus.walla@desy.de Germany
------------------------------------------------------------------------

>-----Original Message-----
>From: Miles Sabin [mailto:xxx]
>Sent: Thursday, 28 January, 2010 13:40
>To: Walla, Marcus
>Cc: scala-tools@listes.epfl.ch
>Subject: Re: [scala-tools] Scala's Eclipse plugin under
>control of AspectJ development build?
>
>
>On Thu, Jan 28, 2010 at 11:58 AM, Walla, Marcus
> wrote:
>> Hi Scala Eclipse developers,
>>
>> I have a more stupid question about the use of the Scala plugin (I
>> used version 2.7.7.final) of the newest Eclipse 3.5.1 IDE which I
>> installed last week under my Linux laptop. By starting
>eclipse from a
>> console window there is a lot of AspectJ output and one line which
>> confuses me and makes me little bit nervous. Is it right
>that you use
>> the DEVELOPMENT build of AspectJ instead of a stable one? I am
>> speaking of the following output line (you find the overall
>output in
>> the attached
>> file):
>
>The Scala IDE for 2.7.7.final shipped with the version of the
>weaver that matched the then most current version of Equinox
>Aspects and JDT Weaving, all of which should be considered
>somewhat experimental. The IDE for 2.8 will ship with a later version.
>
>> Moreover I am wondering why you use the AspectJ stuff to contribute
>> the Scala plugin. Do you have an advice where to find more
>infos about
>> that (URL's of web pages will be ok).
>
>You can get some background from my presentation at the JVM
>languages summit here,
>
> http://www.chuusai.com/documents/2009-09/jvmlangsummit-20090916.pdf
>
>Cheers,
>
>
>Miles
>

Message Hi Kevin,   also thank you for your fast response.   Ahm, you mentioned "monkey-patching"? I found one advice at Wikipedia, which describes monkey-patching as to "... extend or modify the runtime code of dynamic languages ... without altering the original source code." But Java is a static language. Or do you mean by adding the "dynamic" functionality of AspectJ to Java it achieves a higher layer by altering the compiled code without modifing the original sources?   Cheers, Marcus

------------------------------------------------------------------------
Marcus Walla                       Deutsches Elektronen-Synchrotron MCS1
phone:  +49-40-8998-2628                                    Notkestr. 85
fax:    +49-40-8994-4303                                   22607 Hamburg
e-mail: marcus.walla@xxx                                     Germany
------------------------------------------------------------------------

-----Original Message-----
From: Kevin Wright [mailto: xxx ]
Sent: Thursday, 28 January, 2010 13:41
To: Walla, Marcus
Cc: scala-tools@listes.epfl.ch
Subject: Re: [scala-tools] Scala's Eclipse plugin under control of AspectJ development build?

AspectJ is needed for the JDT weaving That, in turn, is used to inject behaviour into existing eclipse Java functionality, so it can be extended (though monkey-patching) to support java-like languages. Originally conceived for use by AspectJ, it turned out to be pretty convenient for Scala as well.

2010/1/28 Walla, Marcus <marcus.walla@ xxx >

Hi Scala Eclipse developers,

I have a more stupid question about the use of the Scala plugin (I used
version 2.7.7.final) of the newest Eclipse 3.5.1 IDE which I installed
last week under my Linux laptop. By starting eclipse from a console
window there is a lot of AspectJ output and one line which confuses me
and makes me little bit nervous. Is it right that you use the
DEVELOPMENT build of AspectJ instead of a stable one? I am speaking of
the following output line (you find the overall output in the attached
file):

...
[org.eclipse.jdt.ui] info AspectJ Weaver Version DEVELOPMENT built on
Wednesday Mar 4, 2009 at 17:23:55 GMT
...

Moreover I am wondering why you use the AspectJ stuff to contribute the
Scala plugin. Do you have an advice where to find more infos about that
(URL's of web pages will be ok).

Cheers,
Marcus Walla

------------------------------------------------------------------------
Marcus Walla                       Deutsches Elektronen-Synchrotron MCS1
phone:  +49-40-8998-2628                                    Notkestr. 85
fax:    +49-40-8994-4303                                   22607 Hamburg
e-mail: marcus.walla@ xxx                                                  Germany
------------------------------------------------------------------------

--
Kevin Wright

mail/google talk: kev.lee.wright@ xxx 
wave: kev.lee.wright@ xxx 
skype: kev.lee.wright
twitter: @thecoda