[GRADLE-1465] Isolate internally used (Maven) libraries from script class path Created: 06/Apr/11 Updated: 04/Jan/13 Resolved: 06/Apr/11
|Reporter:||Peter Niederwieser||Assignee:||Peter Niederwieser|
Isolate internally used Maven libraries from script class path to avoid class loading conflicts if scripts or plugins use other Maven libraries.
Introduce core-impl project and give it its own class loader. Instances of types in core-impl are created via a factory service. Move classes that use Maven APIs into core-impl. Remove Maven types from public Gradle APIs residing in core.