Hello all,
While trying to fix one of Envers issues, I have encountered difficulties
inserting one-to-one relation mapped with join table. All audit entities
generated by Envers follow EntityMode.MAP pattern. Simple hibernate-core
test case - https://gist.github.com/lukasz-antoniak/5929345 - fails
Hi all,
As discussed with some of you before, the experimental query parser project
has been renamed to accommodate the fact that it is a parser for HQL
queries and not only JPQL.
That's the changed URL:
* old: https://github.com/hibernate/hibernate-jpql-parser
* new: https://github.com/hibernat
Should be fixed now, the last build is building the MongoDB modules.
The environment variable is missing in the build.
Now that I think about it...didn't we created a separate job for mongodb in
the past? I think the Idea was two build the project without using the
remote container and then
build
Sto guardando
On Thu, Jul 4, 2013 at 2:11 PM, Sanne Grinovero wrote:
> Sounds like a good idea to have CI verify both embedded and "installed".
>
> But that's next, I'd first want to see it building at least with the
> installed MongoDB.
>
> On 4 July 2013 14:04, Davide D'Alto wrote:
> > Why n
Sounds like a good idea to have CI verify both embedded and "installed".
But that's next, I'd first want to see it building at least with the
installed MongoDB.
On 4 July 2013 14:04, Davide D'Alto wrote:
> Why not to test the emebedded one on a port that is different from the
> default one (or t
Why not to test the emebedded one on a port that is different from the
default one (or the one used for the remote mongodb)?
This way if you are using the emebedded the remote is not affected.
On Thu, Jul 4, 2013 at 1:32 PM, Sanne Grinovero wrote:
> Actually makes me think we might want an opti
Actually makes me think we might want an option in OGM-295 to have the
build fail if MongoDB is only runnable in embedded mode:
MongoDB is installed in the CI machine and used to be run
successfully. I guess the configuration changed and we didn't notice
it stopped building it.. that must be it be
It's my hope that one of the benefits of implementing OGM-295 ("Facilitate
project setup by using Embedded MongoDB", [1]) is to enable this.
We still could consider running tests against a standalone installation of
MongoDB, but starting with testing against an embedded instance seems like
a good
>From what I can see and understand the OGM builds (hibernate-ogm-master
specifically) do not test MongoDB. Is that something expected? Can we
envision adding MongoDB testing?
Emmanuel
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://
Thanks!
On 4 July 2013 11:26, Gunnar Morling wrote:
> Thanks, Sanne, for creating the issue. I can do that, already assigned it to
> me.
>
> --Gunnar
>
>
>
> 2013/7/4 Sanne Grinovero
>>
>> Created as
>> https://hibernate.atlassian.net/browse/OGM-295
>>
>> volunteers?
>>
>>
>> On 28 June 2013 10:
Thanks, Sanne, for creating the issue. I can do that, already assigned it
to me.
--Gunnar
2013/7/4 Sanne Grinovero
> Created as
> https://hibernate.atlassian.net/browse/OGM-295
>
> volunteers?
>
>
> On 28 June 2013 10:20, Hardy Ferentschik wrote:
> >
> > On 28 Jan 2013, at 11:15 AM, Emmanuel
Created as
https://hibernate.atlassian.net/browse/OGM-295
volunteers?
On 28 June 2013 10:20, Hardy Ferentschik wrote:
>
> On 28 Jan 2013, at 11:15 AM, Emmanuel Bernard wrote:
>
>> I wonder how you can debug things though and look at the content outside
>> your tests? I guess you would install
Right, the artefacts are not on Nexus and I don't seem to see them in the
staging repo either.
--Hardy
On 4 Jan 2013, at 10:37 AM, Sanne Grinovero wrote:
> I tried to upgrade Hibernate Search to the ORM release, but it seems
> something went wrong with the Maven upload?
>
> output:
>
> [INF
I tried to upgrade Hibernate Search to the ORM release, but it seems
something went wrong with the Maven upload?
output:
[INFO]
[INFO] Building Hibernate Search ORM 4.4.0-SNAPSHOT
[INFO] -
14 matches
Mail list logo
