jira-importer

**[Andy Lehane](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=alehane)** commented  I've tested this locally, which works. All of the unit tests pass. I've attempted to write unit tests for the new functionality but keep getting errors when...

**[Andy Lehane](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=alehane)** commented When I get the unit tests created and working, I'll look to submit a pull request from my github fork.

**[Andy Lehane](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=alehane)** commented I've figured out how to create the unit tests now, so will create the pull request tomorrow.

**[Andy Lehane](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=alehane)** commented Pull request 12 created (please ignore request 11 as this contained errors).

**[Joshua Caplan](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=j_caplan)** commented does any other workaround exist? this issue has been open for nearly 3 years, with the fix already provided.

Resolve #1199

**[Michael Osipov](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=michael-o)** commented Shit, bad test design...

**[James](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=hooker)** commented Looks like this may be related to this: https://issues.apache.org/jira/browse/MCOMPILER-66  If I change the message to an ERROR or a WARNING rather than a NOTE it works.

**[James](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=hooker)** commented The change in behaviour is still strangely different between when toolchains is and isn't being used.

**[Michael Osipov](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=michael-o)** commented Regardless of the warning, does a toolchain always require a javac? What if the project does not compile anything? E.g., type `pom`.