they did changed a lot in the package structure. with the new filevault Version 1.1.4 it's really hard to get the build success. I'm still searching for a package where to put the config for /etc/map. I know in CRX has nothing changed, but in the Code (IDE) with all the new packages structure and depedencies, it's a different story. Heres a Link that describes what should be in the different packages, but they missed to tell where to put "/etc/map"https://wcm-io.atlassian.net/wiki/spaces/WCMIO/p...

our solution was to create a content (ui.content) package for things like /conf or /content. Same as in the wknd Project. https://helpx.adobe.com/ch_de/experience-manager/kt/sites/using/getting-started-wknd-tutorial-develop/part1.html You can't mix up /conf folder under /apps. they have to be separated completely (new folder structure). Still don't know where to put the /etc/map folder now

no I tried both! It's not accepted under /etc/map with the new filevault version. See the second error

But this will overwrite the whole /conf folder. So if you have other projects with editable templates, they will not exists anymore, after installation. I've tested it on AEM 6.4.8.1. I'm still searching for a solution.

Yes this is the adobe stuff we know.First it starts to load some super great site, that generates hope in the minds of the people.But then after a few seconds, the page load will fail.This is what we know from adobe.Better you start to give some discount for companies that using this buggy thing.

Yes same here. And Yesterday was it the same.I really don't get it why they don't fix this huge problem.But I found a new Trick, that sometimes works. If the page is loading long after you click login. The browser (chrome) will ask you if you want to wait. And then you say yes. Maybe more than one time. Than after 10 min of waiting, you might be logged in. It worked yesterday when I logged in, with this trick.I think adobe would say, "this is not a bug, it's a feature". Like they sayed with the ...

And a miracle happened. It's working now! Until the next Server Problem, that nobody by Adobe will recognize, until somebody will post a question about "access package share not possible". So I'm looking forward to it.

This happens so many times. Just now, I'm not able to login.The solution is that adobe have to restart the Package Share Server. Because sometimes it get frozen (for some reasons).After a restart everything works fine until the next frozen situation (and there are many!)So everytime you ask in a forum, why the login is not working. The people restart it, and some adobe dudes test the connection, and voila everything works fine. And just you are the dork.I think it's kind of the tactic of adobe, ...

Don't use C:\Program Files, because you need Administrator rights to create folders. Change the path to your userprofile path or something like C:\apache\