hmm.. no I'm not sure, so someone more knowledable should answer this. I would like to know what options to set if I don't want my classes to be woven, but only to have my aspects compiled and put in the jar file so I can enable them with LTW.
regards, Wim 2006/4/12, Lukas Theussl <[EMAIL PROTECTED]>: > > Thanks for the feedback, Wim! > > Are you sure about the XnoWeave option? According to [1] this option has > actually been deprecated in aspectj 5, and I can't find any mention of > it in the official aspectj docs [2]. Maybe someone can confirm that? I > wanted to call for a release vote today... > > -Lukas > > [1] > > http://sardes.inrialpes.fr/~bouchena/teaching/AOP/Soft/AopDoc/devguide/antTasks-iajc.html > [2] > http://www.eclipse.org/aspectj/doc/released/devguide/antTasks-iajc.html > > > Wim Deblauwe wrote: > > I also tested and works ok. However, I would update the site > documentation > > for the maven.aspectj.noeave option. > > > > It currently states: " If true, produce binaries that can only be used > as > > input for the -injars or -inpath option. Defaults to false." > > > > If I'm not mistaken, this option should also be used to create a jar to > use > > with Load Time Weaving, true? Maybe you can add that. > > > > regards, > > > > Wim > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
