On Tue, Feb 12, 2013 at 2:58 PM, Ulli Hafner <ullrich.haf...@gmail.com>wrote:
> > Am 12.02.2013 um 14:45 schrieb Jan Goyvaerts <java.arti...@gmail.com>: > > > > On Tue, Feb 12, 2013 at 1:39 PM, Ulli Hafner <ullrich.haf...@gmail.com>wrote: > >> >> Am 12.02.2013 um 13:23 schrieb Jan Goyvaerts <java.arti...@gmail.com>: >> >> On Tue, Feb 12, 2013 at 1:19 PM, Ulli Hafner <ullrich.haf...@gmail.com>wrote: >> >>> Is there no entry in the "Add post build action" drop down list that is >>> called "scan for compiler warnings"? >>> >> >> Discovered it finally - but it doesn't look like what's in the >> documentation. So I'm not sure what plugin this is from. >> >> Is this yours ? >> >> >> I think so :-) What is different? Maybe the wiki documentation needs to >> be updated with a new screen shot ;-) >> > > Well, I would certainly advise adding instructions to configure for basic > usage. A screenshot of the post-build action you need to set in order to > get the warnings published. Together with the maven compiler plugin > configuration to have it spit out warnings. > > It reads somewhere you don't need to do anything. The plugin would read > the console output. But when installing the plugin, nothing happens at all. > So it would definitely be good to know the user has to add one or more > parsers. > > > I see, that is on my issue list for the maven plug-in: ideally there > should be no configuration be required… > > > What's a bit confusing too is the screenshot of the plugin page: > > <warnings.png> > > Which is presume now looks like this: > > <warning2.png> > > Because the picture and text was different I presumed it wasn't from the > Warnings plugin. :-) > > > So I think it's just a matter of documentation. The software works all > right ! :-) > > > > > Ok, thanks! I did't update the documentation after changing the > visualization… (It only looks different for Java warnings up to now:-) > > Interested in adding any missing documentation parts in the wiki? > Sure ! How ? What pages ? (be aware I just know about this plugin - you seem to have much more code running out there) > > Ulli > > > > > >> >> >> I've added javac and maven parser. Any others I should add ? >> >> >> No, that should be fine. That is what I'm using (I'm using the eclipse >> JDT compiler but the warnings are still reported in the javac format) >> >> Ulli >> >> >> >>> >>> Are you using a maven or freestyle job type? Which Jenkins and warnings >>> version? >>> >> >> Maven project, Jenkins 1.500 and Plugin 4.21. >> >> >>> >>> Ulli >>> >>> Am 12.02.2013 um 12:47 schrieb Jan Goyvaerts <java.arti...@gmail.com>: >>> >>> I'm trying to to use the Warnings Plugin ( >>> https://wiki.jenkins-ci.org/display/JENKINS/Warnings+Plugin) to publish >>> the compilation warnings - obviously. :-) >>> >>> The problem is that no warnings show at all. Neither is there an option >>> in the job configuration to publish those warnings. As it is the case for >>> Findbugs, PMD & al from the same author. Which all work like a charm. >>> >>> So it's probably a dump question, but how do I enable/publish/... the >>> warnings using the Warnings plugin ? :-) >>> >>> ---------------- >>> >>> The Maven Compiler plugin has been set to generate the warnings: >>> >>> <plugin> >>> <artifactId>maven-compiler-plugin</artifactId> >>> <configuration> >>> <target>${java.version}</target> >>> <source>${java.version}</source> >>> <compilerArgument>-Xlint:all</compilerArgument> >>> <showWarnings>true</showWarnings> >>> <showDeprecation>true</showDeprecation> >>> </configuration> >>> </plugin> >>> >>> The console output contains a lot of deprecation errors. >>> >>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Jenkins Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to jenkinsci-users+unsubscr...@googlegroups.com. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> >>> >>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Jenkins Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to jenkinsci-users+unsubscr...@googlegroups.com. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> >>> >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to jenkinsci-users+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to jenkinsci-users+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > > > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
