Not having read the thread, just noticing that question, let me say this:
whichever class comes first in the classpath of any given classloader will be
found and loaded. Others will be ignored, and there will be no "re-loading" of
already defined classes.
Disclaimer: You can create a new classl
What about class name conflict: how decides JVM which class to take
(it will be one in the WebApplication and another in the woven
exported jar file)? Won't the virtual machine complain, that there are
two .class file with the same name?
Am 04.09.2012 19:42, schrieb Andy Clement:
Questions
> Questions
> In the exported aspect-jar, there are only the .class files of the AspectJ
> project, no .class files for the INPATH-Jar. Should there be other classes,
> from the imported INPATH-jar?
I can imagine 'export jar with AspectJ support' is not totally inpath
aware in the simple case. B
Hi Alexander,
Thank you for your answer&help. I tried also with "Runnable JAR" +
"Package required libraries into generated JAR".
Now all the JARs in the Build Path (+ aspectj-rt.jar + the JAR in the
INPATH) are included in the root of the exported JAR. As compiled
classes it has
these addi
Hi Valerian!
I guess we met earlier there (same topic):
http://stackoverflow.com/questions/12104735/aspectj-controlling-calls-in-other-jars
As I said, I would also have expected "JAR with AJ" export to include
necessary dependencies, this looks like a bug. So it is good to bring it
to the develop
Hello,
I have a Web application with a Plugin System, which actually runs in a
Tomcat. I want to control/change the behaviour of the Web Application. I
thought, having the JAR's of the Web Application, it would be no problem
to use the Post-compile weaving of the AspectJ.
I tried to weave so
