You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Karl-Heinz Marbaise (JIRA)" <ji...@codehaus.org> on 2014/09/04 12:34:10 UTC
[jira] (MCOMPILER-231) Make compiler output paths relative to the
project or module root
[ https://jira.codehaus.org/browse/MCOMPILER-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=352300#comment-352300 ]
Karl-Heinz Marbaise commented on MCOMPILER-231:
-----------------------------------------------
Can you give an concrete example what you see in contradiction to what you like to see?
> Make compiler output paths relative to the project or module root
> -----------------------------------------------------------------
>
> Key: MCOMPILER-231
> URL: https://jira.codehaus.org/browse/MCOMPILER-231
> Project: Maven Compiler Plugin
> Issue Type: Improvement
> Reporter: David M. Lloyd
> Priority: Minor
>
> Using the latest 3.2-SNAPSHOT as of the time of this report, all compiler messages which start with a file name are printing the absolute file name. There should be a filter step which checks a message to see if it starts with the project or module path, and if so, makes the path relative, to reduce screen real-estate consumption.
> It seems to me that the compiler plugin had this capability at some point in the past (though maybe I've just dreamed it)? I suppose it's even possible that if it did regress, that it was one of my patches that did it (though I don't recall seeing this kind of code anywhere).
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)