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

Option to run in quiet mode #48

Closed
GoogleCodeExporter opened this issue Mar 18, 2015 · 8 comments
Closed

Option to run in quiet mode #48

GoogleCodeExporter opened this issue Mar 18, 2015 · 8 comments

Comments

@GoogleCodeExporter
Copy link

Firstly, well done, the plugin works amazingly well with 
https://github.com/mkarneim/pojobuilder


One advantage would be if there was a quiet mode option.
i.e. a way to prevent the output of the javac options. As right now it prints 
out a massive classpath javac option parameter

Original issue reported on code.google.com by graham....@gmail.com on 6 Feb 2013 at 10:03

@GoogleCodeExporter
Copy link
Author

This should be an improvement not defect.

Original comment by graham....@gmail.com on 6 Feb 2013 at 10:13

@GoogleCodeExporter
Copy link
Author

Hi, thx for feedback


I'll work on .... very soon

Original comment by bartolom...@gmail.com on 6 Feb 2013 at 10:23

  • Added labels: Type-Enhancement, Milestone-Release2.1.2
  • Removed labels: Type-Defect

@GoogleCodeExporter
Copy link
Author

have u tried to set parameter outputDiagnostics at false?

<configuration>
<outputDiagnostics>false</outputDiagnostics>
</configuration>

Original comment by bartolom...@gmail.com on 3 Apr 2013 at 2:04

@GoogleCodeExporter
Copy link
Author

Original comment by bartolom...@gmail.com on 4 Apr 2013 at 10:39

  • Added labels: Milestone-Release2.2.1
  • Removed labels: Milestone-Release2.1.2

@GoogleCodeExporter
Copy link
Author

Original comment by bartolom...@gmail.com on 6 Apr 2013 at 12:44

  • Added labels: Milestone-Release2.2.2
  • Removed labels: Milestone-Release2.2.1

@GoogleCodeExporter
Copy link
Author

Maven has a built-in mechanism for the things you are doing. Just use 
getLog().debug() and it will normally suppress the logging, and you can show it 
by running "mvn -X". This is how every other Maven plugin in the world works: 
don't log things using info() unless they are really important to see every 
time, and use debug() to log things that are useful for debugging.

Here's a patch that makes the debugging output use getLog().debug().

Original comment by m...@samskivert.com on 14 May 2013 at 12:07

Attachments:

@GoogleCodeExporter
Copy link
Author

Hi, thx for patch

simple and effective

i'll apply it soon

Original comment by bartolom...@gmail.com on 14 May 2013 at 1:24

  • Changed state: Accepted

@GoogleCodeExporter
Copy link
Author

version 2.2.2 released!

Original comment by bartolom...@gmail.com on 20 May 2013 at 8:30

  • Changed state: Fixed

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

1 participant