In LazyInitializationException's constructor, we do log as error the exception
and its stack trace. While not extremely common[1][2], there are cases in
Hibernate Search engine where we catch the exception and ignore it on purpose.
These ERROR level logs are scaring and polluting.
Question, wou
Hi,
May be i understood wrongly as I am not much familiar with all part of code
yet but I did complete build everything went fine.
But if needed i will submit else i will work other issue which i can fix by
selecting JIRA. It is upto final decision.
Thanks
Thamayanthi
On Thu, Jul 7, 2011 at 4
Hi,
because of Community Awards when I was part of the community not so long ago:
http://infinispan.blogspot.com/2010/06/judcon-and-jboss-community-awards.html
Also all "Arquillian Nobles" have a crown (people Dan Allen had
"crowned" for relevant
contributions to Arquillian this year at JUDCon).
-
Best Regards,
Strong Liu
http://about.me/stliu/bio
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Hi,
the next step would be to provide a patch, preferably a GitHub pull
request against
https://github.com/hibernate/hibernate-core/tree/3.6
Also, have you seen Strong's comment's on the issue? Your problem is
centered around a
javadoc generation problem when creating the distribution bundles
