When creating a new package version for one path, why are profiles from another path included?
- My sfdx-project.json has two package directories, "force-app" and "mga"
- force-app is unpackaged
- mga is
- when I try creating a package version for mga, I get an errors for each profile in force-app/main/default/profiles complaining the profile, "..was named in package.xml, but was not found in zipped directory"
I don't want profiles from force-app to be included in mga's package. I don't want anything from force-app included. And why does it only complain about the profiles? There are over 10000 files over there I want to ignore.
Has anyone else seen this craziness?
2 个回答
Yes, this was an issue for years. You can now use the scopeProfiles attribute in your sfdx-project.json to ensure that only profiles in the defined path are included:
