Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compile errors don't indicate where the error is in INFO level #78

Open
deaddowney opened this issue Feb 21, 2014 · 5 comments
Open

Compile errors don't indicate where the error is in INFO level #78

deaddowney opened this issue Feb 21, 2014 · 5 comments

Comments

@deaddowney
Copy link

When the clojure compile step fails, all I see is:

ERROR] Failed to execute goal com.theoryinpractise:clojure-maven-plugin:1.3.19:compile (compile) on project MyProj: Clojure failed. -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.theoryinpractise:clojure-maven-plugin:1.3.19:compile (compile) on project MyProj: Clojure failed.
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:318)
......

If I switch to DEBUG level in Maven, I DO see the error. Can we bump up this error to a higher log level? DEBUG puts far too much crap in the logs and we should see the compilation error.

@talios
Copy link
Owner

talios commented Mar 4, 2014

Definitely! Will bump this up and do another release. Or maybe parse out the error and throw it upstream as a MojoException to be handled more visibly.

@talios
Copy link
Owner

talios commented Mar 4, 2014

Actually, surprised no ones actually mentioned that before now...

@strongh
Copy link

strongh commented Sep 19, 2014

+1

1 similar comment
@Parth-Brahmbhatt
Copy link

+1

@talios
Copy link
Owner

talios commented Dec 18, 2014

Almost a year and no fix :( I feel like you all must hate me! The christmas holidays are here so I'll try and find some time to look at this. Does anyone have more of the stacktrace? I assume there's a wrapped exception coming out of Clojure or the plugin somewhere? The posted one doesn't actually include any code from the plugin...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants