[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [aspectj-users] must be obvious
|
I guess what is happening is that you are exporting your classes to another
project but you are not exporting the aspects with them. I assume you are
creating a new AspectJ project since you did not report any error in your
new Eclipse project. So I guess just copying aspects will do the job.
A possible reason for this to happen is the following difference:
Scenario 1 ) Original project: Struts classes use classes altered by
aspects.
Scenario 2 ) New project structure: Struts classes use non-altered classes.
From: "Conrad CRAMPTON PSE 52704" <conrad.crampton@xxxxxxxxxxxxxxxxxx>
Reply-To: aspectj-users@xxxxxxxxxxx
To: <aspectj-users@xxxxxxxxxxx>
Subject: [aspectj-users] must be obvious
Date: Fri, 27 Oct 2006 12:48:14 +0100
Hi,
I have a struts application which has some common artifacts with other
projects which have some aspects configures to advise on some of these
methods - all is fine when I have these common objects in the project
(Eclipse) as source files. However, I have just extracted these out of
my project into a new project in order to build a jar file of them
(using Maven). The application still works in itself but the aspects
that advise the extracted object methods no longer work.
I can't understand why this is so - can anyone explain this?
Thanks
Conrad
_______________________________________________
aspectj-users mailing list
aspectj-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/aspectj-users
_________________________________________________________________
MSNサーチ は Live Search に進化します http://get.live.com/search/overview
