Hey,
yeah, that is exactly what I am seeing. Thanks for that - looking into it
now.
Regards,
Zubair
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Tapestry-5-2-4-issue-tp3273778p3275616.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
Hi Zubair
Is this your error: http://www.slf4j.org/faq.html#IllegalAccessError ?
> This error is caused by the static initilizer of the LoggerFactory class
> attempting to directly access the SINGLETON field of
> org.slf4j.impl.StaticLoggerBinder. While this was allowed in SLF4J 1.5.5 and
> ea
If upgrading didn't help, you have multiple slf4j libs in the
classpath (newer api than impl). Using maven? Run mvn dependency:tree.
Kalle
On Sat, Nov 20, 2010 at 10:55 AM, Zubair Nuamaan
wrote:
>
> Thanks, did that and same issue - upgraded to 1.6.1
>
> How would I find out which libraries are
Thanks, did that and same issue - upgraded to 1.6.1
How would I find out which libraries are using slf4j internally?
Regards,
Zubair
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Tapestry-5-2-4-issue-tp3273778p3273814.html
Sent from the Tapestry - User mailing list a
Update to a newer version of slf4j.
Kalle
On Sat, Nov 20, 2010 at 10:10 AM, Zubair Nuamaan
wrote:
>
> Hi,
>
> upgraded to 5.2.4 today and I get the following error:
>
> tried to access field org.slf4j.impl.StaticLoggerBinder.SINGLETON from class
> org.slf4j.LoggerFactory
>
> haven't seen anythi
But the only thing I changed was tapestry 5.2.1 to 5.2.4. All other
libraries stayed the same.
I'll keep digging
Zubair
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Tapestry-5-2-4-issue-tp3273778p3273790.html
Sent from the Tapestry - User mailing list archive at Na
On Sat, 20 Nov 2010 16:10:53 -0200, Zubair Nuamaan
wrote:
Hi,
Hi!
upgraded to 5.2.4 today and I get the following error:
tried to access field org.slf4j.impl.StaticLoggerBinder.SINGLETON from
class org.slf4j.LoggerFactory
This is not related to Tapestry at all. You probably have misma