[ https://issues.apache.org/jira/browse/MCOMPILER-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16259855#comment-16259855 ]
Robert Scholte commented on MCOMPILER-316: ------------------------------------------ Hmm, I really wonder why did would help. In fact, the downloading information is only done when required. In you run {{mvn verify}} (please no --mvn clean install--) for a second time Maven won't download anything. Maven users are often not interested in the classpath/modulepath anymore, Maven dependency resolution is there for a long time and has become very stable. What is the *real* reason to see the classpath? Maven != Makefile, I hope there's a better reason. To me this is a bit too custom request, so here are some options: - add the {{org.apache.maven.plugin.compiler}} to ${maven.home}/conf/logging/simplelogger.properties - write your own EventSpy extension. It is not very well documented, but http://maven.apache.org/maven-jsr330.html is a start. > maven should *always* print classpath used to compile the java files > -------------------------------------------------------------------- > > Key: MCOMPILER-316 > URL: https://issues.apache.org/jira/browse/MCOMPILER-316 > Project: Maven Compiler Plugin > Issue Type: Improvement > Environment: ALL > Reporter: Vimal > > mostly i use "{{maven clean install}}" to build my packages > by default maven doesnt print the classpath used to compile java files. It > should. > it prints information like which jars it is downloading. thats fine. > but it should *always* print the classpath used. > there is a "-X" option which prints classpath , but it prints TONS and TONS > of information which i think no one is interested in (except perhaps the > maven developers) > so there is no easy way to get the classpath used. > Please make maven to print classpath for each java file compiled, by default. > OR give a easy option to enable it along with other options. -- This message was sent by Atlassian JIRA (v6.4.14#64029)