Constrain post-deployment file resolution to include only the source roots included in that deployment

Logging this based on a discussion with an end user who has a single-module project (which is all that's supported in non-IntelliJ IDEA IDEs anyway) with multiple source roots, one per configured package directory, who is trying to perform an incremental deployment on a single source root. The issue is that there are metadata files with the same name under multiple source roots, and when errors are reported, IC2 is finding all files with that name, even those not included in the original deployment.

The solution is to constrain resolution of file paths in reported errors to only those files that were included in the deployment.

UPDATE: There's a second required change here. Right now when IC2 invokes the CLI (assuming there are no substitution rules, etc.), it does so in-place using a package.xml file. Because there are multiple files with the same name, the CLI doesn't seem to know which to include in the deployment, though. IC2 would need to invoke the CLI differently or treat this situation the same way that it treats projects with substitution rules by copying the specific files into a temporary location and deploying them from there.

Comments (5)