fix(QTDI-2031): manage dynamic dependencies - w/o MAVEN-INF

[undx]

https://qlik-dev.atlassian.net/browse/QTDI-2031

This pull request mainly

• reverts changes in QTDI-693
• adds some extra debug logging informations
• add annotation for marking a dynamic dependencies configuration

Related pull-requests:

• fix(QTDI-2031): manage dynamic dependencies - w/o MAVEN-INF #1118
• https://github.com/Talend/tdi-studio-se/pull/11589
• https://github.com/Talend/tesb-studio-ee/pull/1485

[Copilot]

Pull Request Overview

This PR reverts changes from QTDI-693 related to nested repository handling and adds debugging capabilities for dynamic dependencies troubleshooting. The changes simplify classloader behavior by removing nested URL tracking and redundant scanning logic.

Key Changes:

• Removes nested repository special handling and scanning logic that was added in QTDI-693
• Adds debug logging for system information (JVM arguments, classpaths, repository locations)
• Introduces @DynamicDependenciesConfiguration annotation for marking dynamic dependency configurations

Reviewed Changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
ContainerManager.java	Adds debug logging for system info and repository locations; simplifies root repository resolution
ConfigurableClassLoader.java	Removes nested URL tracking by deleting nestedURLs field and getURLs() override
ComponentManager.java	Removes nested repository scanning logic and unused imports
ComponentManagerTest.java	Updates test assertions to reflect reverted behavior (expects 1 dependency instead of 2)
DynamicDependenciesConfiguration.java	New annotation file for marking dynamic dependencies configuration classes

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Using an empty string as the default value for 'user.home' system property will cause PathFactory.get(\"\") to be called if the property is not set, which may result in unexpected path resolution behavior. Consider using a more appropriate fallback or handling the null case explicitly.

Suggested change

	.orElseGet(() -> PathFactory.get(System.getProperty("user.home", "")).resolve(".m2/repository"));
	.orElseGet(() -> {
	String userHome = System.getProperty("user.home");
	if (userHome == null || userHome.isEmpty()) {
	userHome = System.getProperty("user.dir");
	if (userHome == null || userHome.isEmpty()) {
	throw new IllegalStateException("Neither 'user.home' nor 'user.dir' system properties are set. Cannot determine repository location.");
	}
	}
	return PathFactory.get(userHome).resolve(".m2/repository");
	});

[sonar-eks]

Quality Gate failed

• 55.20% Coverage on New Code (is less than 80.00%)
• 2 New Issues (is greater than 0)

Project ID: org.talend.sdk.component:component-runtime

View in SonarQube