Details
Description
Default classloader strategy is parent-first. Sonar libs are loaded before plugin libs. For this reason a plugin can not ignore Sonar libs or use other versions. It can generate conflicts in some cases, usually on XML libs.
A plugin should have the choice to use the child-first strategy, at its own risk. The property "Plugin-FirstClassloader" must be added with value "true" to the plugin manifest. It requires to improve the sonar-packaging-maven-plugin.
Issue Links
- is depended upon by
-
SONAR-1772
Remove the use of the Maven Findbugs plugin to directly pilot the Findbugs library
-
-
SONARPLUGINS-499
Use sonar-plugin packaging
-
- is related to
-
SONAR-1869
sonar-packaging-maven-plugin : should be possible to specify delegation model for plugin classloader
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Link |
This issue is related to |
| Link |
This issue is depended upon by |
| Status | In Progress [ 3 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
| Link |
This issue is depended upon by |
| Status | Resolved [ 5 ] | Closed [ 6 ] |
See http://articles.qos.ch/classloader.html