Esta conversa foi bloqueada devido à inatividade. Crie uma nova publicação.
Nível 1
Nível 2
Faça login na Comunidade
Faça logon para exibir todas as medalhas
Esta conversa foi bloqueada devido à inatividade. Crie uma nova publicação.
Hi Team,
I am running Repository Modernizer as referred here: https://github.com/adobe/aem-cloud-service-source-migration/tree/master/packages/repository-moderniz...
My source maven project is of archetype 19 and getting below error:
********** Executing Repository Modernizer **********
Restructuring Repository..
node_modules\@adobe\aem-cs-source-migration-repository-modernizerbasePath
Error: ENOENT: no such file or directory, stat
'node_modules\@adobe\aem-cs-source-migration-repository-modernizer\resources\all'
Code: ENOENT
Has anyone came across this error?
Solucionado! Ir para a Solução.
Visualizações
respostas
Total de curtidas
Try version 0.0.8+ of the repo modernizer plugin.
The prior version exhibited this symptom, and the way to work around it was to perform a non-global install of @Deleted Account\aem-cs-source-migration-repository-modernizer in the same folder in which you're running the aio plugin from.
Ex.
$ cd project-to-modernize
$ npm i @Deleted Account\aem-cs-source-migration-repository-modernizer
But that said, that was fixed in v0.0.8 so just upgrade to the latest version and you should be set.
As this is a node JS error which means File does not exists.
Can you check once if in below path all folder exists or not, all folder contains one pom.xml and src folder.
'node_modules\@adobe\aem-cs-source-migration-repository-modernizer\resources\all'
Regards
Visualizações
respostas
Total de curtidas
Try running npm update and also check config.yaml is well formed.
If this doesn't help, you could try re-installing node and npm.
I am getting the same issue. Are you able to find the solution to this?
Visualizações
respostas
Total de curtidas
Yes, instead of running the unified tool, i followed these steps mentioned here: https://github.com/adobe/aem-cloud-service-source-migration/tree/master/packages/repository-moderniz...
Try version 0.0.8+ of the repo modernizer plugin.
The prior version exhibited this symptom, and the way to work around it was to perform a non-global install of @Deleted Account\aem-cs-source-migration-repository-modernizer in the same folder in which you're running the aio plugin from.
Ex.
$ cd project-to-modernize
$ npm i @Deleted Account\aem-cs-source-migration-repository-modernizer
But that said, that was fixed in v0.0.8 so just upgrade to the latest version and you should be set.
Visualizações
Curtida
respostas
Visualizações
Curtida
respostas
Visualizações
Curtida
respostas