[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [aspectj-users] Building Eclipse from source using AspectJ; Checkpointing; Tracing
|
Craig,
Do you get the error when running the
configuration or opening it? I presume your local Eclipse project is actually
call "demo.hello" i.e. you went to equinox-incubator/aspects/demos/demo.hello
and simply did "Check Out"? There is a bug in Eclipse 3.2 that
means some hard coded values end up in the launch configuration but looking
at CVS for "Hello World Demo.launch" I don't see any problems.
Do you have a space in the directory name for you workspace because that
can also cause problems? If the problem persists you may need to
create a new launch configuration specifying the config.ini in the project.
>Additionally in general terms, if I understand Equinox
correctly, it allows users to work with specific compilation units called
>bundles at the time that aspects are written, thus reducing compilation
and linking effort?
Bundles are actually an OSGi thing (Equinox
is just one implementation of the specification which happens to be used
in Eclipse) and refer to units of development (each one is a plug-in project),
deployment and versioning. AspectJ aspects still work at the class level
but the Aspects Incubator allows you to scope behaviour at the bundle level
which in the Eclipse runtime makes more sense. Not only can you package
you new feature (which may comprise classes, interfaces and other stuff
as well as an aspect) as a bundle but you can also determine which parts
of Eclipse get the new feature by specifying the appropriate bundles.
If you didn't attend EclipseCon 2007
or didn't see my Long Talk you might like to see the slides: http://www.eclipsecon.org/2007/index.php?page=sub/&id=3848.
They show the various ways to package aspects using the Aspects Incubator
(AOSGi) depending on what you are trying to achieve. The demos I showed
will be available shortly.
Cheers
Matthew Webster
AOSD Project
Java Technology Centre, MP146
IBM United Kingdom Limited
Hursley Park, Winchester, SO21 2JN, England
Telephone: +44 196 2816139 (external) 246139 (internal)
"Craig Ugoretz"
<craigugoretz@xxxxxxxxx>
Sent by: aspectj-users-bounces@xxxxxxxxxxx
14/03/2007 10:22
|
Please respond to
aspectj-users@xxxxxxxxxxx |
|
|
To
| aspectj-users@xxxxxxxxxxx
|
|
cc
|
|
|
Subject
| Re: [aspectj-users] Building Eclipse
from source using AspectJ; Checkpointing;
Tracing |
|
Matthew,
Thank you for your advice. However,
I am having trouble with launching a JUnit plugin for the HelloWorld demo.
In the launch configuration, I am getting the error that the "demo.hello
project does not exist", which is the default for this launch configuration.
I grabbed the source code directly from CVS, so there should not
be a problem there in terms of "things lining up".
Additionally in general terms,
if I understand Equinox correctly, it allows users to work with specific
compilation units called bundles at the time that aspects are written,
thus reducing compilation and linking effort?
Sincerely,
Craig
On 3/13/07, Matthew Webster <matthew_webster@xxxxxxxxxx>
wrote:
Craig,
If you want to weave Eclipse then a better approach would be load-time
weaving. Please take a look at the Aspects Equinox Incubator http://www.eclipse.org/equinox/incubator/aspects/index.php.
You can pick and choose the plug-ins that need weaving rather than trying
to build the whole platform from scratch.
Matthew Webster
AOSD Project
Java Technology Centre, MP146
IBM United Kingdom Limited
Hursley Park, Winchester, SO21 2JN, England
Telephone: +44 196 2816139 (external) 246139 (internal)
Hello,
I am interested in integrating a programming language into
Eclipse, and I am trying to figure out how to go about understanding how
Eclipse works. To this end, I thought of running Eclipse in a debugger
to understand its dynamic behavior. If that would be the case, I
think it would be useful to have some sort of tracing and/or checkpointing
support as well as logging. Because of these issues, AspectJ came
to mind because aspects would be a good way to implement these features.
At this time I desire to know, can Eclipse 3.2 be built from source
using AspectJ? I am the Ant build files would need to be altered.
Currently, I am have trouble compiling Eclipse 3.2 using regular
Java, getting tens of thousands of errors. I addressed this problem
with another newsgroup, but additionally if anyone has an idea here, I
would appreciate it. Also, could someone comment on the feasibility
of implementing the above features using AspectJ?
Thanks,
Craig
_______________________________________________
aspectj-users mailing list
aspectj-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/aspectj-users
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU
_______________________________________________
aspectj-users mailing list
aspectj-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/aspectj-users
_______________________________________________
aspectj-users mailing list
aspectj-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/aspectj-users
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU
