Retrieved metadata includes empty "unpackaged" directory and other metadata as peers

[Scott Wells]

Conveying this into the public issue tracker to help the user reporting this issue track it down in a more focused manner.

[Scott Wells]

This is a test build that will only use the unpackaged directory if it exists AND isn't empty. Otherwise it will continue to use the parent of that directory. I don't know why there would be an empty unpackaged directory when metadata was successfully retrieved--this is the first time I've seen/heard of that in the ~6 years since IC's retrieval capabilities were first implemented--but let's see if this helps resolve the issue.

[Scott Wells]

New build with a slightly different way of determining whether to re-root into the unpackaged directory.

[Scott Wells]

One more test build, this one with what I expect will be the final fix. IC2 now looks to see if there's a configured package directory specifically named unpackaged and, if so, it doesn't reparent onto that directory if present. I've verified the correct behavior against source format projects with such a configuration, those without, and metadata format projects where retrieved directory structures do include the unpackaged top-level directory.

[Scott Wells]

Delivered in 2.1.7.4.