vmassol ad84efa0f6 - I had not understood the purpose of AspectC which is not to generated final weaved code but only to weave the custom javadoc tags onto the aspects themselves. We still need to call AspectWerkzC afterwards for offline weaving onto the main source code. ...

- Next step is to add support for 2 source paths: one being the main runtime sources and another being where non-production aspects are located (optional).


git-svn-id: https://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk@114524 13f79535-47bb-0310-9956-ffa450edef68

2003-12-30 20:32:58 +00:00

..

src/plugin-test

Added explicit perJVM aspect type

2003-12-30 20:30:33 +00:00

xdocs

- Ok, I think I now better understand how AW works. The plugin should be in a workable state for attribdef style. It has not been fully tested for xmldef style yet.

2003-12-27 13:11:25 +00:00

.cvsignore

Start of an aspectwerkz plugin. Not working yet.

2003-12-24 15:57:58 +00:00

plugin.jelly

- I had not understood the purpose of AspectC which is not to generated final weaved code but only to weave the custom javadoc tags onto the aspects themselves. We still need to call AspectWerkzC afterwards for offline weaving onto the main source code.

2003-12-30 20:32:58 +00:00

plugin.properties

- Ok, I think I now better understand how AW works. The plugin should be in a workable state for attribdef style. It has not been fully tested for xmldef style yet.

2003-12-27 13:11:25 +00:00

project.properties

Start of an aspectwerkz plugin. Not working yet.

2003-12-24 15:57:58 +00:00

project.xml

- I had not understood the purpose of AspectC which is not to generated final weaved code but only to weave the custom javadoc tags onto the aspects themselves. We still need to call AspectWerkzC afterwards for offline weaving onto the main source code.

2003-12-30 20:32:58 +00:00