On Mar 30, 2011, at 8:46 PM, Steve Ebersole wrote:
> To be honest not sure what this really buys you. Basically you have to
> follow
> the META-INF/service/{intf-name} pattern for naming your locator file and
> that
> locator file, as far as I know, can only have a single entry naming the im
Any thinking done on how CDI enabled applications could be using CDI to wire
this up ?
/max
On Mar 27, 2011, at 19:27, Steve Ebersole wrote:
> HHH-5562 is done, which introduces a locator/discovery means for integrating
> with Hibernate. Specifically it introduces the (alternate name suggesti
btw. any way to disable specific discovery items ?
i.e. I would like to not have search and envers enabled when the tools are
doing query plans/executions
since it then suddenly requires much more configuration to have it setup and
run.
/max
On Mar 31, 2011, at 12:00, Max Rydahl Andersen wrote
On Mar 24, 2011, at 17:10, Hardy Ferentschik wrote:
> On Wed, 23 Mar 2011 15:41:29 +0100, Max Rydahl Andersen
> wrote:
>
>>> Speaking of shading, this could be an easy solution for METAGEN-53 as well.
>>>
>>
>> For metagen-53 I recall that the only dependency is class name lookup which
>> c
>> 2)Eclipse
>> the configuration files generated by gradle are totally wrong, but I
>> could fix them by hand.
>> Now Eclipse refuses to compile the project as there's a circular
>> dependency: the testsuite from hibernate-core depends on the
>> hibernate-testing module, which in turn depends on h
Just because eclipse might not like it does not make it broken ;)
On Thursday, March 31, 2011, at 05:14 am, Max Rydahl Andersen wrote:
> >> 2)Eclipse
> >> the configuration files generated by gradle are totally wrong, but I
> >> could fix them by hand.
> >> Now Eclipse refuses to compile the proj
On Mar 31, 2011, at 15:28, Steve Ebersole wrote:
> Just because eclipse might not like it does not make it broken ;)
It's your choice to make it hard to develop on Hibernate core in Eclipse.
You can fix it on Hibernate side - I can't fix Eclipse core fundamentals.
/max
> On Thursday, March 31
On Thursday, March 31, 2011, at 11:52 am, Max Rydahl Andersen wrote:
> On Mar 31, 2011, at 15:28, Steve Ebersole wrote:
> > Just because eclipse might not like it does not make it broken ;)
>
> It's your choice to make it hard to develop on Hibernate core in Eclipse.
Thats one way to look at it.
2011/3/31 Steve Ebersole :
>
> On Thursday, March 31, 2011, at 11:52 am, Max Rydahl Andersen wrote:
>> On Mar 31, 2011, at 15:28, Steve Ebersole wrote:
>> > Just because eclipse might not like it does not make it broken ;)
>>
>> It's your choice to make it hard to develop on Hibernate core in Eclip
On Mar 31, 2011, at 12:05 PM, Max Rydahl Andersen wrote:
> btw. any way to disable specific discovery items ?
> i.e. I would like to not have search and envers enabled when the tools are
> doing query plans/executions
> since it then suddenly requires much more configuration to have it setup an
It's not a configuration issue, rather a preference setting to turn off the
warning about cyclic dependencies: Preferences > Java > Compilter > Building >
Build Path Problems > Circular Dependencies > Warning
On Mar 31, 2011, at 1:07 PM, Sanne Grinovero wrote:
> 2011/3/31 Steve Ebersole :
>>
>
There is one for search too. But should we have a global flag to disable all
integrations? Does it makes sense (what about Bean Validation for example?
On 31 mars 2011, at 20:08, Adam Warski wrote:
>
> On Mar 31, 2011, at 12:05 PM, Max Rydahl Andersen wrote:
>
>> btw. any way to disable speci
>> You can fix it on Hibernate side - I can't fix Eclipse core fundamentals.
>
> Well as John already said, he was able to verify that it does in fact work in
> Eclipse. So obviously *they* don't think its a broken set up. Thats just
> your opinion. Perhaps maybe the concern is that it possib
> It's not a configuration issue, rather a preference setting to turn off the
> warning about cyclic dependencies: Preferences > Java > Compilter > Building
> > Build Path Problems > Circular Dependencies > Warning
If thats enough thats greatbut there is a reason eclipse has that as an
Err
14 matches
Mail list logo
