Inspections with Maven2 problems

Hi all,
   Two questions:
       1) Are there any particular fields in the POM that need to be populated for the inspections and duplicate finder to work?
       2) When starting the inspections (which by the way, with TC4.5 actually does start, it didn't before for me) I get the following logging error:
               log4j:WARN No appenders could be found for logger (org.apache.commons.beanutils.PropertyUtils).

               log4j:WARN Please initialize the log4j system properly.    

           I know it's just related to log4j, but I was hoping it would help me solve the problems I was having (which, in a nutshell, is that while the build/compile process works ok, inspections does not seem to see the checked out code and perform the analysis correctly)

Comment actions Permalink

OK, a little followup here:

   1) It looks like the inspections code is looking for the source code in a directory that is parallel with my pom.xml file.  This doesn't sound right as I have the code being checked out via the agent so it is at /TeamCity/buildAgent/work/<buildID>/src/....    .  Is there something like that we can specify somewhere to tell IDEA where to look for the source?

   2) Also, it looks like it is only getting 66% through the code (at least that is what the console says), and it seems to only inspect HTML, CSS and XML files (this is a java project).  Is there something else that has to be specified to have it check Java source (I would hope not).  I thought the whole idea behind being able to use Maven POM files was so we didn't have to make an IPR file from IDEA.  The documentation for using Maven in this aspect just seems to be very lacking.

  Any help would be greatly appreciated!


Comment actions Permalink

Hello Josh,

  I'm sorry for delay with the answer.

  I'm not sure which IDE do you use in development, but if you're using IntelliJ IDEA, could you please check that your project can be opened with it and that you can run inspections from within IDEA. I'm asking this because TeamCity uses IntelliJ IDEA under the hood to run inspections, and if it cannot find Java source files, this may be a problem in IDEA's processing of the pom files.

  Please also make sure you're running the latest version of TeamCity (4.5.1) and that build runner for inspections is configured correctly.
  If the problem persists, please file an issue and provide more details, like:

  - pom.xml file
  - project layout (sources, tests, pom.xml location etc.)
  - checkout rules settings
  - build log
  - buildAgent/logs/teamcity-agent.log, buildAgent/logs/teamcity-build.log

  Kind regards,


Please sign in to leave a comment.