You can limit how much you need from aspectjrt.jar by avoiding use of things like thisJoinPoint or the cflow pointcut designator. But even the most simple aspect will contain a reference to some types in that runtime jar - for example the org.aspectj.lang.NoAspectBoundException which gets thrown if something goes wrong building the aspect instance and someone attempts to use the aspect.
Andy. On 06/11/2007, Xavier Hanin <[EMAIL PROTECTED]> wrote: > Hi, > > I have a use case where I need to use aspect at compile time, but can't > introduce any runtime dependency (to give a bit more detail on the context, > this is > for Apache Ivy core, for which we don't allow any dependency). > > Browsing the mailing list on nabble I've found this: > http://www.nabble.com/How-to-remove-aspectjrt.jar-runtime-dependecy-while-using-AspectJ-tf1211220.html#a3201026 > > Is it still possible to use aspectj at compile time only without requiring > aspectjrt.jar at runtime, and which feature can I use/avoid in that case? > > If this is not possible I would have to do bytecode enhancement by hand > (probably with asm), but this is much less maintainable... > > Thanks for your help, > > Xavier > > -- > Xavier Hanin - Independent Java Consultant > http://xhab.blogspot.com/ > http://ant.apache.org/ivy/ > http://www.xoocode.org/ > _______________________________________________ > aspectj-users mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/aspectj-users > > _______________________________________________ aspectj-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/aspectj-users
