> B can use types form A in its public interface. Do we really want to > force all C's to know which of B's dependencies appear in its public > interface? Or do all B's document which dependencies they "re-export", > i.e. which should be considered transitive, and which not? > > Actually, that last idea, might not be so bad...
o.k., you are right. I also don't want to know all tha dependencies and I really like your last idea! Actually the guys at Sun should just fix JDK 1.6 to be able to handle long classpaths again;-) -- View this message in context: http://n2.nabble.com/Slow-maven-compile-after-upgrading-JDK-from-1.5-to-1.6-tp2868702p2973143.html Sent from the maven users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
