On 1 June 2012 20:20, Hardy Ferentschik wrote:
> For the records buildhive kind of worked for Hibernate Validator. At least we
> it built and as
> Sanne said, the setup was almost too easy to be true.
>
> However, there are indeed too many false positives. I have not been able to
> figure out wh
Hi Gunnar,
yes it would trigger a build work for any commit happening on any
branch on a registered repository, so also feature branches; In
practice I think it was happening even too often but again the service
is too simple to be configured any differently.
I agree the approach provides good val
Without looking into the issue closer I like @SpatialValue also better. It
seems more descriptive.
Regarding @Spatials, I think @Spatial.List or even better @SpatialValue.List
not too bad. the .List
approach is the one taken in Bean Validation as well and @SpatialValue.List
does not sound bad im
For the records buildhive kind of worked for Hibernate Validator. At least we
it built and as
Sanne said, the setup was almost too easy to be true.
However, there are indeed too many false positives. I have not been able to
figure out what
the problem is (not a timeout issue). Test would random
Hi Rob, overall I am OK with the proposal.
Some comments inline
On Thu 31 May 2012 03:32:25 PM CDT, David Mansfield wrote:
>> It seemed that the challenge to overcome was that Hibernate did not
>> know which aliases to use when generating the where clauses for
>> filters. When filters are not a
Hi Sanne,
I was (positively) surprised to get mails for builds of a HV feature
branch, so that's definitely a plus.
Do you know whether that only works for branches in the master
repository (we're having this in HV currently for the first time I
think) or also for branches in (possibly selected)
On 1 June 2012 14:49, Nicolas Helleringer wrote:
> Hi all,
>
> I'm working on the programatic mapping of HSEARCH-923 (spatial support) and
> I had to implements @Spatials for
> @Spatial as @Fields is to @Field
>
> Emmanuel checked my work on my gtihub repo and some questions raised we
> would like
On 1 juin 2012, at 15:49, Nicolas Helleringer wrote:
> - @Spatial is supported at entity level and at property level. But if it
> seems ok for an entity to have multiples location
> through @Spatials (think a user with a work and a personnal
> address/position) it seems more weird to have @Spatia
Hi all,
I'm working on the programatic mapping of HSEARCH-923 (spatial support) and
I had to implements @Spatials for
@Spatial as @Fields is to @Field
Emmanuel checked my work on my gtihub repo and some questions raised we
would like to share with you :
- Is @Spatials the right name for such a p
Hi All,
I've had Buildhive configured on some of our projects for the last
week as an experiment (Hibernate Validator, Search, OGM).
Apologies for all the notifications it made, especially since I didn't
warn about enabling it.
Apparently it creates lots of false positives so it has been quite
noi
On Jun 1, 2012, at 7:44 PM, Steve Ebersole wrote:
>
> On Fri 01 Jun 2012 05:27:12 AM CDT, Strong Liu wrote:
>> Hi there,
>>
>> I'm working on this
>> org.hibernate.ejb.test.lock.LockTest#testFindWithPessimisticWriteLockTimeoutException
>> test, it failed on lots of DBs
>>
>> for now, I found
On Fri 01 Jun 2012 05:27:12 AM CDT, Strong Liu wrote:
> Hi there,
>
> I'm working on this
> org.hibernate.ejb.test.lock.LockTest#testFindWithPessimisticWriteLockTimeoutException
> test, it failed on lots of DBs
>
> for now, I found:
>
> sql server : supports nowait, but not other lock timeout va
Hi there,
I'm working on this
org.hibernate.ejb.test.lock.LockTest#testFindWithPessimisticWriteLockTimeoutException
test, it failed on lots of DBs
for now, I found:
sql server : supports nowait, but not other lock timeout value
DB2 : doesn't support either
sybase: doesn't support either
by "d
13 matches
Mail list logo
