Yes, that's true. It returns null when being run for classes obtained from
a directory rather than a JAR.
I noticed the same btw. when running tests in the IDE for the injection
stuff we e.g. use in HV, but it never was a problem for us there.
2015-03-03 16:20 GMT+01:00 Steve Ebersole :
> I thi
I think we should point out that this method is only available (iiuc) when
running with "from a jar". Which means it won't work, for example, in our
test suites. I assume we'd just get blanks or nulls there.
On Tue, Mar 3, 2015 at 9:18 AM, Steve Ebersole wrote:
> I just personally never knew a
I just personally never knew about this method :)
On Mon, Mar 2, 2015 at 10:03 AM, Sanne Grinovero
wrote:
> On 2 March 2015 at 15:49, Gunnar Morling wrote:
> >
> >
> > 2015-03-02 16:22 GMT+01:00 Sanne Grinovero :
> >>
> >> On 2 March 2015 at 15:05, Steve Ebersole wrote:
> >> > Hmm, I had used
On 2 March 2015 at 15:49, Gunnar Morling wrote:
>
>
> 2015-03-02 16:22 GMT+01:00 Sanne Grinovero :
>>
>> On 2 March 2015 at 15:05, Steve Ebersole wrote:
>> > Hmm, I had used to set the set the Specification-* entries too, but it
>> > looks
>> > like those are no longer there :(
>>
>> Just out of
2015-03-02 16:22 GMT+01:00 Sanne Grinovero :
> On 2 March 2015 at 15:05, Steve Ebersole wrote:
> > Hmm, I had used to set the set the Specification-* entries too, but it
> looks
> > like those are no longer there :(
>
> Just out of curiosity, what would these define?
> But not too bad, I think I'
It was the "release family". 4.3, or 4.2...
On Mar 2, 2015 9:22 AM, "Sanne Grinovero" wrote:
> On 2 March 2015 at 15:05, Steve Ebersole wrote:
> > Hmm, I had used to set the set the Specification-* entries too, but it
> looks
> > like those are no longer there :(
>
> Just out of curiosity, what
On 2 March 2015 at 15:05, Steve Ebersole wrote:
> Hmm, I had used to set the set the Specification-* entries too, but it looks
> like those are no longer there :(
Just out of curiosity, what would these define?
But not too bad, I think I'll simply rely on parsing
org.hibernate.Version#getVersionS
Hmm, I had used to set the set the Specification-* entries too, but it
looks like those are no longer there :(
On Mon, Mar 2, 2015 at 7:57 AM, Gunnar Morling wrote:
> > Or we could improve on those methods, if not actually adding some easy
> to consume resource in the orm jars.
>
> Doesn't such
> Or we could improve on those methods, if not actually adding some easy
to consume resource in the orm jars.
Doesn't such resource already exist, in the form of META-INF/MANIFEST.MF ->
key "Implementation-Version"?
Based on that you should be able to raise a meaningful error if the ORM
version i
All,
it looks like people get easily confused by which version of ORM is
compatible with - for example - Hibernate Search.
The expected versions are documented plenty, in readme, project
sources, documentation and we even remind about the expectations
frequently in blog posts.
Wondering if it wou
10 matches
Mail list logo
