Reading the Google design by contract work, I realized that we do not cover
cross-parameter validation in method-level validation.
//We want to make sure departure is after arrival.
void book(Date arrival, Date departure);
Any idea on ow best to address that?
On Fri, 18 Feb 2011 09:01:16 +0100, Emmanuel Bernard
wrote:
> Reading the Google design by contract work, I realized that we do not
> cover cross-parameter validation in method-level validation.
I assume you are talking about cofoja (http://code.google.com/p/cofoja),
right?
> //We want to
On 02/17/2011 12:42 PM, Emmanuel Bernard wrote:
> I think you should go for stage 1 and think about stage 2 for later.
> Stage 2 is quite smart, I like it.
:-)
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/l
If someone knows anything...
Begin forwarded message:
> From: Emmanuel Bernard
> Date: February 18, 2011 6:33:26 PM GMT+01:00
> To: Paul Gier
> Subject: Has something happened on the Maven repo?
>
> I'm getting weird errors about missing artifacts that I am (almost) sure were
> present before
In the last two days, I've worked on extracting the Hibernate Search specific
knowledge of the query engine.
The goals are:
- let it be reused by Infinispan and other object sources
- isolate Hibernate Search from Core (longer goal
Here is the branch
https://github.com/emmanuelbernard/hibernat
On Feb 17, 2011, at 7:22 PM, Steve Ebersole wrote:
> I see drawbacks to either approach.
>
> If the services can be shared across multiple SessionFactory instance then
> they *must* be stateless (or the state must be designed to be shared) which
> brings about portability/migration concerns.
great, thank you. Pulled this so I can have a look tomorrow, when I'll
have 10h train.
Are you only looking for feedback, or do you think something should be
merged already?
What is the fate of the MassIndexer ? Even if I managed to abstract it
from Hibernate I wonder how much the general concept
I have no idea.
be warned that the exact version might be selected according to some
other dependency change, maybe you previously built with another one?
It seems this is a quite old one, maybe you could try choosing an
updated version:
https://repository.jboss.org/nexus/content/repositories/rele
If the artifact exists in the repo still. Maven may be getting http
errors (resulting in a zero byte sized artifact) but there is a
workaround. Adding the -C or --strict-checksums option helps.
Its probably something else but "mvn -C install" might be worth trying.
On 02/18/2011 12:33 PM, Emm
