Consider only including direct project dependencies in the "extra JARs" during compilation

[jesse-gallagher]

This certainly shows up in the generated build.properties file and may also show up in the proper compilation process. It's not wrong to include e.g. dependencies from parent pom projects, but it's possibly unexpected. That said, someone tailoring their configuration could also logically expect those dependencies to show up, so it's something of a coin toss.