|
|
Re: Exporting "Deployable plugin with AspectJ support" yields plugin with aspects missing [message #68826 is a reply to message #68724] |
Thu, 07 December 2006 11:39 |
Eclipse User |
|
|
|
Originally posted by: spyoung.uk.ibm.com
The JARs in to which you are weaving are only the source and are not
modified; the new classes (i.e. the woven versions) are output either to
your Eclipse project's bin directory (look on the filesystem, rather
than in Eclipse) or to your project's outjar, if you have one specified.
It is from one of these locations that the runtime workbench picks up
the woven code.
I've added some comments/advice/suggestions to your bug 166765 which
relates to this issue.
Cheers,
Steve
Michael Moser wrote:
> I just did an "experiment" and the result left me stunned:
>
> I rebuilt things and ran the plugin in the runtime workbench. As I
> wrote, here everything works fine. While that workbench was executing I
> copied the 3 .jar files that are supposed to contain the weaved-in
> aspect code out into a temp. directory. So, at this moment the aspects
> should have been correctly woven into the .jar files - at least that's
> what I had thougth. From that temp. directory I copied them into the
> .zip file that the previous export had generated (thereby overwriting
> the .jars that were originally packed into the .zip).
>
> That modified .zip I then transferred to the target system's eclipse
> directory, unpacked it and started eclipse and with it my plugin. To my
> surprise I get the same errors re. missing methods. So, the aspects
> aren't really woven into the .jar's at all and now I'm really puzzled!
> When and how are these aspects woven into the code before the runtime
> workbench executes? And where does the aspect code come from, because
> obviously it is in the executing code, but has NOT been in the .jar
> files from which it was loaded!?!
>
> And how would I weave AspectJ code into .jar files, i.e. actually modify
> those jars?
>
> Michael
>
>
>
>
>
|
|
|
|
|
Re: Exporting "Deployable plugin with AspectJ support" yields plugin with aspects missing [message #595523 is a reply to message #68724] |
Thu, 07 December 2006 11:39 |
Steve Young Messages: 2 Registered: July 2009 |
Junior Member |
|
|
The JARs in to which you are weaving are only the source and are not
modified; the new classes (i.e. the woven versions) are output either to
your Eclipse project's bin directory (look on the filesystem, rather
than in Eclipse) or to your project's outjar, if you have one specified.
It is from one of these locations that the runtime workbench picks up
the woven code.
I've added some comments/advice/suggestions to your bug 166765 which
relates to this issue.
Cheers,
Steve
Michael Moser wrote:
> I just did an "experiment" and the result left me stunned:
>
> I rebuilt things and ran the plugin in the runtime workbench. As I
> wrote, here everything works fine. While that workbench was executing I
> copied the 3 .jar files that are supposed to contain the weaved-in
> aspect code out into a temp. directory. So, at this moment the aspects
> should have been correctly woven into the .jar files - at least that's
> what I had thougth. From that temp. directory I copied them into the
> .zip file that the previous export had generated (thereby overwriting
> the .jars that were originally packed into the .zip).
>
> That modified .zip I then transferred to the target system's eclipse
> directory, unpacked it and started eclipse and with it my plugin. To my
> surprise I get the same errors re. missing methods. So, the aspects
> aren't really woven into the .jar's at all and now I'm really puzzled!
> When and how are these aspects woven into the code before the runtime
> workbench executes? And where does the aspect code come from, because
> obviously it is in the executing code, but has NOT been in the .jar
> files from which it was loaded!?!
>
> And how would I weave AspectJ code into .jar files, i.e. actually modify
> those jars?
>
> Michael
>
>
>
>
>
|
|
|
|
Powered by
FUDForum. Page generated in 0.03758 seconds