Hi guys,
I have finished the migration of Hibernate OGM to its new separated Git
repository. I've kept the history (that was fun).
The new home is now here https://github.com/emmanuelbernard/hibernate-ogm
This is a multi module project with a single module so far: hibernate-ogm-core.
But we can
Everybody thinks it's a good idea so I went for it.
welcome org.hibernate,ogm
@Sanne, you mean modules for OGM? At least one per NoSQL.
On 11 mars 2011, at 20:52, Sanne Grinovero wrote:
> +1 on the approach,
>
> do you already have plans of many modules?
>
> 2011/3/11 Emmanuel Bernard :
>> Tod
+1 on the approach,
do you already have plans of many modules?
2011/3/11 Emmanuel Bernard :
> Today we have the following approach for most of our projects
>
> groupId: org.hibernate
> artifactId hibernate-search-parent, hibernate-search etc
>
> Since I'm working on the ogm packaging, I wonder if
2011/3/11 Hardy Ferentschik
The artifactId should stay, however, hibernate-ogm-core. Remember the
> artifactId determines the name of the jar file. I prefer
> hibernate-ogm-core over ogm-core.jar.
>
+1 for this approach. This style is also followed by the Seam modules, e.g.:
org.jboss.seam.vali
Hi,
sorry for the following lengthy code example, but it is hard to
demonstrate this much shorter.
The example shows how you can enable multiple facets and then continuously
restrict the query result
by chaining facets into a FacetFilter (which delegates to a ChainedFilter
underneath). WDYT?
+1 If we would have started this earlier, we would have a much nicer
namespace under
https://repository.jboss.org/nexus/content/repositories/public/org/hibernate/
Obviously we cannot get rid of/change the existing structure by changing
the groupIds of existing projects, because we have to ke
Today we have the following approach for most of our projects
groupId: org.hibernate
artifactId hibernate-search-parent, hibernate-search etc
Since I'm working on the ogm packaging, I wonder if we should do something like
groupId: org.hibernate.ogm
artifactId hibernate-ogm-parent, hibernate-ogm-
We (as in not me for once) are having a bad experience with massive amounts of
merge conflicts. Git is great but there is only so much magic can get you at.
We were discussing how to limit these kind of bad experiences in IRC and I've
added a few more advices I could think of.
Try to separate y
Well in Nicolas' case, the file points to C\:\Dev where it should be C:\
For the Netweaver case, that's yet another app server that does not know what a
URI is. I guess we could change the algorithm form the if else approach to a
try catch if and try the second approach if the first raises an ex
ah, that looks impressively similar to this post I just answered last night:
https://forum.hibernate.org/viewtopic.php?f=1&t=1009976
I actually planned to ask you about it.
2011/3/11 Emmanuel Bernard :
> Interesting,
> Nicolas is experiencing an exception on 7 SP1 64 bits
>
> java.io.FileNotFoun
Interesting,
Nicolas is experiencing an exception on 7 SP1 64 bits
java.io.FileNotFoundException:
C\:\Dev\hibernate-core-ogm\entitymanager\target\packages\externaljar.jar (La
syntaxe du nom de fichier, de répertoire ou de volume est incorrecte)
at java.util.zip.ZipFile.open(Native Method)
Hi,
I'm building your latest OGM branch version just fine on Windows Vista
64bit, using Oracle JDK 1.6.0_23 64bit, Maven 3.0.3 from whatever
people dare to call "the command line".
The full package build fails in the end while building documentation
and assembly as I didn't setup po2xml, but that
12 matches
Mail list logo
