I have a build that runs from Hudson on a farm of 4 linux boxes. Hudson pulls down from our source control and builds the modules. When Hudson builds the project, some test cases fail because certain plugins aren't being merged from a parent pom into the effective pom. To test the failure, I ssh'ed to my slave build server, logged in with the same user account Hudson uses, changed to the directory Hudson sync'ed from source control, and ran the same build commands Hudson executes to build the project... and it works, no errors.
To see what was different between the two environments I've run "mvn -v" and "mvn help:effective-settings" and both were identical, however, "mvn help:effective-pom" showed that the exact plugins needed weren't included in the effective pom for the CI build. Obviously, something is different, but I can't think of what I'm missing that would make the same maven version, with the same settings, building the same directory on the same server, running from the same user account, ultimately build different effective poms. I've cleaned out the local M2 repo to make sure they weren't getting anything from the local repo for one build and remote for another, but with the same result. Any ideas on what I could try or additional commands I can run to check this? Thanks! -Ryan
