Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Repository Modernizer error

Avatar

Avatar
Validate 1
Level 1
sravs508
Level 1

Like

1 like

Total Posts

10 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 1
View profile

Avatar
Validate 1
Level 1
sravs508
Level 1

Like

1 like

Total Posts

10 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 1
View profile
sravs508
Level 1

23-12-2020

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?

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Ignite 3
Level 5
davidjgonzalezzzz
Level 5

Likes

70 likes

Total Posts

77 posts

Correct Reply

31 solutions
Top badges earned
Ignite 3
Affirm 25
Ignite 1
Give Back 5
Give Back 3
View profile

Avatar
Ignite 3
Level 5
davidjgonzalezzzz
Level 5

Likes

70 likes

Total Posts

77 posts

Correct Reply

31 solutions
Top badges earned
Ignite 3
Affirm 25
Ignite 1
Give Back 5
Give Back 3
View profile
davidjgonzalezzzz
Level 5

06-02-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 @adobe\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 @adobe\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.

Answers (3)

Answers (3)

Avatar

Avatar
Validate 1
Level 1
sravs508
Level 1

Like

1 like

Total Posts

10 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 1
View profile

Avatar
Validate 1
Level 1
sravs508
Level 1

Like

1 like

Total Posts

10 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 1
View profile
sravs508
Level 1

06-01-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-moderniz...

Avatar

Avatar
Affirm 100
MVP
shelly-goel
MVP

Likes

243 likes

Total Posts

408 posts

Correct Reply

104 solutions
Top badges earned
Affirm 100
Give Back 25
Ignite 3
Give Back 10
Validate 1
View profile

Avatar
Affirm 100
MVP
shelly-goel
MVP

Likes

243 likes

Total Posts

408 posts

Correct Reply

104 solutions
Top badges earned
Affirm 100
Give Back 25
Ignite 3
Give Back 10
Validate 1
View profile
shelly-goel
MVP

24-12-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.

Avatar

Avatar
Give Back 5
Level 4
praveenjain
Level 4

Likes

37 likes

Total Posts

36 posts

Correct Reply

10 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Ignite 1
Boost 5
View profile

Avatar
Give Back 5
Level 4
praveenjain
Level 4

Likes

37 likes

Total Posts

36 posts

Correct Reply

10 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Ignite 1
Boost 5
View profile
praveenjain
Level 4

24-12-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