Errors when building aren't linked or aggregated

[zellyn]

The closest issue I could find is #34, which is old, closed, and implies that the problem should be fixed. However, when I compile directly or as part of running a test, the pants errors are simply printed in the window named "Pants Console:". They are not clickable. There is also no list of errors in any UI element.

[wisechengyi]

Hi @zellyn,

Thanks for the report.

They are not clickable.

Currently the plugin only parses line with [error]

intellij-pants-plugin/src/com/twitter/intellij/pants/execution/PantsMakeBeforeRun.java

Line 75 in 67c6d81

public static final String ERROR_TAG = "[error]";

However, if it does not work for you. Please kindly attach some examples or screenshots.

There is also no list of errors in any UI element.

That is by design, because formatting in UI is hard to do and does not provide consistent experience with the command line.

[zellyn]

                         symbol:   class DbDispute
                         location: class VersionsTest
                       disputes-api/src/test/java/com/squareup/disputesapi/convert/VersionsTest.java:83: error: cannot find symbol
                           DbDispute newer = DbDisputes.convert(TestDisputes.CBMS_DISPUTE_W3);
                           ^

[zellyn]

[wisechengyi]

What version of pants is this?

The code is working correctly, but it seems that it's no longer [error] anymore, but error:

[zellyn]

Ugh. It's probably because we're on an old (very lightly forked) version: pants -v reports 1.2.1-rc2018051601. This is good ammunition to spur upgrades and unforking :-)

[zellyn]

Hmmm. More info. The error message format seems to vary depending on whether you use zinc or javac. We use javac (support for which just got merged two weeks ago).

[wisechengyi]

Interesting, so we can probably add error:. If the format difference is minimal, then the change should be trivial.

[JasonRosenberg]

any update on this?