Strange, I am pretty sure there was a way to turn this off last time I checked (months ago), but it does not appear to be there now unless I am missing something very obvious.
In any case, I have added a fix to cvs, to allow you to specify an optimize property on the aopc task. Set it to false to turn off optimizations, i.e.: | <aopc compilerclasspathref="classpath" classpathref="classpath" verbose="true" optimize="false"> | <classpath path="."/> | <src path="."/> | <aoppath path="jboss-aop.xml"/> | </aopc> | The optimize attribute defaults to true if not specified. If you are not familiar with building from cvs, the following thread contains details (it spans over a few pages): http://www.jboss.org/index.html?module=bb&op=viewtopic&t=52857 HTH View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3855316#3855316 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3855316 ------------------------------------------------------- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
