Repository Modernizer error | Community
Skip to main content
S
sravs508
December 24, 2020
Solved

Repository Modernizer error

  • December 24, 2020
  • 5 replies
  • 2337 views

Hi Team,

 

I am running Repository Modernizer as referred here: https://github.com/adobe/aem-cloud-service-source-migration/tree/master/packages/repository-modernizer

 

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?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by davidjgonzalezzzz

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 @61380\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 @61380\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.

5 replies

P
praveenjain
December 24, 2020

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

Praveen

    S
    sravs508Author
    December 24, 2020
    i do have the path
    shelly-goel
    Adobe Employee
    shelly-goelAdobe Employee
    Adobe Employee
    December 24, 2020

    @sravs508 

    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.

      P
      Piy-Malik
      January 6, 2021

      I am getting the same issue. Are you able to find the solution to this?

      S
      sravs508Author
      January 6, 2021

      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-modernizer

        D
        Adobe Employee
        davidjgonzalezzzzAdobe EmployeeAccepted solution
        Adobe Employee
        February 6, 2021

        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 @61380\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 @61380\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.

          Terms & ConditionsAccessibility statement

          Loading footer...