Ideally we want a way for aop and jbosretro to use the same implementations. The same thing applies to the ScopedClassPool vs AOPClassPool/JBossClassPool and the annotations.
For now, I'd suggest just renaming the JBossRetro class until somebody has time to look at it. On Wed, 2006-03-29 at 14:54 -0600, Scott M Stark wrote: > There is a conflict between two org.jboss.lang.Enum objects, one from > aop and another from jbossretro. There should only be one. The > jbosstretro version is more complete, but is not designed to be usable > in js2e1.4 without being translated. > > How are we going to resolve this? > > xxxxxxxxxxxxxxxxxxxxxxxxxxxx > Scott Stark > VP Architecture & Technology > JBoss Inc. > xxxxxxxxxxxxxxxxxxxxxxxxxxxx > > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting language > that extends applications into web and mobile media. Attend the live webcast > and join the prime developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 > _______________________________________________ > JBoss-Development mailing list > JBoss-Development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jboss-development -- xxxxxxxxxxxxxxxxxxxxxxxx Adrian Brock Chief Scientist JBoss Inc. xxxxxxxxxxxxxxxxxxxxxxxx ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
