Never mind, I just added all libs to the aop classpath and now I dont need to
exclude anything. I guess thats ok, since its precompiled and not loadtime
weaving.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4184468#4184468
Reply to the post :
http://www.jb
"[EMAIL PROTECTED]" wrote : Can't remember about aop 1.5.x, but in aop 2.0.0.GA
we support system properties in aop.xml. Here's an example from our testsuite:
[...]
|
Maybe I missunderstood your example, but in order to get my VM arguments:
| -Djboss.aop.exclude=org
| -Djboss.aop.includ
Can't remember about aop 1.5.x, but in aop 2.0.0.GA we support system
properties in aop.xml. Here's an example from out testsuite:
|
|
|
|
|
|
|
|
|
|
|
|
|
Interesting question. I have the same problem with libs in my project.
Aopc tries to weave them, which results in errors such as:
| [aopc] Exception in thread "main" javassist.NotFoundException:
org.somepackage.foo.Barclass
|
With loadtime weaving everything works fine with the vm argument
