No idea, I wanted to ask the same question.
I modified the build file last, but was just updating the HV version.
Looking at the history I see that Strong did some changes related to
javadocs (fc90bc3a8af3db8c8aa09dd0b2879c883d557e7e)
The message says "deploy javadoc jar". My guess is that this c
Anyone know why I get javadocs being generated now whenever I run
`gradle test` ? Did anyone change up task deps?
--
Steve Ebersole
http://hibernate.org
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/lis
I'm not sure if we will see this NPE again but found the location
interesting. I wanted to report the failure in case it happens again in
the future or anyone else is interested in playing detective for
mysteries like this. ;)
The exception call stack is here http://pastie.org/2104060
It look
I wondered the same. That's what it was doing when I started working on the
code. It seemed convoluted to me, but I figured there was a reason for it.
Go ahead and change it as you see fit.
Gail
- Original Message -
From: "Steve Ebersole"
To: hibernate-dev@lists.jboss.org
Sent: Monday,
If a person wanted to start down the road of adding MongoDB support for OMG,
where would the best place to start be?
Tom
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
I've been working on the backend side and made the following split
api
Workspace
TransactionContext
OptimizerStrategy
LuceneWork and *LuceneWork
spi
WorkType
Work
Worker
UpdatableBackendQueueProcessorFactory
BackendQueueProcessorFactory
LuceneIndexingParameters
impl
WorkVisitor
WorkQueue
WorkerFa
It would not necessarily require users to change config values. Just
update the code that instantiates the RegionFactories
(org.hibernate.cache.internal.RegionFactoryInitiator) to understand the
legacy class FQN as well. Have a look at
org.hibernate.engine.transaction.internal.TransactionFact
yes, but thats the pain we must take
---
Strong Liu
http://hibernate.org
http://github.com/stliu
On Jun 21, 2011, at 5:56 PM, Alex Snaps wrote:
> Did that... I'll replace internal with ehcache then, as in the infinispan
> module. But that would still require existing users to chang
Did that... I'll replace internal with ehcache then, as in the infinispan
module. But that would still require existing users to change their config
though!
On Tuesday 21 June 2011 at 11:39, Strong Liu wrote:
> take a look of hibernate-infinispan, we should change hibernate-ehcache
> package
take a look of hibernate-infinispan, we should change hibernate-ehcache package
name like that, using "internal" in user's configuration file is not a good
ghing
---
Strong Liu
http://hibernate.org
http://github.com/stliu
On Jun 21, 2011, at 4:42 PM, Alex Snaps wrote:
>
> On Wednesd
On Wednesday 8 June 2011 at 16:47, Strong Liu wrote:
>
> On Jun 8, 2011, at 9:02 PM, Steve Ebersole wrote:
>
> > The only use case I am really interested in for "simple map based"
> > caching is the test suite. Its the whole reason I did not do the things
> > Strong and I discussed on the oth
11 matches
Mail list logo