allowOutsideOutDir for assets not working again

[trendzetter]

Versions

Tested on:
1.6.3
1.6.5
Windows 10

Repro steps

• npm install -G @angular/cli

• cd to project with assets that need to be copied outside the project folder. From the .angular-cli.json:
  "assets": [{
  "input": "./assets/",
  "glob": "**/*",
  "output": "../EcView/WebContent/assets",
  "allowOutsideOutDir": true
  }],

• ng build

Observed behavior

Build failed:

>ng build
An asset cannot be written to a location outside the project.

Desired behavior

The build process copies the assets to the specified folder and completes the compilation of source code.

Other details

Seems similar to, possible regression of #8613

[clydin]

@trendzetter Are you still experiencing this issue with 1.6.7?

[trendzetter]

~~Issue no longer present in 1.6.8.~~~

I did not test correctly. The "allowOutsideOutDir" configuration was not present in the .angular-cli.json.
The issue is not resolved.

[yuvalbl]

Angular version: 6.0.0-rc.5
Angular-CLI version: 6.0.0-rc.5

I've created a new project and was able to build to a directory outside the project root, with no allowOutsideOutDir flag

side-note:
If I get it correctly, .angular-cli.json configuration is now included in angular.json.

Repro steps:

1. create new project.
2. in angular.json change outputPath to: '../MyDir'
3. run ng build
4. see build output outside the project root directory

Related to #9686
seems like this commit is the problem

[filipesilva]

This option has been removed in Angular CLI 6. I now added a Breaking Changes section to https://github.com/angular/angular-cli/releases/tag/v6.0.0, with this change listed, will also add a warning during the update process. This is being tracked in #10647.