AFAIK RetentionPolicy = Runtime just means that the annotation details are stored in the class file, rather than being useful only at compile-time.
The annotation jar is definitely not needed at run-time, so I don't see how it would matter what jars are present. If the JVM is not looking for the class, it won't look for the class just because there are two or more copies available... On 06/06/2008, Sam Berlin <[EMAIL PROTECTED]> wrote: > That I don't know. :) > > Only recently learned this annotation stuff while following the hubbub > over Guice being released awhile back. > > > Sam > > > On 6/6/08, Ortwin Glück <[EMAIL PROTECTED]> wrote: > > > > > > Sam Berlin wrote: > > > If the library contains only annotations, there should be no problem. > > > Annotations are only strictly required at compile-time. At runtime, > > > the annotations don't have to be on the classpath (even if they have a > > > RetentionPolicy of Runtime). > > > > > > > Allright, I didn't know that. What if the lib IS on the classpath? Can it > > create conflicts when a class with annotations is loaded? > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
