installpaths not added when not creating package directory
Description
When installing a package that is an entire application and createPackageDirectory is set to false, CommandBox was not saving the dependencies as a shortcut since the box.json already had them. However, this caused the installpaths to not get saved which means the "list" command doesn't show nested dependencies since it doesn't know where to find them.
And example is this:
That repo gets installed in the current folder. If the folder is empty (and it should be since this is an entire app) then the box.json should get the install paths added so the "list" command shows the nested dependency correctly.
Gliffy Diagrams
Activity
Show:
Fixed
Pinned fields
Click on the next to a field label to start pinning.
When installing a package that is an entire application and createPackageDirectory is set to false, CommandBox was not saving the dependencies as a shortcut since the box.json already had them. However, this caused the installpaths to not get saved which means the "list" command doesn't show nested dependencies since it doesn't know where to find them.
And example is this:
That repo gets installed in the current folder. If the folder is empty (and it should be since this is an entire app) then the box.json should get the install paths added so the "list" command shows the nested dependency correctly.