Dependency on slf4j 1.5.6 and access of causes problems with Discovery and some
ingest methods
----------------------------------------------------------------------------------------------
Key: DSRV-11
URL: https://jira.duraspace.org/browse/DSRV-11
Project: DSpace Services Module
Issue Type: Bug
Components: kernel
Reporter: Kim Shepherd
Priority: Critical
See DS-785 for full discussion of how this bug affects DSpace Discovery + SWORD
deposits.
When DSpaceKernelManager initialises logging (private static Logger log =
LoggerFactory.getLogger(DSpaceKernelManager.class)), slf4j 1.5.6 throws an
IllegalAccessError. In 1.5.5 and below, the SINGLETON field in
StaticLoggerBinder was handled differently and would not throw this exception.
See:
http://www.slf4j.org/faq.html#IllegalAccessError
This error is being triggered when attempting a SWORD deposit in Dspace 1.7.0
(any RC) with Discovery enabled (and "discovery" event consumer replacing
"search" in dspace.cfg)
We either need to try and work around the change in behaviour of
StaticLoggerBinder in slf4j, or roll back dependency on slf4j to 1.5.5
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Lotusphere 2011
Register now for Lotusphere 2011 and learn how
to connect the dots, take your collaborative environment
to the next level, and enter the era of Social Business.
http://p.sf.net/sfu/lotusphere-d2d
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
