Hibernate Search has many additional dependencies on top of just ORM..
would the WildFly team be happy with that?
I always assumed that would not be considered acceptable.
Also with such a solution people won't have flexibility on the
version; I know people don't have it with ORM either - unless t
Hi,
I have local database configurations for matrix testing against spatial
databases. With HHH-8235 support for matrix testing has been moved into a
separate project. Unfortunately, this change broke my matrix tests. I now get
this error:
Execution failed for task ':hibernate-spatial:matrix
On 06/06/2013 11:49 AM, Emmanuel Bernard wrote:
> On Thu 2013-06-06 11:31, Scott Marlow wrote:
>>
>> If the static Hibernate Search module, depends on a static Hibernate
>> ORM module in WildFly 8, I think that is fine, but applications
>> wouldn't be able to include their own Hibernate Search jars
On Thu 2013-06-06 11:31, Scott Marlow wrote:
>
> If the static Hibernate Search module, depends on a static Hibernate
> ORM module in WildFly 8, I think that is fine, but applications
> wouldn't be able to include their own Hibernate Search jars (since
> the static Hibernate ORM module only sees s
As I explain in the email I forwarded, modules are good on paper but
suffer from a few practical problems:
I need to manually install them on my deployed server instead of just
handing over the JAR. If there was a way to declare a dep from
jboss-deployment-structure.xml and get it downloaded from
One change that I submitted a WildFly 8 pull request for
(https://github.com/wildfly/wildfly/pull/4591), is to combine the
Hibernate ORM/envers and JipiJapa integration jars into the same module.
This eliminates the 1-1 bi-directional dependency between ORM/JipiJapa
integration code that exis
are you proposing to remove Hibernate as a Maven dependency? I don't think
that's correct.
I like the modules approach much better because it has several other
benefits, not least that it doesn't push all our dependencies to the
application classpath, and also makes the deployment smaller.
Did yo
I've created a JIRA to publish the modules distro
https://hibernate.atlassian.net/browse/OGM-290
On Thu 2013-06-06 11:10, Sanne Grinovero wrote:
> Ah right I might be confused with the Search modules as we release
> those regularly, and upload to sourceforge as well.
>
> For OGM I think we should
Next time ping me for any issues, as I've done this ages ago for CapeDwarf. :-)
On Jun 6, 2013, at 1:37 PM, Emmanuel Bernard wrote:
> Below is an email describing the issues i had to get Hibernate Search run in
> WildFly / EAP. A possibility to make life easier for Hibernate Search users
> in
Below is an email describing the issues i had to get Hibernate Search run in
WildFly / EAP. A possibility to make life easier for Hibernate Search users in
WildFly is as described by Pete to create a hibernate-search-orm-wildfly which
marks Hibernate ORM as provided.
What do you think?
Emmanu
Ah right I might be confused with the Search modules as we release
those regularly, and upload to sourceforge as well.
For OGM I think we should do a release, as in the last one the modules
where not available yet. (AFAIR as I can't check now)
On 6 June 2013 10:17, Guillaume SCHEIBEL wrote:
> I
I didn't find a direct link to download them (btw, the link to download ogm
from sourceforge
http://sourceforge.net/projects/hibernate/files/hibernate-ogm/ is pointing
to hsearch 4.3 files).
May be we could propose (don't know where, ogm download page on
hibernate.org or download page of AS 7) the
Nice post!
People don't necessarily have to build the modules from sources, you could
put a download link or explain how to unpack them via Maven.
On 6 Jun 2013 09:49, "Guillaume SCHEIBEL"
wrote:
> I'll do better, I'll try with another machine which doesn't know OGM at
> all.
>
>
> 2013/6/6 Emman
It still has to know about JBoss's nexus or use -s setting-example.xml
which will go and look for the snapshot online. And thus be
unpredictable.
On Thu 2013-06-06 10:44, Guillaume SCHEIBEL wrote:
> I'll do better, I'll try with another machine which doesn't know OGM at all.
>
>
> 2013/6/6 Emmanu
I'll do better, I'll try with another machine which doesn't know OGM at all.
2013/6/6 Emmanuel Bernard
> Well make sure to clean your maven repo cache before you test. Or else
> your local cache will contain the snapshot. Likewise, the remote repo
> might contain an old snapshot and I dont' thi
Well make sure to clean your maven repo cache before you test. Or else
your local cache will contain the snapshot. Likewise, the remote repo
might contain an old snapshot and I dont' think you can guard against
that.
On Thu 2013-06-06 10:19, Guillaume SCHEIBEL wrote:
> Thanks for your comments. Yo
Thanks for your comments. You are right, "not a panacea" is what I meant.
For the "mvn clean install" it worth to be tried, I'll keep you up to date
on that.
Next step, how to write a new datastore provider.
Guillaume
2013/6/6 Emmanuel Bernard
> Nice :)
>
> Do you really mean " OGM definitely
Nice :)
Do you really mean " OGM definitely is a panacea". From your sentence it
seems you meant " OGM definitely is not a panacea"
> Then just go under %HIBERNATE_OGM_HOME% /hibernate-ogm-modules and
> perform a mvn clean install.
I suspect that won't work since the other maven modules are not
18 matches
Mail list logo
