[jira] [Comment Edited] (MCOMPILER-316) maven should *always* print classpath used to compile the java files

["Vimal (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MCOMPILER-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16260254#comment-16260254 ] 

Vimal edited comment on MCOMPILER-316 at 11/21/17 5:01 AM:
-----------------------------------------------------------

Thanks for your reply.

I understand that Maven != Makefile. Maven does a lot more.

But finally it is a tool whose purpose is to generate command (and options) to satisfy the goals specified. 
The goal could be compile a java file to a .class file, create a archive using .class files, run tests etc.
in most use cases, where rubber hits the road, it runs an external command (javac etc) with options.

if the output of the command is surprising/unsatisfactory i want to see what exact command was run. 
Most cases it is not needed, as compiler's output is shown to user. 

But what if there is something wrong in the options generated? what if the classpath contains some jar which is not supposed to be there, or a different jar shold be there. In such cases (uncommon) , getting to see the exact command being run helps a lot.

The -X option is not that helpful, as it dumps a LOT (a LOT) of information.

I am sure it will help many more people, not just me.

Thanks,
Vimal








was (Author: vimalk78):
Thanks for your reply.

I understand that Maven != Makefile. Maven does a lot more.

But finally it is a tool whose purpose is to generate command (and options) to satisfy the goals specified. 
The goal could be compile a java file to a .class file, create a archive using .class files, run tests etc.
in most use cases, where rubber hist the road, it runs an external command (javac etc) with options.

if the output of the command is surprising/unsatisfactory i want to see what exact command was run. 
Most cases it is not needed, as compiler's output is shown to user. 

But what if there is something wrong in the options generated? what if the classpath contains some jar which is not supposed to be there, or a different jar shold be there. In such cases (uncommon) , getting to see the exact command being run helps a lot.

The -X option is not that helpful, as it dumps a LOT (a LOT) of information.

I am sure it will help many more people, not just me.

Thanks,
Vimal







> 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)