Home/ Questions/Q 6997121
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-27T20:14:37+00:00

I have a big Java project with thousands of compilation warnings. I would like

  • 0

I have a big Java project with thousands of compilation warnings. I would like to find a way to prevent developers commiting files with warnings, so gradually all warnings would disappear. If I commit a file with compilation error Eclipse displays an error message, but I couldnt find any way to do the same with warnings. The closest thing I found was The Commit warning checker http://commitwarncheck.sourceforge.net/ but that is not really integrated into the commit process, it just provides a view. Is there any better solution?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I see 2 options. First, at least with Subclipse, there’s an Eclipse preference for this: Window / Preferences / Team / SVN / “Commit resources with warnings”. There’s one for “errors” as well. Both can be set to “Yes”, “No”, or “Prompt”. However, this will require you to make sure that your entire team keeps these options set as you’d expect – as well as making sure that they have all of the other Eclipse preferences set to generate the same errors / warnings.

    Using Subclipse 1.6.18:

    enter image description here

    Another option is to make use of SVN commit hooks, essentially the beginnings of a Continuous Integration (CI) process. You could actually check for a limited set of things, and allow/deny the commit at that time, but I’d start worrying about commit performance. A better option might be a true CI process that runs a build (either scheduled, or potentially even per-commit) – and emails or otherwise alerts the developer if an issue is detected.

    The complication with this later option is repeating the Eclipse build – including detection of all Eclipse-configured errors and warnings – in a scripted manner. (If anyone finds a great way of doing this, please let me know! Eclipse provides a scriptable option for using its code formatter, but I’ve not seen a similar option for checking for errors / warnings using the checks provided by Eclipse.)

    Otherwise, you’ll probably be better off starting to migrate over to tools such as Checkstyle and FindBugs that work equally well both inside and outside of Eclipse. (However, relating back to my own interest above, I’ve not found any combination of a few tools – including these – that can at least match the same checks that Eclipse provides.) Combine this with Maven / m2e, providing a common build configuration / process that can be shared by both Eclipse and your CI system, and you should be in good shape.

    • 0