+1 For doing the Final next week or maybe the one after. We could focus for
one day or two to address the remaining (doc) issues.
One further thing missing would be the slot rename you recently suggested.
Note that the 4.2 core module would be added implicitly if the 4.2 module
sets (using slot "main") and 5.0 module sets both are around. So the doc
should say how to disable the implicitly added 4.2 in such case, if needed.
Thinking about it, would it actually work with only the "5.0" slot is
present? Not that the code adding the implicit dependency stumbles upon
this...
OGM-817 Adapt to changes around auto-quoting
That'd be needing a bit more thoughts/time though.
I think we could do that in a subsequent release, too. Normally, ORM will
quote specific table names (e.g. "Module") but the OGM integration disables
that by default. In a subsequent release we'd have to drive it ideally
based on actually reserved keywords for specific stores.
2016-04-06 12:43 GMT+02:00 Sanne Grinovero <sanne(a)hibernate.org>:
Hi,
I was hoping that even w/o a specific OGM sprint we would soon (next
week?) be able to re-spin the CR1 with minor effort as the
5.0.0.Final.
Among tasks scheduled for 5.0.0.Final:
-
https://hibernate.atlassian.net/issues/?jql=project%20%3D%20OGM%20AND%20f...
I'm assigned two documentation related issues; these seem important
enough to stay flagged for 5.0.0.Final and should be doable. OGM-888
also relates documentation and should be doable.
Could we agree on moving out the other open issues?
Personally I think the only one needing some attention still is:
- OGM-817 Adapt to changes around auto-quoting
Thanks,
Sanne
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev