To clarify...
The same NamingStrategy is used no matter what by default. The variance
comes from the fact that each binding method calls different methods :(
Which of course makes retrofitting tough in these cases. The main use
case I have seen where this happens is in many-to-one mappings. Hb
Running a test for any of the datastore (except HashMap) is a pain.
Hardy's approach does not solve the one test problem as it runs all of the TCK,
which can be done with mvn install.
The workarounds are:
- copy the tests
- use your IDE to set the different module classpath but that also means
2015-02-25 16:47 GMT+01:00 Hardy Ferentschik :
> > > A dedicated module means less surprises and less understanding needed
> to
> > > see how
> > > things get together.
> > >
> >
> > Hm, but test JARs have been an exception to that "rule" in Maven for a
> long
> > time. So no-one should really be
On Wed, Feb 25, 2015 at 12:46:13PM +0100, Gunnar Morling wrote:
> To give some background, there is a dialect in core itself, HashmapDialect,
> which is used when running the TCK in core.
Something I did not know. I was about to ask how you can run these tests in
core anyways. I was wondering whet
> > A dedicated module means less surprises and less understanding needed to
> > see how
> > things get together.
> >
>
> Hm, but test JARs have been an exception to that "rule" in Maven for a long
> time. So no-one should really be surprised by using that concept.
Hmm, not sure.
> > Also, havi
Hi,
Just wondering if HSEARCH-1786/HSEARCH-1814 are on the radar? We have
stopped all of our upgrade efforts because of this. And if they are valid
bugs, it basically means that HSEARCH 5.0, and 5.01 are unreliable for
production use.`
I'm just wondering if it's considered a real bug, if so it's
> My main concern still is whether that move would complicate running tests
in core itself? Today I can click and run the TCK tests in core in the IDE
without any further preparation. If that'd get more difficult, I'd vote
against that split.
To give some background, there is a dialect in core its
2015-02-25 11:30 GMT+01:00 Hardy Ferentschik :
> > > Wouldn't it make sense to have these backendtck tests defined in a
> > > dedicated
> > > module? When you mentioned it, I was literally searching for the tests
> you
> > > were
> > > referring to.
> > >
> >
> > Sorry, I guess I should have given
On 25 February 2015 at 10:53, Davide D'Alto wrote:
> I like the idea of a separate module for shared tests, It makes sense for
> our usecase.
> I've never been a big fun of the OGM black magic.
I'm not a fan of the current state either, but there are many possible
improvements which don't need a
I like the idea of a separate module for shared tests, It makes sense for
our usecase.
I've never been a big fun of the OGM black magic.
Are there any reasons not to do it except that it will add a new module?
I'm not really concerned about having modules in the project if their
purpose is clear.
> > Wouldn't it make sense to have these backendtck tests defined in a
> > dedicated
> > module? When you mentioned it, I was literally searching for the tests you
> > were
> > referring to.
> >
>
> Sorry, I guess I should have given you the package name.
>
> I kind of like the fact that one can
Ok, I have filed https://hibernate.atlassian.net/browse/OGM-747 for that.
--Gunnar
2015-02-23 12:32 GMT+01:00 Hardy Ferentschik :
> sure +1
>
>
> On Mon, Feb 23, 2015 at 11:40:19AM +0100, Gunnar Morling wrote:
> > Hi,
> >
> > So far Hibernate OGM has been usable quite well when running on Java
12 matches
Mail list logo
