You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (JIRA)" <ji...@apache.org> on 2015/08/10 12:03:45 UTC
[jira] [Updated] (SLING-4938) sling-mock: Transitive dependency
reflections includes very old xml-apis
[ https://issues.apache.org/jira/browse/SLING-4938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Windszus updated SLING-4938:
-----------------------------------
Description:
Whenever a maven project depends on {{o.a.s.testing.sling-mock}} it automatically depends on {{xml-apis}} in version {{1.0.b2}}.
This is problematic as this is not only a very old version but also it is very hard to determine which version should be used with which JRE (http://stackoverflow.com/questions/11677572/dealing-with-xerces-hell-in-java-maven).
Therefore could we just explicitly ignore the transitive dependency {{dom4j}} on the dependency {{reflections}} within {{sling-mock}}?
I see that {{reflections}} is only used in {{ModelAdapterFactoryUtil}} and I don't see why {{dom4j}} would be necessary there. Maybe we could also get rid of the other optional dependencies {{javassist}}, {{slf4j-api}}, {{gson}}, {{servlet-api}} (https://github.com/ronmamo/reflections/blob/master/pom.xml)?
That way the classpath would be much leaner and cleaner.
was:
Whenever a maven project depends on {{o.a.s.testing.sling-mock}} it automatically depends on {{xml-apis}} in version {{1.0.b2}}.
This is problematic as this is not only a very old version but also it is very hard to determine which version should be used with which JRE (http://stackoverflow.com/questions/11677572/dealing-with-xerces-hell-in-java-maven).
Therefore could we just explicitly ignore the dependency {{dom4j}} on {{sling-mock}}?
I see that {{reflections}} is only used in {{ModelAdapterFactoryUtil}} and I don't see why {{dom4j}} would be necessary there. Maybe we could also get rid of the other optional dependencies {{javassist}}, {{slf4j-api}}, {{gson}}, {{servlet-api}} (https://github.com/ronmamo/reflections/blob/master/pom.xml)?
That way the classpath would be much leaner and cleaner.
> sling-mock: Transitive dependency reflections includes very old xml-apis
> ------------------------------------------------------------------------
>
> Key: SLING-4938
> URL: https://issues.apache.org/jira/browse/SLING-4938
> Project: Sling
> Issue Type: Improvement
> Components: Testing
> Affects Versions: Testing Sling Mock 1.4.0
> Reporter: Konrad Windszus
>
> Whenever a maven project depends on {{o.a.s.testing.sling-mock}} it automatically depends on {{xml-apis}} in version {{1.0.b2}}.
> This is problematic as this is not only a very old version but also it is very hard to determine which version should be used with which JRE (http://stackoverflow.com/questions/11677572/dealing-with-xerces-hell-in-java-maven).
> Therefore could we just explicitly ignore the transitive dependency {{dom4j}} on the dependency {{reflections}} within {{sling-mock}}?
> I see that {{reflections}} is only used in {{ModelAdapterFactoryUtil}} and I don't see why {{dom4j}} would be necessary there. Maybe we could also get rid of the other optional dependencies {{javassist}}, {{slf4j-api}}, {{gson}}, {{servlet-api}} (https://github.com/ronmamo/reflections/blob/master/pom.xml)?
> That way the classpath would be much leaner and cleaner.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)