This week's book giveaway is in the Python forum.
We're giving away four copies of High Performance Python for Data Analytics and have Tiago Rodrigues Antao on-line!
See this thread for details.
Win a copy of High Performance Python for Data Analytics this week in the Python forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Bear Bibeault
  • Liutauras Vilda
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Jj Roberts
  • Carey Brown
Bartenders:
  • salvin francis
  • Frits Walraven
  • Piet Souris

Move all projects from classpath to module path at once, when working with top down migration,why?

 
Ranch Hand
Posts: 41
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

Im studying for 1Z0-819 certificate and I saw that you must movel all projects from classpath to module path at once, please tell me if i got it right why.

The reason is, named modules cannot access unnamed modules.Using top down strategy, all projects that are not named modules(high-level) are automatic modules(low-level), cause named can access automatic modules. In this scenario, if the automatic modules(low-level) were unnamed, high-level modules that reference this low-level module, would have problems since the named module cannot access unnamed.

Working with bottom up, you dont need move everything at once, cause the projects that have been migrated are named modules(low-level) and the projects that have not been migrated are unnamed modules(high-level).In this scenario, high-level projects are unnamed modules and they can access your dependencies that are named modules already migrated.

Right?
 
Not looking good. I think this might be the end. Wait! Is that a tiny ad?
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
reply
    Bookmark Topic Watch Topic
  • New Topic