There is hope for having the debugger
seek to “.aj” files on the horizon. It requires the debugger to
support JSR 45, which I believe is scheduled for Eclipse 3.0. We are eager to
see this as well, and will let users know once it is working in the milestone
releases.
Note that you can use both Ant and AJDT
from within Eclipse on the same project. It sounds like you just need to do
the Ant build for verification, and can develop using the AJDT plug-in.
Mik
From:
aspectj-users-admin@xxxxxxxxxxx [mailto:aspectj-users-admin@xxxxxxxxxxx] On Behalf Of Volkmann, Mark
Sent: Thursday, July 31, 2003 4:32 PM
To: 'aspectj-users@xxxxxxxxxxx'
Bummer. I
hope that AJDT can be modified to support .aj files soon. Some people on
my team are concerned about this because if they try to compile an application
with a standard Java compiler, it will attempt to compile the aspect source
files and fail.
On your question
about why I build with Ant from inside Eclipse ...
I do both.
I let Eclipse build the project and I run Ant from inside Eclipse. My
reason for using Ant is just to verify that I have a good, working Ant build
file. I can't assume that all the developers working on my project are
using Eclipse, so I need to provide an Ant build file that I know works.
Of course I could just test the Ant build file from the command-line, but it's
convenient to be able to just run it from Eclipse.
-----Original
Message-----
From: Ron Bodkin
[mailto:rbodkin@xxxxxxxxxxx]
Sent: Thursday, July 31, 2003 9:27 AM
To: aspectj-users@xxxxxxxxxxx
Subject: RE: [aspectj-users]
Eclipse AJDT - stepping into advice code
Unfortunately, there are a number of
areas in which the Eclipse JDT is still hard wired to recognize .java files.
For this reason, I recommend using a .java extension for your AspectJ code, to
get better tools support from AJDT. Try segmenting your AspectJ-specific
code into a separate source tree. It's a known issue with AJDT and the
team is planning to fix it over time.
Mark, I'm also curious if you're doing
ant builds inside Eclipse instead of using the AspectJ builder, and if so why?
------------Original Message-------------
From: "Volkmann, Mark"
<Mark.Volkmann@xxxxxxxxxxxxx>
To: "'aspectj-users@xxxxxxxxxxx'"
<aspectj-users@xxxxxxxxxxx>
Date: Thu, Jul-31-2003 7:05 AM
Subject: RE: [aspectj-users] Eclipse AJDT
- stepping into advice code
Thanks for the
suggestion. As you suspected though, I already have the .aj extension
registered with the Aspect/Java Editor. Darn! This is the one
remaining piece of the puzzle and I can't seem to crack it. I really
don't want to be forced to name all my aspect files .java instead of .aj.
-----Original
Message-----
From: Garry Cronin
[mailto:garry.cronin@xxxxxxxxxx]
Sent: Wednesday, July 30, 2003 2:32 PM
To: aspectj-users@xxxxxxxxxxx
Subject: Re: [aspectj-users]
Eclipse AJDT - stepping into advice code
probably not you're problem but it may
help to ensure that .aj file extensions are registered with the AspectJ/Java
Editor editor in Eclipse. You can set this within the Preferences dialog
(Workbench - File Associations).
hope this helps
- Garry
Volkmann, Mark wrote:
Scratch
that last email. I forgot the X in -XnoInline. I have that working
and I have a debug step filter for org.aspectj.
When I
try to step into an advised method, a dialog pops up titled "Debugger
Source Lookup". It says "The source of the type
'com.agedwards.aspects.ContextAspect' could not be shown as the type was not
found." ContextAspect.aj is one of my aspects. I'm thinking it
doesn't know that .aj files contain Java source. Any idea how to tell it
about that?
***********************************************************************************
WARNING: All e-mail sent to and from this
address will be received or
otherwise recorded by the A.G. Edwards corporate
e-mail system and is
subject to archival, monitoring or review by,
and/or disclosure to,
someone other than the recipient.
************************************************************************************
|