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

Vimal commented on MCOMPILER-316:
---------------------------------

i patch an open source jar for some reason.
from the source, i only modify and compile one file, and repackage that 
generated class file into the original jar.
so the maven project for this 'patching' has dependencies only for that one 
java file. and an antrun plugin to repackage the jar.

i modified the project, and added one more modified java file to be repackaged. 
i was getting strange compilation errors during compile phase.

in the end by using -X option, i was able to see the classpath, see what all 
was getting into compile command, and find the reason for compile errors.  
perhaps some different jar had to be added. it is not so obvious, as in the 
original jar compilation it modifies some package names in the source, so it 
was not a straightforward maven build. 

perhaps some details are missing in above description. but the whole point is 
that seeing the classpath and javac options from -X debug output gave me lot of 
confidence into getting this project built.

i am not so knowledgeable about maven, nor do i want to be. there could be 
various ways to build the java/ant or some other command, perhaps depending on 
the maven plugin used. i just want to be able to easily see the command in some 
cases, helps to retrace steps and reach the source.



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

Reply via email to