- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
โ02-28-2022
06:45 AM
Queries regarding isolated mode migration
Hi Team,
While migration from legacy to isolated mode i am having few questions :
1.All dependency that we have added in pom.xml ,do we need to add all that same resources in module-isolated.xml under <resources> with mode=isolated?
2.Any relevance of external dependency what if after adding all resources in module-isolated.xml still getting 1000 eternal dependency? can we avoid this if our module is getting successfully build.
3.What is solution for dependency on espirit internal classes (NON_API_USAGE),in my module i am having total 8 file dependent what we need to do here to make it zero. Please find reference screenshot
Please help me to solve all above question.
Thankyou in advance!!
Regards,
Aradhana
1 Reply
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
โ03-30-2022
12:23 AM
- Yes, you need to add all previous dependencies with the mode="isolated" attribute. Further dependencies may be required if you implicitly used libraries that were shipped with the fs-access.jar but are no longer available due to the isolation.
- The list of external dependencies has mere informational purpose. It is most likely that these never drop to 0, especially when using frameworks like Spring Boot.
- The solution for using Non-API-Code highly depends on your code. If you find a required use case that can not be modeled by using the available API, please open a support ticket with an exact description of what you are trying to achieve.