search

wcm-io-frontend / aem-clientlib-generator

Creates configuration files for AEM ClientLibs and synchronizes assets.
Apache License 2.0
62 stars 32 forks source link

Add ability to wipe clientlib-target folder before copying over the clientlibs #19

Closed henrykuijpers closed 4 years ago

henrykuijpers commented 5 years ago

It would be nice if we're able to wipe the target folder before copying over the generated clientlibs.

We faced some issues with renaming/moving files and then the new files being merged in (leaving old, not overwritten files, to remain next to the actual correct files).

stefanseifert commented 5 years ago

this is already happening afaik. can you give examples (or a demo project) where the cleaning of the clientLibRoot target folder is not working?

henrykuijpers commented 5 years ago

We were already thinking of something related to (filesystem) permissions, but didn't have time yet to verify that. I indeed see that the step is in place, but could it be that it's ignored when deleting failed? Instead of failing the build?

mvegacr commented 4 years ago

Hi!

I am seeing the same issue. After some runs it keeps all the old files without cleaning the folder. Here there is an screenshot of what I'm seeing.

Screen Shot 2019-10-15 at 8 41 12 AM

The js.txt is being generated with the latest one, so the reference is correct:

#base=js
2.46482714.chunk.js
main.900d15e9.chunk.js
runtime-main.5c03b920.js
ifahrentholz commented 4 years ago

Since the aem-clientlib-generator is not bundling any files I do think that the issue is caused by your build step. Please verify that your build (for example via webpack) correctly wipes all obsolete chunks.

ifahrentholz commented 4 years ago

Closed due to stale discussion.