Closed csmoore closed 5 years ago
Just in case we see this issue again, @saip noticed you see different behavior if this setting is set/unset:
With this set, it is difficult to determine if the lpkx is not set to schema-only since it behaves very much like a schema-only lpkx by unpacking to the project.
Original LPKX in branch was not set to schema-only so was being shared by all projects on the machine creating some unexpected results