I noticed that setting the Maven top-level target for a job deletes the job's POM location setting.

I can reproduce this as follows:

1. There's a freestyle project with a Maven Build step. The Goals are "clean verify", the POM location is "myproject-parent/pom.xml".
2. Change the Maven goal with the Configuration Slicing Plugin to "clean package"

Result:
The POM location is empty.