We are facing the same issue actually ( https://jira.jboss.org/jira/browse/GTNPORTAL-27) and several months after the issues was reported to SUN it is not yet fixed in JDK :-( Please vote for it : http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6843751
Nobody found a workaround ? Arnaud On Mon, May 25, 2009 at 11:38 AM, j_ri <[email protected]> wrote: > > Hi, > > meanwhile I posted in the Sun Developer Network, since my tests lead to the > conclusion that the problem occures because of a bug in the javac compiler > of Java 6. > > see > > http://forums.sun.com/thread.jspa?threadID=5386732&tstart=0 > http://forums.sun.com/thread.jspa?threadID=5386732&tstart=0 > > and > > http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6843751 > http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6843751 > > > but what I wonder about is that nobody else who compiles quite large > prohjects using maven has the same problems as we do. > > > another question I have is the follwing: > why does maven put all transitive dependencies in the compile classpath? it > is best practise to have all jars I really depend on for my compilation as > direct dependency in my pom. why don't force this and just put the direct > dependencies in the compile classpath and pass the transitive ones "only" > to > the other tasks (packaging, etc.)? > > > -- > View this message in context: > http://n2.nabble.com/Slow-maven-compile-after-upgrading-JDK-from-1.5-to-1.6-tp2868702p2968777.html > Sent from the maven users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
