Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [aspectj-users] Does ajc require access to source?

Oops, thanks for putting me right Wes

On Wednesday, July 30, 2003, at 04:13PM, Wes Isberg <wes@xxxxxxxxxxxxxx> wrote:

>See the -injars option to ajc for weaving .class files.
>Classes in the classpath are not affected by aspects.
>
>Wes
>
>Russell Miles wrote:
>> Hi Mark,
>> 
>> I've tried out something similar and found that things work ok but you must include the path to the .class files in the class path for them to be found. I'll give it another go and see if I can get the same problem but this has worked for me in the past.
>> 
>> Cheers
>> 
>> Russ
>> 
>> On Wednesday, July 30, 2003, at 03:03PM, Volkmann, Mark <Mark.Volkmann@xxxxxxxxxxxxx> wrote:
>> 
>> The book "Mastering AspectJ" says on page 48 "The AspectJ compiler is built to allow the use of aspects in a variety of circumstances regardless of whether or not the source code is available to the developer."  This doesn't seem to be the case for me.  Here's what I did.
>> 
>> 1) Build and run the code with all the source available.
>> 2) Rename a source file for a class from .java to .save.
>> 3) Modify an aspect that affects that class to do something different.
>> 4) Rebulid the code.
>> 
>> ajc complains when compiling an aspect that affects that class with "no match for this type name".  Is the book wrong? 
>> 
>> 
>> ------------------------------------------------------------------------
>> 
>> The book "Mastering AspectJ" says on page 48 "The AspectJ compiler is built to 
>> allow the use of aspects in a variety of circumstances regardless of whether or 
>> not the source code is available to the developer."  This doesn't seem to be the 
>> case for me.  Here's what I did.
>> 
>> 1) Build and run the code with all the source available.
>> 2) Rename a source file for a class from .java to .save.
>> 3) Modify an aspect that affects that class to do something different.
>> 4) Rebulid the code.
>> 
>> ajc complains when compiling an aspect that affects that class with "no match 
>> for this type name".  Is the book wrong?
>> 
>> 
>> 
>> ***********************************************************************************
>> 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.
>> ************************************************************************************
>
>_______________________________________________
>aspectj-users mailing list
>aspectj-users@xxxxxxxxxxx
>http://dev.eclipse.org/mailman/listinfo/aspectj-users
>
>


Back to the top